I have tried multiple things, but I'm still stuck at the boot loading screen with the X.
I had cyan 5.0.4. - I wiped and flashed to 5.0.5 and now i cannot get past the boot.
I've tried booting back into recovery and wiping and doing a nandroid recovery to 'amon's recovery 1.7.0' but to no avail.
View 12 Replies
My phone is stuck in boot-loader screen and not even showing me Google logo on selecting Start from boot-loader screen, when connect charger then also it shows me boot-loader screen
Steps which i followed to install 4.3 manually is:
1. fastboot erase boot
2. fastboot erase cache
3. fastboot erase recovery
4. fastboot erase system
5. fastboot erase userdata
6. fastboot flash bootloader <bootloader_filename_.img>
7. fastboot reboot bootloader
8. fastboot flash radio <radio_filename_.img>
9. fastboot reboot bootloader
10. fastboot -w update <Rom_filename_.img>
Step 1-9 executed successfully but at step 10 while writing system.img installation got stuck and i waited for 40 mins but nothing happened
Repeated above step 3 times. Need to recovery my nexus 4 to its normal state
I recently used chainfire3d so you know i thought it would work so i tried it out and it said it would reboot the device, then it was going to reboot but it just stayed there nothing else happened. Did i break my phone because i already tried MythTeams stock frimware recovery and it still stuck. Also I am trying to use RSD to fix it but im having no luck so far
View 1 Replies View RelatedI was on 4.2.1 rooted, I found on the notification center that 4.3 is downloaded and ready to install.
after clicking it, I got an error and it restarted and never passed the x screen.I tried hard reset wipe all data. no luck.
I tried N-Cry, nexus 7 toolkit.but nothing worked for me.
I have a nexus 4. Recently tried to root it and install a rom. Guess I did something horribly wrong. Phone is now stuck on the google screen. Ive used the nexus root toolkit to try and restore it to factory settings and tried do a factory resest from the repair tool. Flashed the factory image from the tool kit also. none of this seems to work.
View 1 Replies View RelatedSo I have a GSM Galaxy Nexus that was running stock 4.3 (maguro)
Having been really frustrated with the low volume on the device, I decided to try the method mentioned on this link - Download Fix for Google Galaxy Nexus I9250 Volume Issue - Android Advices (VolumeFix by MoDaCo)
After I applied the fix and rebooted, my phone got stuck at the Google screen. My phone was unlocked prior to applying this fix so I went ahead and installed the CWM recovery - despite that, I cannot go past the Google screen, I haven't been able to install the CWM-SuperSU on my phone yet because I cannot transfer it to my phone without having it connected as a USB storage device. I tried adb push CWM-SuperSU-v0.87.zip /sdcard/ but it says "device not found"
I have even downloaded the stock 4.2.1 ROM to flash my phone with it, but at this stage I cannot do anything. I have logged into recovery and have wiped cache/ partitions/ dalvik etc but still it doesn't work.
Today I tried to restore my phone back to stock ROM and as I was trying to get into recovery mode and complete a nand restore but it wouldn't let me get in. It would just reboot me back into bootloader. I tried updating my superboot and recovery image to 1.7 and it's just stuck at the loading screen now. Is there anyway to restore it?
View 1 Replies View RelatedI just replaced my LCD and digitizer on my Nexus 4 after i dropped it and the screen cracked. It was still in working condition after the damage, but the touch screen was unresponsive. The installation went pretty smoothly but when I went to boot it up after it gets stuck at the bootup screen with the 4 bubbles. I tried some of the solutions people found for a similar problem a few months back when Google released Kit Kat 4.4 for the Nexus 4 but none of them have worked for me. There doesn't seem to be any hardware functionality issues, just some software glitch that I can't figure out.
View 4 Replies View RelatedI tried the 2.2 root process. short and sweet is downgrade 2.2 to 2.1. Bunch of command line stuff. Install usb drivers, open program to flash and it reboots the phone, then more command line stuff, then installs custom 2.2 and you are now rooted. I got to where I install the custom usb drivers and open the reflash program. All it does is go to the bootloader and sit there. I said screw it and was going to just reinstall 2.2 and be done with the attempt of rooting until a 1 click type came out. Problems is, now I cant even install 2.2. Sits at the bootloader screen. Called Sprint and they tried to help me do a factory reset by going to the phone app and typing ##87# or something.
When I hit reset it was supposed to show a screen thats wiping and reinstalling or something. Nothing happen. Stuck at that bootloader screen again. So here is what I think happened and I need help fixing it. I installed a newer bootloader or older one or something and the new 2.2 is having a hard time getting past it or I just completely screwed it all up. I am currently on 2.1 and all is working fine but I cant upgrade or anything. What are my options and how do I get this back to 2.2? Would love to try and root it and be done. Or just plug it into the PC and reinstall everything back to factory but I am coming from the iPhone where that is possible and I guess you cant on HTC.
I have flashed with rsd 2 tiwce without error message but the phone is stuck in bootloader. I have pulled battery after the flask but the phone wont boot into anything...please help.
View 6 Replies View Related[SOLVED] Relocking your Bootloader - xda-developers
View 8 Replies View Related(I'm mainly posting this here for people who don't regularly use XDA-Forums and might not have seen this).
View 9 Replies View RelatedI have LK bootloader source code which I need to build and flash to a Nexus 5 device.
* I got the source code from the Code Aurora website
* I made a guess which branch is the stable branch I need, because I found no mention of it anywhere (I took "kk_2.7-stable", where kk means kitkat)
* On a Debian 7 stable machine, I installed a GCC cross compiler from Deb packages built using Emdebian tools
* I made a guess which target to compile, because the exact chip name didn't have its own: I use msm8960
* I created some symlinks to the cross-building tools because the makefile and the debian cross-building tool names are different
* I ran 'make msm8960' and the build was successful (I also tried earlier with NDK prebuilt GCC but it failed)
* I got a bunch of files with no idea what to do with them
* I attached the device to the computer and re-flashed the stock bootloader to make sure it works
* I checked the fastboot screen: Bootloader unlocked, secure boot is on
* I tried flashing the 'lk' binary file I got from the build process, but fastboot says:
sending 'bootloader' (1702 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
The size of the file is much smaller than the size of the stock bootloader, but I don't know if it matters or what exactly I need to flash. I did a lot of web search, including here on XDA, but found no evidence of struggling with flashing the bootloader.
How do I flash the bootloader after I build it?
[How-To] ROOT Your Nexus One without Unlocking the Bootloader. ALL ROM'S! - Google Nexus One Owners | Google Groups. Ok, I posted this on my Google Groups page where I was able to Tidy it up and update it easier. Sources credited and applied. I did this on 2 N1's. No wiping, no data loss, both T-Mobile with FRF91. No data loss, no wipes, no nothing. The only reason you will have to wipe or anything is if you want to put a custom recovery on it and a custom ROM.
View 14 Replies View RelatedJust ordered an ATT nexus one (getting rid of the pos Samsung Captivate), and I would love to root it and put on a different rom. I have no problem following the guide that is stickied, but I was wondering if z4root (z4root - Android app on AppBrain) works on the n1? I see some appbrain comments saying that it DOES work. Are there different versions of the bootloader and such that it will or will not work on? Also, which modem and kernel do you guys suggest me using (battery life is most important)?
View 9 Replies View RelatedYesterday I got a sort-of-refurbished Nexus S (I9023) which was apparently not in such a good shape...Had problems flashing the system and userdata partitions (kept saying they were flashed fine but after reboot went back to their previous state).
I followed some tip without actually reading up on it and ended up formatting my bootloader partition.
Now, what I get is just a black screen no response or anything but using a tool called UnBrickable Mod I can get it back to fastboot mode and then boot into a recovery image and have adb access.
All in all, I am currently stuck cuz I want to flash a new bootloader image but what i get when i do that is:
Code:
~ # nandwrite /dev/mtd/mtd0 /bootloader.img
Skipping bad block at 0x00000000
Skipping bad block at 0x00040000
Skipping bad block at 0x00080000
Skipping bad block at 0x000c0000
Writing at 0x00100000
Writing at 0x00140000
Writing at 0x00180000
Writing at 0x001c0000
nandwrite: not enough space in MTD device
I have read that NAND blocks tend to go bad when continuously being flashed, but 50% bad blocks on the bootloader partition? Seems pretty unlucky... Is it possible to resize the partitions without any JTAGing or writing custom bootloaders?
Lost root since updating to 2.2.1? Here's a new one click solution!
[APP]SuperOneClick v1.4 (Root, Enable Non-Market App, Get UNLOCK code) - xda -developers
So, my issue is that I simply cannot unlock the bootloader of my Nexus S (i9020T). The phone's connecting to my computer via Samsung Android ADB Interface as seen under the Device Manager. I see the proper device ID when I type "fastboot devices" into the adb command prompt. Then, when I type "fastboot oem unlock" the phone starts the unlock verification process -- I select yes, the phone restarts, but it goes back to the stuck Google screen. Then, if I pull the battery and go into fastboot mode directly, bootloader's still locked. I've tried this quite a few times and same result -- same result trying to unlock w/ toolkits like WugFresh's NRT.
I've also tried to solve it w/ all versions of Odin. None of them detect my phone even after installing Kies w/ drivers. I think I have the required drivers though since I can command the phone fine through adb. And Odin should need bootloader unlocked to work anyway so it won't work if bootloader cannot unlock.... I've even tried a few other things like pushing recovery and bootloader images onto the phone via adb, but these also failed due to the locked bootloader. All options seem to require an unlocked bootloader.
I also cannot enable USB debugging under phone settings either b/c I now can't get past the Google logo/fastboot mode menu. I don't think this is required to unlock bootloader through adb though.
Background: Phone had the latest auto updated version of Android when the phone all of a sudden turned off in the middle of the night recently. Weird b/c the battery was basically full. It now always gets stuck on the Google logo upon normal restart. It goes into fastboot mode OK if I remove the battery and press power/vol. buttons -- I then first tried the restore and recovery functions there, etc, but no effect.
To add, one of the first things I tried was to do a manual factory data reset in the recovery menu (selecting 'yes' to erase all data).
And I tried adb sideload of the OTA .zip file. But installation was aborted. The following appeared immediately under the regular adb sideload instruction in the system recovery menu (under "Now send the package you want to apply to the device..."):
Finding update package...
Opening update package...
Verifying update package...
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
Installation aborted.
I originally rooted my phone with Unrevoked before Froyo came out(can't recall the version). Once froyo came out, I backed up the phone with clockwork, then flashed over Netarchy's stock rooted froyo(backed up afterwards too). Today I went to the link on the unrevoked twitter page and flashed 3.29 to my phone. I flashed it using the update from SD card option in clockwork. Here's the issue. Afterward my phone rebooted and will not go past the bootloader screen. I'm thinking no biggie, I'll just go back into recovery and load a backup or an older working rom. Well there is no recovery. All I get is the phone with a red triangle. So I'm freaked out and thought, well lets just go back to the stock RUU. Well thats getting an bootloader version error. WHere can I go from here? is there a way for me to get those backups I made loaded from the bootloader screen?
View 30 Replies View Relatedwith sprecovery on my phone. I'm trying to force 2.2 but cannot do it through sprecovery for some reason. RSDlite instructions say I must get to a bootloader screen. I cannot because when I hold power and x it goes into the sprecovery/nandroid back up with the Android guy with a ! on him.
View 2 Replies View RelatedI picked up my phone and it had a weird screen on it that looked like some that I saw when people have rooted their phones (from posts). It had options like "bootloader" and "power down" on it so I used the rocker bar to scroll and get out of it by powering down. My question is this: Someone I know was talking about spyware that can be put on laptops and computers and now this happened when they were around. Is this just a glitch or could it be indicative of spyware having been put on my phone?
View 4 Replies View RelatedSo I made the mistake of attempting to root my new HTC one V without knowing what I was doing. I currently can't get past the bootloader screen. I've attempted installing the RUU for my phone with no success. I've resorted to extracting the rom.zip from the RUU, renaming it PK76IMG.zip (required for hboot to recognize it) and putting it on my sd card. Everything works fine up until the end when it says "hboot version is older! Update failed"
View 2 Replies View RelatedTried doing a search for a topic with people having the 3g/2g issue and couldn't find out except for the one people discussing the baseband. For those of you with this problem, what are you experiencing? I just got the nexus activated and it stayed on 3g for about 30 mints before switching to 2g with me sitting in the same spot. then after 30 mints went back to 2g and now its just stuck there. I've checked the map and I should have excellent signal. Is there anything at all I can do? Will rooting and adding custom Rom help?
View 3 Replies View RelatedI turned off my N1 and when I turned it back on it never progressed passed the the N1 boot-up animation. I've taken the battery out multiple times, but it does the same thing. The animation starts up then freezes after ~3 seconds, then the animation starts again and it just repeats. Can anyone help me fix this?
View 10 Replies View RelatedOn my nexus 4 I was trying to download the 4.4 kitkat, but i messed up and deleted something i think.So now i'm just stuck on the Google logo,
View 14 Replies View RelatedWhen I try to start the device normally it gets stuck on the loading screen with the animation.
I go into that bootloader mode and try to restore it to wipe/restore it to factory settings but I get this: [URL] .....
I must have done something wrong when trying to root the phone...what I've done and why wiping the data isn't working.
I thought i broke my phone but it just turned on and I have a screen that says the following Battery OK, OK to Program, Transfer Mode: USB
View 16 Replies View RelatedI have a Samsung Galaxy Nexus 4G on Verizon, and I just unlocked the bootloader, then I tried to gain root access through this guide, started at the "ClockworkMod Method": [HOW TO] Root the GSM/HSPA+ Samsung Galaxy Nexus - Android Forums now when I flash the su.zip and try to reboot, the phone is stuck in the Google reboot screen.
View 3 Replies View RelatedI have been trying to follow the tutorial to take my Nexus 7 (2013) from it's just unboxed state to dual booting Android and Ubuntu Touch. I succeeded in unlocking the tablet. I am using Ubuntu 13.10 on my laptop and installed the whole Android SDK and everything (even though I already had Eclipse installed for learning Java). I've reached two sticking points.
First, the part where I'm told to copy the three files (the MultiROM zip, the kernel zip, and recovery image) to the root directory of the tablet: it's not clear how to do that. The files wouldn't copy except to the internal storage folder. Or is that the root directory?
Second, I am unable to boot to recovery.
Code:
adb reboot recovery
command only brings up the android on his back with the red triangle containing an exclamation mark. That screen lasts a minute or so and then the device reboots normally on its own. I have tried several power and volume button combinations to get a different result at this point, but to no avail.
I try to install the kitkat 4.4 on my nexus 4 and now i stuck on recovery mode.
i see this:
fastboot mode
product_name - mako
variant - mako 16gb
hw version - rev_11
bootloader version - makoz20i
signing - production
secure boot - enabled
lock state - unlocked
what can i do ? can i fix it ?