Hello recently my phone battery went dead than after I charged it I got "optimizing apps" and it just couldn't finish. So then I did "flash stock and unroot" and now I'm stuck with bootloop. Wiping data with stock recovery didn't work, I've tried it many times.
Did you try using fastboot commands to erase userdata, flash userdata.img, and factory wipe before first booting the phone?
I think not, please tell me how to do that :$
Extract the userdata.img file from the stock Google ROM you are flashing.
Boot the phone into fastboot mode, connect the phone to the computer, type "fastboot erase userdata" and press enter. Then type "fastboot flash userdata userdata.img" and press enter. The userdata.img file should be in the same directory where you execute fastboot commands. When the flash has completed, use the volume and power button to go into recovery, wipe data, and reboot.
My PC doesn't even want to recognize my phone...
http://i.imgur.com/E7MYAKX.png
Is the phone in fastboot before it is connected to the computer?
Yeah, it is. Edit: I think I made a mistake because i wrote "adb devices" instead of "fastboot devices". Edit 2: Still stuck in bootloop. Somehow I managed to instal CM 12 but now I have infinite "starting apps".
It could be stuck because you need to flash the userdata.img file.
I have a similar issue here, Wiped, formatted, resized, reflashed bootloader, radio, recovery, system, userdata, cache. Tried stock lollipop, cm12, cm13, everytime each rom flashes successfully. However, upon loading the custom bootloader animation, it stucks there forever. This happens matters not that flash each partition individually, install the zip via TWRP, or ADB sideload. Is there a live boot/verbose option so I can see where it is hanging? I tried so many times it almost feel like it is a hardware issue.
After flashing each stock partition, including userdata.img, are you booting into stock recovery to perform a factory wipe before the first boot of the newly-flashed stock ROM?
audit13 said:
After flashing each stock partition, including userdata.img, are you booting into stock recovery to perform a factory wipe before the first boot of the newly-flashed stock ROM?
Click to expand...
Click to collapse
so I tried to enter recovery with stock 5.1, android with red ! pops up, but no "no command" line. I can't press volume up/power to enter recovery.. thought it is a fluke, I reflashed everything with 4.4.4 stock, same problem, cannot enter stock recovery. what am I missing here?
edit: dumb question, I held the button in wrong sequence, yes I factory wiped and still hangs on boot image
When you went into recovery, did you see an error line at the bottom that said something like invalid format or invalid argument? In recovery, did screen at the bottom say that the cache and data were formatted?
audit13 said:
When you went into recovery, did you see an error line at the bottom that said something like invalid format or invalid argument? In recovery, did screen at the bottom say that the cache and data were formatted?
Click to expand...
Click to collapse
enter recovery "fail to mount cache"
factory reset
"format system"
"format cache"
done
reboot----> hangs
That is what I was hoping to see but it's strange that the phone still hangs.
Maybe boot back into ft aboot be run the commands "fastboot erase cache", "fastboot erase userdata" and reboot.
audit13 said:
That is what I was hoping to see but it's strange that the phone still hangs.
Maybe boot back into ft aboot be run the commands "fastboot erase cache", "fastboot erase userdata" and reboot.
Click to expand...
Click to collapse
done, phone still hangs, do I just need go get another motherboard?
I'm out of ideas and another motherboard may be the only solution. You've done everything I would have done.
ddvche said:
done, phone still hangs, do I just need go get another motherboard?
Click to expand...
Click to collapse
FYI I took the unbootable motherboard out, swap it into a nexus with broken digitizer. Turned it on, and it booted.... so the fix wasn't replacing the motherboard... it was replacing everything else...... probably was a connection issue yes?
In post number 13, you formatted the system?
audit13 said:
In post number 13, you formatted the system?
Click to expand...
Click to collapse
Heh, I think I meant "internal storage"/"data" partition. If no OS it wouldn't hang, just reboot to recovery if I remember correctly.
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Related
hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything
Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going
ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks
Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom
I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.
xda6969 said:
I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.
Click to expand...
Click to collapse
Go here and download the factory firmware for the Nexus 10:
https://developers.google.com/android/nexus/images
Then follow these steps:
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Its for a Nexus 7 but they helped me fix my Nexus 10 too after I got stuck in the bootloop. Just use the different file names for the Nexus 10. You will need something to extract a tgz and a tar file for this process. You will also have to manually boot into the bootloader by powering the 10 off, then hold down volume up + volume down + power until you get the bootloader screen. Then follow those steps. It took me a few tries to get into the bootloader, not sure what that was about.
Initially, flashing a bad recovery got mine stuck, so make sure you grab a confirmed working recovery before you flash it. You will just have to start over, with the exception of unlocking as that would be sticky through this process.
Good luck!
When I flashed the image as in step 8, it said archive does not contain boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!
xda6969 said:
When I flashed the image as in step 8, it said archive does not conatin boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!
Click to expand...
Click to collapse
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
bigdwg71, thanks a million! :good:
beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
I also had to flash system.img manually as well...
beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Those images act like a wipe for the /data & /cache partitions... similar to using fastboot -w
Also, this thread does not belong in the Development forum... Mods, please move this!!
xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.
xda6969 said:
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.
Click to expand...
Click to collapse
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"
espionage724 said:
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"
Click to expand...
Click to collapse
I've used fastboot flash RECOVERY.img on my Galaxy Nexus many times and it was always temporary.
You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app
bigdwg71 said:
You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the clarification.
Hi guys,
I'm experiencing a very big problem with a friend of mine's nexus 4. I've done the same thing in the same order with my phone (nexus 4 too) five minutes before and it worked.
We installed 4.4 stock rom downloaded from official google website via fastboot and all went well on my device. The problem was that we repeated the same identical procedure on my friend's nexus 4 and it went well except for the fact that the phone only had 5gbs available after the flash, so we red on the internet that we had to repeat the procedure using "fastboot -w update" instead of flashing every single file contained in the zip folder.
So it's now that borns the real problem. We've erased all partitions (fastboot erase cache, userdata, system, bla bla) and reflashed all. But from this point it stucks on android 4.4 loading logo.
We've tryied to repeat the operation and we've noticed that "fastboot erase bootloader" command answers with "Failed (remote: bootloader partition does not exist)". So we tryied to install cwm recovery and flash from sideload, it works and loads cyanogenmod logo but stucks on it again, tryied to flash everything possible and it works but after don't start.
The strange thing is that the bootloader appears to not exist but if i do the command: fastboot flash bootloader C:\...\bootloader.img it works and says "writing... OK" so i really don't know what could be the problem.
Please guys help us, my friend is on the point to sell his phone but we both are SURE that if it still can enter on recovery and on bootloader it could be restored!!! But we don't know why! Tryied every possible solution on the web, and nothing worked for now...
Thanks to all in advance!
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
meangreenie said:
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
Click to expand...
Click to collapse
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
fdm91xda said:
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
Click to expand...
Click to collapse
For future references. Most likely the reason why your phone didn't boot up is because you 'erase' a partition and left it unformatted. The 'erase' command wipe out the partition so no data is there and it can't access it. If you erase userdata, then there would be no accessible internal storage and the phone cannot boot.
Which is why after you erase it, you need to either flash something over it or format the partition to make it blank: fastboot format userdata (this is what Format DATA option in TWRP is).
Tired, Frustrated and Helpless I am at the moment.
My A500 was running OK with a Jelly Bean Rom( I forgot which one) with Skrilax_CZ's bootloader V8 and CWM v5.5.0.4.
I decided to try a different Jelly Bean Rom. Forgot to keep a CWM backup and my misery started.
Any rom and gaps will install fine. But after reboot it will be stuck on Cyogenmod or Android LOGO. I have tried several ROM. Exact same result.
This happened a few months back and after trying numerous times I gave up for that time.
But I need to get the tablet back to working.
So, since yesterday I have been trying my best to get this one to work.
Started with "[A500 & A501] Android 4.4.4 (OmniROM unofficial)".
According the installation note for that rom, I installed CWM 6.0.4.5 on secboot following the "[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]" process.
Same exact situation. ROM will install then after reboot it will be stuck on OS load.
Tried with a few other older rom such as CM10-FLEX_V6Supercharged_Rev3.4. Same issue.
I even, Installed TWRP recovery openrecovery-twrp-2.6.3.0-a500 on secboot. Same Issue.
Then, Updated Skrilax_CZ's bootloader V8 to Skrilax_CZ's bootloader V9. Same Issue.
Weird thing is now when I go to "CWM 6.0.4.5" from "Skrilax_CZ's bootloader V9", CWM doesn't really let me do any task. Any menu I enter on CWM 6.0.4.5 it freezes and then reboots the tablet. But initially when I first installed CWM 6.0.4.5 on secboot it worked for the first few times.
I am a noob in this. I do not want to try anything else myself as I think I will eventually brick the device and there will be no coming back.
I have searched on XDA for this issue. Many other people have similar issue with a500 but I couldn't find any situation same as mine.
Need help from you awesome people.
I do not want to give up on this tablet. But without your HELP I am lost.
Please HELP.
Need help on this please.
iamtapu said:
Need help on this please.
Click to expand...
Click to collapse
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
HenrikE said:
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
Click to expand...
Click to collapse
tried that. same issue.
it keeps circling on cyanogenMOD logo.
Apologies for reply late. I was not well and could not attend to you reply.
anything else i can try?
Please help.
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Same here
I have had exactly the same issue and haven't yet found a decent solution.
Mine was stuck on the Acer logo with the stock ICS ROM.
I found my CPUID and SBK, the linux way.
I tried everything you tried, managed to have bootloader V9 installed, TWRP as a recovery (Thor's version), CWM as secboot.
I was able to wipe and flash with no errors, but it would always stuck on the Acer logo. No custom ROM would ever boot.
I will definitely try Unimatrix-zero's solution and tell you guys if it worked for me.
So far, the only thing that worked for me was to use an EUUs package (GEN1) to get back to stock HC 3.01.
As you may guess, there are no more OTA updates via wifi in 2014.
So I downloaded several update packages and so far I only managed to update to HC 3.2. I haven't yet found a working package for stock ICS.
Anyway, if Unimatrix-zero's workaround actually works, a custom ICS ROM will do the trick for me.
Unimatrix-zero said:
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Click to expand...
Click to collapse
Significant result but did not resolve the issue.
As you have mentioned, I have wiped off everything that i can find in the recovery menu.
rebooted after that to recovery and for the first time I could go to TWRP 2.7.
tried to install a custom rom. but same issue. Either it reboots when I tried omni rom 4.4.4 on the "booting from primary" menu or the CM blue circle going on forever, when I tried with a CM 10.1 rom.
and just now after trying the cm 10.1 rom it went back to the way it was before. now the TWRP 2.7 will just keep on blinking on the screen .
Help bro...help....
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Unimatrix-zero said:
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Click to expand...
Click to collapse
you are a GOD SEND for me.:highfive::highfive::highfive::victory::victory::victory::victory::victory:
Did the following as you mentioned.
Code:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
boot recovery TWRP 2.7.
Installed OMNI 4.4 rom.
Installed GAPS.
NOW its booting to OMNI rom...
awesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
OK, 3 days ago I rebooted my ZE551KL and it went into a bootloop. I was completely 100% stock. No root. Locked bootloader. Spent the better part of the weekend trying to troubleshoot it, and I have made almost zero progress.
I've tried a bunch of things, but here is my current status.
Can get into fastboot mode no problem.
POWER + DOWN VOL gets me into stock recovery, but at some point I flashed an older version. I tried flashing TWRP, but after install could never seem to get into it (is that because I'm unrooted and locked?)
Current recovery version: Android system recovery <3e> LRX22G.WW_user_1.16.40.763_20151201
I've tried flashing to a couple different firmware versions from the ASUS website both via ADB and via the SD Card.
Current firmware: UL-z00T-WW-1.17.40.1531-user.zip
Still in bootloop.
Any advice on rebuilding this thing from scratch? I dont care whether I just get stock back, or if I need to root/unlock, install TWRP and a custom ROM. Dont care, just want a functioing phone!
Thanks in advance.
ACFH said:
I dont get it. Did you factory reset your phone? With stock rom, factory work most of the time.
You said that you tried flashing TWRP. If you see successfull message after flash, type "fastboot reboot" and hold volume down button right after hit Enter. If you did right, you can get into twrp, then choses Wipe > format, it more powerfull than factory reset.
Click to expand...
Click to collapse
1. Factory reset from within the phone's OS? No, I cant get that far. Just constant bootloop on ASUS logo.
2. I've used the fastboot erase command to wipe everything, and used the wipe data/factory reset option in the stock recovery. Still bootloop.
3. I've tried flashing TWRP 3.0.0.0 and the newest version of TWRP. I hold down the VOL DOWN key before hitting enter on "fastboot reboot"; it just goes into a faster bootloop, like every half-second. When I release the VOL DOWN key, it goes into the same, slower original bootloop.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Awesome. I'll give that a try and report the results.
I just downloaded the .img with the same date as my recovery version from here. https://asus.kremowka.xyz/categories/show/2
Its been hung at "Verifying update package...." for about 10 mins now. Once this is finished (and probably fails ); I'll give your format commands a try.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Ugh. Didn't work. Here is what I did:
fastboot format userdata
fastboot format cache
fastboot erase system
fastboot format system
Reboot to recovery
install UL-z00T-WW-1.17.40.1531-user.zip from SD card.''
Installation successful.
Reboot.
In a bootloop that shows ASUS logo for 10-15 seconds, flashes a blue screen really quick, then reboots.
What can I try next?