Related
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
hi, by original system image did you mean the stock system image from stock rom? if it is, you need to download the whole Asus Zenfone 2 Firmware from the Official Asus support website and follow either these two steps:
3.1 Tools Required:
Asus USB Drivers
ADB installed on your PC/Laptop
Asus Zenfone 2 Firmware from the Official Asus support website
3.2 Flashing stock Asus Zenfone 2:
Method 1:
Turn off your Zenfone 2
Go to recovery mode
Select apply update from ADB
Connect your zenfone 2 with USB cable to your PC/laptop
Open command prompt in Windows (in the same folder where ADB is located)
Check connection by typing adb devices in the command prompt.. If connection successful there will be a list of Zenfone 2 device.
Type
Code:
adb sideload file.zip (where file.zip is the file name of the Asus firmware)
Wait until the process is complete
Method 2:
Copy Zenfone 2 Firmware to the SD card
Enter Recovery mode
Select Update via SD card
Select firmware
codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
Some modules have been known to cause issues, there is a thread with a list of known mods that are safe to use in Q&A I believe...
cangcan said:
hi, by original system image did you mean the stock system image from stock rom? if it is, you need to download the whole Asus Zenfone 2 Firmware from the Official Asus support website and follow either these two steps:
3.1 Tools Required:
Asus USB Drivers
ADB installed on your PC/Laptop
Asus Zenfone 2 Firmware from the Official Asus support website
3.2 Flashing stock Asus Zenfone 2:
Method 1:
Turn off your Zenfone 2
Go to recovery mode
Select apply update from ADB
Connect your zenfone 2 with USB cable to your PC/laptop
Open command prompt in Windows (in the same folder where ADB is located)
Check connection by typing adb devices in the command prompt.. If connection successful there will be a list of Zenfone 2 device.
Type
Code:
adb sideload file.zip (where file.zip is the file name of the Asus firmware)
Wait until the process is complete
Method 2:
Copy Zenfone 2 Firmware to the SD card
Enter Recovery mode
Select Update via SD card
Select firmware
Click to expand...
Click to collapse
Yes, with original image I mean the stock system image from the stock rom.
I'll try method 1 but I have a question before:
Since I'm able to boot the phone into boot mode (where it receives adb commands) but I'm not able to boot it into recovery mode (it tries to load something and then stops with error)....do you know if it is the same to send adb commands in boot mode instead that in recovery mode (and I refer in particular to the command: "adb sideload stockasusfw.zip")?
Thank you guys
codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
hmm.. i don't see the point to flash original system image if you want again to install Xposed.
Just reflash system.img preroot and install again your Xposed. That's all. (i've done that many times after trying some modules in Xposed getting me in bootloop)
Go in fastboot mode (power + volume UP) and fastboot flash system system.img and you're good to go to install again your xposed framework.
Preroot image is the same as the originale, but with SuperSu in addition.
ilos said:
hmm.. i don't see the point to flash original system image if you want again to install Xposed.
Just reflash system.img preroot and install again your Xposed. That's all. (i've done that many times after trying some modules in Xposed getting me in bootloop)
Go in fastboot mode (power + volume UP) and fastboot flash system system.img and you're good to go to install again your xposed framework.
Preroot image is the same as the originale, but with SuperSu in addition.
Click to expand...
Click to collapse
It's because prerooted image doesn't allow OTA updates.
However thanks, as I've said before this is my first bootloop and I was a little in panic.
Now that everything is clear I'm going to download and flash the system image.
In boot mode
Code:
fastboot flash system system.img
and it said something similar to this
Code:
target reported max download size of 518205818 bytes.
Invalid sparse file format at header magi fastboot
As I've said in a previous post, the phone did not enter into recovery mode because it got stucked on the "dead" robot. Now, don't know what it happens but after some minutes of "dead" robot, while I was surfing the net looking for solutions, it has finally loaded the recovery mode and from apply update from ADB I've tried
Code:
adb sideload blablabla.zip
the result was
Code:
r: device not found
After that...since I were into recovery mod, I've tried a wipe/factory reset and unexpectedly, the simplest thing has worked! I've got my phone back again.
I'm happy thought I don't understand the errors while flashing with adb and don't understand why the phone get at least 5 minutes of "dead" robot before entering into recovery mode...
Thanks for your support and for your patience
HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Should use Asus flash tool. http://forum.xda-developers.com/showthread.php?t=3452082
Sent from my Zenfone 2 using Tapatalk
debopriyobasu said:
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
Click to expand...
Click to collapse
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
kenbo111 said:
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
Click to expand...
Click to collapse
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
sukhwant717 said:
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
Click to expand...
Click to collapse
It was just a question.
Sent from my Zenfone 2 using Tapatalk
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
debopriyobasu said:
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
Click to expand...
Click to collapse
Good to know that was helpful.
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).