Develop Bugs

[Q] Clockwork Recovery

Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron

I would like to help, first lets try using adb, command would be adb reboot recovery

Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R

Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key

I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R

if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good

Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.

Zenfone 2 Z00AD Stuck on usb logo

Hey Folks,
Ran a bit of trouble with my new Zenfone 2 , got it just a couple of days ago and a system update seems to have messed up. The phone froze half way through the update process and I had to turn it off (ran out of patience) and when I booted it up it just loads up to the ASUS logo and stays there for eternity.
I was not able to get to the Recovery mode, had a war with the dead android guy with the red triangle, ( holding power and volume up didn't help). I did however manage to get the device recognized on the Platform tools command like when I connected to my PC. I tried the ADB reboot command, ADB reboot recovery, and they didnt help. I did manage to work a couple of fastboot commands, fastboot erase data and fastboot erase cache BUT, looks like that's got me into deeper trouble.
Ever since I did that, I cannot manually go into the recovery mode anymore using the power and volume keys. I get a white USB logo and something that looks like a battery status bar below it. No combination of keys seem to help.
To make it worse, my device is not recognized on my PC anymore, ADB devices command doesn't list it, and neither does fastboot devices. I did however notice that now on my device manager, the phone shows up as a 'ortable Device - MTP USB Device'. No ammount of uninstalling and re-installing various kinds of ADB and USB drivers seem to help.
I did see a few blogs that give a fix for the same issue on a zenfone 5, but being a noob (hate to admit it) at this, I dont wanna risk it unless I'm sure it will help.
Can anyone help me out on this please? Any kind of help would be much appreciated

Download the Lastest firmware from here
https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
If you WW then download.
keep the zip file in SD card and rename it as MOFD_SDUPDATE.zip
Now go to bootloader and then recovery mode. it will automatically apply update. update may take time 10~20 mins

From your description you probably need to read this thread
http://forum.xda-developers.com/showthread.php?t=3162848
Sorry it's not good news
Sent from my ASUS_Z00AD using Tapatalk

It's showing error (status 7) . Help Me !!

stuck on usb logo
please help me my asus zenfone 2 z008d got the same problem from yesterday . its stuck on usb logo

Search xFSTK for repair/temporary fastboot, do the tutorial. Then goto recovery if still can. If recovery missing try to fastboot recovery. If failed then u must use Asus Flashtool to flash raw image. After that retry to flash droidboot, recovery, boot. Reboot to fastbootand go to recovery, then choose adb. Run adb sideload to flash full firmware.zip

I become an expert at unbricking hehe 
Stuck on USB logo...
Turn your phone off...
Start downloader ..flashing ifwi and fwr dnx and os image..connect phone.
Try flash os image on its own repeatedly ...ignore errors just keep doing it .
Then after 10 goes at it ..flash ifwi and dnx with it repeatedly till success.
Note that when it succeeds ..
Stop! and pause, keep an eye on your screen of phone..you see it flash , might take 5 mins before you see this start ..but when its finished ..you flash raw in flash tool after and it will reboot straight into system all by itself 
Me have been guilty of flashing raw before the flash of downloader...and a bet many others have too.
Ps select, wipe data in flash tool too.

i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help

ritupaul91 said:
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help
Click to expand...
Click to collapse
You may want to reflash your phone using RAW firmware.
Sent from my ASUS_Z00A using XDA Labs

G4 bricked after trying to instal SU - Help

Hi guys!
I really need your help. Few days ago i had installed Cm 14.1 and everything was fine (i had unlocked the bootloader, installed TWRP, rooted the phone) yesterday night i wanted to install SU so i downloaded the .zip, logged in recovery ..and by choosing "install" i flashed the zip ..but after the restart from twrp the cell didnt work anymore , the little cm alien face is always loading. I tried to to get in bootloader mode by pressing the power button and volume down then relasing it and pressing it again but nothing happens. I got in download mode , connected the phone to the pc (after having installed the drivers) but i always get the message "waiting for device" when i try to get into recovery (bootloader recovery command ..well just because bootloader devices doesnt show me any phone connected) . So actually i dunno how to get in bootloader mode and make windows to see it. Any help would be really appreciated.
i add that i worked on a recovery loaded with fastboot command from windows so i didnt really installed it on the g4 even if i copied the img file on the sd card. Therefore i need to get into bootloader mode in order to send fastboot commands again
Thnx

Phone might be bricked. Need help to find a solution!

Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.

Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk

waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)

i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.

Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?

Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition

waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!

Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.

saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?

Zenfone 3 deluxe bootloop problem after update

Hello,
I searched for this problem but i dont see any posts that is related to this. So i got my deluxe, its ZS750kl 2.15 6gb ram unit with nougat OS and it was working well. Last february 2018, it got its automatic system update for Taiwan CHT VoLTE support and battery optimization. A day after the update, it suddenly went into bootloop. My unit is not rooted, running with stock nougat OS with locked bootloader. It was never modified in any form. I do some observations and i noticed that sometimes it boots normally so i successfully done a factory reset but the same problem existed. I cant do a hard reset via vol. down+power since i have a locked bootloader. I am new with fastboot method and i dont know if it will help me solve the problem so i left it untouched from March until this week. Same problem still exist even the battery is totally drained over time.
Is there someone here with the same problem? Is there a possibility of system rollback before the february update?can i flash nougat stock rom hoping it will revert back to the previous OS without VoLTE support? I think the bootloop issue is with that update, since i saw some posts with the same problem but it was after the oreo update, not the same as mine so i concluded that the problem lies somewhere in between the feb. update and the oreo update.
I hope some will look into this and help me or guide me to step by step flashing of nougat stockrom using fastboot. Sorry, im new with the method, i usually flash through twrp but i cant because of locked bootloader.
Thank you in advance,hope you can help me with my problem.
Model: ZS750KL
Ram: 6gb
Frequency: 2.15
Firmware: WW_5.17.44.87_20180222
Location: Philippines

Hi there,
I hope I can post this here.
I don't have an answer but I have a similar problem. The Phone will not start anymore. I ran into bootloop and only fastboot is working.
Any thing i can do?

Hello,
Im looking for a solution too, my phone got bootloop only fastboot is working, partition protected, phone is locked i cannot put even in recovery mode. Any help would be really appricated.
Cheers.

Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Grab the standalone adb/fastboot tools
https://developer.android.com/studio/releases/platform-tools
Grab recovery.img from 15.0210.1808.70, grab twrp-3.2.3-0-Z016-20181014.img
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Grab the latest official update, make sure it's the right frequency (2.15ghz in this case)
https://www.asus.com/us/Phone/ZenFone-3-Deluxe-ZS570KL/HelpDesk_Download/
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.

asianflipboy said:
Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.
Click to expand...
Click to collapse
Hello There,
Thank you for tut*, do you have or know any method about i have exact same phone model but its stuck on boot and keep restarting, no recovery mode available only i can put in fastboot mode when i try to flash or anything it said partition protected... any help would be really appricated.
Cheers.

same problem, I have also opened a new thread but I have not received a reply.
In all cases following this mini-guide I am stopped at the boot twrp command. I'm getting unsigned file error.
I tried the original recovery (taken from the user link above) and the phone gets stuck on the android logo with a red triangle of danger.
ideas?

How did you unlock your bootloader? i cant follow the instructions given because my bootloader is not yet unlocked.

has anyone gotten the steps above to work without unlocking the bootloader?