Hello everybody! i hope everyone is good
the other day i decided to try to install CWM so i could install Xposed Firmware on a phone that wasnt on the list i have an MLS IQTalk Flame 4G iQ1502A that runs Andorid 5.1 Lollipop and its rooted via King Root so after installing Clockwork recovery i realized the sickening mess of my ways...now i have NO recovery whatsoever stock is gone and CWM aint even there,the phone boots normally and i can use it but i cant boot into the recovery mode,im scared stupid right now and dont have any money for a new phone can somebody here please help me ?
You can flash stock recovery with flashify
DeadSquirrel01 said:
You can flash stock recovery with flashify
Click to expand...
Click to collapse
i tried using flashify but its like my stock recovery has got corrupted or something,i really messed up...which is weird for me since i have been installing ROMs and everything on multiple phones over the years...but still thank you
Maybe you corrupted recovery partition, to solve this you can flash any working recovery
Related
after rooting my p506 the other day, my phone decided it wanted to do a system update, afterwards it does not want to boot past cwm at all. anyone have any ideas or a clue where i can download android 2.1
tried flashing with the 506 rom from here http://forum.xda-developers.com/showthread.php?t=1163028
but still not able to do nothing other then boot into cwm recovery
danielvanhouten said:
after rooting my p506 the other day, my phone decided it wanted to do a system update, afterwards it does not want to boot past cwm at all. anyone have any ideas or a clue where i can download android 2.1
tried flashing with the 506 rom from here http://forum.xda-developers.com/showthread.php?t=1163028
but still not able to do nothing other then boot into cwm recovery
Click to expand...
Click to collapse
Flash the stock firmware through KDZ updater. This will bring your stock ROM back. Search the forums for it.
Hello people....
I am new to SGS3 xda forum....i am from Pakistan...its been 2 weeks since i bought a SGS3 (second hand)...probably of 3mobile U.K...i was told by the seller that the phone was unlocked in Pakistan....as i tried system update from settings...it said that my phone was modified and could not be updated....so i decided to install CWM Touch on my SGS3 in order to create backup of my current stock ROM (4.1.1)...my phone is not rooted yet....i followed the instructions given in the following link:
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Odin took 1 second and my phone was booted....Odin gave the Message ''Pass!''...everything went fine as it should have been...but when i went into the recovery mod...Stock Android Recovery is opening instead of CWM Touch....noting my phone is not rooted yet....it is also normally booting and everything is fine....can anybody guide me about the problem that i am currently facing...and its solution as well....?? Help Would Be Appreciated...
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks
Sounds like you were trying to install a cwm without being rooted.
Cwm replaces the stock android recovery. You could now try flashing the cwm touch through your current cwm. Make sure its a zip. If you come and ask for help You should really follow a guide on xda though. They are the best guides around.
Shehram Ahmad said:
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks
Click to expand...
Click to collapse
When you flash a recovery you will delete the previous recovery in doing so, your stock and touch are both gone - replaced with v5.5.0.4.
You can now boot into CWM and install a better recovery, try Philz touch recovery for instance.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Did you fiqure it out
Sent from my SM-G900P using XDA Free mobile app
lsdyna said:
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Click to expand...
Click to collapse
You should be suing TWRP 2.7.0.1 and do not use goo manager.. Go to their site and click on the alternate download.. I do believe TWRP mentioned they disable the goo manage download because of issues.. Make sure you are also choosing the right phone.. I have choosing the wrong phone more than once.. Also when your done flashing in odin, and you reboot into recovery manually, make sure you wait until you see the line about recovery, before you release the 3 buttons, or you will just boot into your desktop.. Also you can use TWRP on KItKat firmware as many have done so..
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
qazplokm said:
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
Click to expand...
Click to collapse
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
qazplokm said:
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
Click to expand...
Click to collapse
I know this thread is a couple weeks old but I thought I'd add something that I have found that might help if someone else has this problem.
The only way I was able to install the new version of TWRP was to install the old one first while rooting the phone then download the new versions .zip and update it via TWRP. I was able to get the new version working that way and now I am able to flash any rom I want with no issues.
Hope this helps others.