Database Users

5.0.1 OTA for ROOTED Shield Tablets (DL Provided)

***For US LTE Tablet***
Here is a .zip you can flash to update to 5.0.1 from 5.0. The OTA was pulled from my device which I factory reset to 4.4.4. It will remove root and it will reflash the stock recovery, but it will NOT relock your bootloader. Make backups! Flash at your own risk! I am not responsible for any damage that occurs.
The reason why the new 5.0.1 OTA does not flash for rooted users is a sha1 hash is generated from the system partition. If it doesn't match what the hash should be from the factory, it fails out. Removing these checks will break your device because of the new differential update method employed, which is why these sha1 hashes are so important. The .zip I have is a standard update (not differential) and can be flashed with any recovery you want
Here is a link:
https://drive.google.com/file/d/0B_iRndxSfhpXRjBXY3FXUG1tNDA/view?usp=sharing

Thanks for your explanation! Any chance for providing the same zip for eu lte?

So is this a modified zip or is it just the full version from nvidia's server?

The rest of the world - LTE - version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.

any zip for wifi only tablet?

Adrixan said:
The rest of the world version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
Click to expand...
Click to collapse
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0

What do you have to do to root after installing this?

RollWii said:
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
Click to expand...
Click to collapse
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
TheCrowing said:
What do you have to do to root after installing this?
Click to expand...
Click to collapse
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.

Adrixan said:
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Click to expand...
Click to collapse
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?

RollWii said:
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
Click to expand...
Click to collapse
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1

Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?

RollWii said:
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
Click to expand...
Click to collapse
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)

Adrixan said:
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Click to expand...
Click to collapse
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?

RollWii said:
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
Click to expand...
Click to collapse
No, but the File from the guy, who started this thread should work for the U.S. LTE version following the same instructions as I just gave.

How long should it be sitting at the NVIDIA screen after flashing the update?
It went after a couple minutes.

Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
sorry but i forgot how to flash the SUperSU update.zip how and where can i find it again?

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk

kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.

USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk

work great
thanks

Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.

kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.

Rooted my Shield two times wth CWM without problems.

astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse

Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)

From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.

If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day

[(GUIDE)] Lg V410 kitkat return to stock w/o pc.

So here's my little guide on returning your v410 to stock unrooted from kitkat.
First of all download the stock rooted rom by @timmytim
http://forum.xda-developers.com/g-p...-v410-onlykot49i-v4101d-4-4-2-rooted-t3040208
Next download the stock recovery img.
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
Have flashify installed
Busy box app by stericson installed, I have pro.
Boot into twrp
Flash stock rom. Do not wipe anything!!
Reboot
Wait for apps to optimize.
Upon reboot flash the stock recovery via flashify. Once succeeded just press the home button to exit out!!
Open busy box wait for it to load and choose uninstall, normal uninstall not smart.
Reboot
Upon reboot open up su. Do not update binary!!
Scroll through settings and tick Full Unroot, select yes and wait.
Once uninstalled it will exit out on it's own
Reboot
Download root checker and check, you should be unrooted and able to factory reset or whatever you choose.
You removed busy box so there should be no traces of root.

Has anyone tried this? I'm desperate to get back on stock OTA/unrooted, this tablet has just been too laggy for my liking on any custom ROM. I'm currently on CM nightlies, on LL.....

So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.

ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.

any updates?
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?.
Click to expand...
Click to collapse
Hey did the same and i'm now in the same predicament. i know its been a while but did u manage to figure it out by any chance?

Nope still sitting on my desk as a mouse pad
sent from a device using an app

LXative said:
So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.
Click to expand...
Click to collapse
did you have a Sim card in it?
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.
Click to expand...
Click to collapse
ok so there is a zip for stock non testbuild. But how did the device pop up with a update wouldn't it not update if you had a custom recovery

How to root LP 5.1.1 with New system-less SuperSU 2.6.X

