Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
Twenty seconds doesn't sound bad. I think it's the normal time for Nexus S to boot into recovery. Try checking some videos on YouTube of nexus a booting into bootloader. That should give you an idea.
Yea checked all that and asked other nexus s users. No one has this problem. going to try an older recovery.
Update on this:
Flashed back to an earlier recovery from fastboot. Its a 2.x version and reboot recovery is instant (or at least the speed it should be) When flashing the latest recovery from rom manager, the problem returns.
So I'm stuck. Obviously its an annoyance more than anything but the first time it happened I thought I bricked my $500 new toy
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
bringonblink said:
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
Click to expand...
Click to collapse
glad to know i'm not crazy. thanks
I been lurking on XDA for a long time just have made any posts, lots of great info has been found here and I usually find my answers without having to ask, that is till now. This might be a long post but I want to give the best information possible to get the best help. I recently updated my tf300t to jb4.2 and that's when the bottom fell out. First I thought I was bricked, flashed the update and it booted fine, flashed twrp and it booted fine, tried flashing Energy rom and that's when it started. Twrp would not mount cache, sd, nothing. Then after rebooting it would give the Asus screen with unlocked bootloader in the top then go straight to twrp, where I could not flash anything. I finally got it to reboot to fastboot where I can reboot to jb but if turned off it will still load straight to twrp and I have to adb fastboot reboot to the RCK android wipe screen and load jb from there using the android. I have tried wiping from that screen, wiping from twrp and even adb push the rom again to wipe with no success. When adb pushing any recovery or rom/software it seems to take but have to manually reboot with power button after to get it to reboot. I tried adb pushing different recoveries with no success along with Energy rom, no success. To me its like I have a dual partition on the storage. Is there any way to wipe everything completely clean and start fresh? Without using recovery since it is not working.
Sounds like you have bricked like a lot of other people. There is a guide in General. Which version of TWRP did you use on the latest bootloader. If it was not TEWRP 2.4.40 or the patched version then you have bricked unfortuntely.....
sbdags said:
Sounds like you have bricked like a lot of other people. There is a guide in General. Which version of TWRP did you use on the latest bootloader. If it was not TEWRP 2.4.40 or the patched version then you have bricked unfortuntely.....
Click to expand...
Click to collapse
I haven't bricked yet, it still works. I just have to adb reboot to bootloader if I power it down and restart it. I just cant wipe it and reinstall anything. I dont remember right off which version of TWRP I did use, but it wont mount anything to allow me to wipe or install from it though.
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
Hey guys. I'm a bit of a newbie at androids. I bought a Moto G, and I decided to root it.
I realized that the android was not unlocked, so I went through a small progress to try get it unlocked so I could install a custom recovery. I chose CWM.
I went through a tutorial on how to install CWM, and I installed it. I used the MotoTool to push Superuser to my android, and was able to install the zip.
It all went wrong when I tried to exit out of CWM.
I selected "Reboot" and it loaded the screen up to CWM again...a bit odd. So I'm trying to reboot so I can use my phone properly, and nothing is working.
What I've tried :
-----> Clearing dalvik cache and cache with CWM -
I tried this and it still didn't work.
-----> Loading into my AP Fastboot with CWM and trying to power off and on from there
Still didn't work and loaded into CWM.
----->Flashing my bootloader
Made it worse. I can't even power up my phone anymore.
In conclusion, my phone is hard-bricked, and I can't even power it up. If anyone has any solutions, it would be extremely helpful. Please feel free to comment or reply if you need more info about my device.
Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?
Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.