Unlock Bootloader in Developer Options - ZTE Axon 7 Mini Guides, News, & Discussion

I haven't seen anybody bring it up, but there is an option to unlock the bootloader in developer options (Latest update to 7.1.1). I don't consider rooting a necessity, but I was wondering if this could help someone create a way to root this phone, since unlocking the bootloader was a major hurdle.

jreed1096 said:
I haven't seen anybody bring it up, but there is an option to unlock the bootloader in developer options (Latest update to 7.1.1). I don't consider rooting a necessity, but I was wondering if this could help someone create a way to root this phone, since this unlocking the bootloader was a major hurdle.
Click to expand...
Click to collapse
How to root???
Sent from my tulip using XDA Labs

jreed1096 said:
I haven't seen anybody bring it up, but there is an option to unlock the bootloader in developer options (Latest update to 7.1.1). I don't consider rooting a necessity, but I was wondering if this could help someone create a way to root this phone, since unlocking the bootloader was a major hurdle.
Click to expand...
Click to collapse
As far as I've seen, there is no root for this phone yet

Root tool for ZTE Axon 7 Mini?
Has anyone tried 'SRSRoot one click rooting tool developed and distributed by 123Unlock GSM Service'?
https://freeandroidroot.com/root-zte-axon-7-mini/

SGH-i200 said:
Has anyone tried 'SRSRoot one click rooting tool is developed and distributed by 123Unlock GSM Service'?
https://freeandroidroot.com/root-zte-axon-7-mini/
Click to expand...
Click to collapse
I haven't, but I'm also not familiar with that at all. Can you give it a try and get back to us? Or give me a rundown and maybe I'll try this weekend.

The instructions are in the linked blog post.

SGH-i200 said:
Has anyone tried 'SRSRoot one click rooting tool developed and distributed by 123Unlock GSM Service'?
Yes, I've tried it along with 2 other "one click' root tools on Axon 7 mini with no success. However I did find a "How to root" guide at androidinfotech.com for the Axon 7 mini. I cant post the link because I'm a new user so just google it. You'll also find links to unlock bootloader, install TWRP and install SuperSu here. Please let me know if you have any luck.
Click to expand...
Click to collapse

ChadB513 said:
SGH-i200 said:
Has anyone tried 'SRSRoot one click rooting tool developed and distributed by 123Unlock GSM Service'?
Yes, I've tried it along with 2 other "one click' root tools on Axon 7 mini with no success. However I did find a "How to root" guide at androidinfotech.com for the Axon 7 mini. I cant post the link because I'm a new user so just google it. You'll also find links to unlock bootloader, install TWRP and install SuperSu here. Please let me know if you have any luck.
Click to expand...
Click to collapse
what is the link
Click to expand...
Click to collapse

http://www.androidinfotech.com/2016/12/unlock-bootloader-zte-axon-7-mini.html
Gesendet von meinem LG-H850 mit Tapatalk
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
http://www.androidinfotech.com/2016/12/root-zte-axon-7-mini-marshmallow-twrp.html
Gesendet von meinem LG-H850 mit Tapatalk

Can someone please try this and confirm that it works?
Thanks!
Mistkäfervertreiber said:
http://www.androidinfotech.com/2016/12/unlock-bootloader-zte-axon-7-mini.html
Gesendet von meinem LG-H850 mit Tapatalk
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
http://www.androidinfotech.com/2016/12/root-zte-axon-7-mini-marshmallow-twrp.html
Gesendet von meinem LG-H850 mit Tapatalk
Click to expand...
Click to collapse

tdm said:
Can someone please try this and confirm that it works?
Thanks!
Click to expand...
Click to collapse
I'll probably try this later today, my phone needs a reset anyway and it's not likely to work...
Reason I say that is I have tried other methods before and I am on Nougat so not likely it still works if it ever did.
Edit:
I have the device in EDL mode, but I cannot get ADB to see it, been a long time since I have messed with these kinds of things, can I get a quick run down.
Running Win10 Pro
forgot to enable usb debugging lol
adb does not see my device in edl mode or recovery.