Hi all,
I just finished testing the new method of rooting using new SuperSU system-less and it's working well on my P600. I don't have other device to test it on, but if you guys could test it out on your device and report back, that would be nice.
Here how to root using new SuperSU system-less app:
Prep:
1) Download Odin 3.09 http://odindownload.com/Samsung-Odin/#.Vm3AglE1I-Q
2) Download SuperSu version 2.6.2 to your SDcard here http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
3) Download TWRP 2.8.7.0 tar file to your PC here https://dl.twrp.me/lt03wifiue/ (you must use Spen to navigate, touch won't work)
For P605 - Please use twrp-2.8.7.0-lt03ltexx-4.4.img.tar version here https://dl.twrp.me/lt03ltexx/
4) Download the full stock 5.1.1 firmware by download this tool to your PC from here http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Then use the tool to download 5.1.1 rom (very fast download). set model=sm-p600, region=XAR, put a check in "Auto" and "Decrypte automatically"
Execcution:
1) Use Odin to flash full factory rom 5.1.1 to your device with "Auto Reboot" checked. If you already using 5.1.1 with root, you can just flash over your current one. Your data will be preserved. It's not nessessary to flash the full firmware but it's easier and less confuse. Once completed your device will reboot. Now boot back to download mode.
2) Use Odin to flash TWRP 2.8.7.0 with "Auto Reboot" UNchecked. Once completed. Hold Vol up+Home+power buttons to boot to TWRP recovery(do not let your device boot up). It will take a while so just wait. You also will see a red message warning about SEdroid security..blah blah...just ignore it. If you want TWRP touch, you can flash this version zip (can't flash through ODIN) before proceed. https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi
3) Once in TWRP, flash the SuperSU 2.6.1 system-less. Becareful here, after hit REBOOT, If TWRP offered to root, DO NOT DO IT (You will bootloop if you miss this step). Hit on "do not install". Your device will reboot. Done!! This SuperSU will patch your kernel and install root. Once completed boot up and enjoy. Your system is now rooted with TWRP installed. Pretty nice!!
EDIT: You also need to disable "Security change" pop up by remove or use Titanium to disable "Security policy updates" and "SecurityLogAgent". I heard report that if you don't your device may bootloop later on.

@joshndroid made his own version of twrp 2.8.7 which has full touch support/recognition (not just the s-pen). Here is the link:
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi Maybe could you put this version in the OP as another option instead of the official twrp?

Guys, a question. Can i use the exynos version of TWRP, ie- lt03wifiue, on my SM-P601, which is also the exynos one, but with 3G support.?
Thanks.

mosimchah said:
@joshndroid made his own version of twrp 2.8.7 which has full touch support/recognition (not just the s-pen). Here is the link:
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi Maybe could you put this version in the OP as another option instead of the official twrp?
Click to expand...
Click to collapse
I don't think he made one for Odin.
Sent from my SM-P600 using Tapatalk

amey2606 said:
Guys, a question. Can i use the exynos version of TWRP, ie- lt03wifiue, on my SM-P601, which is also the exynos one, but with 3G support.?
Thanks.
Click to expand...
Click to collapse
Yes
Sent from my SM-P600 using Tapatalk

buhohitr said:
I don't think he made one for Odin.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Good point, I didn't notice that, however we could flash the official twrp with odin, and then we could flash joshndroid's twrp from the official twrp. So could you add that to the op?

mosimchah said:
Good point, I didn't notice that, however we could flash the official twrp with odin, and then we could flash joshndroid's twrp from the official twrp. So could you add that to the op?
Click to expand...
Click to collapse
Added to OP. Thanks

Ok
Root is present (supersu) seem to work but, don't work with some apps

murigny64 said:
Ok
Root is present (supersu) seem to work but, don't work with some apps
Click to expand...
Click to collapse
Give me a few so I can test them out

murigny64 said:
Ok
Root is present (supersu) seem to work but, don't work with some apps
Click to expand...
Click to collapse
Did you install supersu from the playstore and did it ask to update binaries? I can't remember when I did mine if it asked or not. I don't have any su issues with mine.

Flash firm doj3 with odin
Reboot in bootloader
Flash twrp with odin
Reboot in twrp
Flash supersu 2.61
Reboot.
Kernel seem to be patched (red warning message), Supersu app is present with no binarie update needed.
Reboot in twrp and Flash xposed wanam mod
Result:
Titanium Backup: ok
Rebooter app: nok
Freeze after 2 mins: have to hard reboot, again and again.
So, I flash again with odin and use the old method (boot patched)

how do i uninstall twrp?

tahrang said:
how do i uninstall twrp?
Click to expand...
Click to collapse
Flash a different recovery, either with twrp or odin. Why do you want to remove twrp?

