After pingpong root has been achieved has anyone been able to install a custom recovery? I tried using the TWRP manager to install one and used the correct image but it seems that the locked bootloader will stop you from booting into the system or recovery partition after the recovery has been altered. I was forced to use ODIN to flash back to the stock firmware.
Root does not unlock your bootloader. Still need someone to do that if it will ever happen. Safestrap right now is the only viable solution but you need someone to port that also. Also this is a question so it goes in the question section.
This is not the right section for this thread. Please contact a mod and have it moved to Q&A where it belongs.
Sent from My Samsung Galaxy S6 "Pure" Black
Related
I downloaded the mistakenly flashed android 1.6 recovery image while trying to flash Cyanogen 4.1.999 . And I lost my root . Now I am unable to root my G1 by 1-click rooting process. When I run recovery Flasher, both the i am not able to backup the recovery image and install the new recovery image. Is there any way to root it.
I did a similar thing. You lost your recovery image, yes? I used downgrade-firmware method... DREAIMG.NBH+g1 root in a google search should get you started...or search the forums here sucks you got to start from scratch tho...there may be a way to downgrade to doughnut and try running the 1-click root app to restore a custom recovery image?
That means i need to downgrade to android 1.5 before being able to run Recovery Flasher.
Find a tutorial on the non 1 click root method and reflash a custom recovery image via the rc29 exploit...the power of google is in ur hands or at ur fingertips.
Look through the q&a's there is a pretty straight forward tutorial that gets you back to a rooted state.
you dont need to reroot your phone. look at the last few posts i made in the cyan 4.1.999 installation support thread in this section. it should get you where you need to go. if you need help, post there or pm me
Hi!
So finally my old phone gave up and I decided to go for Xperia SP thinking I would flash Cyanogenmod on it. Now that I have used it for a while I decided I'd keep the stock but still unlock and root the phone to be able to restore data folders (WhatsApp!).
Now most of the rooting methods here are workarounds for locked boot loader models and involve finding the right firmware from Sony and a lot of hassle with the file patching. Even with unlocked models the rooting works by flashing the exploited kernel and using the exploit to gain root.
My question is why is it not possible to just boot (NOT FLASH) modified kernel with security off via fastboot and then upload SuperSU or Superuser files into device and then after installation continue using the kernel provided by the firmware? This is also called the general method.
I will go this route if there are no reasons not to.
PS. Thanks for this wonderful community. As a long time lurker I finally decided to join you!
Hot booting doesn't work anymore in new Xperias. It used to work when I had the xoeria arc. Now for your rooting wherein you want to retain the stock kernel, just use the advance stock kernel of Doomlord, it's pure stock kernel (only with recovery added). Then flash the SuperSU zip in the recovery.
Here's the link for Doom's kernel. http://forum.xda-developers.com/showthread.php?t=2646193
Tapatalked from my Xperia SP
Okay, thanks for the info. Sucks that hot booting is not available but the method you posted seems fair enough.
I still have one question slightly related to this. In my previous phones the recovery has been installed separately (separate ramdisk and maybe even kernel?). Have I understood correctly that in Xperias the recovery is included in the boot.img instead of recovery.img and it depends on bootloader sent parameters whether the phone boots recovery or the normal mode? In other words if I install sometimes in the future a custom ROM and the recovery included is somehow broken I have to fix it via fastboot?
That's what weird thing about Sony, they don't have a separate recovery image partition.
Most Xperia custom ROMs include their own boot.img(with recovery in it) so that's covered.
Tapatalked from my Xperia P
Some Recovery's are built in into the system and that's nasty because if you wipe your system to install a custom ROM you're recovery will let you down and hang
Sent from my C5303 using XDA Free mobile app
We need to find some way to temp install a recovery into /data.. This will prevent issues when installing ROM's and wont even need root since it is "data" dunno if its possible and how to pull of.
Hello, I'm terribly sorry if this is the incorrect place to put this; but I'm desperate. I flashed hyperdrive on my galaxy s4 active NH3, and it booted the rom before I could flash the master patch, and the su update zips. So now im stuck with an unrootable nh3 galaxy s4 active that runs hyperdrive rom fine, but my wifi doesn't work, and I can't get into safestrap to flash the modules, because I can't root to install safestrap. Someone please help me, I can't reinstall my stock rom with Odin right now because my computer isn't working. Please help and thank you so much
The safe strap splash screen doesn't show up at boot? A safe strap ROM should not uninstall safe strap iirc.
Just because the app isn't in your app drawer, doesn't necessarily mean safe strap is gone. Reboot and check if it's still there, it should be.
The splash screen doent come up at all. It just says "samsung galaxy s4 active" and where the ss screen should come up, it automatically boots into the rom, displaying the rom boot animation and booting into the rom
thisisapoorusernamechoice said:
The safe strap splash screen doesn't show up at boot? A safe strap ROM should not uninstall safe strap iirc.
Just because the app isn't in your app drawer, doesn't necessarily mean safe strap is gone. Reboot and check if it's still there, it should be.
Click to expand...
Click to collapse
Could it be that when I flashed the rom in ss I wasnt able to flash the su update, and the rom took away my root? Idk im desperate
Lane5SOS said:
Could it be that when I flashed the rom in ss I wasnt able to flash the su update, and the rom took away my root? Idk im desperate
Click to expand...
Click to collapse
Every single solution I can think of either requires root (lol hardly a solution, huh?) or consists of, "Odin back to stock." Are you able to use Odin at all?
Even if you don't want to Odin back to stock NE3, I think the W0lfdroid method should still be able to root your phone while on hyperdrive, just like on stock NH3. I.e. flash the root kernel to your phone via Odin, boot and run towelroot, Odin flash the NH3 kernel, boot and install/run superSU.
I'm inclined to think that method will still work because for any rom to work on the i537, it automatically has to be compatible with our stock kernel.
thisisapoorusernamechoice said:
Every single solution I can think of either requires root (lol hardly a solution, huh?) or consists of, "Odin back to stock." Are you able to use Odin at all?
Even if you don't want to Odin back to stock NE3, I think the W0lfdroid method should still be able to root your phone while on hyperdrive, just like on stock NH3. I.e. flash the root kernel to your phone via Odin, boot and run towelroot, Odin flash the NH3 kernel, boot and install/run superSU.
I'm inclined to think that method will still work because for any rom to work on the i537, it automatically has to be compatible with our stock kernel.
Click to expand...
Click to collapse
Thank you, ill try that method. I wont be able to get my computer fixed until the weekend so im suck with no wifi or camera until then. Im still very confused as to why it did all of this. When I flashed the rom in ss, the aroma installer launched, and at the end I pressed next and it froze, so I had to take my battery out a place it back in. When I rebooted I expected to see the ss splachscreen so I could proceed to flash the masterpatch and the camera and wifi fix but it just booted right into the rom boot animation and then loads the rom. It continues to do this, so I have no safestrap now. However I do have the safestrap apk saved on my sd card along with the towlroot apk incase I ever lose root while flashing a rom and my wifi doesn't work such as the fist time I flashed hyperdrive with my NE3.
Anyways thanks a bundle
I have SM-N920C dual sim. I managed to install TWRP recovery through odin. The recovery was successfully installed and when in booted into recovery it asked me to keep read only or allow modification. I choosed allow modification. Then i rebooted into system. Now my phone does not boot. It stucks on Samsung Galaxy Note5 logo and reboots automatically.
please help me to fix it.
Jmakhdoom said:
I have SM-N920C dual sim. I managed to install TWRP recovery through odin. The recovery was successfully installed and when in booted into recovery it asked me to keep read only or allow modification. I choosed allow modification. Then i rebooted into system. Now my phone does not boot. It stucks on Samsung Galaxy Note5 logo and reboots automatically.
Click to expand...
Click to collapse
Not enough information. However, it sounds like you allowed TWRP to install root, but still have the factory/stock kernel. Bad combination.
You'll need to use ODIN to flash a custom kernel, or use ODIN to flash the stock firmware (system partition) back.
Next time, read everything you can BEFORE flashing ANYTHING. If you get a prompt that you don't understand the ramifications of, you haven't read/learned enough yet. Also, ensure you know the steps (and have the tools/files) to restore your phone to factory BEFORE you start modifying stuff.
garyd9 said:
Not enough information. However, it sounds like you allowed TWRP to install root, but still have the factory/stock kernel. Bad combination.
You'll need to use ODIN to flash a custom kernel, or use ODIN to flash the stock firmware (system partition) back.
Next time, read everything you can BEFORE flashing ANYTHING. If you get a prompt that you don't understand the ramifications of, you haven't read/learned enough yet. Also, ensure you know the steps (and have the tools/files) to restore your phone to factory BEFORE you start modifying stuff.
Click to expand...
Click to collapse
Thanks for reply. I don't know which custom kernel will work with my SM-N920C dual sim variant. Also I am unable to find stock firmware for dual sim SM-N920C. Should I try to install normal stock firmware for SM-N920C? Will my dual sim functionality work?
Ok I flashed a custom kernel through odin and now the phone is working fine.
Please close the thread.
Thanks.
I know this is not an issue forum but I CANNOT find one for the SM-i757M so this is where I'm going to put my question. One of the mods can move it if they want.
So, I tried to install CF-Auto-Root using Odin V 3.07 on my Samsung Galaxy S II i757M phone. Odin PASSes it, but it gets stuck on the red Chainfire logo with CF-Auto-Root and various info on the bottom sitting solid. It flashes every couple seconds indicating it keeps trying to run the script but it's not working. Upon going to recovery, which isn't custom, it displays the "Firmware upgrade encountered an issue" message. At the top, it's clearly in Download Mode because it says "ODIN MODE" in red. I can even connect to Odin and re-flash CF-Auto-Root again. But it won't work. Can anyone help me either get it to work, or stop it from trying to run so I can boot my phone back into the firmware without having to wipe anything?
Thank you in advance.
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
diabolicalprophecy said:
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
Click to expand...
Click to collapse
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
superluig164 said:
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
Click to expand...
Click to collapse
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
diabolicalprophecy said:
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
Click to expand...
Click to collapse
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
superluig164 said:
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
Click to expand...
Click to collapse
You don't need CF to root after flashing a custom recovery.
Just download supersu.zip and flash from philz or Twpr recovery. (download link is in supersu thread)
Flashing recovery without factory wipe will not cause any loss of data.
Yes you can boot into stock rom with philz touch or twpr as both of them support stock firmware.