Database Users

VZ LG GPad 8.3 OTA VK81024A

04/17/2015 Update to this posting; -24A OTA rooted 1st time using Stump after dozens of Brute Force fails on 23A-
Can anyone else confirm Stump Root working for 24A on their own devices?
Original Stump Thread; http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
New OTA software update VK81024A just released this week. From what I've read and VZW's PDF, the only thing that was changed was 4G LTE coverage. In my experience with Verizon, they only release updates for this device to patch root methods and add bloat. This would have been my 3rd update to my GPad (had I accepted) without measurable positive impact. I personally cannot believe that they spent the time and money to fix LTE coverage that, in my experience, had no noticeable issue to begin with.
I would still be waiting for Lollipop on my VZ G3, if I didn't go ahead and root/ROM just last month. With the Lollipop ROM being available to the Korean G3 as early as November of LAST YEAR, my faith in Verizon getting us the updates we want and deserve (I purchased a flagship phone, and a popular tablet) is nonexistent.
Okay, I'm done ranting (for now) about the "Great Satan" that is VZW...the only carrier with good coverage here in my area of NY. Does anyone have any experience with this update? Anyone try rooting it (maybe Stumproot will start working again)? I am tempted to accept it if I could assist the community by doing so. Please tell me your thoughts.

VK810 OTA update from 23A to 24A keeps root
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf

Just got mine this morning. Hadn't been using the tablet for a few days. Would not take OTA. Downloaded the file but kept kicking an error. Ended up hooking it up USB and using the upgrade assistant. Paranoia got the better of me and I "unrooted" first. Brute force stump (climbed to 6800 I think) did the trick just like before. Must say I was disappointed. I had not read what the "upgrade" consisted off but figured since they jumped from 23A to 24A it would be something substantial. I notice some minor cosmetic changes but that's about it. The 4gLTE "Update: or "Upgrade" isn't going to make much difference in my neck of the woods. 3G is about the best you can hope for here in this little town for the time being.

DeanGibson said:
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Click to expand...
Click to collapse
Did the same thing as you, OTA installed and still rooted

This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.

Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
On every Android device, if you want to take an OTA, you have to either be 100% stock, or at least have stock recovery, kernel, bootloader, and other partitions, and only have done minor things with the system partition - not have debloated at all.
Sent from my VK810 4G

Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
If the LG Mobile Support Tool factory restores the whole phone (recovery included) then this may be the best option till someone posts the KDZ with rooted 24A. This was my root method and it may work for you.
After searching through forums for weeks looking for viable root options (rollback and Purplerake or Towelroot, ADB scripting, and all others) and running Stump as often as I remembered (probably 30 times on 23A) I finally have it! I didn't see any up to date threads on rooting the VK810 and all the old threads had too many broken links to actually perform the steps.
Here's how it went down;
1.) Installed the latest LG USB drivers from LG's site ( http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427 ).
2.) Download LG Mobile support tool ( https://docs.google.com/file/d/0B687...p2NlhhalU/edit ).
3.) Run the LG Mobile Support Tool program.
4.) Switched tablet USB mode to "Internet Connection / Ethernet" and after a few moments the LG Tool recognized my VK810.
5.) In LG Tool, click on "Options -> Upgrade Recovery" on the upright corner.
6.) It should start downloading stock firmware right away, if it says "Downloading" but there is no file size or progress, then you need to disable firewall.
7.) After the download, it will start "Upgrading".
8.) When the tablet rebooted I was on the latest VZW VK81024A which shocked me because I thought it was going to put the factory image (JB 4.2), but not to give up hope, I retried Stump...1st time rooted the thing!
9.) Followed Stump Root's directions (Reboot after app tells you to, Install SuperSU APK from market, Uninstall StumpRoot) and poof!
10.) Enjoy rooted 24A KitKat
It is very possible that 24A broke the fix VZW had for 23A (even though many people had success with 23A) and one need only take 24A OTA to Stumproot if they were not able to prior, but this is how my experience went down.
MANY thanks to @roirraW "edor" ehT, @jcase, & @jim380 for producing the threads and software that led to my rooting.

Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!

Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people

Mr.Ultimate said:
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Click to expand...
Click to collapse
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.

clearbox said:
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
Click to expand...
Click to collapse
Battery retrofitting mod is not to get battery charging - is to keep note7 fail-proof, and with this specific unit that Im talking about it is especially the case only after getting it back to firmware that did not have it bricked.
I know about "OEM unlock" feature in dev mode is a must before any software tampering, so thats not an issue. I am aware phone works while on cable, so I should be able to navigate and activate OEM Unlock from dev menu, also I should be able to do straight ODIN flash with firmware that is of an earlier version without any battery cap's , so my question still remains - is there anything in this latest deadly update from samsung that prevents ODIN from flashing anything to the phone, or is it just charging orientated?

