Installing twrp with locked bootloader - Xiaomi Mi Max Guides, News, & Discussion

I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom

Nice... Did your bootloader get unlocked after you flashed the eu global ROM?

nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter

I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!

Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp

Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!

My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working

tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)

same for me!

g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.

Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.

Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.

Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded

There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.

I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!

Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post

After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB

alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk

iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix

I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.

Related

Need TWRP Backup of UK version, a2017g

Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
shia786 said:
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Click to expand...
Click to collapse
djona12 said:
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
Click to expand...
Click to collapse
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
i cannot seem to find tenfar tool anywhere
DrakenFX said:
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
Click to expand...
Click to collapse
i have found the tool but i think i flashed the US version of the boot image now my phone does not boot up at all,
it goes to stock recovery
if i turn the phone on then it goes to ZTE LOGO for about half a second then the screen goes blank
i can access fastboot but only through stock recovery which when i go to bootloader i cannot run any fastboot commands, even if i run fastboot reboot it does not reboot the phone at all
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Cricius said:
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
Click to expand...
Click to collapse
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
DrakenFX said:
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
Click to expand...
Click to collapse
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
shia786 said:
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
Click to expand...
Click to collapse
Try enable " OEM Unlocking " under developers option and try again
DrakenFX said:
Try enable " OEM Unlocking " under developers option and try again
Click to expand...
Click to collapse
I cannot access the software at all, all I got is stock recovery
shia786 said:
I cannot access the software at all, all I got is stock recovery
Click to expand...
Click to collapse
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
DrakenFX said:
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
Click to expand...
Click to collapse
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
shia786 said:
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
Click to expand...
Click to collapse
You can just boot into TWRP using tenfar tools and Flash the zip.
DrakenFX said:
You can just boot into TWRP using tenfar tools and Flash the zip.
Click to expand...
Click to collapse
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
shia786 said:
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
Click to expand...
Click to collapse
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
shia786 said:
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
Click to expand...
Click to collapse
Hi,
I have the exact same issue
Did you find a way to get your phone booting again ?
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
That doesn't work on the A2017G, you have to use "adb reboot edl", so you see the problem. Also, the A2017G doesn't actually have an EDL mode but something very similar that's ZTE call Handset diagnostic Interface - quite why, who knows, this is ZTE after all...

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.
Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk
Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?
No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.
colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk

[Guide] Flash Stock Rom Asus Zenfone 2 ZE551ML

