I have a Canadian SM-N900W8 Note 3, that I wish to revert to complete stock, lollipop. I mostly have been using custom roms, and have recently reverted back to Stock using Kies. I rooted the device using this file.
After the rooting process, the softkeys do not function properly. The 'back' key does not function, and the 'menu' key acts as if I am holding it when I press it. The home key functions normally. Using the S-Pen, pressing on the softkeys, they work as intended. I have tried reflashing(and clearing cache) the stock rom from both kies, and sites like sammobile, but the issue persists.
After reading around, I found out that the file I used is not intended for my Canadian SM-N900W8, but for another model. The intended file for my device does not support lollipop, but only supports 4.4.2. After even more reading, I found the issue was related to the kernel. I flashed idlekernel, and the issue was resolved. The issue is, I want to have everything stock on the device, that includes stock rom, and kernel(or atleast appear stock). Upon booting with idlekernel, 2 messages, "KERNEL IS NOT SEANDROID ENFORCING" and "Set Warranty Bit: kernel" appear. I want to get rid of the messages.
So, my question is, is there a way to either:
1) Fix the softkeys without a custom rom/kernel(essentially reverse the root), or,
2) Get rid of the SEANDROID and warranty messages, while running idlekernel
Thanks!
Flash the latest stock ROM from sammobile.com using Odin.
audit13 said:
Flash the latest stock ROM from sammobile.com using Odin.
Click to expand...
Click to collapse
As said in the OP, I have already tried this, multiple times.
You used kies or Odin? Your post doesn't mention Odin.
The file linked in your post looks like the same file from chainfire's website which does support LP: https://autoroot.chainfire.eu
audit13 said:
You used kies or Odin? Your post doesn't mention Odin.
The file linked in your post looks like the same file from chainfire's website which does support LP: https://autoroot.chainfire.eu
Click to expand...
Click to collapse
I used both, at different attempts. Sorry if I was not clear.
Here is where I read the file incompatibilities
hlteub is for LP, hltevl is for MM.
The Mexican and Canadian Note 3 may be exactly the same model just like it is for the s3.
Did you try smartswitch?
You used the emergency firmware recovery option in kies?
Flashes of the stock ROM were successful in Odin? You performed a factory wipe before booting the stock ROM for the first time? You were flashing the latest LP rom?
Did you try different versions of Odin?
The SEAndroid message cannot be removed if the phone is running a custom recovery.
audit13 said:
hlteub is for LP, hltevl is for MM.
The Mexican and Canadian Note 3 may be exactly the same model just like it is for the s3.
Did you try smartswitch?
You used the emergency firmware recovery option in kies?
Flashes of the stock ROM were successful in Odin? You performed a factory wipe before booting the stock ROM for the first time? You were flashing the latest LP rom?
Did you try different versions of Odin?
The SEAndroid message cannot be removed if the phone is running a custom recovery.
Click to expand...
Click to collapse
If hlteub is for LP, and hltevl is for MM, should I ignore the android versions listed?
If they were the same model, why is there a softkey issue that this post is about?
Yes, I used the emergency recovery option in Kies.
All flashes I did were successful(Softkey issue is present always, even in setup wizard, and throughout the device).
Before installing new firmware, I factory wiped every time.
I have made sure what I flashed is latest, and have confirmed every time through Software Updates in about phone settings.
Smart Switch did nothing that Kies didnt already do.
Other people who have the same issue have said that flashing stock 4.4.2 fixes the issue(but upon upgrading back to 5.0, issue occurs), but I do not want to go back to that version.
Both the ub and vl are for the am-n900w8.
When rooting, it appears that you used a kk root file on an lp rom. Is this correct?
So the soft keys work on kk? If yes, did you flash to lp via Odin or did you run the ota update? Did you try flashing with a pit file?
audit13 said:
Both the ub and vl are for the am-n900w8.
When rooting, it appears that you used a kk root file on an lp rom. Is this correct?
So the soft keys work on kk? If yes, did you flash to lp via Odin or did you run the ota update? Did you try flashing with a pit file?
Click to expand...
Click to collapse
I initially tried the hlteub file(for lp). This is what caused the issue. I later tried the vl file, and nothing different happened. 4.4.2 works, but upon using the OTA update the issue comes back when on lollipop. Same goes for Odin. I have not tried using a PIT file, how would I go about finding one that I will need?
The issue has been resolved!
Here is the solution.
Related
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
exclaimed said:
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
Click to expand...
Click to collapse
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Solved.
The problem was that I didn't flash the stock rom that came with my phone. I flashed that and my phone was restored to its factory settings. However my imei was messed up, it was showing me 0049. I rooted, flashed twrp recovery and used twrp to restore from a backup and I got my imei back along with my data.
I will wait for 4.3 to become flashable and see how it goes then.
hypergamer1231 said:
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Click to expand...
Click to collapse
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
volkantipi said:
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
Click to expand...
Click to collapse
i had this issue on my gs3 , try to move the odin md5 rom file and the odin folder to C: or my documents . maybe one of those directories where u have them right now are too large (odin has issues with long directories)
After I updated my Verizon Galaxy S5 to Lollipop, I tried to flash a lower version official .tar through Odin, and got stuck in a bootloop I can still flash .tars through Odin, but I cannot actually use my phone. How do I get my phone working again? Can I?
waffleman1230 said:
After I updated my Verizon Galaxy S5 to Lollipop, I tried to flash a lower version official .tar through Odin, and got stuck in a bootloop I can still flash .tars through Odin, but I cannot actually use my phone. How do I get my phone working again? Can I?
Click to expand...
Click to collapse
Can you be more specific? What TAR did you flash? Did you flash an older corresponding kernel?
What is your ultimate goal?
Thanks
kprice8 said:
Can you be more specific? What TAR did you flash? Did you flash an older corresponding kernel?
What is your ultimate goal?
Click to expand...
Click to collapse
I figured out how to restore on my own. Turns out I can only restore to NCG. I fixed my own problem. Thanks for helping though!
To any users who visit this form in the future, you can only flash back to NCG after updating to OTA Stock Lollipop.
waffleman1230 said:
I figured out how to restore on my own. Turns out I can only restore to NCG. I fixed my own problem. Thanks for helping though!
To any users who visit this form in the future, you can only flash back to NCG after updating to OTA Stock Lollipop.
Click to expand...
Click to collapse
This is not true. You can restore back to whatever version you want. If you get stuck in a bootloop just hold down the home, volume down and power buttons for about 10 seconds and the phone will boot in to a maintenance menu. From there select factory data reset with the volume down key and then press the home button to execute the option. It should boot normally after that. To avoid this just enter the stock recovery after flashing the tar in Odin and factory data reset from there.
I think I know what you did
waffleman1230 said:
After I updated my Verizon Galaxy S5 to Lollipop, I tried to flash a lower version official .tar through Odin, and got stuck in a bootloop I can still flash .tars through Odin, but I cannot actually use my phone. How do I get my phone working again? Can I?
Click to expand...
Click to collapse
If you downgraded the kernal it won't let you so you have to go back to a lower verison of android or flash the lollipop kernel
I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Which version of TWRP did you use? As far as I know, the latest only supports up to kitkat (4.4)
Maybe this is what causes your problems?
That's what i thought, I'm using the latest one (2.8.6.0). I ask other users in another thread and they said this version is working flawlessly with lollipop...
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Tornade69 said:
I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Click to expand...
Click to collapse
1. Are you sure you installed correct TWRP? The correct one for your device: HERE.
2. Seems that mod for datamobile button doesn't work for your device. Reflash rom, re-root and don't install that mod. Try that update firmware for some days and tell me how it works :highfive:
I used HLTECAN 2.8.6.0. When i was on 4.4.2 NB7, i was using the same file and i had not problems at all. If you re-read my first post, i said my data toggle is working fine now but i needed to re-flash the entire rom without wiping data to get rid of the many apps errors. I guess i need to reflash everything from scratch... Will use another USB wire and another USB port. Maybe it'll help... Or maybe i should try another root method ??? I used CF-Root for SM-n900w8...
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
how do you root n900w8 lollipop rom ?
phberb said:
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Click to expand...
Click to collapse
I want to root my n900w8 too ...tell me intrusions before tell is it safe .
phberb said:
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
Click to expand...
Click to collapse
Hi, can I root N900W8 running N900W8UBU2DOG2 firmware from region TTT with twrp? If not is there any other method I can use to root my device ?
SOLVED! Edit end of the post.
Hello guys i'm having a weird problem,
I had installed the S6 Portc 5.0.1 for a almost a year without any problem but recently i had to go Stock NB1 for testing a SIM CARD Carrier that i was getting "Invalid SIM Card" and it was the same thing, no biggies, perphas that carrier is not compatible with this phone, i tried a couple of guide thinking my phone was not "full" unlocked and ended it up locking the phone instead, lol. Anyway, i managed to unlock it again, so i go ahead and try to update my TW to OK2 and now i can't? Any ROM that i flash trough FlashFire o SafeStrap fails at installing(FF: Hangs at booting, SS: it yells something like symlinks errors). Odin Stock install correctly and Update through to stock recovery like NB1 to NJ4 and so on installs good too.
What do you guys think? I was thinking about to one more time to ODIN Stock NB1 Rooted but with a PIT aswell to see if that fixes my problem but i'm really scared of using the PIT file.
Things i have tried:
* NB1 to NC1: TR>SuperSU>Stock OK2 with FF = Hangs no install
* NB1 to NC1: TR>SuperSU>Stock OK2 with SS = Symlinks errors no install
* ODIN Stock NB1 Root = Good, installs correctly
* OTA's NB1 to OK2 = Good, but no SuperSU, Custom Roms and VERY SLOW Install process.
* OTA's NB1 to OK2 = KingRoot > SS > Custom ROM = Sysmlink error no install
* PIT File + Stock NB1 Stock Rooted ODIN = Good, Tried to install OK2 Keep Root with FF = Hangs, no install.
I'm out of ideas...
EDIT: That's the log from FF attached.
Solution: Yes! Solved! After all the struggle someone posted this interesting post. I tried to install that version and didn't help because the app closed it self everytime i tried to open it... BUT it turns out chainfire put a timebomb to February 01 2017 in this version (v0.53) (You can read it here) So, i changed my time/date before that time and voila! Everything went smooth! Woohoo!. Thank you guys.
So you're on NB1? I would wipe the the phone clean then just take the OTA to the latest firmware and update that way then try installing a ROM.
StoneyJSG said:
So you're on NB1? I would wipe the the phone clean then just take the OTA to the latest firmware and update that way then try installing a ROM.
Click to expand...
Click to collapse
I already tried that sadly, didnt work. i can't install anything that is not stock.
EDIT: Even the OK2 Stock from muzniz through FF doesnt install
Does these phone have a locked bootloader? If it does, only custom roms based on a stock ROM will work afaik.
audit13 said:
Does these phone have a locked bootloader? If it does, only custom roms based on a stock ROM will work afaik.
Click to expand...
Click to collapse
It's a S6 Port based on TW ROM, it's a TW ROM. I tried OK2 with FF/SS that i previously installed a year ago without any problem but know fails, i don't know why.
This one: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-update-to-i337oc3-5-0-1-keeproot-t3075814
and this one: https://forum.xda-developers.com/galaxy-s4-att/development/port-albe95-s6-port-4-6-updt-30-10-15-t3241212
The custom ROM has to be based on a stock att s4 ROM, not a port from another Samsung ROM.
audit13 said:
The custom ROM has to be based on a stock att s4 ROM, not a port from another Samsung ROM.
Click to expand...
Click to collapse
Thank you for the help but:
* I had this ROM in my phone before, it's compatible with I337 Locked Bootloader you can check the description.
* I still can't install the other ROM that's specific for ATT I337 (The OK2 Rooted Keep linked in my previous post). It's like Stock with Root ready.
I understand now.
Could it possibly be a hardware issue? I'm not sure since I don't have an att s4.
Edit: Congratulations on your success and sharing your solution.
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