Hi all,
Im using cwm recovery (6.x.x.) And recently went to flash a zip. After a successful installation I hit reboot now to exit cwm and it told me there was a chance that the phone might factory reset on boot and asked me if I wanted to disable flash something. I hit yes to fix it and since then whenever my phone shuts off there's a 50/50 chance that on boot I loose all my data and settings. I am using cm10.1 and have been for a few months with no problems.
Thanks for any help!!!
Related
Hello all,
I recently botched the install to the Nightly 1.3 (or 13) Cyanogen Mod 7, and when performing a factory reset, the phone simply boots back to CM7. Is there a way to completely erase everything and start back with stock Froyo/Android 2.2?
As it stands, I can't even go into recovery mode from Rom Manager for some reason. It either freezes upon boot, shows an "unpacking" image and goes nowhere, or simply shuts down the phone.
Thank you in advance for your help.
You'll have to flash a different ROM, a factory reset just wipes data.
Sent from my Nexus S 4G using XDA App
you can use odin and your into download mode
tick re-partition、Auto Reboot、F.Reset Time to flash
Was trying to flash the ICS ROM V5 but it got stuck on the boot animation. I did a factory reset, surprisingly it was still there. So i used "Team Win Recovery Project" aka "twrp-crespo-2[DOT]0[DOT]0RC0[DOT]img" in nexusshacks.com. I went in there to do a factory reset but i wiped the ACTUAL system instead. So when i reboot i am stuck on Google. Unfortunely i only had 1 back up which is in ClockworkMod, but i cant access that. I dont mind my lost files because i can recover that but i want my phone to work again. Can i copy the nexus s contents from another nexus s and place it in my SD and will it work? If you guys have ideas please do reply because i need my phone fixed asap. Bootloader unlocked and rooted using superuser.
nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
okay,am not very familiar with TWRP but your problem doesn't seem that big,you wiped the /system which should not affect your USB storage data (even if you wiped the USB storage it's not a problem),try to boot into the bootloader (volume up + power button) then go to recovery,mount the USB storage and put a ROM on it,then just flash the ROM and your device should boot up normally,i think you weren't stuck at the bootanimation since when you flash a new ROM the first boot could take from 5 to 10 minutes.
i usually do a clean install before flashing a new ROM (format system,data,cache,boot) and the device just boot up normally after flashing the new ROM so it's not a problem if you wiped your system just flash a new ROM.
TigaTiger said:
Was trying to flash the ICS ROM V5 but it got stuck on the boot animation. I did a factory reset, surprisingly it was still there. So i used "Team Win Recovery Project" aka "twrp-crespo-2[DOT]0[DOT]0RC0[DOT]img" in nexusshacks.com. I went in there to do a factory reset but i wiped the ACTUAL system instead. So when i reboot i am stuck on Google. Unfortunely i only had 1 back up which is in ClockworkMod, but i cant access that. I dont mind my lost files because i can recover that but i want my phone to work again. Can i copy the nexus s contents from another nexus s and place it in my SD and will it work? If you guys have ideas please do reply because i need my phone fixed asap. Bootloader unlocked and rooted using superuser.
nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Click to expand...
Click to collapse
I did this same thing a few weeks ago. I just had to reinstall everything (including the recovery) from fastboot. Worked like a charm.
I used the nexusshack tut to root my nexus had no problems.
You could go into recovery, mount usb storage, find the clockworkmod directory and copy that to your pc..
do a full data wipe and flash a new rom, then install rom manager flash CWM recovery . move the clockworkmod directory back to your phone. boot into recovery and restore you backup.
Just an idea .. not sure if it could work..(take no responsibility is it doesnt)
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
Cannot reboot system from Clockworkmod Recovery
Hello, my phone detected that there is an update then i click the update after that it told me to confirm for reboot my phone enter CWM recovery then I clicked on reboot system now. It showed the Samsung Logo and the Splashscreen, but then enters the CWM recovery. I also tried pulling out the battery and then pushing the power button, but it still boots into CWM recovery. Any help? It looks like my phone got messed up and I can only use it in CWM recovery. Help is much appreciated. for everyone information i did root my phone a year ago.
So no problem at all.Wipe the data there and enter into mobile.It should work..
well the thing is i already tried that. i dont remember how many time i wipe it clean. then tried to reboot but still comeback to CWM recovery.
If there are any roms for ur device then fladh it .Of restore the nandroid backup...:thumbup:
wipe dalvik cache
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.