Done and completed
twrp not working correctly, it did previously, but after the update, it doesn't.
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
buhohitr said:
Hi all,
I just finished testing the new method of rooting using new SuperSU system-less and it's working well on my P600. I don't have other device to test it on, but if you guys could test it out on your device and report back, that would be nice.
Here how to root using new SuperSU system-less app:
Prep:
1) Download SuperSu version 2.6.1 to your SDcard here http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
2) Download TWRP 2.8.7.0 tar file to your PC here https://dl.twrp.me/lt03wifiue/ (you must use Spen to navigate, touch won't work)
3) Download the full stock 5.1.1 firmware by download this tool to your PC from here http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Then use the tool to download 5.1.1 rom (very fast download). set model=sm-p600, region=XAR, put a check in "Auto" and "Decrypte automatically"
Execcution:
1) Use Odin to flash full factory rom 5.1.1 to your device with "Auto Reboot" checked. If you already using 5.1.1 with root, you can just flash over your current one. Your data will be preserved. It's not nessessary to flash the full firmware but it's easier and less confuse. Once completed your device will reboot. Now boot back to download mode.
2) Use Odin to flash TWRP 2.8.7.0. Once completed. Hold Vol up+Home+power buttons to boot to TWRP recovery(do not let your device boot up). It will take a while so just wait. You also will see a red message warning about SEdroid security..blah blah...just ignore it. If you want TWRP touch, you can flash this version zip (can't flash through ODIN) before proceed. https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03wifi
3) Once in TWRP, flash the SuperSU 2.6.1 system-less. Becareful here, If TWRP offered to root, DO NOT DO IT. This SuperSU will patch your kernel and install root. Once completed boot up and enjoy. Your system is now rooted with TWRP installed. Pretty nice!!
Click to expand...
Click to collapse
HELP!
yes I'm screaming, sorry.
I followed these instructions, and now my note is stuck in loop - starts with samsung galaxy note 10.1 2014 logo, goes to samsung logo and restarts.
Please, please help
thanks
Now it is stuck on samsung logo, and doesnot go any further.
Ok, now I'm starting the whole thing again. hopefully, this will go better
third time is the charm! succeeded.

What do i do when i already have the spanish firmware? Do i need to flash it again with the 5.1.1 code XAR? Or can i flash TWRP with Odin now.?

vuurvlinder said:
What do i do when i already have the spanish firmware? Do i need to flash it again with the 5.1.1 code XAR? Or can i flash TWRP with Odin now.?
Click to expand...
Click to collapse
I flashed the xar update, even though i already had the spanish one, plus i was rooted. then i flashed twrp and supersu like in the post above.
thanks
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
murigny64 said:
Flash firm doj3 with odin
Reboot in bootloader
Flash twrp with odin
Reboot in twrp
Flash supersu 2.61
Reboot.
Kernel seem to be patched (red warning message), Supersu app is present with no binarie update needed.
Reboot in twrp and Flash xposed wanam mod
Result:
Titanium Backup: ok
Rebooter app: nok
Freeze after 2 mins: have to hard reboot, again and again.
So, I flash again with odin and use the old method (boot patched)
Click to expand...
Click to collapse
did you get the wanam again after the old method? if so, please tell me how.
thanks

Hmm - I've Odin'd the new XAR v.5.1.1 just fine, but when I try to Odin TWRP 2.8.7/6/3, they all fail in Odin 3.09. I've tried multiple times with same result. Any suggestions?

Michael in ATL said:
Hmm - I've Odin'd the new XAR v.5.1.1 just fine, but when I try to Odin TWRP 2.8.7/6/3, they all fail in Odin 3.09. I've tried multiple times with same result. Any suggestions?
Click to expand...
Click to collapse
Did you boot up after Odin XAR 5.1.1? boot up then boot down to Odin download mode and try again.

Not able to Odin TWRP
buhohitr said:
Did you boot up after Odin XAR 5.1.1? boot up then boot down to Odin download mode and try again.
Click to expand...
Click to collapse
I sure did, and should've been clearer. I'm running 5.1.1 XAR that I Odin'd yesterday. USB debugging is enabled, and Odin tries/fails when trying to load up to 4 versions of TWRP that I've tried. Further, I get corrupted firmware after it tries, and have to reinstall v5.1.1 (if that tells those much smarter than I anything)

Michael in ATL said:
I sure did, and should've been clearer. I'm running 5.1.1 XAR that I Odin'd yesterday. USB debugging is enabled, and Odin tries/fails when trying to load up to 4 versions of TWRP that I've tried. Further, I get corrupted firmware after it tries, and have to reinstall v5.1.1 (if that tells those much smarter than I anything)
Click to expand...
Click to collapse
Can you try to boot int recovery to see if you can access stock recovery? Possible you need to do format storage?

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!