I have a Galaxy S5 (Verizon) SM-G900V that's running stock rooted Lollipop. Safestrap is on here, but yes, the bootloader is locked. Other than going to Marshmallow (and losing root), are there any custom ROMs (I'm looking for speed and stability) that this phone can take? Or am I stuck with stock, which means I'm stuck with Lollipop if I want to stay rooted?
My choice is this one without root for CID11 or full-featured systemless devbase for CID15.
Thank you. I assume I use safestrap to install on my rooted stock CID 11, but on this new one without root won't be able to restore apps from Titanium. Are there any other alternatives an 11 can use and keep root, and if I try one can but change my mind can I restore a backup in safestrap to get back to rooted stock?
bbsc said:
My choice is this one without root for CID11 or full-featured systemless devbase for CID15.
Click to expand...
Click to collapse
androidman807 said:
1) is that right that it's possible to safestrap a different ROM with my locked bootloader?
2) If yes, how can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
3) if I have a SS backup of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL? Or could I just re-install the stock LL image?
4) can I/should I update the modem in this process, or does the locked bootloader prevent that?
Click to expand...
Click to collapse
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Thanks. I've tried casting a broader net, unsure if my problem was Verizon-specific or not. Turns out, it's even more specific than that, as at least some 900Vs have unlocked bootloaders and some (mine) don't.
As I look back over my journey, you were there from the beginning when I was trying to upgrade from 4.4.2 to my current Lollipop and keeping root. Following the steps of the amazing @jrkruse led to different problems, which still persist. There seems no way to fix that, from which I conclude the jrkruse stock ROM and this phone don't get along. Hence, the idea to try a different ROM other than this LL. It seems that my locked bootloader has me on stuck on this particular stock ROM if I want to keep root. There is no list of other ROMs I can put on this CID11, and I'm not sophisticated enough to know which I can try and Safestrap back safely if things aren't wonderful. This has me doing a hot reboot every day or two when I see wifi can't get DNS, but I don't see any other option other than buying a newer Galaxy with a microSD card and an unlocked bootloader (maybe the S8?). Regardless, this sums up my journey, I've learned a lot along the way, and both you and @KazuDante were extremely helpful and earned my Thanks button many many times. Thanks again.
bbsc said:
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse
bbsc said:
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.
androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.
Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
bbsc said:
androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.
Click to expand...
Click to collapse
androidman807 said:
Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
Click to expand...
Click to collapse
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Titanium is a big reason why I want to keep root. So BOK3 and DQI2 are ones I can root and still return to PB1. Thanks, I'll start looking for them and their rooting procedures.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse
androidman807 said:
So BOK3 and DQI2 are ones I can root and still return to PB1.
Click to expand...
Click to collapse
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.
androidman807 said:
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.
Click to expand...
Click to collapse
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.
Thank you. I was hot on the modem idea when I was going to switch to Lineage or something else as a natural step. But since it's tied to 4G and cell service and not my sporadic DNS-on-wifi issue, I'm not sure I see the benefit, but then I could be wrong. I figure a different ROM will have different drivers for the wifi radio and solve things. At least that's been my hope all along.
KazuDante said:
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.
Click to expand...
Click to collapse
Thank you! I will likely flash this with Odin over the weekend (or with SafeStrap?). I've found QI2 here, the first of the two links. Just to be prepared, what steps will I take to rooting this new ROM?
bbsc said:
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse
Where can I find BOK3, and how do I root it after installation if I don't have TWRP (but only safestrap)?
Edit: here's OK3 with steps on how to root it, but they're quite scary and possibly outdated.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse
Thanks again - I flashed with Odin the DQI2 I found but didn't know how to root it (Safestrap erased and no TWRP). Maybe the answer is the same as the other post I just replied to. That's obviously a blind spot I have that has me stuck on PB1 - I don't know how to root anything else on this CID 11.
bbsc said:
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse
Related
Hi folks. I don't know what I'm doing wrong here. I know I am bound to safestrap at this point but NONE of the safestrap ROMs work for me. I don know what the deal is. I've done probably 5-10 other phones with CWM or TWRP and I never really have too much trouble. I cannot for the life of me get any ROMs to work other than flashing the tar build of the Sammy Stock ROM via Odin. That's the only thing that I can get working. If anyone would help me troubleshoot I would be really grateful. Here is what I have been doing:
1. First ROM was stock Sammy 4.4.4 (i think). whatever the latest that there was for Sammy stock OTA update.
2. Went through days of nonsense after a VZ to ATT phone flash on accident.
3. I now I have Safestrap working when I want it to.
4. Basically my process starts with flashing stock Sammy Rootable 4.4 with Odin
5. Next I root with towl and install safestrap.
6. Then I download and copy ROMs to the SD card.
I do notice that when I install Safestrap, click Install Recovery, it confirms but the second part of the app says "not active". Is that right?
fuzzyreets said:
Hi folks. I don't know what I'm doing wrong here. I know I am bound to safestrap at this point but NONE of the safestrap ROMs work for me. I don know what the deal is. I've done probably 5-10 other phones with CWM or TWRP and I never really have too much trouble. I cannot for the life of me get any ROMs to work other than flashing the tar build of the Sammy Stock ROM via Odin. That's the only thing that I can get working. If anyone would help me troubleshoot I would be really grateful. Here is what I have been doing:
1. First ROM was stock Sammy 4.4.4 (i think). whatever the latest that there was for Sammy stock OTA update.
2. Went through days of nonsense after a VZ to ATT phone flash on accident.
3. I now I have Safestrap working when I want it to.
4. Basically my process starts with flashing stock Sammy Rootable 4.4 with Odin
5. Next I root with towl and install safestrap.
6. Then I download and copy ROMs to the SD card.
I do notice that when I install Safestrap, click Install Recovery, it confirms but the second part of the app says "not active". Is that right?
Click to expand...
Click to collapse
For every ROM i have flashed through Safestrap, I have always had to flash it to the 'stock' slot. Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel) root it, then install safestrap, then reboot into safestrap, wipe everything except sd, and flash the Safestrap compatible TW-based ROM you want from the zip on your extsd into the stock-slot. Then, while still in Safestrap, flash Venom's KitKat magic AT&T modules. At least, that's how I have done it. Follow the Install Instructions section of the [Index] thread: http://forum.xda-developers.com/showthread.php?t=2616221
Once you root and get Safestrap installed, you should only use Odin in case you screw up and softbrick and need to get back to your base stock ROM to start the process over again.
Good luck.
manstable said:
For every ROM i have flashed through Safestrap, I have always had to flash it to the 'stock' slot. Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel) root it, then install safestrap, then reboot into safestrap, wipe everything except sd, and flash the Safestrap compatible TW-based ROM you want from the zip on your extsd into the stock-slot. Then, while still in Safestrap, flash Venom's KitKat magic AT&T modules. At least, that's how I have done it. Follow the Install Instructions section of the [Index] thread: http://forum.xda-developers.com/showthread.php?t=2616221
Once you root and get Safestrap installed, you should only use Odin in case you screw up and softbrick and need to get back to your base stock ROM to start the process over again.
Good luck.
Click to expand...
Click to collapse
Couple questions about what you wrote....
"Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel)"
This is something I have been trying to understand. What is MK2 vs what is NB1? I don't understand these pieces of this rooting puzzle. In my mind currently I have the Boot puzzle piece which is safestrap at this point and the ROM which is WHATEVER. No?
"flash the Safestrap compatible TW-based ROM"
Does it have to be a TW ROM? I'm doing this to try to get away from Touchwiz.
Thank you VERY much for your reply. I appreciate your time in explaining. Outside of flashing the ATT modules, I think I have been doing the other procedure the same.
fuzzyreets said:
Couple questions about what you wrote....
"Once you Odin to stock (or for me on NB1, I actually odin to MK2 but retain my NB1 kernel)"
This is something I have been trying to understand. What is MK2 vs what is NB1? I don't understand these pieces of this rooting puzzle. In my mind currently I have the Boot puzzle piece which is safestrap at this point and the ROM which is WHATEVER. No?
"flash the Safestrap compatible TW-based ROM"
Does it have to be a TW ROM? I'm doing this to try to get away from Touchwiz.
Thank you VERY much for your reply. I appreciate your time in explaining. Outside of flashing the ATT modules, I think I have been doing the other procedure the same.
Click to expand...
Click to collapse
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.
manstable said:
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.
Click to expand...
Click to collapse
This is invaluable information. I can't thank you enough. I would hit the THANKS button 100 times if I could for you. You totally saved me here and put the pieces together for me for the most part. I don't completely understand it but I have things working now. Thank you VERY much.
manstable said:
MK2, MF3, NB1, NC1, etc., are all different versions (or builds) of the baseband software our ROMs run on. A kernel (as I understand it at least) is the underlying software that sits below the ROM and is intermediary software that connects the top-most software we interact with (the ROM) to actually control our phone's hardware -- the IR blaster, wifi chips, touch screen capacitive sensors, etc. When playing around with ROMs, you need to know what kernel you are on (i think it's unchangeable for phones with locked bootloaders like ours) -- but more importantly what BASEBAND you are on. The baseband (and possibly the kernel?) updates from taking OTA updates direct from AT&T/Samsung. You can only flash ROMs that are compatible with the baseband you have upgraded too -- which you can see on your "About Device" page in settings. For example, I am running Goldeneye v34 which is a XXUGNE8 build, on my AT&T SGH-i337 that is on a baseband of I337UCUNB1.
Edit: Unfortunately, you have to flash TW-based ROMs...due to our bootloaders being locked (and us being stuck on the stock-kernel). Safestrap is the only way we can flash ROMs with firmware that is MF3 or newer (several several builds ago) but only works with TW-based ROMs.
Please click THANKS if you found this helpful...trying to get posting privileges in dev forums that i've been lurking in for way too long.
Click to expand...
Click to collapse
I saw the issue is resolved. Good work. Just to clarify, though... The baseband in the "about device" page is actually your modem. Most of time the modem will match the kernel and bootloader, but it's not always the case...
1. MK2 base users that use the magic tool to flash kitkat roms, end up flashing the mld modem in odin (part of the magic tool files). After they flash a rom, their baseband will show up as mld.
2. You can flash any modem in safestrap and you will see your baseband change... http://forum.xda-developers.com/showthread.php?t=2496517
Unless you are on 100% stock where you know the base matches the modem, the best way to verify your base can be found in post 4 here... http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
I usually do this for the Note 3 I have, and it comes in really useful for devs, those running other roms, etc, that just want to upgrade the modem/wifi, bootloader, and CSC without messing with everything else. It's also handy to replace the stock kernel if you need it for whatever reason (towelroot anyone? ). Since I recently picked up a Tab Pro 8.4 from swappa, I did this for mine to do the upgrade, and thought I'd be nice and go ahead and share the extracted parts for everyone else to enjoy.
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new T320 1NK1 Firmware. In desktop Odin 3.09, Kernel and recovery would go in AP. Modem + NON-HLOS goes in CP, Bootloader in BL. If you flash the bootloader separately, make sure to tick the box that says bootloader update.
Bootloader:
CSC: http://www.mediafire.com/download/dje1u61d8pk8dou
Kernel: http://www.mediafire.com/download/bi2jsdcub9c9k82
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/3x5bela3la8mllh
modem.bin: http://www.mediafire.com/download/oatak8vgg5vdlu5
NON-HLOS.bin: http://www.mediafire.com/download/xuaar11efato1j7
Recovery: http://www.mediafire.com/download/206e1b2g1uact6s
Full Stock Image T320UEU1ANK1-T320XAR1ANK1: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5
If you have trouble getting the bootloader and/or Modem to stick, install "Triangle Away" by @Chainfire and follow the directions to reset your counter (even if it says zero), then boot into download mode, and re-flash them with Odin and they should stick (WARNING: Triangle Away WILL TRIP KNOX).
NOTE: It has also been noted by several people that booting directly into download mode from a powered-off device and flashing the BL/Modems will make them stick as well.
To verify, you can download "Phone Info - Samsung" and make sure that all applicable items say either T320UEU1ANK1 or T320XAR1ANK1 (Bootloader,, PDA and CSC). NOTE: Not all functions of this app work for our tablets, but most do.
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Enjoy, and as always, slap that Thanks button!
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Deca4 said:
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Click to expand...
Click to collapse
You can use the kernel in my post.
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T
Thank you!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
bigmike35 said:
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
Click to expand...
Click to collapse
My Tab Pro 8.4 (Wifi) shipped with the latest firmware already installed. I didn't want to use CF Auto-Root because it trips the Knox flag, so I flashed this kernel (http://forum.xda-developers.com/showthread.php?t=2786800) and then was able to use TowelRoot, which doesn't trip Knox.
Nice job. I upgraded using the full image, downgraded the kernel, rooted my T320, restored your kernel. Very simple and all worked great. Thanks for this.
@toastido Could you give me a link to Kernel BNI1 (Portuguese version) plz?
Thanks in advance.
I just got an A300FU, and would like to know a few details about how to root it, basically: do I have to root it first, and then update it to Lollipop?
I take it, while on 4.4.4, CF Auto-Root should work just fine, but what after that? Can I use Samsung's software update app to download Lollipop? If not, does it have to be flashed with Odin?
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
The way i prefer to root is through a Customer Recovery. Flashing preferably TWRP, will allow you to flash the latest SuperSU package, or it will ask you to root with any older version from it's ability to detect root access.
I am not aware nor informed of any root method keeping knox 0x0 as i never bothered with it.
PlutoDelic said:
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
The way i prefer to root is through a Customer Recovery. Flashing preferably TWRP, will allow you to flash the latest SuperSU package, or it will ask you to root with any older version from it's ability to detect root access.
I am not aware nor informed of any root method keeping knox 0x0 as i never bothered with it.
Click to expand...
Click to collapse
Yeah, I know that, but what I'm asking is, whether to root first, while I'm on KitKat, and then update to Lollipop (and if that's possible after rooting), or root it after updating to Lollipop.
King-V said:
Yeah, I know that, but what I'm asking is, whether to root first, while I'm on KitKat, and then update to Lollipop (and if that's possible after rooting), or root it after updating to Lollipop.
Click to expand...
Click to collapse
I suppose you dont give a damn about Knox? Good.
You should flash Lollipop first, as it features a newer Modem and Bootloader, unfortunately we dont know the changes, but they can add to things like better battery life, better signal.
so, download any latest Stock ROM, if you are branded (Carrier) then choose a branded rom as it has a hidden partition which doesnt match with the Unbranded ones. You can tell if it's branded as sites that keep firmware information put the Carrier on brackets, look here i.e for A300FU, just hover over the Region value.
The latest Unbranded firmware is A300FUXXU1BOL3 CYV (Cyprus), there are loads of Branded OL3 as well.
After you do all this, flash TWRP, flash SuperSU. and your set.
PlutoDelic said:
I suppose you dont give a damn about Knox? Good.
You should flash Lollipop first, as it features a newer Modem and Bootloader, unfortunately we dont know the changes, but they can add to things like better battery life, better signal.
so, download any latest Stock ROM, if you are branded (Carrier) then choose a branded rom as it has a hidden partition which doesnt match with the Unbranded ones. You can tell if it's branded as sites that keep firmware information put the Carrier on brackets, look here i.e for A300FU, just hover over the Region value.
The latest Unbranded firmware is A300FUXXU1BOL3 CYV (Cyprus), there are loads of Branded OL3 as well.
After you do all this, flash TWRP, flash SuperSU. and your set.
Click to expand...
Click to collapse
Nah, Knox doesn't really matter all that much.
So, I have my A3, currently on 4.4.4. I go download the firmware you linked, flash it using Odin, and then flash TWRP, through Odin as well.
I don't know. I feel like there's something I'm missing... don't I have to flash CF Auto-root before SuperSU?
Also, sorry for bothering, but are there any other place to download the firmwares? The one in the link originally said it would take ~5 hours, but then failed twice already.
King-V said:
Nah, Knox doesn't really matter all that much.
So, I have my A3, currently on 4.4.4. I go download the firmware you linked, flash it using Odin, and then flash TWRP, through Odin as well.
Click to expand...
Click to collapse
Exactly, the Stock ROM will update the overall stuff, the TWRP will replace the Recovery. The TWRP is actually optional, it's up to you if you want a custom recovery, personally it makes things easier.
King-V said:
I don't know. I feel like there's something I'm missing... don't I have to flash CF Auto-root before SuperSU?
Click to expand...
Click to collapse
CF Auto-Root, it's the only (easy) way to have root without touching the Recovery. If you have TWRP, no need to go for CF Auto-Root, instead you just flash the SuperSU.
Just so you know, CF Auto-Root and SuperSU are made by the same person, and CF Auto-Root includes SuperSU, thats why you dont need it if you have a custom recovery.
King-V said:
Also, sorry for bothering, but are there any other place to download the firmwares? The one in the link originally said it would take ~5 hours, but then failed twice already.
Click to expand...
Click to collapse
you can use sammobile, it offers a bit extra speed if you register.
Kingroot works on lolipop (5.02) without triggering knox. I successfully rooted my phone (simple: I downloaded apk, install, root).
Personally, i'd trust rooting only what contains SuperSU.
Kingo has its own manager and desktop software which make it very uncomfortable to use.
Fairly though, it's the only non-knox flipping root method
PlutoDelic said:
There are numerous ways. If you are rooted, and lose know fuse warranty, then you might as well do a proper job.
Click to expand...
Click to collapse
I know thread is old, but I am trying to find a walkthrough to help a buddy with his A300FU...
Where do I find an updated guide to root, TWRP and find a basic slim rom?
phaleg said:
I know thread is old, but I am trying to find a walkthrough to help a buddy with his A300FU...
Where do I find an updated guide to root, TWRP and find a basic slim rom?
Click to expand...
Click to collapse
The roms are on the Original Dev and Developer boards. That's exactly where you'll find TWRP too (just search A300FU and A3FU on these boards and you'll have a view of your options).
And flash SuperSU in twrp for root.
PlutoDelic said:
The roms are on the Original Dev and Developer boards. That's exactly where you'll find TWRP too (just search A300FU and A3FU on these boards and you'll have a view of your options).
And flash SuperSU in twrp for root.
Click to expand...
Click to collapse
Hi!
Would you link me these please?
I find only an older version of these recovery 2.8.x
phaleg said:
Hi!
Would you link me these please?
I find only an older version of these recovery 2.8.x
Click to expand...
Click to collapse
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a72015-sm-a700f-t3362283
PlutoDelic said:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a72015-sm-a700f-t3362283
Click to expand...
Click to collapse
Thanks!
So I understand I have to flash that *.tar recovery file using Odin, after rooting, correct?
Would you use Odin to root or Kingo PC version?
phaleg said:
Thanks!
So I understand I have to flash that *.tar recovery file using Odin, after rooting, correct?
Would you use Odin to root or Kingo PC version?
Click to expand...
Click to collapse
I dont like/trust any other rooting method except SuperSU.
1. Flash TWRP.tar with odin, make sure you untick auto-reboot on odin, as it will reflash the stock recovery.
2. Flash SuperSU.zip in TWRP.
DONE.
PlutoDelic said:
I dont like/trust any other rooting method except SuperSU.
1. Flash TWRP.tar with odin, make sure you untick auto-reboot on odin, as it will reflash the stock recovery.
2. Flash SuperSU.zip in TWRP.
DONE.
Click to expand...
Click to collapse
Can I reboot to system after that?
How can I reboot to recovery with buttons?
When should I flash a basic ROM and gapps?
Which one would you suggest, considering that she does not expect additional weird functions but just a rom (at least 5.1) without bloatware and other heavy stuff to load
ROM and gapps are up to you, there are a few of AOSP options you can choose.
To flash TWRP through odin, use vol down + home + power
To boot to recovery (twrp), vol up + home + power.
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
I'll start off explaining my situation and then explain what myself and lots of other people seem to be confused about.
I was on Kikat last week and then upgraded to PB1 and unlocked my bootloader using method 1 by jkruse. Everything went fine and I was running stang5litre. I wanted to try Phoenix but I could not find instructions on how to get to PD1 first. I then saw that I could go right from PB1 to CM 13. I booted to recovery, wiped, installed CM and gApps, and everything went fine also.
I know my baseband is still PB1 but I'm guessing since I'm on CM now that I'm not actually on any official build right? (PD1, PF4, etc). So with that being said I don't understand how to go to other ROMs or back to LP.
I tried going back to recovery, wiping, and installing stang5litre again but my phone would not boot past the Samsung screen. Guessing something with the kernel? Soni flashed back to CM for now and I've been reading like crazy on here.
I'm trying to understand the process for switching between LP and MM. I found instructions by jkruse in the Phoenix forum (post #68) which talk about upgrading/downgrading bootloader but they are not clear and also they specifically say "Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom". Well I'm not on a 5.0 TW ROM now.
I've seen countless posts in multiple forums showing a lot of other people are confused about this stuff. If I had all the details (clear instructions, file links, etc) I would glady make a very easy to follow guide and explanation of everything. I'm good at writing out stuff like that and making it very easy to understand.
Some things I want to understand so I can make a guide..
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
-How to go from CM to stock rooted PD1
-How to go from CM back to stock rooted PB1
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Any help/explanation would be greatly appreciated. Some of this info might be scattered across different forums but I think a guide specifically for switching between all the builds would be a huge help to a lot of people. Please link files also. I will definitely give credit to all who help if I do get the info needed to make it!! Thanks!
Bumppp
If you need help finding these things maybe you shouldn't be making a guide....
Sandman-007 said:
If you need help finding these things maybe you shouldn't be making a guide....
Click to expand...
Click to collapse
Please dont bother commenting pointless stuff. I read these forums every day and see lots of people looking for clarification for how to go back and forth between MM and LP. Mainly how to go back to LP. You will also find threads and posts with people giving different instructions. Some say just flash the PD1 rooted stock in recovery.. some say that won't downgrade the bootloader..
Some say to follow Jkruses guide in the second post of the bootloader unlock thread. The part about going back and forth between bootloader's.. which is a way more complicated method. There is different information all over
I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Click to expand...
Click to collapse
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
Click to expand...
Click to collapse
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Click to expand...
Click to collapse
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Click to expand...
Click to collapse
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.
ruokuo said:
I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.
Click to expand...
Click to collapse
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.
aholeinthewor1d said:
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.
Click to expand...
Click to collapse
The SS/FF method was old instruction. People sometimes has hit or miss. I think Jkruse found out the cause (my guess is the binary status). Please go for the latest one, which is at the OP of the link I gave you.
If you still have the unlocked bootloader, you can always odin the twrp image (I recommend v3.0.0.0).
If you happened lost the unlocked bootloader status, then I would recommend you to odin the original PB1 tar, root, unlock bootloader, odin twrp, then follow the 2nd part of the OP.
I hope this helps.