I trying to modify build.prop and reboot the device but after that my device didnt rebooted,
I manged to get him into twrp at the first time and tried to replace the modify build.prop with his backup but now the device is stuck and dont let me get into bootloader and his loading up the HTC logo (that you can see when the device is boot up) every something like 5 minutes.
and the pc isnt recognized it too.
do I have something to do? when I pressing Volume up +power the device is restarting and showing the HTC logo but staying on black screen.
sorry for my poor english but I really need some help.
Did you make a nandroid before making the build.prop changes? If so, just restore the backup.
If not, why the heck not???
Do you have custom recovery (TWRP or CWM) installed, or stock? Any custom ROM zip on the phone? If you have custom recovery and a ROM zip on the phone, try flashing it.
Do you have adb/fastboot working, and any response when you use the command:
fastboot devices
If you have working fastboot, push a ROM zip to the phone and flash with custom recovery; or sideload in TWRP.
redpoint73 said:
Did you make a nandroid before making the build.prop changes? If so, just restore the backup.
If not, why the heck not???
Do you have custom recovery (TWRP or CWM) installed, or stock? Any custom ROM zip on the phone? If you have custom recovery and a ROM zip on the phone, try flashing it.
Do you have adb/fastboot working, and any response when you use the command:
fastboot devices
If you have working fastboot, push a ROM zip to the phone and flash with custom recovery; or sideload in TWRP.
Click to expand...
Click to collapse
I am new in that htc thing but i just backup the build.prop I have no clue what nandroid is...
I have TWRP installed but I cant boot into it, and when im trying adb/fast boot its says waiting for device.
btw my htc one m8 is connecting to the pc for a second only and thats not allows me to do adb things
romhaja said:
I am new in that htc thing but i just backup the build.prop I have no clue what nandroid is...
I have TWRP installed but I cant boot into it, and when im trying adb/fast boot its says waiting for device.
btw my htc one m8 is connecting to the pc for a second only and thats not allows me to do adb things
Click to expand...
Click to collapse
A nandroid is a full recovery image made with custom recovery (TWRP in your case), same as a TWRP backup. You should always make a nandroid when making changes to system files. Especially if you are inexperienced with making such changes.
Bootloader is always available as long as the screen comes on. If you can't get into bootloader, its because you aren't doing the button combo correctly:
1) While the screen is on, press and hold vol up and power button until the device reboots (takes 10 seconds or more).
2) The instant the screen goes dark and the phone start to reboot, let go of the power and vol up buttons, and start holding the vol down button. Don't let go of the vol down button until the bootloader comes up.
3) If you don't go into bootloader, you either didn't start holding the vol down button fast enough, or you let go of it too soon.
Once in bootloader, try going into recovery (TWRP). Although TWRP is of limited use if you don't have a nandroid, don't have a ROM zip on the phone, and if you don't have PC connectivity. You are going to have to troubleshoot the PC connectivity. Or you can try to put a ROM on a MicroSD card, and flash in TWRP.
Whatever you do, do not do a factory reset in bootloader. This will corrupt the phone's internal memory and make your situation even more complicated.
Did adb/fastboot work previously? If not, its hard to get out of your present situation without PC connectivity. Try re-installing the HTC drivers (HTC Sync), try another USB cable, or a different USB port, or even a different computer.
redpoint73 said:
A nandroid is a full recovery image made with custom recovery (TWRP in your case), same as a TWRP backup. You should always make a nandroid when making changes to system files. Especially if you are inexperienced with making such changes.
Bootloader is always available as long as the screen comes on. If you can't get into bootloader, its because you aren't doing the button combo correctly:
1) While the screen is on, press and hold vol up and power button until the device reboots (takes 10 seconds or more).
2) The instant the screen goes dark and the phone start to reboot, let go of the power and vol up buttons, and start holding the vol down button. Don't let go of the vol down button until the bootloader comes up.
3) If you don't go into bootloader, you either didn't start holding the vol down button fast enough, or you let go of it too soon.
Once in bootloader, try going into recovery (TWRP). Although TWRP is of limited use if you don't have a nandroid, don't have a ROM zip on the phone, and if you don't have PC connectivity. You are going to have to troubleshoot the PC connectivity. Or you can try to put a ROM on a MicroSD card, and flash in TWRP.
Whatever you do, do not do a factory reset in bootloader. This will corrupt the phone's internal memory and make your situation even more complicated.
Did adb/fastboot work previously? If not, its hard to get out of your present situation without PC connectivity. Try re-installing the HTC drivers (HTC Sync), try another USB cable, or a different USB port, or even a different computer.
Click to expand...
Click to collapse
adb worked with my phone at the first time so I think I will try to reinstall the drivers, and if it won't work I will buy a micro as writer/reader and will put a rom there to flash.
Thank you for helping me! Do you have any recommendation about the sd writer?
Thanks again!
romhaja said:
Do you have any recommendation about the sd writer?
Click to expand...
Click to collapse
Not really. Any one should work, even cheap ones that go for $5-10 US.
Related
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.
Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
shawnchalfant said:
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
Click to expand...
Click to collapse
Thanks for the reply. Do you have a link for the one click root with CWM Recovery ? Can't seem to find it... Also, when I connected my phone to the computer and opened oneclickroot (basic) it says my phone needs to have USB debugging activated (which it did).
I can't get into recovery mode anymore, the phone just loops back to fastboot with no error message.
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
shawnchalfant said:
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
Click to expand...
Click to collapse
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Boot into fastboot, Vol Up + Power, once it vibrates quickly press and hold volume down a few seconds. Fastboot should appear. Then run the batch file. Adb does not run in fastboot mode.
m3j said:
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Click to expand...
Click to collapse
there is still hope ... go for a lower version of recovery, boot (flash it in fastboot) and then keep the rom by keeping it in the external sd card renaming it to MOFDS_Update (i dont remember the name ). flashing should be done on its own...
search "Tutorial Upgrade / Downgrade / Unbrick Zenfone 2" in Asus ZenTalk. it helps for me
Thank you all for trying to help but I wasn't able to repair the phone.
I sent it back and by some miracle they accepted to give me my money back. Buying a new one now but I won't do anything stupid with it this time !
Trying to install TWRP v3. Phone is unlocked (not rooted yet as not necessary atm). I'm able to sucesfully push the .img to the sdcard via adb and install via "fastboot flash recover twrp.img" but the moment I reboot the phone and try to access recovery to get into TWRP, all I get is a little icon of an android mascot lying down with his belly open. No TWRP.
I know the phone will auto-overwrite custom recovery's if the correct combination of hardware buttons are not pressed after the first TWRP install (as TWRP needs to patch the default recovery the first time to stop the phone from constantly trying to overwrite TWRP every time) but so far i've not been able to find out what it is (i.e. not the usual vol +- and power all at the same time. Its gotta be something else?).
Edit: Delete his post. I figured it out. Turns out it isn't a good idea to execute "fastboot reboot" immediately after TWRP installation
Don't restart the Phone!
Flash Recovery and the do the following:
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
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?