Z00AD no fastboot no recovery but the phone works normally - ZenFone 2 Q&A, Help & Troubleshooting

Hello,
I have a problem with my Z00AD. The phone works ok but I wanted to root it. The problem is that it goes in fastboot but after going in fastboot it just doesn't work... It says continue fastboot process and it is not recognized in fastboot devices command. Recovery mode doesn't work at all. ADB mode works very well though. Please note that I unlocked the bootloader and activated USB debugging and all the drivers are installed.
What can I do to get fastboot and recovery working?

Asphyxiate666 said:
Hello,
I have a problem with my Z00AD. The phone works ok but I wanted to root it. The problem is that it goes in fastboot but after going in fastboot it just doesn't work... It says continue fastboot process and it is not recognized in fastboot devices command. Recovery mode doesn't work at all. ADB mode works very well though. Please note that I unlocked the bootloader and activated USB debugging and all the drivers are installed.
What can I do to get fastboot and recovery working?
Click to expand...
Click to collapse
Reboot to bootloader,Press Vol+ once , in bootloader ? Any connection then ?

timbernot said:
Reboot to bootloader,Press Vol+ once , in bootloader ? Any connection then ?
Click to expand...
Click to collapse
install terminal emulator on device. download recovery for the same firmware you are on. or alternatively you can use custom recovery. place that recovery image file in root drive. i mean /sdcard/
now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
# reboot recovery
you will reboot into recovery

@Asphyxiate666
sukhwant717 said:
install terminal emulator on device. download recovery for the same firmware you are on. or alternatively you can use custom recovery. place that recovery image file in root drive. i mean /sdcard/
now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
# reboot recovery
you will reboot into recovery
Click to expand...
Click to collapse
great info :good:

timbernot said:
@Asphyxiate666
great info :good:
Click to expand...
Click to collapse
thanks

Related

[Q] Can I downgrade 10.3 with Windows?

Hello,
Still working on my kids KF2. I got root, yeah! However at some point it updated to 10.3. Can someone point me in the right direction for getting its bootloader downgraded from a Windows 7 x64 platform? I can use a RHEL box at work if I really need to, but rather not.
so I get CM on this thing
thanks!
http://forum.xda-developers.com/showthread.php?t=2100963
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2100963
Click to expand...
Click to collapse
Does that mean I need a fastboot cable? I can make one no problem... but better if I don't have to
I ran: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin, device off, it said waiting for device, but then it just boot up to the lock screen.
Sorry im a little confused on this one.
Code:
adb shell su -c "reboot bootloader"
soupmagnet said:
Code:
adb shell su -c "reboot bootloader"
Click to expand...
Click to collapse
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
s10010001 said:
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
Click to expand...
Click to collapse
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
soupmagnet said:
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
Click to expand...
Click to collapse
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
s10010001 said:
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
Click to expand...
Click to collapse
Close
Make backups
Fastboot with that command
Install downgraded bootloader
Install 2nd bootloader
Install TWRP & kernel(boot.img)
Factory Reset in TWRP
Install rom
enjoy..
Enjoyment is relative, of course
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
s10010001 said:
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
Click to expand...
Click to collapse
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
soupmagnet said:
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
Click to expand...
Click to collapse
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
s10010001 said:
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
Click to expand...
Click to collapse
If your device is completely off, and you plug a working factory cable in, it will boot into fastboot.
Info on pin layout
You need a 5-pin usb cable BTW.
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
s10010001 said:
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
Click to expand...
Click to collapse
Were you able to successfully backup your boot, recovery, and system partitions before everything went wrong?
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
s10010001 said:
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
Click to expand...
Click to collapse
Possibly, but depending on where things went wrong, you may have to restore first. Do you know what the error was?
Something like this max-download-size: 486,539,264
s10010001 said:
Something like this max-download-size: 486,539,264
Click to expand...
Click to collapse
You are supposed to save your partition images with the 'dd' command using the shell:
Hashcode said:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
Click to expand...
Click to collapse
You won't see a "max-download-size" message unless you are using fastboot to flash those images.
ohh ok.. so I dont have a backup
But the fastboot cable is working! Im in fastboot
keeps telling me no device found
do I want the "Android ADB Interface" or "Andriod Composite ADB Interface"?
Also once booted in to fastboot with the cable, do I just leave the cable or put the stock cable back in? Shouldnt matter... but just want to make sure.

trying to turn on USB Debug not through the Firmware...question