Rooting via EDL mode / B2017G (ZTE Axon 7 Mini)
fallen00sniper said:
I have the device in EDL mode, but I cannot get ADB to see it, been a long time since I have messed with these kinds of things, can I get a quick run down.
Click to expand...
Click to collapse
Have you looked into the info for the "Axon 7" (non-mini)? Maybe you get some guidance from the infos there:
[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click to expand...
Click to collapse
Another: [Guide] [A2017(G)] - Unlock, TWRP, Flash with Toolkit

SGH-i200 said:
Have you looked into the info for the "Axon 7" (non-mini)? Maybe you get some guidance from the infos there:
[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade
Another: [Guide] [A2017(G)] - Unlock, TWRP, Flash with Toolkit
Click to expand...
Click to collapse
I have removed the drivers and re-installed with the supplied driver.
zadig provided driver output
Code:
PS E:\Axon> adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully * <--- Device reboots to EDL mode, QHSUSB__BULK displays under Universal Serial Bus devices
PS E:\Axon> adb devices
List of devices attached
PS E:\Axon> adb get-state
unknown
adb usb, adb devices results in adb being blind.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click to expand...
Click to collapse
I see the device now under Ports tab of device manager, running commands again.
Link provided driver output
Code:
PS E:\Axon> adb reboot edl
PS E:\Axon> adb devices
List of devices attached
PS E:\Axon> adb usb
error: device '(null)' not found
PS E:\Axon> adb get-state
unknown
still is not visible to adb.

EDL mode is not visible to adb, only to EDL tools.

tdm said:
EDL mode is not visible to adb, only to EDL tools.
Click to expand...
Click to collapse
Well that would make more sense, got anything you want me to try out?
I tried those tools again and saw the same error, Failed to connect for both.

fallen00sniper said:
Well that would make more sense, got anything you want me to try out?
I tried those tools again and saw the same error, Failed to connect for both.
Click to expand...
Click to collapse
No, it looks like the firehose isn't compatible.

tdm said:
No, it looks like the firehose isn't compatible.
Click to expand...
Click to collapse
So where does this leave root at the moment?
Waiting for a talented dedicated dev that codes stuff like @AdamOutler or just stuck with no root ever?

fallen00sniper said:
So where does this leave root at the moment?
Waiting for a talented dedicated dev that codes stuff like @AdamOutler or just stuck with no root ever?
Click to expand...
Click to collapse
I'm sorry. I cannot help. I have contractual obligations and insider information. For the most part I've not been able to participate in this forum for the last couple of years due to my job.

AdamOutler said:
I'm sorry. I cannot help. I have contractual obligations and insider information. For the most part I've not been able to participate in this forum for the last couple of years due to my job.
Click to expand...
Click to collapse
I remembered that from a few couple years ago, we need someone epic like you to come and storm the gates of this device.

So it looks like I've acquired a firehose. I'll be building a program to dump boot, recovery, and fbop.
What OSes do you guys use? I can build for Linux, Mac, and Win64. But I prefer to avoid Win64 because of its USB driver brain damage.

Related

[Q] [HELP] Root failed! Command Write failed (Too many links)

Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
EDIT: I was able to unlock the bootloader but I still do not have root access!
saadster25 said:
Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
Click to expand...
Click to collapse
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
I second this
Sent from my Nexus 5 using XDA Premium 4 mobile app
That and don't use s USB 3 port.
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
El Daddy said:
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
aooga said:
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
Click to expand...
Click to collapse
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
saadster25 said:
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
Click to expand...
Click to collapse
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
We consider it a toolkit because it does things (a couple of them) for you. Now you run into issues and don't know what failed because it was doing hidden tasks.
The manual method besides doing the job, will teach you a thing or 2 or 3, plus will help you to troubleshoot simple things.
aooga said:
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
Click to expand...
Click to collapse
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
Technically, yes, but here is a thread with all the workarounds http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
If you only unlock the BL/root the phone and don`t uninstall/replace system components you will still be able to receive and install OTA`s with the stock recovery. You`ll have to reroot afterwards though, but that only takes a minute.

Root/Unlock Bootloader/TWRP for Metro Stylo

Anyone have a link or instructions on how to root, unlock the Bootloader, and install custom recovery on the Metro varient running stock 6.0? Been searching around and can only find 5.1 and down instructions. Cant afford to brick.
from what i am reading, you should be able to use the same method that they used to root the tmobile 6.0 update found here http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/
i havent tried it myself yet, so if you have the courage please report back and let us know how it goes
edit i couldnt wait anymore...i kdz'd back to stock and im trying to force the ota to come through...will post back with results when i get it and attempt to root
Thank you for this link. This worked beautifully. i was able to get into TWRP and do a full backup and install Super SU. Yes, I'm using MS631 with Android 6.0 and now I can say I'm successfully rooted. This made my day being able to root the Stylo after the upgrade.
Encase you're unsure on how to gain access to a command line through Windows hold down shift key and right click the file. Should see the option to open command line and from then on follow the steps.
czjrli said:
Thank you for this link. This worked beautifully. i was able to get into TWRP and do a full backup and install Super SU. Yes, I'm using MS631 with Android 6.0 and now I can say I'm successfully rooted. This made my day being able to root the Stylo after the upgrade.
Encase you're unsure on how to gain access to a command line through Windows hold down shift key and right click the file. Should see the option to open command line and from then on follow the steps.
Click to expand...
Click to collapse
cool deal glad it worked out for you...im just sitting around waiting to get the update now...hopefully when the phone gets fully charged and check again i will see it
Any way at all possible to accomplish this without a pc?
AP2FTW said:
cool deal glad it worked out for you...im just sitting around waiting to get the update now...hopefully when the phone gets fully charged and check again i will see it
Click to expand...
Click to collapse
If you manually change your time to 11pm local time and then reboot your phone you should see the upgrade message in the system update section
czjrli said:
If you manually change your time to 11pm local time and then reboot your phone you should see the upgrade message in the system update section
Click to expand...
Click to collapse
didnt work
I woke up to the system update message 2 days ago. Yall should see it soon. Now if only i could root without a pc....
Goongydin said:
I woke up to the system update message 2 days ago. Yall should see it soon. Now if only i could root without a pc....
Click to expand...
Click to collapse
I had sucessful root on 6.0 via kingroot. Be sure to go into developer options and enable I am unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
tokenpoke said:
I had sucessful root on 6.0 via kingroot. Be sure to go into developer options and enable I am unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
Click to expand...
Click to collapse
I thought you had to fastboot oem unlock the bootloader before rooting?
Revenant Ghost said:
I thought you had to fastboot oem unlock the bootloader before rooting?
Click to expand...
Click to collapse
It doesn't automatically reboot for me. So I don't think it matters as long as you unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
I didn't doo fastboot btw.
Sent from my LGMS631 using XDA-Developers mobile app
Revenant Ghost said:
I thought you had to fastboot oem unlock the bootloader before rooting?
Click to expand...
Click to collapse
Yes i thought so too otherwise you risk a secure boot error correct?
Goongydin said:
Yes i thought so too otherwise you risk a secure boot error correct?
Click to expand...
Click to collapse
That's right. That's what happened to me. The only ways to fix the problem is either by flashing a KDZ (with a computer), or send it to LG for repairs. Better safe than sorry.
Hey guys kinda stuck need root(apps req) no access to a pc that i can install anything on (outta town in a hotel) no way to root with out the pc? Rooted several phones in the past mostly samsungs. Most already had one click root available....
Lgms631 mm6.0
Ok june 6th new king root update works!
Am I the only one having trouble getting into fastboot?
jjswag said:
Am I the only one having trouble getting into fastboot?
Click to expand...
Click to collapse
nope. It happens to me too. I think you have to have Android SDK Tools installed on your PC alongside ADB for it to work, sadly
jjswag said:
Am I the only one having trouble getting into fastboot?
Click to expand...
Click to collapse
shawnster480 said:
nope. It happens to me too. I think you have to have Android SDK Tools installed on your PC alongside ADB for it to work, sadly
Click to expand...
Click to collapse
Did you install ADB and Fastboot?
http://forum.xda-developers.com/showthread.php?t=2317790
tube517 said:
Did you install ADB and Fastboot?
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
I did, it turns out, I had to install the appropriate drivers fro the Stylo MTP, then I had to install the appropriate ADB Drivers by updating to LGE Mobile ADB Drivers, then after that, I had to do "adb reboot-bootloader" and that booted it straight into the fastboot interface, but to no avail, I couldn't get fastboot to recognise the device, so I went into device manager, and I saw "(something)com bootloader interface", I expanded that, and saw Android Bootloader interface. So I updated the software, hit load from PC, and hit Android Bootloader Interface Version 9.0.0.0 instead of 11, and fastboot saw my phone
message me further if you need any help, if you want me to Teamspeak you so I can show you directly, I'll be glad to help you
Can somebody please help me I'm trying to root my phone when it comes to rooting I'm a virgin to it and I heard it's pretty safe to do using I have a LG Stylo 2 plus Metro model LG ms550 6.0.1 marshmallow but I'm not too dumb lol I know how to load up XBMC put add-ons on their use different builds load up operating systems programs on computers and stuff like that but rooting a phone is totally different to me
Root help lg stylo ms631 metro pcs
I unlocked the bootloader on my phone but i cant root i tried kingroot it just tells me it cant root my device then i tried adb and fastboot everytime i tried to, flash twrp via fastboot then install super su from twrp, i get failed remote: unknown command i used the command, "fastboot flash recovery twrp.img" im on lg stylo ms631 6.0 metro pcs and my computer is windows 10

[ROM][Android][Stock] Alcatel One Touch Fierce XL 5054

Instead of being split in different posts in a really large and broad topic about this phone, I decided to create a new topic to share the stock roms I recently uploaded.
They have been untouched: they all are large exe files (~1 gb) which unpack and automatically launch the flashing software.
I have no more information about these files: everything written here is all I have. They come from a trusted source.
In the previous topic, at least 2 persons reported successes unbricking their phone with these files.
If these files save your phone, don't forget to thank this post. You can also donate using this link: http://forum.xda-developers.com/donatetome.php?u=269273
D6UUPU0 (First Package, 2015-12):
https://mega.nz/#!GhwBQSDY!Y2GMYRXWddRl7H9UKUPA3X5C7g6IxB4jeQ7FmvF9OT8
D6UUPU0 (Second Package, 2015-10, was in a folder named "Change file"):
https://mega.nz/#!m0QUkYIS!XLoD8cmALKz7u361Xqkn7C2qyTaHd6uuCoOOlw3RsiU
D6UUPU0 (2016-05):
https://mega.nz/#!zlo2zTbY!w7ZiOMdAsstcaiUntxC9JP6nyc_3pVl_Y5inH9I3pb0
D6UUMU0:
https://mega.nz/#!utxCyBIZ!5r6P78EP1qO35t71n_E5S5qersdWxLJxB9oC0704_N8
D76UM60 ("Without SML", "Change File")
https://mega.nz/#!XkpmGYqB!nchZp3EaenbRbROfmAh1nmdyft9Ms-pWMUO8bhRbayA
D76UM70 ("With SML"):
https://mega.nz/#!DlIXwYqS!cvgVTihhvyp40PA4Ua-etpveUJSwY5UFf2T31ox8R0Q
D79UM90:
https://mega.nz/#!TxpDnapT!zGSjD6tLyG07h6b6a090psgogUwncTfNU5NMeisElWM
D64 ("A-GPS Cold Start"):
https://mega.nz/#!boAAGKSB!inp-2lEATFIE8-6TTK4Q71P3cczH0Q06Fqkzh7O8kSo
D6TUP0 ("Unchange File"):
https://mega.nz/#!b8QWHRoT!7kCMc8ljXB9JSlOu9VVMCW5I_g6zDE0_7pYpz_37KKQ
D6TUP0 ("Change File"):
https://mega.nz/#!C1JDSBxa!XG2g95AFiBQGnuRVOH6LBH-fw6pgLswSE5IO-QIBQ38
Brilliant!!
Great to see another thread created. I was thinking of asking someone to do this and make this one the dev section and link to the other thread for general discussion.
EDIT: Are you going to explain certain things like "With SML"? It could help some .
Excellent, hooray
kirito9 said:
Great to see another thread created. I was thinking of asking someone to do this and make this one the dev section and link to the other thread for general discussion.
EDIT: Are you going to explain certain things like "With SML"? It could help some .
Click to expand...
Click to collapse
I would love to tell you Unfortunately, it's an information I don't have
I was thinking about SiMLock but I don't think a ROM can alter the SIM lock status of a phone. It may be related to SIM lock anyway...
I was also thinking of Qualcomm Snapdragon Math Libraries...
I will probably upload a Windows Mobile 10 FFU file soon.
SML might be a reference to Standard ML, a functional programming language that excels at pattern matching.
Sent from my SM-G935V using XDA-Developers mobile app
Originally Posted by TristanLeBoss
In request of the selling brands, fastboot is not enabled on these phones. What this app is probably doing is putting the phone in the Qualcomm QDLoader 9008 mode and flashing the ROM this way.
You can do that yourself using the "emmcdl.exe" program and the corresponding Firehose flasher (for your phone, it should be "prog_emmc_firehose_8909_lite.mbn"). You also need ROM files: rawprogram0.xml, patch0.xml and all the needed MBN files.
Click to expand...
Click to collapse
Maybe related to this - I have activated the "Developer Mode" on mine (multiple tapping on "About Phone") and I saw an option that is new to me: "Enable OEM unlock - Allow the boot loader to be unlocked". It was OFF by default, I turned it on.
Also on rooted phones the "System Updates" won't work anymore: "It was detected that your device has ROOT access. Upgrade is disabled". Hmmm... "Hide my Root"?
Tried and it stops at 2% and after a while I get this prompt?
COM0->PC[2] Search Disk over time! Please check the handset or driver! (Error code = 40011)
How do I know I have the correct driver for this tool to work? Have in mind that I have messed around with qualcomm drivers on this win8 laptop...
Any chance for some details/instructions so we all get there smoothly
Thanks!
---------- Post added at 05:46 PM ---------- Previous post was at 05:42 PM ----------
SoNic67 said:
Maybe related to this - I have activated the "Developer Mode" on mine (multiple tapping on "About Phone") and I saw an option that is new to me: "Enable OEM unlock - Allow the boot loader to be unlocked". It was OFF by default, I turned it on.
Also on rooted phones the "System Updates" won't work anymore: "It was detected that your device has ROOT access. Upgrade is disabled". Hmmm... "Hide my Root"?
Click to expand...
Click to collapse
We've been through this basics early in the original thread and nooo, to enable OEM unlock does NOT help us to unlock the bootloader
And if you have faith in MetroPCS regarding a System Update, then you just unroot in the Kingroot app...
nyttliv7 said:
Tried and it stops at 2% and after a while I get this prompt?
COM0->PC[2] Search Disk over time! Please check the handset or driver! (Error code = 40011)
How do I know I have the correct driver for this tool to work? Have in mind that I have messed around with qualcomm drivers on this win8 laptop...
Any chance for some details/instructions so we all get there smoothly
Thanks!
Click to expand...
Click to collapse
The drivers are part of the program. In the "Option" menu, there is an "Install & Uninstall Driver" option.
If you launch the program and if you don't close it, the drivers files are also present in a "usb_driver" subfolder of the folder where the program extracted itself (look at your "C:\Users\{username}\AppData\Roaming" folder).
You may want to use the "Device Manager" to uninstall all the drivers related to Qualcomm. You can also view hidden devices by checking "show hidden devices" under the "View" menu.
In the other thread, few people reported successes so they maybe able to tell you how they did that.
nyttliv7 said:
Tried and it stops at 2% and after a while I get this prompt?
COM0->PC[2] Search Disk over time! Please check the handset or driver! (Error code = 40011)
How do I know I have the correct driver for this tool to work? Have in mind that I have messed around with qualcomm drivers on this win8 laptop...
Any chance for some details/instructions so we all get there smoothly
Thanks!
Click to expand...
Click to collapse
I uploaded a setup which install the required drivers:
https://mega.nz/#!aw4TAZga!AitSSwsvqfekj3_Ln30ZofyNnC749cok4VCHo3i2kFc
TristanLeBoss said:
I uploaded a setup which install the required drivers:
https://mega.nz/#!aw4TAZga!AitSSwsvqfekj3_Ln30ZofyNnC749cok4VCHo3i2kFc
Click to expand...
Click to collapse
Wish it was a universal standard to include an "uninstall all conflicting drivers" when installing a new driver. Been there so many times, puuh
Here we go again
Thanks for quick response
Ok, I'm now 99.99% sure the "SML" mention refers to SIM lock. The "file" mention in the folder name is also related to the unlock/lock phone: it actually refers to the MBN file of the security partition. Unfortunately, I don't know what "change"/"unchange" mean.
Indeed, on this phone, there is a small security partition (~700kb) which contains the SIM lock status. Unlock software like SigmaKey use this partition to unlock the phone.
Can you check the before/after status of the SIM lock after you flash one of these ROMs?
TristanLeBoss said:
Ok, I'm now 99.99% sure the "SML" mention refers to SIM lock. The "file" mention in the folder name is also related to the unlock/lock phone: it actually refers to the MBN file of the security partition. Unfortunately, I don't know what "change"/"unchange" mean.
Indeed, on this phone, there is a small security partition (~700kb) which contains the SIM lock status. Unlock software like SigmaKey use this partition to unlock the phone.
Can you check the before/after status of the SIM lock after you flash one of these ROMs?
Click to expand...
Click to collapse
I can check that. Will update later today.
Sent from my SM-G935V using XDA-Developers mobile app
nyttliv7 said:
Tried and it stops at 2% and after a while I get this prompt?
COM0->PC[2] Search Disk over time! Please check the handset or driver! (Error code = 40011)
How do I know I have the correct driver for this tool to work? Have in mind that I have messed around with qualcomm drivers on this win8 laptop...
Any chance for some details/instructions so we all get there smoothly
Thanks!
---------- Post added at 05:46 PM ---------- Previous post was at 05:42 PM ----------
We've been through this basics early in the original thread and nooo, to enable OEM unlock does NOT help us to unlock the bootloader
And if you have faith in MetroPCS regarding a System Update, then you just unroot in the Kingroot app...
Click to expand...
Click to collapse
What Mode Do You Put Your Phone In For This To Work?
Here we go, it worked at last
I used USB-Deview to see everything that happened when connecting my phone to the laptop. A good software to delete unwanted drivers. I had to restart my laptop AND my phone. Restart my phone might be the wrong words though, but when you have the Alcatel Upgrade software open and connect the phone and start the process, the phone switch from turned off (and charging) to qualcomm hs-usb qdloader 9008 mode (which you already mentioned) and to get out of this mode on the softbricked phone, you have to get into the built in recovery and from there, turn off the phone for a fresh start again. I had to do this a couple of times before it worked.
And now I'm not afraid to experiment again, wiiipppiiihoooaaah
Thanks a lot TristanLeBoss
---------- Post added at 01:15 AM ---------- Previous post was at 01:11 AM ----------
TheOnlyAmbition said:
What Mode Do You Put Your Phone In For This To Work?
Click to expand...
Click to collapse
If you refer to flashing the system, you leave the phone turned off, and if your computer is free from conflicting USB drivers, it will work (sooner or later)
I am so glad this phone is out of its shell, thank you guys.
Just a quick question. Will the flash tool put the phone in stock?
I haven't looked on this forum for weeks. Because I thought this phone was a goner but thank you TristanLeBoss ???
Sent from my 5054N using XDA-Developers mobile app
I get a "load nprg error 5001" every time I try.. My phones not even rotted metro Sim unlocked it an 2 hours on at&t network it restarted into a boot loop
TwentyFoursWorld said:
I am so glad this phone is out of its shell, thank you guys.
Just a quick question. Will the flash tool put the phone in stock?
I haven't looked on this forum for weeks. Because I thought this phone was a goner but thank you TristanLeBoss
Sent from my 5054N using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, phone will go back to stock.
Flash to Win10?
So it looks like the T-Mobile variant is same specs. Can you help me convert my 5054N to Win10? I can offer a $10 donate, thanks!
nyttliv7 said:
Tried and it stops at 2% and after a while I get this prompt?
COM0->PC[2] Search Disk over time! Please check the handset or driver! (Error code = 40011)
How do I know I have the correct driver for this tool to work? Have in mind that I have messed around with qualcomm drivers on this win8 laptop...
Any chance for some details/instructions so we all get there smoothly
Thanks!
---------- Post added at 05:46 PM ---------- Previous post was at 05:42 PM ----------
We've been through this basics early in the original thread and nooo, to enable OEM unlock does NOT help us to unlock the bootloader
And if you have faith in MetroPCS regarding a System Update, then you just unroot in the Kingroot app...
Click to expand...
Click to collapse
Ever since using exe files to unbrick my phone I have since installed Kali nethunter, viper4android and flashed an update for SuperSU too..all with th e FLASHFIRE(chainfire)apk.. NO B.BS
TristanLeBoss said:
I would love to tell you Unfortunately, it's an information I don't have
I was thinking about SiMLock but I don't think a ROM can alter the SIM lock status of a phone. It may be related to SIM lock anyway...
<br>
I was able to use the stock unlock app on the phone to perform a sim unlock. I'm now using the Metro phone on my Tmobile plan.
was looking online for TWRP or CWM for this device and found the previous thread.
Let me know if you need any help, I'm down for testing.
I got this device for free from a friend, because his dad couldn't remember his gmail account, and did a factory reset.
He got stuck on the google FRP setup wizard.
I was able to use the keyboard swipe gesture (from swipe key, to the "s" when you have a word highlighted) to search for metroweb and open a browser. from there it was easy to install "quick shortcut maker" and enter the settings. I went to the manage app settings and cleared the data for settings, then I went to the backup account section and added my gmail as a backup account. Rebooted the phone and now I'm here looking for Custom recovery lol..
I'm not scared of a brick. I've had this phone for two weeks as a brick in FRP mode.
I thought I would share how I got past FRP mode.
Click to expand...
Click to collapse

Oppo R7sf with no fastboot mode, no recovery mode. Please Help :(

Please help me.
So I think I accidentally removed some bloatware when my phone still great.
When I restart the phone hope for a more speedy and light everyday use, it goes bootloop instead.
Here is My Oppo R7sf back then:
1. Already rooted via Oppo Tools, I downgraded the firmware to 151210 version.
2. Booloader not unlocked yet.
3. Cant boot into fastboot mode via buttons, and if I keep holding it = always bootloop, but if I stop pressing it = the logo stucks.
4. Cant boot to Recovery mode nor Hard Reset, and if I keep holding it = same bootloop logo, even I can tell its blinking every 2 seconds. and if I stop pressing it, the logo stucks.
So I was trying how to do fastboot mode via adb and command prompt, but when I type adb devices, it always says "device unauthorized", 12 hours and I have no idea how to get rid of these as far as I know we have to enable usb debugging first, but my phone cannot boot... so... is there any solutions?
Any feedbacks will be much appreciated. Thankyou for your kindness.
My guess is your phone is entering Qualcomms Emergency Download Mode. Try connecting your phone to an PC USB port and look for driver install attempts.
celoxocis said:
My guess is your phone is entering Qualcomms Emergency Download Mode. Try connecting your phone to an PC USB port and look for driver install attempts.
Click to expand...
Click to collapse
Ive done it, trying to flash with QFIL, loading .mbn files, rawprogram0, patch0, and the software cant run..
Ive tried with Msm8974 download tool, finished and sahara failed or something like that.
I really lose my hope.. Please everyone... :
ojankun said:
Ive done it, trying to flash with QFIL, loading .mbn files, rawprogram0, patch0, and the software cant run..
Ive tried with Msm8974 download tool, finished and sahara failed or something like that.
I really lose my hope.. Please everyone... :
Click to expand...
Click to collapse
You just need the proper factory flasher.
I will send you a pm when I get to my terminal.
celoxocis said:
You just need the proper factory flasher.
I will send you a pm when I get to my terminal.
Click to expand...
Click to collapse
I'm now trying to download miui rom for Oppo Find7 so then I can proceed it with MiFlash. I dont know this will work or not, because I think my only solution is playing around with this Qualcomm things. I've already download MsmDownloader for Find7 too. And I have R7sfEX_11_OTA_005_all_201511191402 stock firmware ready, but have no idea how to flash it because I cant get through fastbood mode via Phone nor ADB devices.
Thankyou, I'll be waiting for your PM. Thanks for your kindness.
Best regards.
ojankun said:
I'm now trying to download miui rom for Oppo Find7 so then I can proceed it with MiFlash. I dont know this will work or not, because I think my only solution is playing around with this Qualcomm things. I've already download MsmDownloader for Find7 too. And I have R7sfEX_11_OTA_005_all_201511191402 stock firmware ready, but have no idea how to flash it because I cant get through fastbood mode via Phone nor ADB devices.
Thankyou, I'll be waiting for your PM. Thanks for your kindness.
Best regards.
Click to expand...
Click to collapse
ok check your PM
celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Okay, thank you so much I will try this and will report you back.
Thankyou.
celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Finally it works, thanks mate very very big thanks i owe you my life
YESSSSSSSSSSSSSSSSS!!!! :victory:
Hello,
Could I also please have the link to this file. I'm basically in the exact same situation.
Thank you!
InspireM3world said:
Hello,
Could I also please have the link to this file. I'm basically in the exact same situation.
Thank you!
Click to expand...
Click to collapse
You can PM celoxocis there, mate.
celoxocis said:
ok check your PM
Click to expand...
Click to collapse
Please PM me, same my problem
chua83 said:
Please PM me, same my problem
Click to expand...
Click to collapse
Check your PM
Hi, if you can help me too ... Oppo R7 PlusM
I'm stucked in the "download mode". No Recovery, No Fastboot. I wasn't unable to find the right MSMDownloadtool.
Can you help me? Thank you a lot
mast3rf0x said:
Hi, if you can help me too ... Oppo R7 PlusM
I'm stucked in the "download mode". No Recovery, No Fastboot. I wasn't unable to find the right MSMDownloadtool.
Can you help me? Thank you a lot
Click to expand...
Click to collapse
I can't help for R7PlusM only R7S.
celoxocis said:
I can't help for R7PlusM only R7S.
Click to expand...
Click to collapse
I only need the MSM8939 program utility. The R7s should have the same qualcomm chip. For all others files there are no problem, I should have all necessary.
If are the same, can you send me the link?
Thank you a lot
mast3rf0x said:
I only need the MSM8939 program utility. The R7s should have the same qualcomm chip. For all others files there are no problem, I should have all necessary.
If are the same, can you send me the link?
Thank you a lot
Click to expand...
Click to collapse
No it's not that simple.
The program utility uses headers to compare which phone is plugged it. It compares those headers with the headers of the phone plugged in.
There is no way to force the program utility to flash a different phone than the ones containing the headers it was shipped with.
celoxocis said:
No it's not that simple.
The program utility uses headers to compare which phone is plugged it. It compares those headers with the headers of the phone plugged in.
There is no way to force the program utility to flash a different phone than the ones containing the headers it was shipped with.
Click to expand...
Click to collapse
Ok. For what I understand the process is quite similar to those I've see for MTK. A correct list of the memory and the right flasher.
I've analyzed the content of the directory and seems that the "key" is inside the flasher and a correct settings.xml and rawprogram0.xml.
The various MSMDownloadTool I've found until now can be grouped in : ver.1, ver.2.0 and ver.3.0 (the last one). Everyone of this version have a "range" work using various types of flasher (number.mbn). I belive that the 3.0 should be able to program qualcomm Smartphone of last generation.
However the last MiuiFlasher should be able program everything.
So the main problem is to find the Mbn flasher with Sahara support and right settings files.
I can't find the right flasher.
Maybe I can get a wrong way ... ... correct me for everything I've missed out :angel:
mast3rf0x said:
Ok. For what I understand the process is quite similar to those I've see for MTK. A correct list of the memory and the right flasher.
I've analyzed the content of the directory and seems that the "key" is inside the flasher and a correct settings.xml and rawprogram0.xml.
The various MSMDownloadTool I've found until now can be grouped in : ver.1, ver.2.0 and ver.3.0 (the last one). Everyone of this version have a "range" work using various types of flasher (number.mbn). I belive that the 3.0 should be able to program qualcomm Smartphone of last generation.
However the last MiuiFlasher should be able program everything.
So the main problem is to find the Mbn flasher with Sahara support and right settings files.
I can't find the right flasher.
Maybe I can get a wrong way ... ... correct me for everything I've missed out :angel:
Click to expand...
Click to collapse
Yes that's correct. However there is a thread here somewhere in the R7Plus forum which is specifically for the R7PlusM and in there somewhere is a download link to the factory flasher you are looking for.
I know it because months ago I came across it and downloaded its, saw that it contains only Chinese based Oppo files and deleted it later on.
So I suggest you search that thread for what you need.
celoxocis said:
Yes that's correct. However there is a thread here somewhere in the R7Plus forum which is specifically for the R7PlusM and in there somewhere is a download link to the factory flasher you are looking for.
I know it because months ago I came across it and downloaded its, saw that it contains only Chinese based Oppo files and deleted it later on.
So I suggest you search that thread for what you need.
Click to expand...
Click to collapse
Ok ... I will search. Thank you for your useful information.:good:
celoxocis said:
I can't help for R7PlusM only R7S.
Click to expand...
Click to collapse
I have an R7S which has been bricked; details originally posted here but no reply yet.
Additionally to the quoted post above, if I attempt to go into recovery mode and plug the phone into my PC at the same time, the logo stays on but nothing else. I'm not sure if this is sitting in fastboot mode, however I still can't communicate via adb.
Could you please help me resurrect my phone.

RCA Voyager rct6873w42 rooting help

I was wondering does anyone know of a working way to apply root to this device. I have tried kingo root, king root, iroot, one click root, and impactor. Everyone of them fails when trying to apply the root. i thought maybe i could attempt to unlock the bootloader on the deivce cause that might be what is causing them to fail. I booted into recovery and then clicked reboot into bootloader and the device just boots normal so i am unable to get into the bootloader to even attempt to unlock it. I'm at a roadblock with this device. If anyone can help me get root on this device i would be grateful.
Well I believe that you have enable bootloader unlock in developer tools before you can unlock the bootloader
i enabled oem unlock in developer options what now
---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------
i tried adb reboot fastboot get a blank screen
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
i tried adb reboot bootloader and just does a normal reboot
---------- Post added at 11:16 PM ---------- Previous post was at 11:16 PM ----------
im using minimal adb and fastboot program for windows
I tried framaroot no go kingoroot app gets to 70 % then gives me a download error idk what else to try only one site has the rct6873w42 firmware and its paid adb shell reboot fastboot also fails with blank screen
sent from my nexus 4 using Tapatalk I also own a voyager tablet and I also own an I phone 4s
[email protected] said:
I tried framaroot no go kingoroot app gets to 70 % then gives me a download error idk what else to try only one site has the rct6873w42 firmware and its paid adb shell reboot fastboot also fails with blank screen
sent from my nexus 4 using Tapatalk I also own a voyager tablet and I also own an I phone 4s
Click to expand...
Click to collapse
When you reboot into fastboot mode a blank screen is correct... you can use the fastboot commands from the connected PC
at this point.
I have got this far however I have had no luck thus far in unlocking the bootloader, this is not an indication that it cant be done
just that I do not know the proper command in fastboot, most of my work on Tablets has been on the Allwinner SOC's and I
almost never had to use Fastboot in modding those since the bootloader is not locked on those SOC's for the most part.
RCA has very little useful info on their site nor even a Firmware download available... I would love to get ahold of a firmware for this Tablet in order to make modding it easier, failing that if I can manage to root it I should be able to pull the partitions and create a useable firmware mod... If you have any more luck with this please share whatever info you get and I will do the same.
Thanks
Fastboot oem unlock is the normal command to unlock the bootloader for Fastboot devices i saw another reason tablet on xda developers I believe it was called rca viking or something similar there is a bootloader unlock and root thread for that device maybe worth looking at
Here is the paid site I have 2g so I can't check the website to see if it legitimate
http://www.sitelinks.info/notepad.p...ggYMAU&usg=AFQjCNE5BXp8BnP_V6-WI_RI7-1grLywDQ
Sent from my iPhone using Tapatalk
---------- Post added at 09:02 AM ---------- Previous post was at 08:38 AM ----------
This website claims to http://www.srsroot.com/ have rooted the tablet but they are known for false root proclamations worth a check
Sent from my iPhone using Tapatalk
[email protected] said:
Fastboot oem unlock is the normal command to unlock the bootloader for Fastboot devices i saw another reason tablet on xda developers I believe it was called rca viking or something similar there is a bootloader unlock and root thread for that device maybe worth looking at
Here is the paid site I have 2g so I can't check the website to see if it legitimate
http://www.sitelinks.info/notepad.p...ggYMAU&usg=AFQjCNE5BXp8BnP_V6-WI_RI7-1grLywDQ
Sent from my iPhone using Tapatalk
---------- Post added at 09:02 AM ---------- Previous post was at 08:38 AM ----------
This website claims to http://www.srsroot.com/ have rooted the tablet but they are known for false root proclamations worth a check
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I tried the oem unlock command and it does not work, returns command fail...
The Viking uses the MT8127 SOC which would tend to have a different Firmware.. since that is a chinese SOC I expect the unlock to be
a bit easier typically i have found that on Tablets they often do not even lock the bootloader... the Sofia 3gr or Atom X3 is in the tab we have I have been looking into similar devices... so far I have not got much reading done on these... I will have a look at any info I can locate on here regarding the Viking .. but I have already read about some of the other Model # / versions of the Voyager on here and ours is not the same. The ones I have read up on so far do not seem to have a major problem rooting. This one is a bit of a pain as I cant use adb in root mode which when possible makes rooting much easier...
The link to the Paid site you posted seems to be dead...
I have tried SRSRoot which also does not work... actually i have attempted using Kingoroot, iroot, rootgenius, framaroot, towelroot, tunesgo
and OneClickRoot none have any success at all... they do indicate varying degrees of progress but in the end the most that any has accomplished is to push their app to the tab.
I will keep trying and looking... perhaps I will locate a firmware for these out there so i can examine the partitions and their contents more
closely...
Thanks
fsebentley said:
I tried the oem unlock command and it does not work, returns command fail...
The Viking uses the MT8127 SOC which would tend to have a different Firmware.. since that is a chinese SOC I expect the unlock to be
a bit easier typically i have found that on Tablets they often do not even lock the bootloader... the Sofia 3gr or Atom X3 is in the tab we have I have been looking into similar devices... so far I have not got much reading done on these... I will have a look at any info I can locate on here regarding the Viking .. but I have already read about some of the other Model # / versions of the Voyager on here and ours is not the same. The ones I have read up on so far do not seem to have a major problem rooting. This one is a bit of a pain as I cant use adb in root mode which when possible makes rooting much easier...
The link to the Paid site you posted seems to be dead...
I have tried SRSRoot which also does not work... actually i have attempted using Kingoroot, iroot, rootgenius, framaroot, towelroot, tunesgo
and OneClickRoot none have any success at all... they do indicate varying degrees of progress but in the end the most that any has accomplished is to push their app to the tab.
I will keep trying and looking... perhaps I will locate a firmware for these out there so i can examine the partitions and their contents more
closely...
Thanks
Click to expand...
Click to collapse
Were you ever able to gain root?
I haven't yet
Sent from my iPhone using Tapatalk
just a bird xo said:
Were you ever able to gain root?
Click to expand...
Click to collapse
No I have still not got root access, I have unlocked the tablet and am exploring ways to load a recovery image from fastboot without flashing it. I have also inquired with RCA about getting a copy of the Firmware and I continue to search google etc. for the firmware. Once I have the firmware I am confident that I can root the Tablet fairly quickly.
How did you get bootloader unlock?
Sent from my iPhone using Tapatalk
[email protected] said:
How did you get bootloader unlock?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
fastboot flashing unlock while pressing vol + button on tab... if you simply enter the command while watching the screen you can see the display flash a message calling for input... if you press no buttons it auto enters a no answer... it goes by really fast so the only way I have been able to catch it is by pressing the + vol button then enter the fastboot flashing unlock
that does the trick.
Thanks
Sent from my iPhone using Tapatalk
fsebentley said:
fastboot flashing unlock while pressing vol + button on tab... if you simply enter the command while watching the screen you can see the display flash a message calling for input... if you press no buttons it auto enters a no answer... it goes by really fast so the only way I have been able to catch it is by pressing the + vol button then enter the fastboot flashing unlock
that does the trick.
Click to expand...
Click to collapse
Which mode do I have to be booted in for this to work?
I've tried entering adb reboot bootloader as well as adb reboot fastboot & I can't seem to get it to unlock.
just a bird xo said:
Which mode do I have to be booted in for this to work?
I've tried entering adb reboot bootloader as well as adb reboot fastboot & I can't seem to get it to unlock.
Click to expand...
Click to collapse
I usually just go into adb shell, then do reboot fastboot.
The Tab will reboot with an apparent blank screen, if you look closely you will note that there is a faint backlight. Once in this mode your PC will have a new device in device manager, if it is unrecognized device you can manually assign a device driver. I have the intel drivers installed as well as the google drivers. Woth the intel drivers you can do an Update driver select Browse my computer for driver software, then Let me pick from a List of device drivers on my computer, then scroll down to the Intel Android Device in the list and select either the Intel Android Bootloader device or the Android Bootloader Device, Both seem to work fine.... If you do not install the intel drivers then you should be able to select the USB devices option then select theADB Device. This also seems to work fine...
When in fastboot mode you will havea blank screen however when you enter certain fastboot commands there will be a very brief flash of information/input needed on the screen, it seems the ui in this mode is inhibited in some way.
Also worth noting on this model almost all the commands previously done using oem [command] are now done with flashing [command].
I have now located a firmware for this device and am downloading it. The file is on baidu so is going to take some time to get but once I have it I should be able to do something with the bootloader to allow rooting by most of the conventional apps... as well as make my own rooted version of the firmware and likely get started modding it...
Well the first one I found is a bust... the files contained in the .zip are not in a format that is directly usable or they are corrupted. It appears to contain files from an MTK scatter and has MTK info in the text based config files.. so either someone pulled these using the MTK tool incorrectly or they labeled the file incorrectly as rct6873w42 firmwares... or this could be something I am not aware of...
either way these are taking some time... baidu is slow...
Well it seems that all the ones I have found and downloaded so far have turned out to be mislabeled firmwares for other models of the RCA devices. I will keep pulling them in hopes of finding one that works but meanwhile I will look into some other avenues as well.
So far I'm with you guys up to unlocking the bootloader. Have we made any progress with locating rootable firmware? I've rooted a phone before but never a tablet let alone such a pain in the neck tablet.
I have run
fastboot flashing unlock
and got all that squared away, is there anything else to do at this point? Is it safe to continue to use it in it's current state? You guys are awesome by the way I couldn't find anything anywhere else online for this model. Y'all are making history!
We need to port a custom recovery to this tablet a lots harder than it sounds
Sent from my iPhone using Tapatalk
[email protected] said:
We need to port a custom recovery to this tablet a lots harder than it sounds
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Anything we can do to help? Can't be too crazy can it?

Categories

Resources