I did an update from 10b to 10d and tried booting into cwm recovery.
When the phone restarted, it just came up with a little animation (an android man in a box with loading bar) and my phone was reset to default.
How do I uninstall CWM and reinstall it? Am I right in thinking it's just a case of unrooting and re-rooting? Don't really want to do it and lose everything again.
download rom manager and go to the bottom tab on it and flash the 4.0.0.7 cwm and then go back to the top tab and reflash the 4.0.0.9 and then it should be all okay for you again take a matter of 2 mins if that
projectsome said:
I did an update from 10b to 10d and tried booting into cwm recovery.
When the phone restarted, it just came up with a little animation (an android man in a box with loading bar) and my phone was reset to default.
How do I uninstall CWM and reinstall it? Am I right in thinking it's just a case of unrooting and re-rooting? Don't really want to do it and lose everything again.
Click to expand...
Click to collapse
Hi,
A little note while using cwm, I have difficulty too in booting in cwm so what I'm doing is I'm using the reboot to recovery feature of cwm 4.0.0.9, from there I never had problems again in booting to cwm.
Sent from my unbricked O3D.
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
XDvinSL said:
I was trying to install EagleBlood ROM to run Gingerbread on G2x, and followed all instuctions, installing ROM manager, using that to flash to their recovery, then deleting caches, then flashing the ROM. After a reboot, EagleBlood is stuck on a bootloop, displaying an image of and android surrounded by a sparkly blue circle. If I take out the battery and then try to boot into recovery, the recovery image is displayed for a while, but then resets and goes back to rebooting without opening recovery. I am very scared that I may have bricked my brand new phone and do not want to pay for a repair. Any help is very much appreciated.
Click to expand...
Click to collapse
I would suggest that you NVflash clockworkmod by reading the thread here. Once you do that, you can access your recovery via volume down and power. If you do not have CWM installed via NVflash, for now, you should be able to reset everything by pressing the volume down and power to restore your phone to a factory state.
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
XDvinSL said:
Thank you very much for that tool! Booted up the recovery and am currently recovering from earlier today on the stock ROM. If this is my last post, it was a success!
Click to expand...
Click to collapse
Now, when you install a rom through CWM, i would suggest wiping data (if you are switching between roms) and cache. This will prevent you from going into bootloops. I would also suggest after flashing a new rom, going into CWM > Advanced > Fix Permissions. You should now be golden.
Hey there guys.
I rooted my Blaze back in October, and loaded CWM 10. Things weren't working 100% right and I decided to unroot today to get the phone back to factory settings. Unfortunately, no matter how many times I follow the directions for unrooting the Blaze--using the .pit, and the updated firmware .tar--my phone still gets stuck in a reboot loop. It gets past the T-Mobile Blaze screen, but gets stuck on the SAMSUNG screen (it just has SAMSUNG flashing over and over, and then loops into the Android screen).
I've tried to flash the stock .tar about seven times now, and each time it's done the exact same thing. I haven't been able to find a thread to help me, despite searching enthusiastically, so I hope you guys can help me out. Basically, I've done everything the unrooting guides have told me to do, but my phone still appears to be soft-bricked. I can still get into download mode, Odin still recognizes the phone, and it always says that my process has succeeded, but then the phone still gets stuck in a reboot loop.
Any ideas?
Have you booted to the recovery and factory resetted and wiped cache?
Romman0 said:
Have you booted to the recovery and factory resetted and wiped cache?
Click to expand...
Click to collapse
I did before I tried to unroot it the first time, yes, with CWM. Now, the phone seems to think it's unrooted, so it won't let me go into recovery mode and factory reset.
Romman0 said:
Have you booted to the recovery and factory resetted and wiped cache?
Click to expand...
Click to collapse
Oops, sorry, I misinterpreted your question. Yes, when I boot into recovery mode I can factory reset, wipe cache, etc. I've done all those things before trying to flash the stock rom, and it hasn't helped.
jadeth said:
Hey there guys.
I rooted my Blaze back in October, and loaded CWM 10. Things weren't working 100% right and I decided to unroot today to get the phone back to factory settings. Unfortunately, no matter how many times I follow the directions for unrooting the Blaze--using the .pit, and the updated firmware .tar--my phone still gets stuck in a reboot loop. It gets past the T-Mobile Blaze screen, but gets stuck on the SAMSUNG screen (it just has SAMSUNG flashing over and over, and then loops into the Android screen).
I've tried to flash the stock .tar about seven times now, and each time it's done the exact same thing. I haven't been able to find a thread to help me, despite searching enthusiastically, so I hope you guys can help me out. Basically, I've done everything the unrooting guides have told me to do, but my phone still appears to be soft-bricked. I can still get into download mode, Odin still recognizes the phone, and it always says that my process has succeeded, but then the phone still gets stuck in a reboot loop.
Any ideas?
Click to expand...
Click to collapse
I
So first register at www.sammobile.com, then search SGH-T769 under firmware and download the August 2012 ICS or The Feb 2013 ICS Firmware, wait for the download to finish (took me 30 minutes) then extract which ever firmware zip you downloaded then using Odin click on PDA and select the .md5 file which is located in the extracted ICS Firmware Folder that you've downloaded from sammobile.com
Download the PIT file here
http://forum.xda-developers.com/showthread.php?t=1919228
Click on PIT in Odin and then select the one downloaded from the link above
then make sure re-partition isn't checked and start the flashing process after it is done flashing and reboots you'll have stock ics
*BOOT LOOP MIGHT OCCUR*
To fix boot looping after flashing stock ICS just boot into stock or custom recovery and wipe data and cache then reboot and you're good to go.
Sent from my SGH-T769 using xda app-developers app
Thank u i thought i was fully bricked
Thank u for the post my phone is alive again thank u alot i was trying to install twrp after i had cwm recovery and i wasnt able to install it so it soft bricked my phone but i used ur steps and it all worked out thanks :victory:
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)
I have here a brand new GT-I8262, JB 4.1.2
Here's what I did,
1. I rooted my phone using farmaroot, it was a success.
2. I wanted to install CWM recovery just to do a nandroid backup, I followed this tut http://forum.xda-developers.com/showthread.php?t=2517850 I used the 1st method and it was a success, ODIN software said It passed. Then I tried to boot into CWM recovery, but it keeps on booting into downloading mode.
3. So I downloaded ROM Manager to check the status of my phone if CWM is installed, but it says its not installed.
4. Then finally, I go to settings, do a "factory reset" and wipe all my data, now my phone suddenly reboots into CWM recovery mode, I'm in the main menu, but when I tried to " Reboot system now" it reboots the phone and back again to CWM. I can't get out of CWM...
Please Help me, IDK this, is this kinda soft or a hard brick?
Please help, I can't get this to samsung service because I have a Yellow Triangle and I've already reset once my binary count.
I still have warranty, I don't want it to be voided. :crying::crying::crying:
http://forum.xda-developers.com/showthread.php?t=2661201
Use this stock recovery.Flash it via CWM,reboot and you will see the recovery stock,then reboot again.
Or you should flash CWM again..
Thanks guys,
I fixed my phone by using this tut, by flashing stock firmware.
http://forum.xda-developers.com/showthread.php?t=2505436