so i have bootloader open and I want to turn on USB Debugging. I dont have access to the firmware since i am trying to flash the TWRP Recovery.
How can I turn this on so I can complete the flash, setup the root and be on my way?
Please help!
dankduke said:
so i have bootloader open and I want to turn on USB Debugging. I dont have access to the firmware since i am trying to flash the TWRP Recovery.
How can I turn this on so I can complete the flash, setup the root and be on my way?
Please help!
Click to expand...
Click to collapse
You don't need USB debug on to flash recovery, you need to use fastboot commands not adb.
First boot into bootloader and then connect device to PC. Next open a command prompt in the folder you have adb.exe and fastboot.exe in. Now type
fastboot devices (hit enter)
This Should show your devices serial number. If it does then you need to rename your twrp IMG file to twrp.img then move it same folder that has fastboot.exe. now type
fastboot flash recovery twrp.img (hit enter)
This should flash twrp to your device. Now boot into recovery and choose reboot then choose system. It should ask if you want to fix root, chose yes.
Hope this helps and good luck!
Sent from my A500 using xda app-developers app
Mod has moved this to q&a for you.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

Root Armani in 2018

Method 1:-
Download Custom Recovery for armani in your pc and rename it to recovery.img
and download root zip and paste it in your sdcard
Download 15 seconds adb & fast drivers and follow the instructions....
In pc type the following commands by opening cmd from shift+right click and open command prompt here after connecting the device to pc
Code:
adb devices
after successful install of drivers you will see the device listed in that
Code:
adb reboot bootloader
After rebooting into fastboot mode type the following commands
Code:
fastboot flash recovery recovery.img
after successful flashing of recovery then type this
Code:
fastboot reboot recovery
Flash SuperSU/Koush superuser in your TWRP/CWM/Philz recovery
Method 2:- Download Kingo ROOT and root
Method 3:- Download Kingo ROOT pc version in your pc and load it and connect your device to pc and root....
Method 4:- Download KingRoot and click to root....if it fails in first attempt, try atleast 5 times...
Yes these are indeed the best methods to root this phone.
Also, note that Magisk will not work for the stock MIUI because the phone has Android 4.4 and Magisk probably requires 5.0+. So, Magisk should be used for newer custom ROMs.
HemanthJabalpuri said:
I want to root my MIUI 9 armani in 2018.....
I don't have PC
Click to expand...
Click to collapse
Also, like you had said earlier, if you don't have a PC due to some reason, you can use another phone or tablet for that purpose (to flash the custom recovery). I've read somewhere that most Android devices having 5.0 and below came preloaded with adb fastboot binaries (for newer Android phones, you can easily obtain the binaries online and add them into the /system/bin folder if it is rooted) and hence you can connect your Redmi to this other device using an OTG cable and use the shell (any terminal app) to issue the commands. The only important thing to be considered in this approach is that the other (host) device should have a big enough battery to be able to provide sufficient current to the Redmi phone such that it should not get disconnected during the process.
This method is usually ignored by people, but it really works.
Reserved
Reserved
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Cannot issue the last command.
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
I am on MIUI 9. Not rooted. I am trying to get a custom recovery but I fail. Please help.
blazzer12 said:
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Click to expand...
Click to collapse
Are you sure recovery was flashed properly?
Try this while in fastboot mode :-
Code:
fastboot devices
Make sure that your device is listed properly.
Try this
Code:
fastboot erase recovery
fastboot flash recovery <path to recovery img>
Then reboot using
Code:
fastboot reboot recovery
If still doesn't work out, try to directly boot into recovery image
Code:
fastboot boot <path to recovery img>
If still doesn't work out, then there might be a problem with the fastboot binary on the PC, try to reinstall the latest version of it on the PC and try again.
---------- Post added at 22:03 ---------- Previous post was at 21:55 ----------
blazzer12 said:
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
Click to expand...
Click to collapse
If the issue is specific to TWRP Recovery, try to flash other recoveries. For example, older version of TWRP or maybe try Philz Touch recovery as well.
Yes, the fastboot devices is being listed. Still #2 didn't work. But #3 worked perfectly.
So for me flashing recovery didn't work. I had to temporarily boot into the recovery and then again flash the recovery from there.
Thank you for the help. :good:
Now we can root with Magisk too...
https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post78829088
Note:- Magisk v22.1 is the last version to support Android 4.4.2

Unable to find device in adb and fast boot while phone is in download or recovery

when I do adb devices when my phone is on it finds the device and when I do adb reboot download it goes to download mode but when it gets to download mode and I do adb devices again or any command the phone isn't there and the command fails ... ive tried googling my issue but there is very little information
BoganRabbit said:
when I do adb devices when my phone is on it finds the device and when I do adb reboot download it goes to download mode but when it gets to download mode and I do adb devices again or any command the phone isn't there and the command fails ... ive tried googling my issue but there is very little information
Click to expand...
Click to collapse
Adb only works on a running OS or in twrp. Any other mode you need to perform fastboot commands
Mr Hofs said:
Adb only works on a running OS or in twrp. Any other mode you need to perform fastboot commands
Click to expand...
Click to collapse
Ok will Give that a go thank you very much

Categories

Resources