Related
[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.
Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
yeah! good work!
Srsly. Awsom.
Someone sticky this....
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.
cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery
cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?
Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.
i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky
In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed
distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
I can confirm that this method works, without unlocking the BL or erasing the SD part.
This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.
cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.
Hi,
Searched through Google and XDA couldn't find a proper step by step instruction to enable LTE on my Nexus 4 with latest Lollipop version. Every website says the same ditto instruction as they have copy pasted from one another.
I am sure some one can give me detailed instruction to enable LTE on my nexus 4 which is not rooted. I understand from different threads that it should be rooted to flash the LTE modem image, but is it possible to achieve it without custom ROM like TWRP and without wiping the data?
s.rajkumar said:
Hi,
Searched through Google and XDA couldn't find a proper step by step instruction to enable LTE on my Nexus 4 with latest Lollipop version. Every website says the same ditto instruction as they have copy pasted from one another.
I am sure some one can give me detailed instruction to enable LTE on my nexus 4 which is not rooted. I understand from different threads that it should be rooted to flash the LTE modem image, but is it possible to achieve it without custom ROM like TWRP and without wiping the data?
Click to expand...
Click to collapse
Not if your bootloader isn't unlocked. To do an ADB push, you need to have an unlocked bootloader, and unlocking your bootloader wipes your data. At this time you can't root your Nexus 4 without unlocking the bootloader on Lollipop. If you were rooted, there is an app that locks/unlocks the bootloader on later Nexus devices without wiping your data (although I don't know if it works on 5.0).
s.rajkumar said:
Hi,
Searched through Google and XDA couldn't find a proper step by step instruction to enable LTE on my Nexus 4 with latest Lollipop version. Every website says the same ditto instruction as they have copy pasted from one another.
I am sure some one can give me detailed instruction to enable LTE on my nexus 4 which is not rooted. I understand from different threads that it should be rooted to flash the LTE modem image, but is it possible to achieve it without custom ROM like TWRP and without wiping the data?
Click to expand...
Click to collapse
1)TWRP isn't a ROM but a Recovery
2)Is it that bad to install a custom recovery in order to achieve this thing?
3)If it is, what are you doing on XDA?
4)Just install TWRP
5)Just flash the .zip file
6)Just do it.
Does everyone forget you can BOOT recovery and NOT flash it?!?! I understand completely why the OP doesn't want TWRP, it will stop further OTA's and cause bootloop conditions on an otherwise stock device if an OTA is received.
If you really want to remain stock, except LTE enabled, and are unlocked, download the TWRP image and have working ADB and fastboot, boot TWRP with the command
fastboot boot openrecovery-twrp-2.8.2.0-mako.img
then flash the LTE enabler ZIP... Or just use the Wugfresh's toolkit and flash the ZIP... both options will not install TWRP, just boot a temp copy to flash the needed files, leaving every thing else but the radios and LTE enable SQL database changes completely stock.
Remember this will only enable Band 4 LTE (1700/2100Mhz AWS), it doesn't enable any other LTE as it isn't supported in the hardware, and that band is only used in Canada, Mexico, USA, and a few central american countries.
BTW, this has been discussed and walked through step-by-step in the LTE Enabler thread and Mako Hybrid modem thread, if people would bother to read more then the first and last post, it would be right there...
fr3quency said:
1)TWRP isn't a ROM but a Recovery
2)Is it that bad to install a custom recovery in order to achieve this thing?
3)If it is, what are you doing on XDA?
4)Just install TWRP
5)Just flash the .zip file
6)Just do it.
Click to expand...
Click to collapse
Thanks fr3quency. Sorry I am still learning and getting used to all the terms.
I had my TWRP recovery installed to enable LTE in Kitkat, but had issues in Lollipop OTA as it lands in TWRP Screen during update and i am lost, not knowing what to do. So I flashed it with Stock and then did the OTA. Looking at XDA if there are any options without TWRP or overcome the problem i had in future OTA.
acejavelin said:
Does everyone forget you can BOOT recovery and NOT flash it?!?! I understand completely why the OP doesn't want TWRP, it will stop further OTA's and cause bootloop conditions on an otherwise stock device if an OTA is received.
If you really want to remain stock, except LTE enabled, and are unlocked, download the TWRP image and have working ADB and fastboot, boot TWRP with the command
fastboot boot openrecovery-twrp-2.8.2.0-mako.img
then flash the LTE enabler ZIP... Or just use the Wugfresh's toolkit and flash the ZIP... both options will not install TWRP, just boot a temp copy to flash the needed files, leaving every thing else but the radios and LTE enable SQL database changes completely stock.
Remember this will only enable Band 4 LTE (1700/2100Mhz AWS), it doesn't enable any other LTE as it isn't supported in the hardware, and that band is only used in Canada, Mexico, USA, and a few central american countries.
BTW, this has been discussed and walked through step-by-step in the LTE Enabler thread and Mako Hybrid modem thread, if people would bother to read more then the first and last post, it would be right there...
Click to expand...
Click to collapse
acejavelin, Yes I wanted to be on stock and LTE Enabled on T-mobile, wanted to check if it can be done with out TWRP and erasing all content.
s.rajkumar said:
acejavelin, Yes I wanted to be on stock and LTE Enabled on T-mobile, wanted to check if it can be done with out TWRP and erasing all content.
Click to expand...
Click to collapse
Gotcha... Only real requirement is you must be unlocked, and there are ways to unlock without wiping... Google can be your friend for that info. ?
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Safestrap no longer works with lollipop. Flashfire is the only real way to install zips after android 5.0.
Cheers,
B.D.
Nakerenski said:
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Yeah I'm having the same problem EXACT problem, feel like I bought this phone for no reason. But, I'm having the idea of downgrading to 4.3 somehow (If it's even possible, Odin maybe?) and installing SafeStrap there, and from there I'll install a custom 6.0 ROM.
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
bftb0 said:
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
Click to expand...
Click to collapse
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by
bftb0 said:
- get unlocked
Click to expand...
Click to collapse
do you mean to SIM-unlock? Cheers.
GoatH3ad said:
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by do you mean to SIM-unlock? Cheers.
Click to expand...
Click to collapse
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
bftb0 said:
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
Click to expand...
Click to collapse
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
GoatH3ad said:
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
Click to expand...
Click to collapse
Did you:
- Check to make sure your phone CID value starts with 0x15 ?
- Record any error messages that occurred in either of the two runs of the unlocker program?
- Boot into Odin Mode to see if it says "MODE: DEVELOPER" in the last line of text over in the upper left hand side of the Odin/Download screen?
The symptoms you mention sound as if you are rooted, but failed to unlock the bootloader.
I note that you would not be asking these questions if you had read THE WHOLE THREAD as I suggested. Would you prefer that I stop helping?
Hi Guys,
Long story short, I bought the LeEco Pro 3 US version due to the awesome Tmobile network support. The modem supports band 12 and WiFi calling and I was happy with it. But eventually notification issues and the horrible EUI got under my skin and I decided to install CM13 keeping the phone as untouched as possible so that I can revert back to stock whenever needed.
I followed below steps:
1. Enabled developer options and enabled USB debugging.
2. Went the Developer Options and enabled OEM Unlocking.
3. Did adb reboot bootloader to get into the bootloader menu.
4. Did fastboot unlock-go command to unlock the bootloader. I noticed that if I did this command and rebooted the phone, the phone reverted back to being locked again. But I could run the command again from bootloader screen and unlock it (as long as the developer options had the OEM unlocking enabled). So I was never permanently unlocked, just unlock at will whenever I wanted.
5. Then I downloaded the twrp.img file and from fastboot screen i did fastboot boot twrp.img, which booted me inot twrp screen. I was able to switch the language to english but i didnt do the permanent system modification. I did not root the phone as well through the menu.
6. Now, I plugged in a USB OTG drive in the phone. Usb OTG drive had CM13 ROM + Gapps on it.
7. Using the TWRP menu, I did a factory data reset and made a backup of all partitions of the LeEco Phone and saved it into USB OTG drive.
8. Then I installed the CM13 rom on the phone. Followed by Gapps and then rebooted the phone. The phone wouldnt boot.
9. I immediately rebooted the phone into the fastboot menu and tried to run the fastboot boot twrp.img, and got an error message that the device is not unlocked. Which is when i noticed that the phone is bricked.
So Long story short, I have a locked bootloader and I want to to retain my modem. I was given a suggestion to boot into the stock recovery and put the x720 update.zip file and install it. But that would flash the CN modem as well. Can I delete the modem file from the CN rom and flash the update.zip? Can someone help me there? All I want is the modem for the US rom and CM13, thats it.
Thank you guys for reading this post, it helps to talk to XDA about such issues, my wife would just kick my butt because I broke a phone, again!
Did you wipe the system using twrp before installing CM?
sunbinyuan said:
Did you wipe the system using twrp before installing CM?
Click to expand...
Click to collapse
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.
This is the reason why I am hesitant to do this thing as there are no clear (step-by-step) procedures and there is no solid benefit (in fact your will lose some features). Can't it be possible to just create a CM or any other ROM that could be downloaded and rename into update.zip and load it directly renaming the X720 ROM? ^_^
Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img
srikanthc said:
Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img
Click to expand...
Click to collapse
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.
zoid_99 said:
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.
Click to expand...
Click to collapse
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk
ceo.mtcl said:
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.
zoid_99 said:
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.
Click to expand...
Click to collapse
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk
ceo.mtcl said:
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
That is from the US baseband. That rom will convert a CN install back to a US install.
zoid_99 said:
That is from the US baseband. That rom will convert a CN install back to a US install.
Click to expand...
Click to collapse
Thank you, is that from your phone or did you found it in some other post out here that I missed Zoid? I'm just looking for source of the file.
Sent from my LEX720 using Tapatalk
It's from this thread.
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
"
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
"
ceo.mtcl said:
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.
Click to expand...
Click to collapse
Sorry for the late answer but to add to that, it happened to me that the ROM didn't have a wipe script thus bricking another of my device. I reinstalled it after wiping the system and it worked.
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal