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.
Related
Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/
noob here with a question... rooting is the same as unlocked bootloader??
coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.
I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?
flash custom recovery first, from there flash the rom
if you're s-on, bootloader is still locked....
artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying
I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.
how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.
HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.
Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.
I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.
Hey. I had rooted 5.1.1 Moto X Style and did a return to stock 5.1.1. eu version (relocked bootloader). After booted up, I received update to Marshmallow, I installed it. It worked. Later I wanted to root it, so I unlocked bootloader again and also did flash custom recovery - TWRP (twrp-2.8.7.1-clark). Later I restarted device and its was stuck on logo of Motorola. Nothing boots up.
Cant find solution for this. Thanks.
UPDATE:
Solved my issue here.
UPDATE2:
If there is problems upgrading your device to Marshmallow, I would suggest install custom ROM TruPureXMM with custom KERNEL Frankenclark. I am using this combo for long period of time and now I can suggest to others too!
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
dgato said:
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
Click to expand...
Click to collapse
You need to reflash the LP radio from the restore all file ( NON-HLOS.bin ). That should do it.
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
JayShams said:
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
Click to expand...
Click to collapse
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
ChadMan097 said:
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
Click to expand...
Click to collapse
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
JayShams said:
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
Click to expand...
Click to collapse
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.
Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
JayShams said:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
Click to expand...
Click to collapse
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262
Its Pure modem with band 12 fix.
I was using his Rom for some hours and didnt like it, my personal opinion:
Good: easy to install; twrp, supersu, xposed is working.
Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.
Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.
patt2k said:
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
Click to expand...
Click to collapse
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
ChadMan097 said:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
Click to expand...
Click to collapse
Either do systemless or 2.52 had same issue til I flashed 2.52
Sent from my XT1575 using Tapatalk
Solved my issue here.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
donebrasko said:
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Click to expand...
Click to collapse
For this you need adb files on your PC.
You should read this thread, for how to get this files on your PC.
Then:
Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.
But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!
Good luck!
Kennyeni said:
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
Click to expand...
Click to collapse
Hello!
Have you read my other thread?
I have explained all my steps there, my device is Moto X Style (XT1572).
But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!
Good luck!
No luck with reflashing NON-HLOS.bin
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
[email protected]@lker said:
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
Click to expand...
Click to collapse
Lets start from beginning.
What is your device codename (region)?
Hello.
With hexeditor, I've seen that:
MM aboot:
Code:
fastboot mode.
dload mode key sequence detected
%s%sINFO%sFAILCould not allocate memory for fastboot buffer
.app/aboot/fastboot.cunknown reasonunknown commandOKAYdata too largeDATA%08xdwcUSB30 needs to be enabled for this target.
getvar:download:version0.5fastboot
LP aboot:
Code:
fastboot mode.
dload mode key sequence detected
oem read_regoem read_pmicflash:erase:continuerebootreboot-bootloaderoem unlockoem lockoem verifiedoem device-infopreflashoem enable-charger-screenoem disable-charger-screenoem select-display-paneloem boot-cpusoem big-freqoem small-freq boot_cpus= androidboot.earlyboot_cpus=%s%sCould not allocate memory for fastboot buffer
.app/aboot/fastboot.c
You can see the difference ?
All commands are erased on MM aboot so, no chance for us to unlock or using fastboot on our phone with MM
murigny64 said:
Hello.
With hexeditor, I've seen that:
MM aboot:
Code:
fastboot mode.
dload mode key sequence detected
%s%sINFO%sFAILCould not allocate memory for fastboot buffer
.app/aboot/fastboot.cunknown reasonunknown commandOKAYdata too largeDATA%08xdwcUSB30 needs to be enabled for this target.
getvar:download:version0.5fastboot
LP aboot:
Code:
fastboot mode.
dload mode key sequence detected
oem read_regoem read_pmicflash:erase:continuerebootreboot-bootloaderoem unlockoem lockoem verifiedoem device-infopreflashoem enable-charger-screenoem disable-charger-screenoem select-display-paneloem boot-cpusoem big-freqoem small-freq boot_cpus= androidboot.earlyboot_cpus=%s%sCould not allocate memory for fastboot buffer
.app/aboot/fastboot.c
You can see the difference ?
All commands are erased on MM aboot so, no chance for us to unlock or using fastboot on our phone with MM
Click to expand...
Click to collapse
Did you try to modify Mm aboot?
No can't modify, it's RSA signed.
But, if you see more, there is %s%sINFO%sFAIL after "detected", and OKAYa little further. That is not present in LP aboot.
Perhaps, we have to enter a "magic keyword" to decrypt some features ?
I know, santa clause doesn't no exist
maybe @Unjustified Devcan be our santa, where is he
yash_rathore25 said:
maybe @Unjustified Devcan be our santa, where is he
Click to expand...
Click to collapse
or waiting for info from Alcatel (sending mail)
murigny64 said:
or waiting for info from Alcatel (sending mail)
Click to expand...
Click to collapse
@Alek Dev and myself also sent mail to them but no reply till date
yash_rathore25 said:
@Alek Dev and myself also sent mail to them but no reply till date
Click to expand...
Click to collapse
Yes i sent 3 emails but there's no reply
Alek Dev said:
Yes i sent 3 emails but there's no reply
Click to expand...
Click to collapse
yeah so wierd ?
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
Looks like instead of waiting for unlock, i have to do whole process to gain root.
which will cost me heavy
Alek Dev said:
Yes i sent 3 emails but there's no reply
Click to expand...
Click to collapse
Can you create a "petition" thread with info to send a mail to alcatel to unlock phone and fastboot ?
more mails, more bored :cyclops::silly:
murigny64 said:
Can you create a "petition" thread with info to send a mail to alcatel to unlock phone and fastboot ?
more mails, more bored :cyclops::silly:
Click to expand...
Click to collapse
LOL
HERE'S
link to thread
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
famewolf said:
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
Click to expand...
Click to collapse
Doesn't work..i tested..it will stay at alcatel powered by android because again THE system to boot needs adintional new partitions
famewolf said:
You want MM with fastboot? All you need to do is backup your existing MM via twrp. Use mobile q to downgrade your device to 5.0.2. Unlock bootloader and flash twrp then restore your backup of system/boot. You will be just like the non 6045i variants..on mm with full fastboot and twrp.
Click to expand...
Click to collapse
Yes, everybody know that. But when mobile upgradeQ are released with MM, how can you do
We have to think to future.
murigny64 said:
Yes, everybody know that. But when mobile upgradeQ are released with MM, how can you do
We have to think to future.
Click to expand...
Click to collapse
Then I'd use the panasonic eluga software and flash a locally saved copy. In future I won't be installing Alcatel updates directly. I'll grab the update.zip and remove any code for partitions other than system/boot. Should allow retention. Your point is still understood however. The first time I've ever used mobile q was tonight and ironically it was because I was trying to build a flashable zip to restore the old partitions so users could restore fastboot without having to run mobile Q. I managed to turn it into a paperweight then recovered it but decided to go ahead and use mobile q to downgrade while I was at it. I'm a linux user so I had to set up a windows laptop for this purpose.
Flashable zips for MM and Fastboot
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Contents: twrp 3.0, aboot,spl1,hyp,rpm and tz. Does not overwrite modem.
famewolf said:
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Click to expand...
Click to collapse
how can i directly flash on MM, stock recovery will not detect it. Previously i was trying to supersu directly from stock MM recovery but it wa not detecting it.
i have to use mobile upgrade q n downgrade n do the whole process
yash_rathore25 said:
how can i directly flash on MM, stock recovery will not detect it. Previously i was trying to supersu directly from stock MM recovery but it wa not detecting it.
i have to use mobile upgrade q n downgrade n do the whole process
Click to expand...
Click to collapse
Stock recovery won't flash anything that isn't signed by Alcatel. You HAVE to use TWRP.
It depends...I'm not sure if they left the fastboot boot command in which just boots a file without installing it....it would allow you to boot twrp and THEN use it to flash my zips.
famewolf said:
Stock recovery won't flash anything that isn't signed by Alcatel. You HAVE to use TWRP.
It depends...I'm not sure if they left the fastboot boot command in which just boots a file without installing it....it would allow you to boot twrp and THEN use it to flash my zips.
Click to expand...
Click to collapse
no it is not letting twrp even to boot.
famewolf said:
How about this then......flashable zips for MM and fastboot.
Install the first one and you get TWRP 3.0 as well as the files you need to restore fastboot access. TWRP will let you boot straight to the bootloader.
Restore the 2nd one and you get TWRP 3.0 as well as the files you need to boot a mm rom.
You can swap between them as needed. You should not even have to mess with your mm rom if you just need quick fastboot access. The files are from a 6045i but should work for any of the variants.
Contents: twrp 3.0, aboot,spl1,hyp,rpm and tz. Does not overwrite modem.
Click to expand...
Click to collapse
Hello @famewolf
I'm becoming lost with all these discussions and things to flash.
I want to flash a MM ROM (material by The Marionette). Py phone is running stock rooted 5.0.2, with fastboot commands working.
Which files do I need to make the MM ROM boot, and not lose fastboot command ? If I do understand, I just need to flash the second zip you provided and flash mm rom. Then , if I lose fastboot, I flash the first one. Do I have understood well ?
frankee207 said:
Hello @famewolf
I'm becoming lost with all these discussions and things to flash.
I want to flash a MM ROM (material by The Marionette). Py phone is running stock rooted 5.0.2, with fastboot commands working.
Which files do I need to make the MM ROM boot, and not lose fastboot command ? If I do understand, I just need to flash the second zip you provided and flash mm rom. Then , if I lose fastboot, I flash the first one. Do I have understood well ?
Click to expand...
Click to collapse
If you want to boot a marshmallow rom then you need the file that says it's to boot a marshmallow rom. You WILL lost fastboot...you however will keep twrp. If you ever NEED fastboot you can flash the other one to temporarily downgrade and then access bootloader/fastboot via TWRP..then when done with fastboot flash the 1st one again to boot a mm rom.
Hi
I am new to the OnePlus 2. When I bought it, stock 5.1.1 installed, I downloaded and installed the latest Marshmallow stock build via an OTA update. I then followed the official OnePlus video guide on unlocking the bootloader and rooting the device. I successfully unlocked the bootloader, flashed TWRP and then went on to flash SuperSU. Unfortunately, then device did not reboot - and I was soft-bricked, stuck on the boot animation. I am not sure what went wrong here.
In order to un-brick and recover my device, I downloaded the latest Marshmallow OxygenOS 3.0.2 zip from OnePlus. I was able to get this onto my device and I flashed it successfully in TWRP, and all is well.
My questions are:
1) Having flashed the latest stock, Marshmallow OxygenOS 3.0.2, will my bootloader still be unlocked?
2) Will I still have TWRP recovery, or stock recovery?
3) How can I successfully root?
Thank you in advance
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
qingmui said:
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
Click to expand...
Click to collapse
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
pretty pixel said:
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
Click to expand...
Click to collapse
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
LordHelmchen89 said:
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
Click to expand...
Click to collapse
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
pretty pixel said:
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
Click to expand...
Click to collapse
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
LordHelmchen89 said:
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
Click to expand...
Click to collapse
Thank you for the reassurance
Just bought this phone...i tried using the toolkit and the recovery menu...phone wont boot into fastboot mode. Can someone point me in the right direction on how to fix this.
Axebladewarrior said:
Just bought this phone...i tried using the toolkit and the recovery menu...phone wont boot into fastboot mode. Can someone point me in the right direction on how to fix this.
Click to expand...
Click to collapse
well it actually shouldn't. axon7toolkit should flash fastboot onto your phone
But I thought the Chinese still had fastboot... Did you enable OEM unlocking?
Try enabling USB debugging too, and use a pc with ADB to issue 'adb reboot bootloader'. maybe it'll get there,maybe not
Thanks for the help...i flashed b13 and eventually unlocked the bootloader, flashed twrp and root however when i flash a rom the zte screen comes up then the phone shuts down
Axebladewarrior said:
Thanks for the help...i flashed b13 and eventually unlocked the bootloader, flashed twrp and root however when i flash a rom the zte screen comes up then the phone shuts down
Click to expand...
Click to collapse
Just don't lock the bootloader again, like, ever
Did you install the Universal Bootstack and the modem file before flashing the ROM?
Choose an username... said:
Just don't lock the bootloader again, like, ever
Did you install the Universal Bootstack and the modem file before flashing the ROM?
Click to expand...
Click to collapse
That was the problem....i flashed them both and the rom flashed with no problems...thanks for all the help. Last phone was the original nexus 5...was a breeze to flash
Axebladewarrior said:
That was the problem....i flashed them both and the rom flashed with no problems...thanks for all the help. Last phone was the original nexus 5...was a breeze to flash
Click to expand...
Click to collapse
Just read everything... you know, forgetting about stuff like that can DFU-brick your phone or lose your IMEIs