I have MDK stock ROM rooted from the start. In the past I have installed ROM manager and used it to flash recovery. Sometime in the past I flashed TWRP (v2.6.3.1) and I don't remember how I did that flash, I think GOOMANAGER. Anyway I would like to use ROM manager again and no matter how many times I have tried to use ROM Manager to flash recovery the phone ONLY shows TWRP.
Any Ideas? Has this happened to anyone else?
Thank you in advance!!
The Necris
TheNecris said:
I have MDK stock ROM rooted from the start. In the past I have installed ROM manager and used it to flash recovery. Sometime in the past I flashed TWRP (v2.6.3.1) and I don't remember how I did that flash, I think GOOMANAGER. Anyway I would like to use ROM manager again and no matter how many times I have tried to use ROM Manager to flash recovery the phone ONLY shows TWRP.
Any Ideas? Has this happened to anyone else?
Thank you in advance!!
The Necris
Click to expand...
Click to collapse
You could flash the factory mdk image and that will pit a stock BL on your phone. Then re root and flash recovery same as before. Just don't take an ota obviously.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Related
I rooted my tab and installed rom manager to install clockwork mod. went to reboot into recovery and pphhhttt! it keeps cycling through the samsung icon. I know I had root with the su app installed I'm just not sure what I need to do to restore or how to get it off this boot loop could someone please help me?
automaddux said:
I rooted my tab and installed rom manager to install clockwork mod. went to reboot into recovery and pphhhttt! it keeps cycling through the samsung icon. I know I had root with the su app installed I'm just not sure what I need to do to restore or how to get it off this boot loop could someone please help me?
Click to expand...
Click to collapse
rom manager can sometimes create issues. im still not sure why people use it when you can easily flash cwm recovery through odin and it only takes about 2 seconds. im sure you didnt make a backup considering you were trying to flash recovery. the only thing you can do now is flash a stock rom via Odin now to get back up and running. for the future i would suggest you flash cwm through odin instead of trying to do it via rom manager.
thank you so much for responding. ok I think I might have odin installed on my pc. it says "odin in a nutshell". honestly I have no idea how to use it.
I have Galaxy note 1 i717D from Telus canada. it was giving me some troubles so i decided to download stock firmware from this link
http://androidromupdate.com/2013/05...elly-bean-upgrade-on-telus-galaxy-note-i717d/
Everything went okay but after restart its showing me these errors
https://share.htc.com/3mq2dJEj7
Could anybody please let me know what is this and how can i go from here. I tried wipe device, wipe cache but all are coming back with red error lines.
I took out the battery to restart it its showing me android sign with ball spinning in its tummy
Thanks
Update your recovery to TWRP 2.5.
rangercaptain said:
Update your recovery to TWRP 2.5.
Click to expand...
Click to collapse
Could you please let me know how can i do this, I am trying to find it myself too but if anycase you have tried please let me know, Do i need to do it even when I am trying to do stock recovery ?
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
You should be using Odin to do the install as instructed in the link. I don't understand why the stock recovery is even showing after a restart or why the you would toggle it after a flash.
Agoattamer said:
I don't see what installing TWRP 2.5 has anything to do with this install. OP is installing stock ROM with odin which means stock recovery.
Click to expand...
Click to collapse
Let me draw you a picture. Flash TWRP with Odin. Let it root the phone. Use TWRP to flash the rom, stock or custom.
Installing stock anything doesn't mean stock recovery. Odin is used when phone is in download mode.
But the ROM he is flashing is a stock.tar. That can only be flashed with odin. Custom recovery has nothing to do with it and will not help him achieve what he is wanting to do. OP has even mentioned he wants stock recovery. What he is doing in stock recovery after flashing the ROM with Odin has me baffled.
I don't know why "Install TWRP" is the answer to all problems on this forum. Running the updated CWM has suited me just fine and has been able to flash any ROM I wanted to try.
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
jmdearras said:
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
Click to expand...
Click to collapse
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
k1mu said:
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
Click to expand...
Click to collapse
Do you know what GooManager does before rebooting? I'd like to manually remove it.
Where is the stock ROM for Verizon 4.2.2? Or can I just Odin 4.3?
Thanks much!
Jim
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.