Hey Guys. This guide will help you if
1. If Using Custom Rom and want to revert to latest stock rom.
2. If Stock Rom got corrupted or became laggy.
3. You want to reinstall stock rom.
Warning:
1. Method 1 require unlocked bootloader. If you want to unlock then go Here . Method 2 doesn't. Don't worry.
2. This will clean your phone just like new phone.
3. First read the post twice carefully then proceed.
4. ALL .bat FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2
5. I may change name of files in folder. Use common sense to identify them.
Pre-requisites:
1. Charge your phone atleast 60%.
2. Backup any important data you might not wanna loose to either sd card or usb drive or pc.
3. Copy the rom zip in the sd card of your phone. (The one with size in GB)
4. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
5. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
4. Common sense, patience.
Download Link:
For Method 1
Click here Android Filehost
Download these folders: TWRP, STOCK RECOVERY, STOCK ROM, DRIVERS
For Method 2
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Procedure:
METHOD 1​Step 1. Flash TWRP recovery if not installed by using "TWRP.bat" (Given in twrp folder) in fastboot mode or bootloader mode whatever you call it.
Step 2. Go to Twrp recovery then choose "wipe" then choose "Advance wipe" and tick everything except "SD card or external sd card". then swipe to wipe.
Step 3. Go to fastboot/bootloader mode and flash stock recovery running appropriate .bat file. It is given in "Stock Recovery" folder.
Step 4. When the command executes from the above step, Go to "recovery" by pressing volume down button, then press "power" button.
Step 5. You will see a dead android logo. Nothing else. Then go to stock recovery options.
If you don't know how then use following methods
Method 1:
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
Method 2:
Go to fastboot mode. Connect your device and open command prompt there. Then Type
Code:
fastboot erase cache
Step 6: You should see stock recovery options. Then choose "Update from sd card" and select the rom zip you pasted in SD card.
(If you don't have sd card, then paste rom in internal memory and don't tick "internal storage" in twrp in step 2) But micro
sd is preferable.
Step 7: Wait. Your phone may take 20-30 or more minutes. So leave it on charging.
METHOD 2​Step 1: Download and Install all drivers given in download folder. Download RAW firmware for your phone. See above in download links.
Step 2: Install "ASUS FLASH TOOL"
Step 3: Go to fastboot/bootloader mode on your phone. Run asus flash tool, select your phone model and browse for the raw firmware. Check wipe all data. And start the process.
Step 4: Wait for program to say successful. If it takes more than 30 minutes. Disconnect your phone and check phone if rom installed or not.
If this process does not work. Then switch methods.
If you have any questions, problems .. Just Comment it.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
MOD EDIT: LINK REMOVED
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
2. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
File Credits:
1. RealYoti
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Click to expand...
Click to collapse
Thanks for suggestion. But the reasons​ are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Kapil Tapsi said:
Thanks for suggestion. But the reasons​ are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Click to expand...
Click to collapse
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Click to expand...
Click to collapse
It is a guide only. Users are free to choose from where to download. Thats it. I only shared my collection.
E: footer wrong
E: footer wrong
Installation aborted
I need your help!
I follow the instructions in Method 1 but the device give me this error message when I try to update via SD-card...
May I know whats the solution?
Rom used: Fastboot Rom WW-4.21.40.327
Thank you very much!
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks, finally got it
Hey...when I get to part 6 I get this Error >>
footer is wrong
signature verification failed
installation aborted
Hey..I also Tried Flashing with the method 2 it was installing but i got an error after
Man, this thread saved my ass. thank you for all your time all!
I have the Asus Zenfone 2 ZE551ML with sound issues, (it's only when the phone rings that the speaker works) and I put it into recovery mode to wipe cache/data, but it got stuck while doing that and I forced it off. But now, it's stuck at the Asus Boot logo with the rotating icon underneath.
Please help!!!!
Hello, my 551ml has stock LP, it's rooted with bootloader unlocked and Xposed installed. If I want to install the latest MM with through the raw flashing tool, should I install the MM bootloader first or it is included into the raw file? Thank
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
stevegtrlmk said:
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
Click to expand...
Click to collapse
use asus flash tool
damn my asus flash tool says error flashing image failure.... (remote not allowed to flash this partion)
ow btw i already bricked it cause it only does boot fastboot lol no more android
how do i flash it back again i need to send the phone back to amazon by 18/05 lol i mean i can just send it back and say also that it wouldnt boot cause i tried to reset it to get my touchscreen to work but yeah lol dont want them to refuse my retour
No way to simple flash the stock rom through/keeping twrp in the device, like I do with other Custom Roms?
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
euphrodil said:
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
Click to expand...
Click to collapse
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Kapil Tapsi said:
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks, i'll look for a thread that explain this.
euphrodil said:
Ok thanks, i'll look for a thread that explain this.
Click to expand...
Click to collapse
did you find any?
i want to remove the lineageos and install latest stock LP but i have no clue how to do it

X720 bricked, kind of ;)

Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?
Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.
Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?
1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?
trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode
Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.

Axon 7 not bricked but almost.....pls help

Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck
Following this post, you device should be rescued.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
If your phone can not automatically boot into edl mode, then try follow method.
1) Power off your phone,
2) connect your phone to PC with a USB cable while holding hold vol up and vol down at same time.
here2for said:
Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck
Click to expand...
Click to collapse
Thanks for reply but link is 404...pls resend tks
:::::::::::::::::::::
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
further....
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??
Run command： fastboot devices
If you device show up, then you can flash twrp by command
fastboot flash recovery "path"/"twrp file name".img
here2for said:
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??
Click to expand...
Click to collapse
mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!
....tried to install a couple different roms (placed them on the SD card) twrp....begins to install but then generates the error - "zip signature verification failed" ?? have tried resurrection remix and aokp nougat for axon 7.... get same error. Thoughts please
you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
here2for said:
mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!
Click to expand...
Click to collapse
llaalways said:
you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
Click to expand...
Click to collapse
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck
which model is your phone? A2017U, A2017G, or A2017?
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck
Click to expand...
Click to collapse
I suggest stock rom, you can follow this post to flash it.
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
llaalways said:
which model is your phone? A2017U, A2017G, or A2017?
Click to expand...
Click to collapse
axon 7 almost bricked....
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse
Do not forget install Magisk16.4 after install ROM.
And try factory reset and then reboot disemmcwp.
If there is still problem, try format data again.
here2for said:
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Categories

Resources