So i have successfully rooted my droid razr m and unlocked the bootloader. i tried using safestrap to avail, i it didnt work at all. Then i tried clock work recovery flashed through with adb. It got flashed successfully. Then tried to get recovery open didnt work. I wanted to know if the unlocked bootloader message is the cause of both programs not working. or can you guys give me maybe better instructions to start flashing roms on phone on a rooted and unlocked bootloader. THANK YOU. I wanna put a rom on my device so my phones themes look cool.
I am also on 4.4.2 stock. and how do i get rid of the unlocked bootloader message.
shawnsingh said:
So i have successfully rooted my droid razr m and unlocked the bootloader. i tried using safestrap to avail, i it didnt work at all. Then i tried clock work recovery flashed through with adb. It got flashed successfully. Then tried to get recovery open didnt work. I wanted to know if the unlocked bootloader message is the cause of both programs not working. or can you guys give me maybe better instructions to start flashing roms on phone on a rooted and unlocked bootloader. THANK YOU. I wanna put a rom on my device so my phones themes look cool.
I am also on 4.4.2 stock. and how do i get rid of the unlocked bootloader message.
Click to expand...
Click to collapse
you don't need ss any more with an unlocked bl, although it should still work. however, the version you tried probably isnt compatible with kk.
as for cwm and twrp, make sure you have the correct version for kk, and after you install it you want to boot directly into it. do not let the phone boot the os the first time or it will wipe the recovery back to the stock one. also you should grab the su flashable zip and flash that when your in recovery the first time, so you have a properly working root.
after all that you can put a rom on your phone and flash it, but make sure you get one that is on kk base or it will just bootloop.
there is a method to remove the ul bl warning, check you forums general section for the post. i know there is one in the maxx/hd forum, but i don't know if they are cross compatible.
XT907
So is there any downloads i need. Can you be alittle bit more specific. I am stuck i can root i can flash 4.4.2 kk. Just need help with flash =ing custom roms and what i need for it. Thank
bwen diord said:
you don't need ss any more with an unlocked bl, although it should still work. However, the version you tried probably isnt compatible with kk.
As for cwm and twrp, make sure you have the correct version for kk, and after you install it you want to boot directly into it. Do not let the phone boot the os the first time or it will wipe the recovery back to the stock one. Also you should grab the su flashable zip and flash that when your in recovery the first time, so you have a properly working root.
After all that you can put a rom on your phone and flash it, but make sure you get one that is on kk base or it will just bootloop.
There is a method to remove the ul bl warning, check you forums general section for the post. I know there is one in the maxx/hd forum, but i don't know if they are cross compatible.
Click to expand...
Click to collapse
Related
Hello,
Im using a previous boot loader for the 4.1 JB versions and would like to update to the latest boot loader, i have tried to look on these forums but nothing specific about updating. I dont know what version bootloader im on but could some one guide me to the steps and where i can get the files from.
olster said:
Hello,
Im using a previous boot loader for the 4.1 JB versions and would like to update to the latest boot loader, i have tried to look on these forums but nothing specific about updating. I dont know what version bootloader im on but could some one guide me to the steps and where i can get the files from.
Click to expand...
Click to collapse
Well im assuming your unlocked, so if you flash an asus stock firmware for twrp it will upgrade the bootloader also. From memory i think i flashed the bootloader file in the energy rom thread, but i wouldnt recommend that method unless youve got access to nvflash.
Help! I cannot flash a custom recovery onto my phone (Verizon/RAZR Maxx HD). I used to have SafeStrap installed and it worked fine. One day I took a OTA update and lost root. So I used RSD Lite to re-flash my stock partition so I could take advantage of Towelroot and Motopocolypse while they still worked and was successful in doing both. So my phone was unlocked and rooted again and I was so happy I just used it as is for a few months. Later on, on decided it was time to try a new ROM, at which point I attempted to flash CWM recovery and it failed. So then I tried flashing SafeStrap again, and now that also failed. Then, in the process of troubleshooting failure to flash a custom recovery I managed to unroot myself (thanks to someone's bad advice). ... And of course this happened after I already took the OTA update that patched the towelroot exploit. So now my phone is Unlocked but not rooted anymore. I still cannot flash CWM (which is what I'd like to do) and use a custom ROM. Any helpful advice or constructive feedback would be greatly appreciated... Thanks!
Currently on Android 4.4.2, System Version 183.46.15.xt926.Verizon.en.US
Are you sure you are unlocked? Boot into your fastboot screen and tell us what it says. If you are unlocked, it's easy to regain root. Flash a recovery (try TWRP since CWM seems to not work) and flash a SU zip.
Sent from my HTC6525LVW using Tapatalk
Same Issue
Apparently they slipped in a fix for towelroot because I losr root. Still have an unlocked bootloader thanks to motopokalyse. I actually jacked my stock recovery and am working on fixing now. I'll let you know if I get it fixed and can flash a recovery.
I'm gave my daughter my old S3 for Christmas and I want to get it up to date.
It's running a Clean 4.1.2 ROM from back in the day. TWRP is like on v 1.x (I kid you not). I think the bootloader is unlocked because there is no Safestrap. It goes right into TWRP, no "slots".
I want to get her up to 4.3 at least, 4.4 hopefully. I tried to download on of the new ROMs but TWRP didn't even see it so I'm suspecting I need to upgrade TWRP first?
anywho...looking for a path to the latest ROMS...would rather not lockup the bootloader unless someone can make a good case for it.
Thank you very much in advance.
God Bless,
Matt
sudermatt said:
I'm gave my daughter my old S3 for Christmas and I want to get it up to date.
It's running a Clean 4.1.2 ROM from back in the day. TWRP is like on v 1.x (I kid you not). I think the bootloader is unlocked because there is no Safestrap. It goes right into TWRP, no "slots".
I want to get her up to 4.3 at least, 4.4 hopefully. I tried to download on of the new ROMs but TWRP didn't even see it so I'm suspecting I need to upgrade TWRP first?
anywho...looking for a path to the latest ROMS...would rather not lockup the bootloader unless someone can make a good case for it.
Thank you very much in advance.
God Bless,
Matt
Click to expand...
Click to collapse
Yes you need to update twrp to the latest version. And your bootloader almost has to be unlocked because if it wasn't you would not be able to install a custom recovery.
I would go with a custom rom, stay away from bootloader locked roms. There's nothing special about the new TW 4.4.2 rom other than it locks the bootloader down tight, as far as roms that's your own choice but I'd do some reading before I did anything
From my S3 running BlissStalk
You can grab the latest twrp here http://techerrata.com/browse/twrp2/d2vzw
Both .tar and .img files, the .tar requires Odin and you can install the .img through an app called flashify (requires root), its in the play store. After that read some of the ROM threads. You might want to also update your firmware and baseband. Most of the ROM threads will recommend this and give you links to proper firmware, making sure not to lock the bootloader.
Good luck
samsgun357 said:
You can grab the latest twrp here http://techerrata.com/browse/twrp2/d2vzw
Both .tar and .img files, the .tar requires Odin and you can install the .img through an app called flashify (requires root), its in the play store. After that read some of the ROM threads. You might want to also update your firmware and baseband. Most of the ROM threads will recommend this and give you links to proper firmware, making sure not to lock the bootloader.
Good luck
Click to expand...
Click to collapse
Nevermind this post, this was intended for another thread
From my S3 running BlissStalk
i unlocked the bootloader but theirs no way to root without downgrading to kk..
is theres a way fo rooting with this update can i have it
im new to sony and had a bricked problem yesterday
played a little bit with flash tool and managed to get out of it with the Unlocked bootloader..
And you were aware of such keywords like "camera DRM", "TA partition", "backup" before unlocking, right?
I've aswered you elsewhere too, but, the procedure is kinda universal (for Z phones that is): downgrade to KK, giefroot, XZDR, update to pre-rooted LL.
What's your issue with that? You do it once and you just flash the next version, keeping data, but wiping dalvik&cache.
i didnt keep the drm backup...
now i dont think i can restore it
it doesnt matter all i need to do it to root this and have the full power to my self
done and rooted and everything works fine..now i nned toknow if theres any pure android marshmellow available??
...
To root with an unlocked boot loader is the easiest thing, just flash an insecure kernel.
As for ROMS, head over to the development section and take a browse there.
gregbradley said:
...
To root with an unlocked boot loader is the easiest thing, just flash an insecure kernel.
As for ROMS, head over to the development section and take a browse there.
Click to expand...
Click to collapse
what is an insecure kernal??
im bit affraid coz i flashed a kernal and it ran into a bricked mode and had to use a stock rom flash via flashtool to recover it
i have the unlocked bootloader eka what can i do to update and how can i ??
can you please give me a guide link
thanks a lot man
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
cd2xtac said:
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
Click to expand...
Click to collapse
On OK3 the bootloader is locked. You cannot downgrade to 4.4.2 or 4.4.4 or any other previous version. You also cannot install custom recoveries like ClockworkMod or TWRP. You are relegated to Safestrap or FlashFire as discussed in jrkruse's threads.
You can ONLY use SafeStrap. TWRP and Clockworkmod cannot load because we have a locked bootloader.
You must flash a kitkat kernel to boot into safestrap, which I gather you didn't do. Then when you're done in Safestrap, flash a safestrap-flashable lollipop kernel BEFORE EXITING SAFESTRAP to boot back into your ROM.
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
cd2xtac said:
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
Click to expand...
Click to collapse
You will remain tied to OK3
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Dudash said:
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Click to expand...
Click to collapse
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
jrkruse said:
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
Click to expand...
Click to collapse
Thanks for clarifying