Database Users

[Q] One Click/Very Straightforward Bootloader Unlock?

I've been on the Original Development Forum for the past few days, and I've tried and failed to understand the proper procedure for getting a custom recovery on the phone. The thought of bricking it is really scary to me, so I only want to unlock it if I really know what I'm doing, or there is a one click method of unlocking. Any instructions, explanations, or one click solutions would be greatly appreciated!

Technically the bootloader is not unlocked, only bypassed. Two, if you're that scared I recommend not doing it but if you really want too it's extremely simple.
Go to the Play Store and download "Goo Manager". (YOU MUST BE ROOTED!), From there select Install OpenRecovery Script and Goo Manager will guide you through the rest and install TWRP which is loki'd and ready to go. After that though you can only flash ROM's that have been loki-fied or you won't be able to boot.

cosmicmoonranger said:
I've been on the Original Development Forum for the past few days, and I've tried and failed to understand the proper procedure for getting a custom recovery on the phone. The thought of bricking it is really scary to me, so I only want to unlock it if I really know what I'm doing, or there is a one click method of unlocking. Any instructions, explanations, or one click solutions would be greatly appreciated!
Click to expand...
Click to collapse
An automated method hasn't been created yet. If you'd like some help, PM me.
---------- Post added at 08:45 PM ---------- Previous post was at 08:44 PM ----------
Thermalwolf said:
Technically the bootloader is not unlocked, only bypassed. Two, if you're that scared I recommend not doing it but if you really want too it's extremely simple.
Go to the Play Store and download "Goo Manager". (YOU MUST BE ROOTED!), From there select Install OpenRecovery Script and Goo Manager will guide you through the rest and install TWRP which is loki'd and ready to go. After that though you can only flash ROM's that have been loki-fied or you won't be able to boot.
Click to expand...
Click to collapse
Now you got me there :good:
Good call.

Thermalwolf said:
Technically the bootloader is not unlocked, only bypassed. Two, if you're that scared I recommend not doing it but if you really want too it's extremely simple.
Go to the Play Store and download "Goo Manager". (YOU MUST BE ROOTED!), From there select Install OpenRecovery Script and Goo Manager will guide you through the rest and install TWRP which is loki'd and ready to go. After that though you can only flash ROM's that have been loki-fied or you won't be able to boot.
Click to expand...
Click to collapse
So, just to clarify, if I click install OpenRecovery Script in the app, it will install a loki'd TWRP? Will there be anything in the process of installing where I would click anything besides "yes" or "continue"?
Also, will goo manager automatically flash roms? is this better or worse than doing it manually through TWRP?
Thanks!

cosmicmoonranger said:
So, just to clarify, if I click install OpenRecovery Script in the app, it will install a loki'd TWRP? Will there be anything in the process of installing where I would click anything besides "yes" or "continue"?
Also, will goo manager automatically flash roms? is this better or worse than doing it manually through TWRP?
Thanks!
Click to expand...
Click to collapse
Yes that's correct, but you must be rooted with Motochopper first. Goo Manager can download ROMs for you, but any automated ROM flashing app is discouraged.

Am I missing something? I downloaded GooManager and I don't see any OpenRecovery Script option. I don't see anything pertaining to recoveries other than Reboot to recovery.

nyeazyone said:
Am I missing something? I downloaded GooManager and I don't see any OpenRecovery Script option. I don't see anything pertaining to recoveries other than Reboot to recovery.
Click to expand...
Click to collapse
Hit the menu key in Goo

Ok. What an I missing. Goo manager will download twrp but it won't flash it. What's the next step once goo downloads the recovery image?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

milicigoran said:
Ok. What an I missing. Goo manager will download twrp but it won't flash it. What's the next step once goo downloads the recovery image?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Are you rooted with Motochopper? If so, go into recovery, and it will be TWRP, it doesn't flash it, it uses Terminal commands to install it. You see nothing happen.

[Q] CMW success, SU fail :(

Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.

jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used

leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.

jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.

leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager

actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.

No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card

scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice

jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!

noob here, lost at rooting

hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)

I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk

update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?

You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk

Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?

If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk

I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)

beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app

beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.

Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)

so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?

Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Another "software not authorized by ATT" plead for help

Reaching out for some help... I'm stuck at this point. I need to get a recovery working. Preferably cwm at this point. All other questions I found when searching were users on previous versions of Android and honestly the whole baseband build thing confuses it. I can still boot to the normal phone and use it as usual but I do want to get a working recovery again.
Device: I337 / Rooted
Android: 4.4.4
Baseband: I337UCUAMF3
Rom: Cyanogenmod Nightly 8/6/14
Kernel: 3.4.0-cyanogenmod-g433243c / [email protected] #1 / Wed Aug 6 2014
I was on TWRP and tried flashing to CWM with Rashr. I did this because TWRP was not compatible with the new CM nightlies.
Recovery now only boots to: "System software not authorized by ATT has been found on your phone"
Is there a way I can get a working recovery going now?
Help is appreciated.
Thanks.

did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--

rugmankc said:
did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--
Click to expand...
Click to collapse
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.