we shall all see once it comes across, should be following week, Im actually eager to start working with it. May as well just go ahead and order myself a S7 battery too so less time to waste waiting

I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.

teslapolaris said:
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
Click to expand...
Click to collapse
Vey well, I have some extra ideas too, we shall see

Besides, what are your current plans for your note7?
are you willing to sell it by any chance?

Mr.Ultimate said:
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Click to expand...
Click to collapse
I'm hoping to revive the Note 7 and use it if this is possible at all.
Won't mind selling if there are no other option.

Ok, so got my disabled charging note7, it has about 24% battery remaining and it stays this way if I keep it plugged in on USB or on wireless charger.
I tried flashing TWRP both versions available, both had flashed OK with ODIN however, it still has standard recovery...? wtf...
I remember my S7edge did have very similar behavior, odin would flash TWRP just perfectly fine but when going in to recovery on the phone it still starts in standard recovery, and this would continue until I flashed CF-Autoroot IMG.TAR file , but this time I cannot find it anywhere for note7....
Im thinking trying KingoRoot or OneClickRoot tools but I wanna hold back a little before I launch on those.

Ok good news (so far) , flashed custom kernel via ODIN, worked, but now I figured phone takes charge again while phone is off just on USB, so charge disable mode is within latest kernel update only.
I can still enter my standard recovery and do all I want there (havent tried factory reset yet!)
When powered off from recovery, phone began charging! now I have noticed it went from 23% to 24% and it is showing it is charging, where as before it would vibrate for second when plugged in and then show battery symbol which soon after would go offline and phone would be unresponsive like it is not plugged in - in not charging state. So for now 1:0 me vs note7
EDIT!
YESSS! IT IS CHARGING! NOW @ 26%!!!
Now @ 30% ... ok I should let it charge to 50% and then try perform more firmware DIY

ok, I will confess, I could not wait any longer, thought screw this sh*t, went in to recovery and wiped cache/factory reset, rebooted phone, then witness phone startup OK, welcome wizard started OK with 30% on battery and indicator on shows On-charge thought "yess!!!" , then I get this notification about battery is gonna run out and no longer recharge blah blah blah, but hey , it still charges and now Im at 33%
Yes, latest firmware and custom kernel and VIOLA , note7 is back in the game!
Also got this notification from device security thing asking me to reboot phone to try undo the changes... I guess I will not try just yet out of curiosity will try again to do TWRP reflash, this time it should work
Confirmed, now TWRP flash via ODIN worked liek a charm, so I should root via TWRP now and see if I can disable something in current latest software to disable these notifications playing around now

ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks

Wow, that's great. I've been trying for weeks but unable to get through to anything. Will it be possible to share on how you get to flash TWRP successfully? Thanks
---------- Post added at 12:36 AM ---------- Previous post was at 12:32 AM ----------
Mr.Ultimate said:
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Click to expand...
Click to collapse
I'm don't know about the editing stuff but if you could get TWRP to work, wouldn't it be simpler to flash custom ROM that already have KNOX etc disabled?

I was disabling all kind of random packages just to see what results will I get from doing it all , was expecting to somehow find package that relates to USB/wireless pad power circuit monitoring so I could work on it while maintaining the latest patched firmware but no nagging popups every time phone is powered on or plugged in to USB/wireles pad. Otherwise I observe phone is 99.99% perfect aside from the notification that I have described and security centre prompts warning time to time that device has been modified , click restart to undo-modification, which I actually tried and it undone-nothing, so it is permanently patched this way regardless what you try to do within the phone now.
I am in favor of keeping stock rom and stock appearance of note7 as much as possible.... dont know if it makes much sense but I love the way note7 is... with all functions working as much as possible as close to standard as much as possible, so thats why my reasoning trying to make this latest rom work.
I have few firmwares which were the original ones V.1 and V.2 but not V.3, which is what I have, so even if I install custom rom now, there is no way going back to factory firmware since V.3 full factory rom is nowhere to be found.
I am going to look in to ways on how to extract entire current firmware so I can go and learn a bit and maybe do few ROM builds myself, this is actually exciting now once I got this far.

Able to link me to the custom Kernel that you use?

teslapolaris said:
Able to link me to the custom Kernel that you use?
Click to expand...
Click to collapse
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347

Mr.Ultimate said:
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Click to expand...
Click to collapse
Thanks. It works!!!. Thank you so much.
I managed to flash TWRP and Hydra ROM onto it. Everything works except mobile network. Somehow it is unable to detect the SIM card.
Will fiddle with it further. Hopefully I could get it up and running.
Thanks again.

