WOW. I just used the Factory binary and was playing with stuff... On my Note 8 US. In factory Binary, enable Dev mode the usual way, then in Developer Options the OEM unlock option was there and I flipped it!!! This has been unreachable until now on US models...am I right???
Also when I back arrow out of D.O., and go back in the OEM Toggle always has turned itself off...
Woot! Kept messing with it and got the popup saying turning it on could blow up my phone blah blah... now ehen i exit dev options and reenter it stays on!!!!!!!!!!!!!!!!
work in progress to be sure. Any devs reading please advise. !!!!!
I took screenshots and will try to pull them from my SD...but powershell has been saying my phone is unreachable when i try and do "adb reboot bootloader"... not sure if I fcked something up on not... Any thoughts would be appreciated!
Had anyone ever used the settings in Factory binary to try and enable OEM before?
OptimuSlime said:
Had anyone ever used the settings in Factory binary to try and enable OEM before?
Click to expand...
Click to collapse
Never tried, what exactly did you do? can you list the steps
I used the k2(?) Factory binary for Note 8 us. I clicked the 9 dots in the upper left corner. It opened up apps. I clicked settings in the upper right corner of that screen. Then turned on dev options clicking build number...
Inside dev options in settings in factory binary...
Was OEM UNLOCK. I clicked it on and off and one of the times it gave me the security popup, after that it "stuck" when I exited the settings menu.
kilayo said:
Never tried, what exactly did you do? can you list the steps
Click to expand...
Click to collapse
Can you send the steps you took to get the oem unlock option there..
See above for OEM steps. AGAIN this was in Factory Binary, the COMBINATION file I used was made from the one BlueFox hosts on AFH... "N950USQU2AQK2" I believe it is missing Meta-data due to my phone having had the IMEI repaired and this is the way the repair guy left it on my PC. When I write new FW to the phone it obviously is then missing the OEM Option, so we need a rom that would support Snapdragon, and have the OEM Option pulled from the combination file I think.
cdnsnOw said:
Can you send the steps you took to get the oem unlock option there..
Click to expand...
Click to collapse
Upload this if you can or send link
The regular N950U1SQU2AQK2 combination file should work. It's hosted on AFH by BlueFox (I think there is a number after his name) Just search "carrier switching note 8" to find him, and the Combo file is in the top of the thread.
https://androidfilehost.com/?fid=962021903579496616
That should be the one I used. I doubt removing the metadata had any effect, pretty sure it'll work as is for you. Metadata just messes with my new IMEI lol so I have to remove it from AP's and Combos to get them to work for my phone, but if you have original IMEI it doesn't affect you.
Just so you know. We have known about it for awhile. It doesnt unlock he bootloader. all it does is flip a 1 to a 0 or vice versa in the props. its useless.
me2151 said:
Just so you know. We have known about it for awhile. It doesnt unlock he bootloader. all it does is flip a 1 to a 0 or vice versa in the props. its useless.
Click to expand...
Click to collapse
Well there goes my hopes and dreams
again sad mode.
Now i feel like what is OEM BOOTLOADER...have we ever seen it :crying:
me2151 said:
Just so you know. We have known about it for awhile. It doesnt unlock he bootloader. all it does is flip a 1 to a 0 or vice versa in the props. its useless.
Click to expand...
Click to collapse
Ya I heard
Hey what is the build.prop line that is changed?
I mean in an Exynos Note 8 or S8
OptimuSlime said:
https://androidfilehost.com/?fid=962021903579496616
That should be the one I used. I doubt removing the metadata had any effect, pretty sure it'll work as is for you. Metadata just messes with my new IMEI lol so I have to remove it from AP's and Combos to get them to work for my phone, but if you have original IMEI it doesn't affect you.
Click to expand...
Click to collapse
This is unrooted correct?
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
OptimuSlime said:
Ya I heard
Hey what is the build.prop line that is changed?
I mean in an Exynos Note 8 or S8
Click to expand...
Click to collapse
there is a default.prop says oem_unock_supported=1 or =0
I believe it changes it
default.prop is inside root directory.
not in system
N950USQU3CRC2 por favor ocupo el combination se les agradece de antemano
rodsola said:
N950USQU3CRC2 por favor ocupo el combination se les agradece de antemano
Click to expand...
Click to collapse
Please post in English too please, you can use Google translate if needed.
The enable oem unlock toggle does more than change the build.prop.
If you pull the persistence partition you will find that the first 2 lines are changed by the switch.
Ive been doing some testing with my note 8 and my Galaxy Tab E.
The tab is qualcomm chip and allows unlocking the bootloader.
May already have a way to get the bootloader unlocked. I didnt know about the setting in the build.prop.
That setting along with writing the unlocked persistence partition my do the trick.
Beyond that my past experience tells me that there is at least 1 more partition on the device that is never written to by any firmware update that will have some bytes changed for unlocking.
If someone with the non qualcomm Note 8 can do a dd copy of theese partitions with the phone both locked and unlocked it might give me the answer. MY FIRST GUESS is the MISC Partition.
The idea here is to compare all these partitions in binary hex format to see who changes for unlock.
Theese are the partitions for the N950U
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 steady -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 storsec -> /dev/block/sdd20
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 sec -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 nad_refer -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 omr -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 pad -> /dev/block/sdd22
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 param -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 persist -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 persistent -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 misc -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 fsc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 fsg -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 devcfg -> /dev/block/sdd19
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 devinfo -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 dpo -> /dev/block/sdd17
lrwxrwxrwx 1 root root 16 2017-12-11 10:21 dqmdbg -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2017-12-11 10:21 dsp -> /dev/block/sdd7
Get me thoose form the non us device and were on our way.
In adb shell do
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
ls -al
That will match your partition blocks to the partition names.
Thanks for the help.
Wish I could help. For anyone who doesn't know @BigCountry907 has unlocked other bootloaders so please help him out.
dushotgun said:
Wish I could help. For anyone who doesn't know @BigCountry907 has unlocked other bootloaders so please help him out.
Click to expand...
Click to collapse
Contact the samfail team, they for sure will assist you!
Most likely they didn't overlook any changes from oem unlocking but there is a spark of hope.
On the snapdragon models the bootloader unlock is done in the STEADY partition(yes im talking about U/U1/W models but the HK models also use STEADY)
I know exactly how to unlock the snapdragon bootloaders however its almost impossible to forge the ticket.
Related
I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
aequitas3 said:
I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yes I have tried flashing the Canadian V11A kdz and no luck with that one either. The touch screen is still mirrored, but not entirely sure what the firmware version is, if it stays 12 or changes.
Sent from my LG-P769 using xda app-developers app
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
No LG logo is normal and not inversely colored. Although I didn't think to wiping system with fastboot and then flashing the kdz, I'll give that a try in a little.
Sent from my LG-P769 using xda app-developers app
Lelus said:
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
Click to expand...
Click to collapse
Yeah i think u r right about the updater not updating the touch screen firmware...because i get to see several parameters errors reoccurring while flashing any kdz....and if there was any way to reflash the touchscreen firmware then maybe the problem would resolve....i think the TS firmware in the v10E is different (if any user could confirm) then is it possible to downgrade to that firmware...as it seems that flashing the Indian kdz has downgraded the TS firmware....sorry had to get my doubts cleared in front of the experts
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Tablechair said:
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
Click to expand...
Click to collapse
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
Lelus said:
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Click to expand...
Click to collapse
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
PROgenitor said:
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
Click to expand...
Click to collapse
Unfortunately not... a kernel would have to have touch screen firmware v13 or higher and p769v10g is 6 which is probably latest.
http://forum.xda-developers.com/showpost.php?p=39268215&postcount=24
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
I'll give it a try after testing the wiping of /system via flashboot doesn't do any good lol
Sent from my LG-P769 using xda app-developers app
Anyone give a try? I would but im kinda poor and this is my only phone.
Lelus said:
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
Click to expand...
Click to collapse
I just saw the 19.bin file and as told by you, its 10kilobytes of just Null characters (Hex Code 00).
Are you replacing file with name "firmware" and size only 89bytes with a file of 10000bytes? The file "firmware" actually is a text file which holds only firmware version number. Will this work? Anyone tried?
Doesnt KDZ flashing replaces this file too?
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
there isn't module for the touch screen, it's statically compiled into kernel
Lelus said:
there isn't module for the touch screen, it's statically compiled into kernel
Click to expand...
Click to collapse
I see.
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
C:\Root\stuff>adb shell
[email protected]:/ $ su -
su -
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 67 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ # uname -a
uname -a
sh: uname: not found
127|[email protected]:/ # ls -la /sys/devices/omapdss/display0/driver
ls -la /sys/devices/omapdss/display0/driver
lrwxrwxrwx root root 2013-03-12 13:22 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/ #
Click to expand...
Click to collapse
PROgenitor said:
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
Click to expand...
Click to collapse
Does this mean, you have not yet tried LELUS method alongwith direct flashing of P769V10G or P769V11A?
If not yet done, try that with HARDRESET to phone before and after the flashing with Lelus root. :good: Good luck.
Could someone with a phone other then p769 check their touchscreen firmware version.
Lelus said:
Could someone with a phone other then p769 check their touchscreen firmware version.
Click to expand...
Click to collapse
P765 V10G India , Touch Firmware Version: 12.
EDIT:
3845#*765# ---> H/W Device Test --->Touch Test --->Touch Firmware Version : 12
P765: IPS Display
P769: Corning Gorilla Glass
I've done a stupid thing. I have tried to find a post that would help me out of this but haven't made any headway.
I rooted and unlocked my Apollo, installed TWRP and slim. Everything was working for a while. Long story short, I did a stupid thing and instead of factory resetting it, I hit format data. I should know better.
Now, no matter what I do, I am stuck in a bootloop at the gray kindle fire screen. I can access TWRP, but flashing a ROM does me no good whatsoever. I reflashed TWRP, but that didn't do anything either.
I am good at following the guides that you all post, and have rooted many phones and tablets based on all your hard work, but I'm over my head here. Can someone help get me back to Kansas?
Thanks in advance.
You have an unlocked bootloader, you have a working recovery with ADB&MTP: you can do anything you want.
I don't know which partitions have you formatted and what is the filesystem there.
Load the recovery, start the adb shell, check the state of your partition table with parted&mke2fs.
Normal situation for the KFAPWI 16:
Code:
Model: MMC MAG2GC (sd/mmc)
Disk /dev/block/mmcblk0: 15634MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 0.52MB sbl1
3 135MB 135MB 0.03MB dbi
4 201MB 201MB 0.03MB DDR
5 268MB 268MB 0.00MB misc
6 268MB 271MB 2.10MB aboot
7 271MB 271MB 0.51MB rpm
8 336MB 346MB 10.5MB boot
9 403MB 403MB 0.51MB tz
10 403MB 404MB 1.05MB pad
11 404MB 406MB 1.57MB modemst1
12 406MB 407MB 1.57MB modemst2
13 470MB 471MB 1.57MB fsg
14 537MB 537MB 0.00MB fsc
15 537MB 537MB 0.01MB ssd
16 604MB 614MB 10.5MB dkernel
17 614MB 749MB 134MB ext4 dfs
18 749MB 759MB 10.5MB recovery
19 759MB 793MB 33.6MB ext4 persist
20 793MB 826MB 33.6MB ext4 persistbackup
21 826MB 1900MB 1074MB ext4 cache
22 1900MB 3209MB 1309MB ext4 system
23 3209MB 15634MB 12426MB ext4 userdata
I don't know the memory size of your device, also there can be some differences between the cellular and wifi models. Use this info as a reference but don't break anything further because you can kill the recovery partition and I'm not sure that you'll be able to write a recovery by a fastboot when you don't have a recovery partition.
Thanks for your response, Crash. I will run through this this evening when I get home or tomorrow morning at the latest.
Ok. I got the tablet and ran parted. My partitions all match those in size and file system, save for the userdata which is larger since mine is a 32gig model.
What's my next step?
Thanks again
gr3yg00s3 said:
Ok. I got the tablet and ran parted. My partitions all match those in size and file system, save for the userdata which is larger since mine is a 32gig model.
What's my next step?
Thanks again
Click to expand...
Click to collapse
Have you tried reflashing the 3.2.3.2 bootloader update (here)? Possible it might lay down a file the device is looking for early in the startup sequence.
I would also try flashing a safestrap compatible version of FireOS v3.1.0 (no bootloader or recovery code) followed by a full version of 3.1.0 if the former is unsuccessful which will obviously overwrite your custom recovery (twrp) and unlocked bootloader. If it works you can easily unlock again (even easier if you saved the unlock code). Both suggestions are long shots and carry increasing levels of risk.
Davey126 said:
Have you tried reflashing the 3.2.3.2 bootloader update (here)? Possible it might lay down a file the device is looking for early in the startup sequence.
Click to expand...
Click to collapse
I gave this a shot, and it was unsuccessful.
I would also try flashing a safestrap compatible version of FireOS v3.1.0 (no bootloader or recovery code)
Click to expand...
Click to collapse
Tried this as well with no luck.
followed by a full version of 3.1.0 if the former is unsuccessful which will obviously overwrite your custom recovery (twrp) and unlocked bootloader. If it works you can easily unlock again (even easier if you saved the unlock code). Both suggestions are long shots and carry increasing levels of risk.
Click to expand...
Click to collapse
I'm hesitant to try this yet because I'm afraid that I'll be completely stuck if I lose TWRP. Any other thoughts before I get to this point?
I've tried the CM rom as it includes a boot image, but that didn't do it either. Is there any way to troubleshoot the gray screen stage of the boot sequence?
I may be trying to punch over my weight class, so forgive my ignorance. I'm researching the boot sequence, and I'm looking at my system/etc folder. I see an init.rc, but I don't see an init.apollo.rc.
ADB starts up at some point in the gray screen, but logcat doesn't work.
gr3yg00s3 said:
I'm hesitant to try this yet because I'm afraid that I'll be completely stuck if I lose TWRP. Any other thoughts before I get to this point?
I've tried the CM rom as it includes a boot image, but that didn't do it either. Is there any way to troubleshoot the gray screen stage of the boot sequence?
I may be trying to punch over my weight class, so forgive my ignorance. I'm researching the boot sequence, and I'm looking at my system/etc folder. I see an init.rc, but I don't see an init.apollo.rc.
ADB starts up at some point in the gray screen, but logcat doesn't work.
Click to expand...
Click to collapse
Understood - I would have similar reservations. Unfortunately, I'm at the limit of direct experience. Further suggestions (from me) would be pure conjecture.
A recently created thread (today!) by @ONYXis may offer some hope. Your unlocked device is obviously eligible. Might want to strike up a dialog w/ONYXis to see if it's worth trying given you still have some control.
Davey126 said:
Understood - I would have similar reservations. Unfortunately, I'm at the limit of direct experience. Further suggestions (from me) would be pure conjecture.
A recently created thread (today!) by @ONYXis may offer some hope. Your unlocked device is obviously eligible. Might want to strike up a dialog w/ONYXis to see if it's worth trying given you still have some control.
Click to expand...
Click to collapse
I just saw this as well. It sounds like what he's doing is getting everything reset one step at a time and it involves putting TWRP on it anyway. Worst case scenario is it doesn't work. I'm going to give it a shot once it finishes downloading, and i'll follow up here to close this out one way or another.
Thank you for all your help so far. Wish me luck.
I currently own the newest model of the Samsung galaxy J3 (SM-J320V).
If you search it up, literally the only other thing you will find on it is its specs, and there is nothing on this forum about it.
ALL of the rooting tutorials I have seen are of variants, such as the J320P or other things.
Seriously, I have looked everywhere and tried every single one click root, but so far all of them have failed.
ANY sort of help or something to help me root my phone would be appreciated
I know that I'm probably in a minority here, as all the other models of this phone seem to be rootable, but I can't find any info on how to root this, but I'm sure someone else on this forum has this problem.
It would really be a HUGE favor if someone could reach out and help me root my phone.
Thanks!
I just got this phone last week and I'm still searching for a root method .
SkyZero03 said:
I currently own the newest model of the Samsung galaxy J3 (SM-J320V).
If you search it up, literally the only other thing you will find on it is its specs, and there is nothing on this forum about it.
ALL of the rooting tutorials I have seen are of variants, such as the J320P or other things.
Seriously, I have looked everywhere and tried every single one click root, but so far all of them have failed.
ANY sort of help or something to help me root my phone would be appreciated
I know that I'm probably in a minority here, as all the other models of this phone seem to be rootable, but I can't find any info on how to root this, but I'm sure someone else on this forum has this problem.
It would really be a HUGE favor if someone could reach out and help me root my phone.
Thanks!
Click to expand...
Click to collapse
Yeah Verizon isn't to Keen on exploits
Same Problem
Yeah, I do too! The part I get stuck on is when you go into download mode and when you click start on Odin and it fails and your phone says"SECURE CHECK FAIL RECOVERY".
Any progress?
I have the same phone would like to root any solutions?
I have same variant the j320v
[email protected] said:
Yeah Verizon isn't to Keen on exploits
Click to expand...
Click to collapse
I've been waiting for a way to root mine as well it seems like it may be a lost cause I was hoping XDA would have had a solution but it the people here havent figured it out then its probably just not possible lol
Anyone find a solution?
I found a way into the file system but I have no idea what to do with it a few files
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found
---------- Post added at 05:12 AM ---------- Previous post was at 05:06 AM ----------
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found and I see the root file just don't have any idea how to gain access I could really use a developer to help exploit this vulnerability
Filesystem
Stevens7731 said:
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found
---------- Post added at 05:12 AM ---------- Previous post was at 05:06 AM ----------
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found and I see the root file just don't have any idea how to gain access I could really use a developer to help exploit this vulnerability
Click to expand...
Click to collapse
How did you get into the file system?
Stevens7731 said:
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found
---------- Post added at 05:12 AM ---------- Previous post was at 05:06 AM ----------
The phone is a Samsung sm j320 v running marshmallow I have access to the dev file went though block folder to bootloader folder but have absolutely no idea where to go from here. Do i move bootloader I feel if I delete the block folder the bootloader is in I'll lose access to bootloader I'm completely new to computer's and how file system's work some help would be appreciated I can see the loop folders maybe those I should get rid of please help before I'm discover in the hole I think I've found and I see the root file just don't have any idea how to gain access I could really use a developer to help exploit this vulnerability
Click to expand...
Click to collapse
Can you upload that file you have? I need to take a look at it.
I have helped gain root on several of these devices so far. This one may be able to be added to the list.
See the forum here: https://forum.xda-developers.com/t/galaxy-j3-2016
.
Has any progress been made in this?
Hello everyone, has anyone find the root for J320v? i have the same problem while loading recovery file, it failing on every file i have tried.
---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------
:fingers-crossed:
ashyx said:
Can you upload that file you have? I need to take a look at it.
I have helped gain root on several of these devices so far. This one may be able to be added to the list.
See the forum here: https://forum.xda-developers.com/t/galaxy-j3-2016
.
Click to expand...
Click to collapse
Has anyone cracked it yet?
My verizon sm-j320v is rooted
This phone is tedious at almost every level but yes push the issue on the root and you will get it i used an individuals files to root this device and im not that individual so whats the policy on me putting them on here ??
Regards
Tmt926 said:
This phone is tedious at almost every level but yes push the issue on the root and you will get it i used an individuals files to root this device and im not that individual so whats the policy on me putting them on here ??
Regards
Click to expand...
Click to collapse
Could you please help us out with how you did this? I have been pulling my hair out over here unable to figure it out for months. It's literally driving me insane.
jkknight said:
Could you please help us out with how you did this? I have been pulling my hair out over here unable to figure it out for months. It's literally driving me insane.
Click to expand...
Click to collapse
Yes my friend I Will gladly assist you...... your going to download a boot tar and sboot file meant for engineering (engineers need to obviously be able to do what ever the **** they want to on the device in order do their job) point being once you flash the eng boot/sboot file in the
AP slot in Odin 3 you set selinux to permissive after doing this download kingroot and let it take over your phone temporarily allow device admin allow all permissions etc. You will be going at kingroot for a good while .....all night?? Maybe ...but be disciplined and you will gain root keep retrying root over and over
Pm for files
Tmt926 said:
Yes my friend I Will gladly assist you...... your going to download a boot tar and sboot file meant for engineering (engineers need to obviously be able to do what ever the **** they want to on the device in order do their job) point being once you flash the eng boot/sboot file in the
AP slot in Odin 3 you set selinux to permissive after doing this download kingroot and let it take over your phone temporarily allow device admin allow all permissions etc. You will be going at kingroot for a good while .....all night?? Maybe ...but be disciplined and you will gain root keep retrying root over and over
Pm for files
Click to expand...
Click to collapse
Could I have the files too? Many thanks in advance!
Tmt926 said:
Yes my friend I Will gladly assist you...... your going to download a boot tar and sboot file meant for engineering (engineers need to obviously be able to do what ever the **** they want to on the device in order do their job) point being once you flash the eng boot/sboot file in the
AP slot in Odin 3 you set selinux to permissive after doing this download kingroot and let it take over your phone temporarily allow device admin allow all permissions etc. You will be going at kingroot for a good while .....all night?? Maybe ...but be disciplined and you will gain root keep retrying root over and over
Pm for files
Click to expand...
Click to collapse
http://https://drive.google.com/file/d/18BP4zRaeTw_mcnb566WHUN_D_SggRDnu/view?usp=drivesdk
Sorry Kingoroot failed to root the device even after flashing ENG Boot.
Tried too many times.
Now trying Kingroot.
Damn WiFi not working after ENG Boot So Kingroot APK is not working. ;(
Kingroot PC version also failed to root the phone.
You look in your about phone section and se for android set to permissive?
Also oem unlock ticked and usb debug assuming you have developer options enabled if not u need to enable it by tapping on build number in about phone 10 times if u did not do that that is why
Download hidden menus apk off apkpure.com and under user debug google oem mode to "on"
Hope this helps hit me up if u have other issues this phone will be rooted with kingroot u just need to keep pressing root again and again no matter if it fails a few times or not
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
.::Rizwan::. said:
Sorry Kingoroot failed to root the device even after flashing ENG Boot.
Tried too many times.
Now trying Kingroot.
Damn WiFi not working after ENG Boot So Kingroot APK is not working. ;(
Kingroot PC version also failed to root the phone.
Click to expand...
Click to collapse
You need a WORKING MOBILE DATA CONNECTION bro wifi will be broken from this flashing there is away to fix this with build prop edit but u need to look in that becuse i dono exact process
SkyZero03 said:
I currently own the newest model of the Samsung galaxy J3 (SM-J320V).
If you search it up, literally the only other thing you will find on it is its specs, and there is nothing on this forum about it.
ALL of the rooting tutorials I have seen are of variants, such as the J320P or other things.
Seriously, I have looked everywhere and tried every single one click root, but so far all of them have failed.
ANY sort of help or something to help me root my phone would be appreciated
I know that I'm probably in a minority here, as all the other models of this phone seem to be rootable, but I can't find any info on how to root this, but I'm sure someone else on this forum has this problem.
It would really be a HUGE favor if someone could reach out and help me root my phone.
Thanks!
Click to expand...
Click to collapse
we are in the same pal for months that i am looking for the root for this model j320v android 7.1.1 still can not find any method.
How do i root my zte z831/chapel? if there is one will somebody please explain it to me?:crying:
ZTE MAVEN 2 Z831 - Android 6.0.1 - Messaging App .3
I just got this new AT&T phone and need to root it to delete this bloatware!! Also need to fix Messaging App .3 - I just got this phone and the Messaging App is crashing constantly!
I've searching all around, tried everything recommended, Kingo desktop and one-click as well as SRS... tried all recommended fixes for Messaging App and NOTHING ...
Experts please reply?!?
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Ok... So are we saying it's not possible? Or it is possible with a difficult process?
Lookingforinfo said:
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Click to expand...
Click to collapse
Mine has an OEM unlocking option under Developer options ...
Sent from my LG-V410 using XDA-Developers mobile app
Has anyone made progress with the Z831
errata
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Tested kingroot 5.0.5, achieved partial root and it doesn't persist. cannot grant SU privilege to some apps. cannot remount partition as R/W, so you are not really "deleting" the bloatware, it will come back after reboot. Also very unstable, will have frequent random power offs which resets root. Tried to replace with Super SU and make changes via terminal but nothing worked yet.
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
smith.ks1028 said:
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
Click to expand...
Click to collapse
Make sure you are running the latest version of kingroot.
is there a forum for this phone?
cfli1688c1 said:
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Click to expand...
Click to collapse
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
I got perm root did u miss my last post where it shows it? We don't have a forum to my knowledge for the maven 2 for me to post a guide if we get one I will post a guide on how to root it perm with kingroot
Nope,
I didn't see that post. Would you mind sending it to me?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU
Also: if any mods/admins read this, could you please make a forum for ZTE Maven 2? I would love to get this guide out more so more people can root their phone.
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king oh SuperSU u have to keep enabling I guess. U can disable all the annoying stuff kingroot has
---------- Post added at 02:47 PM ---------- Previous post was at 02:41 PM ----------
Also u didn't list at the end once u have root u can reflash reg recovery back unless I mean the SuperSU part needs it still the same
madvane20 said:
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king
Click to expand...
Click to collapse
Yup, your post for the warp 7 helped me a lot, I gave you credit in my post too.
You can replace KingRoot without any risk of brick, only problem is SuperSu is only temproot. To get root back after reboot you just have to run a quick command in adb shell, it's inconvenient, but I think it's much better than the alternative of having KingRoot.
Edit:
I haven't tried putting recovery back, so i'm not sure if that would work or not. I'll put that in the post though.
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
madvane20 said:
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
Click to expand...
Click to collapse
Yeah SuperSu perm would be nice, I think we just need to add a startup script or something? Also, I feel bad since I kinda stole your guide, I can delete my post if you want.
The phone allows you to enable bootloader unlocking in the developer options. So, I was wondering what command is needed to enable it?
I have no clue, I've been searching high and low, trying to figure out a way to root this device and I've hit a wall at every turn. Any help would be appreciated
Zte firmware needed
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
uni-android unlock tool will unlock bootloader so you can root the n9137 and many other devices... it cost 50 bucks and its good for a year of unlimited unlocking. GOOD LUCK!
Any progress on this front? I have a ZTE Tempo X N9137 HW1.0 from Assurance Wireless (Free Gov't phone).
I Just want to root this phone, so I can run rooted apps. I am not interested in installing other ROMs (I am not sure, but my feeling is that I have to leave the original ROM alone in order for this phone to continue to work w Assurance Wireless under the gov't lifeline free cell program - someone correct me if I am wrong and it is confirmed that I can actually ROM better ROMs into this ZTE and continue to work normally with Assurance Wireless.)
Do I need to install TWRP or CWM in order to root the ZTE, or can I use ADB and Fastboot to unlock the bootloader and install Magisk or SuperSU to allow root?
I googled around, but I can't find TWRP or CWM for the ZTE N9137.
Any help or link to guides specifically for the ZTE Tempo X N9137 is greatly welcomed and needed,
Thanks
What is needed?
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
SP6RK said:
If someone can find the zte firmware/stock rom i can install magisk into it untill someone can build a twrp recovery for it
---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------
If someone finds the firmware i can root it untill someone can build twrp for it
Click to expand...
Click to collapse
Root ZTE Tempo X N9137 Assurance Phone
sketchscarz said:
I have this phone as well. You still need the firmware? DO you need the version or the actual firmware file?
Click to expand...
Click to collapse
Any luck rooting this phone using KingRoot?
Has the Bootloader been unlocked yet?
If I ever get this phone rooted,. will I be able to replace the ROM?what will happen to the Assurance portion of it? WIll it still work as a free gov't phone, or does it need to have the Assurance software to work as the free government phone?
I need to root this phone so I can run rooted app to expand the very limited built in storage space. I cannot install any new app because there is no more storage space. The solution is to allow App2SD or other app that install apps into the SD card, but this requires root access.'
any help greatly appreciated
Hey guys - I good news to report. I successfully rooted my ZTE X N9137. Running Android 7.1.1 build version N9137V1.0.0B08 which is the most current. My phone came with a Sprint SIM and the phone service is Q-Link I have screenshots of the installed root apps I used and also all the bloatware removed gone from the Apps Drawer. I rooted using KingRoot but not via the apk. I am working on a guide and also going to recreate to verify the steps. I used the combo of scripts that I found from site that I linked below. The requires an account to download but it's free. A couple of things I discovered
Start with the phone in EDL Mode:
The phone needs to be in EDL mode (blank screen but is still powered on).
from adb run this command
adb reboot edl
Or run the edl.bat from the /root/ folder
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
https://www.filehosting.org/file/de...ucion de Desbloqueo 100% TESTED Halabtech.rar
Original script package:
https://support.halabtech.com/index.php?a=downloads&b=folder&id=33472
Stock Firmware Site:
https://combinefile.com/index.php?a=downloads&b=folder&id=15471
I was able to download one from their site before having to pay money. YMMV
https://drive.google.com/drive/folders/1GhQof56lwMZvAsk25J-ONo-DEesXliQ3
This guy has an older version: N9137V1.0.0B04
How to flash ZTE roms:
https://www.leakite.com/how-to-flash-zte-stock-rom-firmware-via/
Service Mode - Enter this dial:
*983*0#
Here are screenshots of my ZTE N9137 without all the bloat! "Kingroot - Remove Bloatware" removed
40 pre-installed apps which most were installed as a service which requires to root to remove.
Everything runs some much smoother now.
Based on the overwhelming response with my previous posts, I am continuing ahead. I was again successful at getting root. Attached a couple of pics.
Since I have been unable to unlock the bootloader, the process is only temp
Unlock hotspot, add to APN internet.. APN type default,dun,mms,hipri. Use by4 setting editor to unlock hotspot
Link to mirror of the script is broken. Anyone have a copy? I have found a copy of the script. I can confirm it works. If anyone needs it let me know
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Nice to see things advancing. Any progress with TWRP yet? Looks like you've been working on it based on your GitHub deadman...
Help Rooting ZTE N9137
Hi! I'm kind of a newb at the rooting process so I was hoping someone had a guide on how to root this phone. My version of this phone is from Qlink Wireless with a Sprint SIM installed. Thank you in advance!
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
CivicObligation said:
Flashing always faults out with a read error once it gets to carrier.img. Any ideas?
Click to expand...
Click to collapse
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
deadman96385 said:
That happens when the img is 0 bytes, remove any of the imgs that are 0bytes from the rawprogram0.xml. Then restart your device to edl again and restart your flashing program and try again.
Click to expand...
Click to collapse
Thank you! Seems so obvious after you explained. Any suggestions or advice on FH loader errors? The log says my device is not on the current port once it tries to actually write to the device.
deadman96385 said:
I have ordered one of these phones, in the meantime here is the N9137 Firehose and support files (rawprogram0.xml and patch0.xml)
https://www.androidfilehost.com/?fid=1395089523397897020
QFIL flashable V1.0.0B23 Sprint/Boost Firmware
https://www.androidfilehost.com/?fid=1395089523397897018
A guide to flash the firmware (Replace the firmware in the guide with the one above) and individual images.
https://forum.xda-developers.com/maven-3/how-to/how-to-return-to-stock-flash-images-qpst-t3901510
Click to expand...
Click to collapse
Can you confirm if this technique will network-unlock an N9137 linked to Assurance Wireless? Or is this not possible yet?
Thank you
---------- Post added at 11:46 PM ---------- Previous post was at 11:10 PM ----------
n2locarz said:
Root / Unlock
Script used was : Unlock ZTE-N9137_1_DEVICE.bat
The script requires many reboots and it was after UNLOCKING PHONE STEP 3 is when Kingroot was installed.
This is when I debloated . During this step my wifi was inaccessible (firmware mismatch I suspect)
The script then performed another reboot and I lost root and recovery is non accessible
Mirror of the script package:
filehosting.org link
Original script package:
hablatech.com link
Click to expand...
Click to collapse
Both of the above links don't work. The filehosting.org link is broken or dead and the hablatech.com download is behind a paywall, even if you create a free account on their site.
Does anyone have a link to this script? Also if successful, will this approach network-unlock my phone?
PS. I'm not allowed to post links with a new account so I had to edit them out of the above quote. However you can find them in the original post.
Hello again,
I've proceeded to try Deadman's strategy to install the stock rom he provided. I've implemented the fix to remove references to empty '.img' files in the rawprogram0.xml. The helper files and the rom have been unzipped to the same folder, such that Deadman's rawprogram0.xml and patch0.xml have overwritten those provided in the firmware image folder, which I believe is the correct method.
When I reboot my phone into EDL mode using adb, the QFIL application recognizes the phone as "Qualcomm HS-USB QDLoader 9008 (COM6)" and I can begin the flash.
However, the flashing hangs or stops when it reaches the following stage:
Code:
2019-04-15 12:42:34.015 12:42:33: INFO: {percent files transferred 2.78%}
2019-04-15 12:42:34.016 12:42:33: INFO: In handleProgram('recovery.img')
2019-04-15 12:42:34.016 12:42:33: INFO: Looking for file 'recovery.img'
2019-04-15 12:42:34.017 12:42:33: INFO: =======================================================
So it appears that there is an issue with the recovery.img file. However this file is both present in the same folder and non-empty. What could be the issue here?
Cheers.