Heyyo, Slenderman8090 here! I am currently on the newest firmware build that Verizon Sent out. I am downgrading so I can flash/root OB6 Firmware. TWRP doesn't seem to want to flash via ODIN, but I keep getting an AUTH error on ODIN. I am a 3 Year patron of XDA/General Development, and I am not familiar with Verizon and it's lockdowns. So, what ever I can do, please let me know.
Thanks so much,
Slenderman8090
EDIT:
I HAVE FIGURED OUT HOW TO FIX IT, NOW AROMA DOESN'T WORK ON MY TWRP, WHAT VERSION IS NEEDED?
Slenderman8090 said:
Heyyo, Slenderman8090 here! I am currently on the newest firmware build that Verizon Sent out. I am downgrading so I can flash/root OB6 Firmware. TWRP doesn't seem to want to flash via ODIN, but I keep getting an AUTH error on ODIN. I am a 3 Year patron of XDA/General Development, and I am not familiar with Verizon and it's lockdowns. So, what ever I can do, please let me know.
Thanks so much,
Slenderman8090
EDIT:
I HAVE FIGURED OUT HOW TO FIX IT, NOW AROMA DOESN'T WORK ON MY TWRP, WHAT VERSION IS NEEDED?
Click to expand...
Click to collapse
As far as everything I've been able to keep up with and read, in order for our Verizon (hltevzw) Galaxy Note 3 phones to be bootloader unlocked with a properly functioning TWRP recovery that also handles AROMA files as well, TWRP v2.8.7.0 (4.4 (the Verizon "hltevzw" variant), is the correct/proper variant that you'll need to flash onto your phone instead of the version that you've got currently. Also, it apparently doesn't matter at all whether or not you've already got a newer version of TWRP recovery installed, any newer version after v2.8.7.0 can't flash AROMA. So since you want to flash AROMA files, TWRP v2.8.7.0 (4.4) is apparently the last official version to be released which supports AROMA. I'm not sure why it didn't carry on into newer releases, but I'm sure the devs had a good enough reason for not doing so.
Related
I'm trying to learn more about the S5 root world. I am currently running the OTA NHA build, and am rooted using towelroot, and have the latest safestrap installed (also have supersu and busybox). What i am trying to understand is how the custom rom's work now. I just got the S4, and never had my bootloader locked since i rooted/rom'd earlier on and never ran stock, and i was using TWRP so there were no rom slots or the like; you downloaded a rom, wiped your phone, flashed it, done.
This bootloader/kernel/baseband talk is what's confusing me. A question that i've been trying to find the answer for is as such: let's say i have my NHA rooted phone, but there is an NE9 rom on the forum i want to try (extreme syndicate/alliance). Can i just flash that to a rom slot and go, or do i flash the kernel as well? if i flash the kernel, won't that mess with my stock rom, or does that just patch the kernel inside of the rom slot?
I already understand that chronologically, the baseband/build versions are NCG>NE9>NHA>NI2, so understand that rom's baseband is a version behind NHA. Someone please help clarify some of this for me
I bought a new Samsung Galaxy S5 today at a local T-Mobile store. But it turns out that the model number is SM-G900T3, for which I cannot find any information on how to root and install custom recovery. Has anyone had any luck with this model? It's build LMY47X.G900T3UVU1FOF6 Android version 5.1.1
Thanks!
What to do for G900T3 S5
Same here. I went from S4 running cyangenmod 12.1 to s5 g900t3. All because i cracked the screen on my s4. I don't like the stock firmware too much on the s5 so I've been researching rooting it. But run into the same issue. No info on rooting this model. The only thing I can think of to do is downgrade to 4.2 using Odin then root and install CWM. Yet I found a forum where someone posted they were unsuccessful in downgrading the g900t3. So HELP PLEASE.
Turns out it's actually simpler than that. If your goal is to replace the stock firmware with a custom one, such as cyanogenmod then you don't even need to root your stock firmware. All you need to do is flash TWRP custom recovery with Odin, then reboot into TWRP recovery and create a backup of your stock firmware just in case. After that you should be good to go ahead and install cyanogenmod or any other supported custom firmware. This is exactly what I've done with my SM-G900T3.
But if you really want to root your stock firmware then here is a guide for that:
http://forum.xda-developers.com/tmo...t/root-kernel-root-method-fof6-5-1-1-t3158005
Hope this helps.
OK thanks for the link. It does state not to flash if I'm on FOG6 Build, which I am. Even though my baseband version is FOF6. Guessing the Build is more important. Last night I tried to downgrade to 4.4 using Odin, that immediately didn't work. So I Flashed Philztouch CWM on it then tried to install superuser from the galaxys5 root page, but it was stuck in bootloop on the T-mobile screen. I realized the superuser was for 5.0 version. So then I used Odin again to flash my firmware back on to it the g900t3 5.1.1 FOG6 from the Sammobile website. After that, because I saw I had a reply on here, I used Philztouch to install Cyanogenmod 12.1 nightly recovery (don't know which on it was, either klte or klteusc) without rooting and I was stuck in the Cyan's big eyed alien face thing bootloop screen again. So then I had to reinstall my stock firmware once more. Basically after 4+ hours of rooting I'm back where I started. LOL. I don't know what else to do. I'm still researching FOG6 to see if I find anything.
zizidiesel said:
ok thanks for the link. It does state not to flash if i'm on fog6 build, which i am. Even though my baseband version is fof6. Guessing the build is more important. Last night i tried to downgrade to 4.4 using odin, that immediately didn't work. So i flashed philztouch cwm on it then tried to install superuser from the galaxys5 root page, but it was stuck in bootloop on the t-mobile screen. I realized the superuser was for 5.0 version. So then i used odin again to flash my firmware back on to it the g900t3 5.1.1 fog6 from the sammobile website. After that, because i saw i had a reply on here, i used philztouch to install cyanogenmod 12.1 nightly recovery (don't know which on it was, either klte or klteusc) without rooting and i was stuck in the cyan's big eyed alien face thing bootloop screen again. So then i had to reinstall my stock firmware once more. Basically after 4+ hours of rooting i'm back where i started. Lol. I don't know what else to do. I'm still researching fog6 to see if i find anything.
Click to expand...
Click to collapse
i got it actually fina****ingly. Got it rooted and cyanogenmod 12.1 nightly installed. I am retrieving my old apps and data as i'm typing. Success feels good. Many thanks to you for taking an interest and responding and to this entire community. Woot woot
liquidsnake54 said:
Turns out it's actually simpler than that. If your goal is to replace the stock firmware with a custom one, such as cyanogenmod then you don't even need to root your stock firmware. All you need to do is flash TWRP custom recovery with Odin, then reboot into TWRP recovery and create a backup of your stock firmware just in case. After that you should be good to go ahead and install cyanogenmod or any other supported custom firmware. This is exactly what I've done with my SM-G900T3.
Click to expand...
Click to collapse
Would this be the same procedure to follow if I wanted to put a stock T-Mobile version of 4.4.2 on my SM-G900T3? Or would that not work?
Hi all, I wanted to get some info on this topic, I have done allot of searching/reading and still have a bit of confusion. Currently I have a SGH-I337 AT&T S4 that is running 5.0.1 that I rooted. I want to update to the custom 6.0 ROM, which I downloaded from the JDC Team along with Gapps and superSU 2.52. I am going to follow the directions on their thread, but my issue is flashing the latest correct version of TWRP. I am able to boot into recovery and when Im flashing the TWRP version they have on their site (recovery,flash from SD, TWRP-2.8.7.2-F2FS.ZIP) I get a footer and authenticate error. Im assuming this version of TWRP is not compatible with this ver. S4? Or is there another way I have to flash it to the phone. Please point me to a thread that has the steps to do this if possible.
jgig73 said:
Hi all, I wanted to get some info on this topic, I have done allot of searching/reading and still have a bit of confusion. Currently I have a SGH-I337 AT&T S4 that is running 5.0.1 that I rooted. I want to update to the custom 6.0 ROM, which I downloaded from the JDC Team along with Gapps and superSU 2.52. I am going to follow the directions on their thread, but my issue is flashing the latest correct version of TWRP. I am able to boot into recovery and when Im flashing the TWRP version they have on their site (recovery,flash from SD, TWRP-2.8.7.2-F2FS.ZIP) I get a footer and authenticate error. Im assuming this version of TWRP is not compatible with this ver. S4? Or is there another way I have to flash it to the phone. Please point me to a thread that has the steps to do this if possible.
Click to expand...
Click to collapse
Your phone has the newer bootloader which is locked. Only variants with older bootloader, mdl and mdb will be able to flash twrp.
You can still use flashfire but your options are limited and marshmallow isn't one of them.
Airtioteclint said:
Your phone has the newer bootloader which is locked. Only variants with older bootloader, mdl and mdb will be able to flash twrp.
You can still use flashfire but your options are limited and marshmallow isn't one of them.
Click to expand...
Click to collapse
Thanks..
jgig73 said:
Hi all, I wanted to get some info on this topic, I have done allot of searching/reading and still have a bit of confusion. Currently I have a SGH-I337 AT&T S4 that is running 5.0.1 that I rooted. I want to update to the custom 6.0 ROM, which I downloaded from the JDC Team along with Gapps and superSU 2.52. I am going to follow the directions on their thread, but my issue is flashing the latest correct version of TWRP. I am able to boot into recovery and when Im flashing the TWRP version they have on their site (recovery,flash from SD, TWRP-2.8.7.2-F2FS.ZIP) I get a footer and authenticate error. Im assuming this version of TWRP is not compatible with this ver. S4? Or is there another way I have to flash it to the phone. Please point me to a thread that has the steps to do this if possible.
Click to expand...
Click to collapse
Currently I have the same phone and carrier...
If you are still interested in a custom recovery our only option is SafeStrap Recovery, you might want to check out this thread: http://forum.xda-developers.com/showthread.php?t=2448925. I was able to install SafeStrap and utilize NC1 Flasher to facilitate booting into SafeStrap Recovery with no problems whatsoever. Once you have SafeStrap Recovery operational on your phone you can also flash custom TouchWiz ROM's.
I hope that helps and, I'm far from an expert but, don't hesitate asking any questions!
PEACE
I have a S5 with the new Marshmallow update via the Telus network in Canada. I had root for the Lollipop but took it out so I could update without problems. Lo and behold the Marshmallow update went in without a hitch but when I tried to flash TWRP with ODIN it didn't work. Am I missing something or does rooting the Marshmallow update require a new TWRP version? I used TWRP and SUPER SU last time to root Lollipop and al I did was put SUPER SU in a folder and flashed TWRP and then installed SUPER SU with TWRP and I was rooted. I just want the easiest step by step way to root my S5 again with the Marshmallow update. My provider is Telus from Canada.
Which model S5?
Unless MM locked your bootloader, TWRP 3.0.0.0 and SuperSU 2.71 beta are what I used to root MM
ODIN 3.10.7
*Detection* said:
Which model S5?
Unless MM locked your bootloader, TWRP 3.0.0.0 and SuperSU 2.71 beta are what I used to root MM
ODIN 3.10.7
Click to expand...
Click to collapse
SM-G900W8VLU1DPD3 Baseband Version Model #SM-G900W8 Build# MMB29M.G900W8VLU1DPD3 These are all the pertinent numbers. Do you have the steps needed to unlock and then ROOT. I'm not sure if the bootloader is locked. Hopefully you can help me get rooted again.
randyboy99 said:
SM-G900W8VLU1DPD3 Baseband Version Model #SM-G900W8 Build# MMB29M.G900W8VLU1DPD3 These are all the pertinent numbers. Do you have the steps needed to unlock and then ROOT. I'm not sure if the bootloader is locked. Hopefully you can help me get rooted again.
Click to expand...
Click to collapse
Hey do you have the .tar file for the firmware? im looking to update as well
Redbull10927 said:
Hey do you have the .tar file for the firmware? im looking to update as well
Click to expand...
Click to collapse
I wasn't thinking when I first read your post. If you"re looking for the MM Firmware I think I have what you are after. I got it from the S Mobile site, so if the guys don't mind me posting it with this reply here it is. I just tried to upload it and it's too big so if you have a way please tell me how and I'll get it to you. Even zipped it's like 1.2 GB.
randyboy99 said:
I wasn't thinking when I first read your post. If you"re looking for the MM Firmware I think I have what you are after. I got it from the S Mobile site, so if the guys don't mind me posting it with this reply here it is. I just tried to upload it and it's too big so if you have a way please tell me how and I'll get it to you. Even zipped it's like 1.2 GB.
Click to expand...
Click to collapse
I actually updated through Samsung Kies. And re-rooted. Though I haven't found an ASOP ROM that works with the MM bootloader
Been off this thread for awhile (you know how life gets in the way) and was wondering if there are any meaningful upgrades to an S4 with 1545VRUGOF1 rooted via Flashfire. with stock.
C
If you want marshmallow, then custom ROMs are the only way to get it.
Which s4 do you have? Isn't flash fire for the i337?
audit13 said:
Which s4 do you have? Isn't flash fire for the i337?
Click to expand...
Click to collapse
SCH-1545
Android 5.0.1
I545VRUGOF1
At the time, Flashfire was the only path to root
Look here for a possible answer: http://forum.xda-developers.com/galaxy-s4-verizon
Any guidance? I have the VRUGOF1 Bootloader and consequently was only able to root with Flashfire. Not sure if there has been any development to allow Marshmallow to be put on this device
wedmiston said:
Any guidance? I have the VRUGOF1 Bootloader and consequently was only able to root with Flashfire. Not sure if there has been any development to allow Marshmallow to be put on this device
Click to expand...
Click to collapse
Yes, there are ROMs for that device. But you can only flash with a custom recovery so you'll have to find one.
Look in the Verizon forum. This forum is for the international version of the s4.
Pwnycorn said:
Yes, there are ROMs for that device. But you can only flash with a custom recovery so you'll have to find one.
Click to expand...
Click to collapse
Maybe I'm not being clear, but I was uder the impression if you have the OF1 Build you can only root with Flashfire, and, you cannot install CWM or TWRP as it will brick your device. I am not looking to add another ROM, I am fine with stock. My goal is to see if there is a way to go from Lollipop to Marshmallow safely given my specific device parameters
wedmiston said:
Maybe I'm not being clear, but I was uder the impression if you have the OF1 Build you can only root with Flashfire, and, you cannot install CWM or TWRP as it will brick your device. I am not looking to add another ROM, I am fine with stock. My goal is to see if there is a way to go from Lollipop to Marshmallow safely given my specific device parameters
Click to expand...
Click to collapse
If you can't install any custom recovery, then there isn't any way you can.
There is no official TouchWiz Marshmallow ROM for the S4, as such, the only way to get marshmallow is through a custom ROM.
A custom ROM can only be flashed via custom recovery.
Ergo, if you can't flash a custom recovery, there is no way to get marshmallow.
The Verizon OF1 bootloader is locked and not exploitable. Only the MDK bootloader had that luxury. You also cannot downgrade to it. If you want to flash a ROM other that stock head to the Verizon Galaxy S4 development forum and read up on SafeStrap and ROMs that can be installed with it. A custom recovery such as TWRP is not able to be installed on your device. Because of that ROMs such as CM, JDC custom ROMs, etc. are out of reach for you.
Pwnycorn said:
If you can't install any custom recovery, then there isn't any way you can.
There is no official TouchWiz Marshmallow ROM for the S4, as such, the only way to get marshmallow is through a custom ROM.
A custom ROM can only be flashed via custom recovery.
Ergo, if you can't flash a custom recovery, there is no way to get marshmallow.
Click to expand...
Click to collapse
Thanks
So to summarize, since I am on the OF1 build and could only root via Flashfire, the bootloader remains locked...consequently I still cannot flash TWRP or CWM, and as you put it, out of luck to get Marshmallow.
However, has anyone successfully used Flashfire and Xposed? I saw it on another thread: https://www.reddit.com/r/AndroidQuestions/comments/406o9w/verizon_galaxy_s4_unlocked_bootlaoder/
but there was no definitive conclusion that it was successful. Anyone have any direct experience with this? Since Safestrap and Flashfire are both custom recoveries installed alongside of your locked bootloader, do either work to get to Marshmallow?
wedmiston said:
Thanks
So to summarize, since I am on the OF1 build and could only root via Flashfire, the bootloader remains locked...consequently I still cannot flash TWRP or CWM, and as you put it, out of luck to get Marshmallow.
However, has anyone successfully used Flashfire and Xposed? I saw it on another thread: https://www.reddit.com/r/AndroidQuestions/comments/406o9w/verizon_galaxy_s4_unlocked_bootlaoder/
but there was no definitive conclusion that it was successful. Anyone have any direct experience with this? Since Safestrap and Flashfire are both custom recoveries installed alongside of your locked bootloader, do either work to get to Marshmallow?
Click to expand...
Click to collapse
You are a little confused. SafeStrap is not a custom recovery so to speak, TWRP is. SafeStrap allows the installation of some mods, etc. on devices with a locked BL. A quick look in the Verizon S4 Android Development forum does not show a MM build that can be installed via SS, only LP builds.
The issue with a locked BL and SS is you cannot install a different kernel which limited what could be installed.
I saw a set of OF1 instructions out on Stang5litre's OP for his ROM. Has this been validated as a stable rom for those of us on OF1?