RiG14LA said:
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.
Click to expand...
Click to collapse
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app

Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--

jd1639 said:
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rugmankc said:
Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--
Click to expand...
Click to collapse
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:

RiG14LA said:
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:
Click to expand...
Click to collapse
It's not so bad. Use Odin to get your system up and running again. Then use this to root and get a custom recovery on http://forum.xda-developers.com/showthread.php?p=41892523
Sent from my Nexus 5 using XDA Free mobile app

Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk

if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.

OP has MDL build his radio "baseband" is mf3. He can flash any radio he wants after rooted.
Sent from my SGH-I337 using Tapatalk

iateshaggy said:
if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.
Click to expand...
Click to collapse
He's using twrp and cm. Baseband is most likely from the cm version here's on.
Sent from my Nexus 5 using XDA Free mobile app

rugmankc said:
Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?

RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?
Click to expand...
Click to collapse
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk

rugmankc said:
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?

RiG14LA said:
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?
Click to expand...
Click to collapse
Yes I change recoveries as needed but have been on current for awhile. Read up on flashing CWM to be sure you know of any issues and exact steps. If it is a zip no issues should be encountered. Never liked to use Rom MGR.
Sent from my SGH-I337 using Tapatalk

Read last 7 pages of cm11 thread. They talked about changing updater script of cm rom. If you flash CWM recovery zip remember to flash loki before rebooting. Uncheck sig check in twrp before flashing CWM. You can't restore twrp nandroid with CWM and vice versa. They list a flashable CWM zip there too.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, My M9 milestone seems to be last stable build--many reboots etc on recent nightlies. But, that is part of the game with nightlies. As I "age" I need more stable roms--less stress--
---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------
RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
Click to expand...
Click to collapse
Oh, the salvation of nandroids--:good::good:
I used an app like Rashr long time ago, but didn't like it. Maybe not a bad idea to have it and keep a backup just in case--

Trouble flashing ANY custom rom!

Hey all, Ive had this weird issue lately when it comes to to flashing custom roms. I Have just rooted and unlocked the bootloader on my phone and i want to install a custom rom
but every time i try to flash it in twrp it fails and says "This package is for build hltetmo your device is ."
My phone IS hltetmo so im very confused on whats going on here
Any help?

Ferkacete said:
Hey all, Ive had this weird issue lately when it comes to to flashing custom roms. I Have just rooted and unlocked the bootloader on my phone and i want to install a custom rom
but every time i try to flash it in twrp it fails and says "This package is for build hltetmo your device is ."
My phone IS hltetmo so im very confused on whats going on here
Any help?
Click to expand...
Click to collapse
What recovery are you using? Some (<= android 6) ROMs require TWRP 2.8.7 hltevzw and some (>= android 7) require TWRP 3.1.1 hlte or higher.

cssr said:
What recovery are you using? Some (<= android 6) ROMs require TWRP 2.8.7 hltevzw and some (>= android 7) require TWRP 3.1.1 hlte or higher.
Click to expand...
Click to collapse
Im using twrp and the recovery img i used is called twrp-2.8.7.0-hltevzw-4.4.img.tar and im lollipop with OF1
The roms im trying to flash are Oreo roms so does that mean i need a more updated version of twrp?

Ferkacete said:
Im using twrp and the recovery img i used is called twrp-2.8.7.0-hltevzw-4.4.img.tar and im lollipop with OF1
The roms im trying to flash are Oreo roms so does that mean i need a more updated version of twrp?
Click to expand...
Click to collapse
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!

cssr said:
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!
Click to expand...
Click to collapse
The roms work now! Thank you so much

Ferkacete said:
The roms work now! Thank you so much
Click to expand...
Click to collapse
Great!

cssr said:
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!
Click to expand...
Click to collapse
I can't get TWRP to stick. Can u help?

jerryspring said:
I can't get TWRP to stick. Can u help?
Click to expand...
Click to collapse
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!

cssr said:
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!
Click to expand...
Click to collapse
Seems as if I have both recoveries. SS and twrp
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
cssr said:
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!
Click to expand...
Click to collapse
Yea. I did. I am on 4.3 boot loader, and I flashed sepl1 modem. Baseband says sepl1 even though I'm on 4.3 boot loader. Even when I flash stock ROM, the stock ROM won't flash, even though Odin says successful

jerryspring said:
Seems as if I have both recoveries. SS and twrp
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
Yea. I did. I am on 4.3 boot loader, and I flashed sepl1 modem. Baseband says sepl1 even though I'm on 4.3 boot loader. Even when I flash stock ROM, the stock ROM won't flash, even though Odin says successful
Click to expand...
Click to collapse
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.

cssr said:
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.
Click to expand...
Click to collapse
I thought bootloader unlock was only capable with 4.4...and will the stock firmware flash successfully? and I don't know why it did not last successfully. I originally came from mje firmware and I was flashing 5.0

cssr said:
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.
Click to expand...
Click to collapse
I tried flashing of1.. it goes to blue writing saying recovery booting and hangs. Stock firmware will not flash!