Related
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
FIXED, Just type this adb command when you are in recovery mode....
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
BunnyHoo said:
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
Click to expand...
Click to collapse
I have the same problem when i select factory mode on bootloader then the phone starts only...
Otherwise it boots into twrp recovery
I have the same problem. Only boots into system via bootloader.
Otherwise it boots into twrp recovery.
After successfully booting into system it told me "system update failed".
I guess its because the system update routine is to be flashed via stock recovery and therefore its booting into recovery until it is flashed? Just guessing, but if so could I just flash the update manually?
Thanks in Advance :good:
same here, ps. thanks for the tip of boatloader !!
bubo23 said:
same here, ps. thanks for the tip of boatloader !!
Click to expand...
Click to collapse
np, i still w8 for a solution!, i try some methods but not seems to work
Xt1687 here - same issue. Can I get confirmation that flashing the stock firmware fixes it?
Sorry if I'm wrong you cannot update when bootloader unlock ,have to wait some one make a fash zip so we can fash on twrp
Same here, I have to go to Mount then check System and then Reboot, Bootloader and finally Start. It's very annoying. I tried some ADB commands but nothing seemed to work.
Update: So I got annoyed enough by it to finally flash a different rom, wiped /data /system /cache and installed
Cosmic-OS 3.1 Universe but still can only boot via bootloader...
Any suggestions? Do I have to reformat the whole phone in bootloader via Computer?
Thanks in advance :good:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
I'll try bro, thanks.:good:
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
IT WORKS!!!!, THANKS A LOT!.
Just TYPE FIRST CODE and see the magic!
It worked, thanks for the link!
Hello i have a probleme twrp in my moto g5 plus i unlock bootloader i install twrp but if i want to make a reboot into twrp didnt work . The one methode for reboot into twrp is reboot bootloader and press star , plz i need a solution for normal reboot
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html
Solved (update)
In the end I finally understand that it was possible reinstall a stock rom with Android Nougat, the hard part was find the correct stock rom, then with fastboot method, one command at the time I managed to get back my phone with stock Nougat and solve the reboot issue.
Now I will wait if the official Oreo update comes for this phone too and see if it can be updated.
High everybody's, I see there's few trend that talk to the same problem I'm experiencing with my moto g4, but none one get a solution to this, so I try too.
First, I'm using a resurrection remix rom (nougat), when I reboot or turn off and then on again the phone goes always in recovery (twrp). So I have to select reboot to bootloader and from there select start to properly boot the phone.
I already try using this command from my PC with the phone connected in fastboot mode:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
But nothing happened.
I can change the ROM if it worth to solve the problem, also I see there's a resurrection remix with android Oreo or wait for official Oreo ota that could possibly be on line soon.
Second, in case I can't solve it with a custom rom, there's a way to come back to the original ROM (android 6), and wait for the official update or the downgrade it is impossible?
Thanks to anyone that can give me any advice or help.
Well, how did you fix the recovery boot issue?
shadymnms said:
Well, how did you fix the recovery boot issue?
Click to expand...
Click to collapse
Hi, thanks to the help of @echo92 in this forum, here the link of the topic: https://forum.xda-developers.com/mo...e-nougat-to-marshmallow-t3487201?goto=newpost
He share the proper and last official nougat stock ROM NPJS25-93-14.7-8, is specific to XT1625/XT1644 my device it's XT1625.
Then connecting my device to my PC and using fastboot command I reinstall each part of the stock firmware.
If you search the way to use fastboot command here one of the topic where explain it: https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Bye