I have tried root my nextus 4 for install blinkfeed (http://forum.xda-developers.com/showthread.php?t=2696399)
enter into Fastboot mode.
and unlock the bootloader:
fastboot oem unlock
Then, without rebooting the phone, I installed ClockworkMod
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-mako.img
So I went to turn on the phone and I found it with the surprise that no turn on
the phone not pass the splash screen, with the drawing of circles moving.
But the phone enters fastboot mode if I press volume down and Power buttons.
appreciate any help.
excuse my English.
UPDATE
I have tried:
wipe data/factory reset
wipe cache partition
wipe dalvik-cache.
from fastboot, adb devices does not list anything. But "fastboot oem unlock" and fastboot "flash recovery recovery-clockwork-6.0.4.3-touch-mako.img" work.
really appreciate any help
Flash the factory image, then re-flash install cwm. Not rebooting after unlocking the bootloader is what is causing your problem
Sent from my Nexus 5
these
jd1639 said:
Flash the factory image, then re-flash install cwm. Not rebooting after unlocking the bootloader is what is causing your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
excuse my ignorance.
I downloaded the factory image from developers.google.com/android/nexus/images
It contains a .bat called flash-all.bat.
Do I run the. bat? Or just need only re-flash the bootloader?
rockdrigo16 said:
excuse my ignorance.
I downloaded the factory image from developers.google.com/android/nexus/images
It contains a .bat called flash-all.bat.
Do I run the. bat? Or just need only re-flash the bootloader?
Click to expand...
Click to collapse
I'd use the flash-all.bat. you'll have to put the custom recovery back on and root
Sent from my Nexus 5
jd1639 said:
I'd use the flash-all.bat. you'll have to put the custom recovery back on and root
Sent from my Nexus 5
Click to expand...
Click to collapse
it worked! I love you.
Thank you very much.
Related
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.
Made a silly mistake. I was going to flash M-kernel to my device after updating to 4.2.2 and while I was in Team Win recovery I chose to wipe cache and system. I flashed the kernel and now when I select to reboot it says "No OS installed! Are you sure you wish to reboot?" I still have the file to flash 4.2.2 but don't know how I can get it on the device in it's current state. Any help would be greatly appreciated.
I tried this method here: http://forum.xda-developers.com/showthread.php?t=1667929 however I can't get Unmount/sdcard to work in the recovery menu and therefore can't push the OS file using the cmd prompt.
You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.
hlxanthus said:
You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.
Click to expand...
Click to collapse
I use Root Tool Kit to root and unlock. I have android sdk installed on the PC but not sure what fasboot is. Can you explain how to "fasboot the system.img and boot.img into place"?
If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Will doing this cause me to lose everything I have on the Nexus already?
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!
Status: Stuck on boot image
Solutions tried:
1. Factory reset + custom rom
2. Factory reset + stock rom
3. Full wipe with stock image from google dev.
4. WugFresh Root tool kit - Soft bricked + stuck in bootloop option.
I think that covers most of the solutions out there that I could find. It is always stuck on the boot screen. Left it for hours but it was basically stuck. I've seen other people's issues resolved by doing at least one of the above.
IS there something I'm missing? Any solutions?
Update: Ended up getting a replacement (was under warranty). I tried all possible solutions. The factory setup for 4.2.2 was the only one that would boot. But I did not have IMEI and Baseband. Nothing seemed to work. Not sure what would cause that.
Quest_in said:
Status: Stuck on boot image
Solutions tried:
1. Factory reset + custom rom
2. Factory reset + stock rom
3. Full wipe with stock image from google dev.
4. WugFresh Root tool kit - Soft bricked + stuck in bootloop option.
I think that covers most of the solutions out there that I could find. It is always stuck on the boot screen. Left it for hours but it was basically stuck. I've seen other people's issues resolved by doing at least one of the above.
IS there something I'm missing? Any solutions?
Click to expand...
Click to collapse
Did you try this guide here
mrhiab said:
Did you try this guide here
Click to expand...
Click to collapse
Thanks. Yes I tried that right after the recoveries failed to do anything. Its really weird because once the system is stuck at the boot image, the computer after a while tries to communicate over USB but fails. As if the boot animation is just a front and Android is trying to do something to load for the first time. I'm not sure what got corrupted. All this started randomly 4 days after I had flashed a nightly update on Omni.
Update: So i tried to flashing a custom ROM (oh WTH moment) and see if that makes any difference. (CM 11 Nightly from JAN 26). The system actually booted up to the android is upgrading screen this time. Now it is stuck on "Starting Apps" screen. Progress? i'm not sure if the stock was already NOT doing this behind the scene. Is there a reason for it to be stuck here? Is this some sort of indicator?
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab the latest twrp.img
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
Go to advanced
Choose adb sideload
adb sideload nameofrom.zip
adb sideload gapps.zip
Reboot
Profit
Sent from my Nexus 4 using XDA Premium 4 mobile app
Factory reset + Factory image + Bootloader relock + bootloader unlock + install twrp + factory reset
demkantor said:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab the latest twrp.img
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
Go to advanced
Choose adb sideload
adb sideload nameofrom.zip
adb sideload gapps.zip
Reboot
Profit
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
blttalas said:
Factory reset + Factory image + Bootloader relock + bootloader unlock + install twrp + factory reset
Click to expand...
Click to collapse
Hello I'm experiencing the exact same problem, tried both these solutions to no avail. Stock 4.2.2 image the the only one that boots, but with no IMEI or network connection whatsoever. Is there anything else I can try to fix this? Thanks.
I have the US version of the ZTE Axon 7 running the B29 build.
I recently unlocked the bootloader successfully, When I flashed the TWRP recovery via fastboot soon after, it worked perfectly. Phone booted properly and worked normally. When I tried to install the TWRP app in the OS, I was told to download the latest TWRP version from the website and flash it (even though I had the latest version already flashed from fastboot). I did that. Now I have no recovery menu at all. I have access to the bootloader menu, and I can boot into the phone. When I try to boot into recovery, all I get is a black screen. I tried to reflash the TWRP recovery img from fastboot like I did originally with no success this time. Fastboot recognizes the phone when I type devices, but when I type the fastboot command to flash recovery twrp.img, it says it can't load the file. I then downloaded the ZTE stock recovery img and tried to flash that with the same result. I assume the recovery partition is locked somehow now? What can I do to recover the recovery? Am I stupidly forgetting something trivial.
hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck
I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.
lafester said:
I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.
Click to expand...
Click to collapse
yeah. live and learn. too late to help at this point. I'll try the tool you suggested
Bucci83 said:
hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck
Click to expand...
Click to collapse
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.
[email protected] said:
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.
Click to expand...
Click to collapse
I think he means go to fadtboot and do fastboot clear cache or something like that, Google fastboot cache clear command