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
Related
I was attempting to flash a custom recovery before I caught wind that the vruame7 was a hard cookie to crumble and killed my recovery, is there anyway to get a recovery back on the phone so it can at least be updated?
leaddore said:
I was attempting to flash a custom recovery before I caught wind that the vruame7 was a hard cookie to crumble and killed my recovery, is there anyway to get a recovery back on the phone so it can at least be updated?
Click to expand...
Click to collapse
The ME7 bootloader won't let you flash a custom recovery - the stock recovery is still installed.
However, the attempt to flash the custom recovery set a flag that forces the device to boot into downloader mode.
The way to get out of this is to flash a stock ROM on top. I'd try the no-wipe ME7 ROM, then if that fails, the full-wipe.
(I'd suggest the Verizon recovery assistant for that.) Just be aware of the fact that the full wipe will cause you to lose everything on your phone.
k1mu said:
The ME7 bootloader won't let you flash a custom recovery - the stock recovery is still installed.
However, the attempt to flash the custom recovery set a flag that forces the device to boot into downloader mode.
The way to get out of this is to flash a stock ROM on top. I'd try the no-wipe ME7 ROM, then if that fails, the full-wipe.
(I'd suggest the Verizon recovery assistant for that.) Just be aware of the fact that the full wipe will cause you to lose everything on your phone.
Click to expand...
Click to collapse
Thanks for the advice, downloading the required things now. Hopefully I will get everything back to normal.
I did the exact same thing as you Leaddore.. you will be just fine following the above directions.
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
First, you should have done more research. You can't install a custom recovery on 4.3 (or MJ7). The only thing available is a "questionable" root method. No custom ROMs and no Safestrap.
Second, once an update has been applied, there is no way of going back.
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
If that doesn't work, try this one. http://forum.xda-developers.com/showthread.php?t=2507253.
Make sure you read ALL instructions first.
Good luck.
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
k1mu said:
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
Click to expand...
Click to collapse
Thanks! Knowing this, I think I will just stick with root but no recovery...hopefully, something will change and allow me to unstick myself from this situation in the future.
riker147 said:
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
Click to expand...
Click to collapse
This worked well when I had the same issue. I did lose root even with Survival Mode enabled on SuperSU, but otherwise no issues. Thank you.
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/
I rooted my LG G3 with StumpRoot. Everything went fine and I had successful root. Checked it and all. Then I flashed the new Barren ROM (v1) and I lost root. I tried re-running StumpRoot and StumpRoot is claiming I already have my device is already rooted. However, any application that requires root or Superuser, it says that root is not detected. I have Superuser on my phone.
Did you flash through TWRP?
Can you still boot into recovery, and does TWRP come up as your recovery?
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
engine95 said:
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
Click to expand...
Click to collapse
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
CodeCompile said:
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
Click to expand...
Click to collapse
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
engine95 said:
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
Click to expand...
Click to collapse
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
CodeCompile said:
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
Click to expand...
Click to collapse
The only thing I can think of is that the download was corrupt. I would try flashing TWRP with Flashify again. If that works, then reinstall SuperSU. That should get you root back. Then download a ROM again, verify the MD5, and flash in TWRP.
If Flashify won't run, then try reinstalling SuperSU, and see if that helps. If not, I think you'll have to revert to the stock ZV4 ROM with LG's Flashtool.
I suggest the Barrin V2 ROM. It's the latest version of Barren, built on the ZV6 ROM instead of ZV4: http://forum.xda-developers.com/sprint-lg-g3/development/rom-barrin-odexed-deodexed-t2950747
I tried using flashify and it gave me an error saying I needed root. I tried booting intorecovery husing the instructions and it either just boots up regularly or goes into safe mmode. Have I bricked my phone to this Rom?
Revert to stock as explained here:http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Then reroot, and start over.
HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
clarinetboy said:
HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
Click to expand...
Click to collapse
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
MehStrongBadMeh said:
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
Click to expand...
Click to collapse
Hmm. Ok so I installed TWRP 2.8.3 via Flashify, and successfully rebooted to recovery. I then flashed JFLTE-GPE 5.0 (jan. 2nd version). Now can't boot to either recovery or ROM, both of which are saying "secure fail: kernel." I did not loki doki. Ahh help!
Update: After rebooting multiple times, I can now reboot to recovery, but not to ROM.
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
clarinetboy said:
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
Click to expand...
Click to collapse
I ran into a similar problem, and had to completely restore to stock via Odin.
What were your steps here? Also I had trouble getting loki to install, which steps did you use?