hi peeps, i really have a problem right now with my one s, i upgraded my supersu to supersu pro, after that i restarted my phone and now my one s keeps booting into clockworkmod, even i select reboot system now still boot in to clockworkmod. help please dont know what to do...
anybody please help me...
guys,i reallyneed help, my phone dont turn off anymore when i press power button it keeps turning backon to CWM. i try to restore it with my backup viperones but same results still booting into CWM.:crying:
Relax. You aint getting help faster just because you constantly bump the thread. Usually it has quite the opposite effect.
Use twrp recovery instead of cwm, its much better than cwm. Try full wipe, or reinstall OS (system).
yfcpunishment said:
hi peeps, i really have a problem right now with my one s, i upgraded my supersu to supersu pro, after that i restarted my phone and now my one s keeps booting into clockworkmod, even i select reboot system now still boot in to clockworkmod. help please dont know what to do...
Click to expand...
Click to collapse
The phone bootlooping into CWM normally means your ROM is messed up. Also the One S isn't supported by CWM so you should really stop using it since it has bugs that haven't been and never will be fixed. Switch to TWRP.
If your lucky you can boot into CWM and wipe cache and the davlik cache and that will let you back into the rom.
If you're not lucky you need to flash the ROM again and fastboot flash the boot.img for the rom.
dc211 said:
The phone bootlooping into CWM normally means your ROM is messed up. Also the One S isn't supported by CWM so you should really stop using it since it has bugs that haven't been and never will be fixed. Switch to TWRP.
If your lucky you can boot into CWM and wipe cache and the davlik cache and that will let you back into the rom.
If you're not lucky you need to flash the ROM again and fastboot flash the boot.img for the rom.
Click to expand...
Click to collapse
thanks guys, i manage to get back to stock rom, relock bootloader.
thanks all
yfcpunishment said:
thanks guys, i manage to get back to stock rom, relock bootloader.
thanks all
Click to expand...
Click to collapse
Now stop using CWM as our phone isn't supported and it has lots of bugs.
Related
Hi guys I've been looking around and I'm a total noob at all this, but I went ahead and tried to root my Nexus S anyway.
Here's the site I used,
http://forum.xda-developers.com/showthread.php?t=878446
I don't really know what happened, but I have the little unlocked logo under google, but that google screen is all I can get. I can start it in fastboot mode, and when I click recovery it brings me to clockwork recovery page. I kinda just tried a bunch of weird things but everytime I try anything it keeps getting stuck at the google screen over and over again.
I'm really clueless.. If anyone could help me please give me your advice!
If it helps, I have clockwork version 3.0.0.0
you have to perform a nandroid restore or flash a ROM.
might as well update your recovery too.. wouldn't hurt
http://forum.xda-developers.com/showthread.php?t=988686
rename img to recovery.img
boot into bootloader
fastboot flash recovery recovery.img
go into recovery
when you finish downloading the rom/nandriod, go into mounts and storage and mount usb and put your sdcard
I'm sorry what is rom flashing or nandroid restore?
The clockwork update is confusing too.. I'd like to avoid that if possible..
Sorry looked up both of them and it looks like I actually need my phone to be working in order to do it?
I've read and it says it doesn't really help on stocked android phones?
The nadroid restore is the -backup and restore option in clockwork yes?
lanstrange said:
I'm sorry what is rom flashing or nandroid restore?
The clockwork update is confusing too.. I'd like to avoid that if possible..
Sorry looked up both of them and it looks like I actually need my phone to be working in order to do it?
I've read and it says it doesn't really help on stocked android phones?
The nadroid restore is the -backup and restore option in clockwork yes?
Click to expand...
Click to collapse
It doesnt really help if you reboot the phone cause with stock rom, every reboot flashes back the stock recovery.
what you should do is follow the steps @Zephik described above ( but without rebooting the phone) and you'll be able to enter the clockwork recovery ( a modified recovery allowing you to do a backup or rom flashing...) '
rom flashing is installing a rom modified by users for a better and faster user experience.
lanstrange said:
Hi guys I've been looking around and I'm a total noob at all this, but I went ahead and tried to root my Nexus S anyway.
Here's the site I used,
http://forum.xda-developers.com/showthread.php?t=878446
I don't really know what happened, but I have the little unlocked logo under google, but that google screen is all I can get. I can start it in fastboot mode, and when I click recovery it brings me to clockwork recovery page. I kinda just tried a bunch of weird things but everytime I try anything it keeps getting stuck at the google screen over and over again.
I'm really clueless.. If anyone could help me please give me your advice!
Click to expand...
Click to collapse
You should tell us your carrier and phone model, it might help the guys here to get you on the right recovery.
hxxp://flickr.com/photos/asuerio/5716164499/
hxxp://flickr.com/photos/asuerio/5716163423/in/photostream/
hxxp://flickr.com/photos/asuerio/5716162899/in/photostream/
hxxp://flickr.com/photos/asuerio/5722383955/
error when trying to access the sdcard by recovery: is not possible to mount the sdcard
I try to do everything to access the sdcard has this error
Have you fixed this? I have the same issue!
So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.
Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..
Are you able to get into bootloader?
Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?
same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.
I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.
You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader
So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?
ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.