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.
Related
I installed 2.2 ota from verizion then I rooted
Root works
I then installed clockwork from the market and tried to install by flashing from the app.
After I reboot the phone it goes in to the default recovery app and says invalid signature.
How can I get clockwork recovery install with the 2.2 rooted ota update.
Right after you install cwm you have to boot into recovery right after and flash a non stock kernal or cwm wont stick.
Sent from my SCH-I500 using XDA Premium App
i havent done it personallly after an ota update( i hate vzw) but usually u have to install it through odin.. check noob thread in general
I did reboot in to recovery and thats when it tried to do an install and then told me it had and invalid signature.
Awesome development. Next time, post your question in Q&A.
To fix the problem, you need to flash CWM in Odin. "Flashing" it via ROM Manger only provides the update.zip on the SD Card. You need to flash a custom recovery kernel, as well as a modified regular kernel to be able to use CWM.
What kernel should I flash
I had similar trouble on 2 of our 3 phones. I had to Odin the file several times in a row before it stuck so I could boot into it and select my zip. It was like it wouldn't recognize it if you only did it once. I was probably doing something wrong, but lets just hope the end justifies the means.
Now have 3 phones running the Community Rom and we are hoping our batteries last more then a couple hours. They are certainly faster, my sons was almost unusable and my wife couldn't delete pictures after the OTA.
I still and at a loss for what kernel to flash Im fine with the stock rom. I eventually want to go to CyanogenMod when it it stable for the fascinate.
This might help.
http://forum.xda-developers.com/showthread.php?t=1053567
Try the OTB kernel
You can find it under the fascinate development forum. It's currently one of the first posts.
Sent from my SCH-I500 using XDA App
How do I flash that kernel to my phone?
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
hobokenshmo said:
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
Click to expand...
Click to collapse
what rom firmware where you be fore flashing the new rom? did you tried to wipe cache/date after flashing?
Well I restored back to factory 4.3 stock, then use another 4.3 custom rom.
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.
Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE
Hi i want just install cwm on my s3, and be with stock firmware , i dont wanna install Custom Roms or same like that, just be with CWM and stock rom. so still root required when CWM INSTALLED FROM ODIN? SORRY FOR DUMP QUESTION
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
audit13 said:
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
Click to expand...
Click to collapse
Neither has the s3 and twrp is known for borking your nand, so much so that they have a section on it on twrp website.
My opinion, use the last official cwmr for your device.
@shivadow, I didn't know that twrp affected the s3. The last version I recall using on the last few sgh-i747m phones I had was 2.87.
Do you have a link to the twrp section regarding this issue? Might be good to have it stickied?
Thank you.
Twrp buggers all devices in the end, not just the s3. It's like there's a bug that can't be solved.
Quick Google found this https://github.com/TeamWin/Team-Win-Recovery-Project/issues/773