only downside I see so far with current latest kill firmware and this patched kernel are those nagging notifications regardless battery charging to 100% ok, security center notification about modifications and about restart with attempt undoing them, which obviously will fail anyway anytime, and just now noticed it takes a little more time to activate wifi to show available networks, usually its instant, like 0.1second, and now its like 3-5 second delay once switch is toggled to ON position. Also, found out that when network sim card inserted, now phone prompts for network customization and asks to restart now or later to apply settings changes, and I tried restarting but this keeps coming on anyway, so finding the service package and disabling it solves this issue.
Besides no any network issues here, signal comes on every time I change sim cards around and all connectivity is there with data and all is OK, maybe try different kernel? I tried one with APO ,mine is European exynos SM-N930F model

I tried out Hydra kernel but it didn't work. Then I found this https://forum.xda-developers.com/note-7/how-to/spacex7-rom-kernel-kill-galaxy-note7-t3536693. I flash it and my SIM card works again.

This may help someone
Hi.
As I've read that there are people in the forum with problems after the last update from samsung, I decided to write my experience.
My first Note 7 was the Hong Kong version. It was amazing, because it had an fm radio built in, but of corse I couldn't flsh a costum rom on it, as there as none in the forum. In time, a gave up and send it to samsung, and I am glad for, since by now, I would have a death phone.
Anyway, after 2 months with a s7 edge, I found a person selling is international note 7, cause he would go to Brasil, and was afraid to had it apprehended at the aeroport. So I bought it, even with the limited charge at 60% problem.
First, I tried the Dr. Keatan rom, but the limited battery charge still persisted.
So I tried the TEKXodus rom, and I say its amazing.
My phone now as the batery charging to 100%, and even the shealth works fine, if you don't update it.
If it as an automatic update by google, just downgrad it and is fine.
When I received the samsung notification for the last update, I just needed to be sure that the update function was turn off, that the processes in the background were off too, and, with titanium backup, to freeze 2 "urgent update" apks.
Everything works fine.
So, for those who have problems, I recommend the TEKXodus rom.
Best regards

Zenfone 5 LTE (T00P) Erroneous Behaviour

Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.

Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....

Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.

Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.

U System firmware on BLv5/6 Phone

1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!

Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks

Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.

Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.

lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself

elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.

lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.

elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?

lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.

It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.

lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then

sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.

Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.

I need help, my wifi not work

I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?

Wellfare11 said:
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Click to expand...
Click to collapse
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?

weazie said:
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
Click to expand...
Click to collapse
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?

Wellfare11 said:
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Click to expand...
Click to collapse
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.

weazie said:
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
Click to expand...
Click to collapse
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.

Wellfare11 said:
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Click to expand...
Click to collapse
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.

weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I already tried, I installed the rom corresponding to the model of the cell phone and the wifi still does not work, the base band is still unknown, I also checked if the sim card was correctly placed, and everything is fine

weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp

Wellfare11 said:
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Click to expand...
Click to collapse
Great that you have an idea. ?
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea. ?

weazie said:
Great that you have an idea.
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea.
Click to expand...
Click to collapse
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund

Wellfare11 said:
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Click to expand...
Click to collapse
Does the phone ask for a pin code at any point?

weazie said:
Does the phone ask for a pin code at any point?
Click to expand...
Click to collapse
does not request any code at any time

Wellfare11 said:
does not request any code at any time
Click to expand...
Click to collapse
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. ?*

weazie said:
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. *
Click to expand...
Click to collapse
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work

Wellfare11 said:
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Click to expand...
Click to collapse
Hello, colud you solve the problem? Because I am havig a very similar one...

Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.

I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.

bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
I have the exact same problem, I wasn't able to repair it so I sent it to service and tomorrow they will try to fix it for $35. The problem with goign back to previous versions is that you loose the IMEI and MAC . The problem with the pie version I believe is the baseband. If the service is able to fix it I will post the solution here for you to fix it .

bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
caradobeco said:
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
Click to expand...
Click to collapse
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you

juampapo546 said:
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
Click to expand...
Click to collapse
I am still working on this, I actually did this to a work phone (I had permission to root/unroot). Something that has helped me so far is just getting familiar with the whole flashing process - https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/. I think from this article the problem lies in the modem/radio rom. That *should* be the only thing you need to flash on. However, I have noticed with a lot of roms on here, a modem rom is not included on the stock firmware. But that needs to match well to your phone from what I understand. I have tried a few modem roms already, unfortunately, but no luck.