Related
Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9
Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.
The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9
So you cannot even access fastboot?
No
Sent from my GalaxyS2 with CM9
This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?
this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes
Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?
yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF
Hi All,
Good day.
Need some help regarding the error I encounter when flashing raw file. The fastboot in my ZF2 text also turns to red which I guess there's something wrong with my zf2. Also when trying to use XFSTK downloader, I get error also. Kindly refer to the images below. Hoping someone could help me regarding this. Thank you so much.
Btw, my phone is currently on Stucked Asus Logo.
Can u boot into stock recovery?
yakub234go said:
Can u boot into stock recovery?
Click to expand...
Click to collapse
Always looping in error and Installing update when I enter recovery mode.
pinuno said:
Always looping in error and Installing update when I enter recovery mode.
Click to expand...
Click to collapse
very first of all stay away from xfst if you are able to go into fastboot
download raw firmware. after that i will tell you commands you have to run step by step
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
just go to fastboot and run following commands. don't use flash tool.
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
fastboot oem unlock
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
first boot may take long time. so have patience
GPT = Grand Partition Table
Beyond my knowledge unfortunately .
Keeping an eye on this thread to see if theres a fix .
Can you describe how you got into this state ?
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
Maybe the file u r flashing is corrupt
pinuno said:
I already have raw file but when I try to flash the raw file via Asus Flashtool, I alway get GPT command failed error.
Click to expand...
Click to collapse
check your personal message folder
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
pinuno said:
Im getting error when try to run 6. fastboot oem partition /tmp/partition.tbl which is GPT command failed error.
Also fastboot oem unlock is unknown command, need on help on this. Thanks,
Click to expand...
Click to collapse
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
ygwstr said:
Hi,
The same problem is occurring in my ze551ml.
I am in great trouble.
Does anyone know the solution?
Click to expand...
Click to collapse
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
flash raw with commands method. run all the commands even if some of them fails. see section how to flash raw without AFT.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
ygwstr said:
Hi
Following the instructions, i changed "2.20.40.194" raw file to zip file and unzipped.
Then, i typed the following command in Commandprompt.
Failed at number 5 and 14, error indication wrote below.
but I typed 1 to 21.
1. fastboot devices
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
failed remote gpt command failed
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
failed remote tee_token_write() call failed return=0xcab1200d
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
However, the loading state at startup is not fixed.
I waited for two hours, but the start screen remained loading.
Click to expand...
Click to collapse
no way to fix until you have UFI box or any other emmc repair box
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
ygwstr said:
Oh, what a thing.
In other words, my device really become a bricked?
If I get UFI BOX it means that I may be able to repair it.
But UFI BOX is very expensive for me.
sukhwant717 thanks for answering my question.
Click to expand...
Click to collapse
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
sukhwant717 said:
absolutely that is for professional repair shops. i am still working on the issue for alternatives. will revert back once i get it worked
Click to expand...
Click to collapse
Thank you
I hope you find another solution to this problem.
sukhwant717 said:
no way to fix until you have UFI box or any other emmc repair box
Click to expand...
Click to collapse
Hi, i have the same problem.
Is there a solution, now?
Thanks
"No Sim Card detected" (due to TWRP backup restore) fix through fastboot commands?
Yesterday I had to restore my phone to a previous ROM (stock MM) from RR 5.8.5 Nightly. This was due to my working from home and needing to generate an RSA soft token, which is set up on an app on the backup, yadda yadda... Anyway, my restore worked fine, and I was able to generate my key and work from home.
However... when I went to use my phone, I noticed that the SIM card was no longer detected. I tried restoring my RR rom, and it too would not detect my Sim card.
In my attempts to find a fix, and then my attempt to restore the stock firmware and bootloader (that seems to be the only fix), I managed to royally hose my phone by attempting to flash the Full Stock LL ROM, which failed and must have overwritten the bootloader and recovery partitions. Trying to turn the phone on resulted in a vibration, but only a black screen. I was able to unbrick the phone using various guides I scrounged up and utilizing XFSTK and IntelSOC drivers, which must be installed when Windows 10 is booted with the special option to install unsigned drivers enabled (hold shift when you click restart, then option 7). I can post what I went through when I get home to my files and stuff if anyone requests it. Asus Flash Tool refused to flash the raw firmware (wrong format my ass), so I had to manually run the fastboot options. Everything was hunky dory after this.
Every fix for the SIM card issue pointed to reverting to stock firmware, which is what I did. However, I'm thinking there must be some key partition that I flashed in fastboot that revived the SIM. I performed the below commands from this thread . Does anyone see a command that screams "I'm fixing sim card issues"?
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Click to expand...
Click to collapse
If we can get the fix for an undetected SIM card after TWRP backup down to a few (or single) fastboot command, it'd be a nice convenience for us all.
Alternatively, does anyone know of a proper way to restore TWRP backups without losing SIM card detection?
UPDATE SECTION
I had found this site while searching for a solution yesterday, and it has the following fastboot commands for fixing the sim issue:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
So in this case, the modem partition is being erased. But I don't see anything in the unbricking fastboot commands that erases the modem partition. Am I just missing it? I could see my IMEI in Sim Slot 1, so maybe it wasn't a modem partition issue.
-------------------------------------------------------------------------------------------------------------------
Found this thread (How did I miss it before?): https://forum.xda-developers.com/zenfone2/general/guide-how-to-zenfone-t3173314
The minimal boot options he listed are all in TWRP 3.1.1-0. The only thing I was missing before was config... I'm thinking that might be the key to preventing this. Next step is to determine if there's a config partition, and what happens when you do stuff to it (and ultimately how to restore the partition when you don't have a TWRP backup on hand).
I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.
Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.
mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands
help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.