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.
Related
Hello,
Is it possible to update from 5.0 to 5.1 if i have unlocked the bootloader? I also have TWRP. I downloaded the 5.1 update, but when i want to install it the phone reboots and i get into TWRP menu. Is there any way to flash the OTA update without losing my current data on the phone?
Thank you!
Dealing with the same problem here.
IIRC TWRP automatically handled OTA updates in the past but it doesn't seem to be working anymore.
What was the procedure you were using before? You just installed as a normal zip from TWRP ?
For the ota to work you have to be 100% stock system, recovery, and kernel. I'd just flash the system and boot images from 5.1 in fastboot to update.
Sent from my Nexus 5 using XDA Free mobile app
So sad. I will lose all the stuff I have on the device.
tzeus said:
So sad. I will lose all the stuff I have on the device.
Click to expand...
Click to collapse
Not if you just flash the System and Boot images and remove -w from the Flashall.bat command to prevent the wipe instead of using the OTA. If you use the OTA, you will have to be stock as the previous posted stated, which since you are rooted with a custom recovery, would require you to flash the stock image, wiping your device, before you could run the OTA. This is the result of a change in the way Android 5.+ authenticates, which is why it worked previously. It now checks the whole partition, and one byte out of place will abort it.
That said, you can always backup your phone (which is a good thing to do anyway before flashing/upgrading) to prevent data loss.
Edit: Actually, thinking about it, I think Wugs added a No Wipe option to his toolkit, just flash System and Boot images from there is likely easiest for you.
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
tzeus said:
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
Click to expand...
Click to collapse
To be clear, you do not need to relock your bootloader. You can just flash 5.1 and then root and install a custom recovery like TWRP again, yes. If you are not familiar, Wug's NRT make this a breeze. Once you get 5.1 installed, just hit root. It will install the latest TWRP version and root/install SuperSU and Busybox for you.
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
tzeus said:
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
Click to expand...
Click to collapse
No, download the image and extract it. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
MM modified DM removed removed force/encryption and custom sepolicy to allow system root.
DOWNLOADS FOR 7.0 OFFICIAL
NRD90M(Decrypted)(System_root hopefully coming soon)
https://drive.google.com/file/d/0B4yuQy7Zn1WSYm5sTXNhZmsxcVk/view?usp=sharing
DOWNLOADS FOR MM
MTC20F(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSeVc1bjdDOGFETDA/view?usp=drivesdk
MTC19V(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSY3FZaVNXMjhEN2c/view?usp=drivesdk
MTC19T(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSWXMyRHF1bGQ2YUU/view?usp=sharing
MCH19q
https://drive.google.com/file/d/0B4yuQy7Zn1WSclZ6dGhCNXNUUEk/view?usp=drivesdk
DOWNLOADS FOR ANDROID N Preview builds
NPD90G
https://www.androidfilehost.com/?fid=24572369242689017
NPD56N
https://drive.google.com/file/d/0B4yuQy7Zn1WSM3FORTl4ejlUV2M/view?usp=sharing
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSTklfZW1McXZxQUk/view?usp=drivesdk
NPC91k
https://drive.google.com/file/d/0B4yuQy7Zn1WSSG5WTGNBMHVvZXc/view?usp=sharing
DIRECTIONS
fastboot flash boot boot.img
Good to see your work here as well. :good:
Would love to see more.
F.A.Q - Frequent Answers and Questions
Bringing the love to 5x!!!
To users:
Don't question just follow his directions and profit
Sent from my Nexus 5x using XDA-Developers mobile app
Tigerstown said:
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
So this is a decrypted and DM checks have been removed. flastboot this boot.img when flashing N preview factory imgs. Also i will be posting a MM modified boot.img the has DM removed removed force/encryption and custom sepolicy to allow system root. but for now here is the N boot.img
DIRECTIONS
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
To my knowledge you need to decrypt phone then flash N and before boot flash decrypt boot img then boot twrp then flash super su 2.71. To be decrypted rooted N.
Now to begin that process you need a decrypted phone which is why i am waiting for m decrypt boot begore i proceed.
Tigerstown can correct me if i am wrong.
Sent from my Nexus 5X using XDA-Developers mobile app
m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
m.daziale said:
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
Click to expand...
Click to collapse
No bootloop guarantee, until you do something different than this. :victory:
DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This is exactly what I was just going to reply. If your on N flash boot.IMG and decrypt using fastboot like said above.
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
Yes, perfectly alright. Avoid the recovery image, in case you have TWRP installed.
zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
that is How I do it on my 6P. After flashing I boot to twrp and do factory reset myself. You don't need to flash the N recovery.
Sent from my Huawei Nexus 6P using XDA Labs
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
exploreresp said:
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
Click to expand...
Click to collapse
Hey no problem just glad to be helping out.
Sent from my Huawei Nexus 6P using XDA Labs
Op has been updated added MM MCH19q support. Still have to work on sepolicy for system root on 5x like I have it for 6P. Once I get it right I'll update with that.
Sent from my Huawei Nexus 6P using XDA Labs
aaaaand thanks again for the MM boot.img ! Glad to have both actually
Thanks for this, waiting for rootable version.
Hey thanks you for this
But if i flash only the modified boot on android n and i don't make a userdata wipe ?
What happen ?
khanjui said:
Thanks for this, waiting for rootable version.
Click to expand...
Click to collapse
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Tigerstown said:
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I can test it.
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
EvanVanVan said:
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
Click to expand...
Click to collapse
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
+1 Flashfire
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
EvanVanVan said:
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
Click to expand...
Click to collapse
The other issue with TWRP was backing up and restoring the EFS partition, it seemed that 3.0.2-1 corrupted it on restore which would be a problem. They did have a work around. They suggested using -0 would be fine. I have -2 and did a N to N restore with no issue, but I did not restore EFS. I'm always extra careful with new versions, I tend to backup my data and backups off-phone just in case.
dratsablive said:
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
Click to expand...
Click to collapse
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
smallvan said:
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
Click to expand...
Click to collapse
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
dratsablive said:
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
Click to expand...
Click to collapse
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
smallvan said:
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
Click to expand...
Click to collapse
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
dratsablive said:
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
Click to expand...
Click to collapse
I believe I am looking for a suitable way to upgrade my 6p from MM to N that I have explicitly stated at my wrong thread post. This is absolutely not my intention to return my 6p back to stock of MM. And there is every reason to upgrade to N, thus, vendor.img is no doubt a must for an amateur like me.
Nevertheless, thanks for dratsablive kind suggestions.
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. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.
unroot before updating and flash stock recovery
hoodoo_mc said:
Hi. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.
Click to expand...
Click to collapse
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.
muradulislam said:
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.
Click to expand...
Click to collapse
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.
hoodoo_mc said:
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.
Click to expand...
Click to collapse
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.
muradulislam said:
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.
Click to expand...
Click to collapse
Many Thanks.
I think I know what I'm doing now.
(famous last words)
hoodoo_mc said:
Many Thanks.
I think I know what I'm doing now.
(famous last words)
Click to expand...
Click to collapse
Don't worry mate, we will all be here
muradulislam said:
Don't worry mate, we will all be here
Click to expand...
Click to collapse
Thanks for the support.
OK, I'm going to leave it for today, and try again tomorrow.
Basically, I go through the steps to flash the stock recovery but can't complete this first step ;
By the way, there are 2 files in the update.app - recovery.img and recovery2.img. Does it matter which one I use?
And does the header file need to be in the same location, or can that be ignored for this step?
Anyhoo, after flashing via command line, and then do the final 'fastboot reboot' the phone just goes into a continuous boot loop until I interrupt by holding down all of the buttons.
Am I doing something wrong here?
I seem to remember I had this same issue when I first got the phone and was trying to get TWRP recovery installed using this method, and can't for the life of me remember how I got through it
@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system system.img
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!
non-toxic said:
@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system.img system
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!
Click to expand...
Click to collapse
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.
hoodoo_mc said:
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.
Click to expand...
Click to collapse
Enjoy your phone buddy... Don't forget to get greenify and titanium backup.
I love these two apps.
;
muradulislam said:
Don't forget to get greenify and titanium backup.
Click to expand...
Click to collapse
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (on my device = 6%/24h! -GSM2 -no WLAN -no GPS -noBT -no DATA sync)
non-toxic said:
;
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (6%/24h!)
Click to expand...
Click to collapse
For me it does make sense as I don't want Facebook and similar apps to run in the background nagging me with updates. I want them to run and update myself when I have time and tap on them. For battery, it does save some juice for me.
What's the comment about TWRP and Huawei update.
I am not sure what you mean by it.
ah, ok i see... it is neccesarry for YOU!
BtT. and thx bro:good: