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?
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.
Hello!
I have a HTC One X (EU-version), and it's unlocked.
I used to have Android Revolution HD ROM installed, and would try a new kernel. So I downloaded the new faux kernel (faux_004b5_arhd_7.0.0_modified.img)
Somehow it didn't work, and my phone keep restarting. So I go to the recovery mode, and tried to reinstall the ROM, without whip.
After that I made a reboot, my phone keep reboot. Now I can't go to the recovery mode, either can I flash my device.
I really don't know what to do now.
I hope someone can help, and I posted in the right section.
DownClock said:
Hello!
I have a HTC One X (EU-version), and it's unlocked.
I used to have Android Revolution HD ROM installed, and would try a new kernel. So I downloaded the new faux kernel (faux_004b5_arhd_7.0.0_modified.img)
Somehow it didn't work, and my phone keep restarting. So I go to the recovery mode, and tried to reinstall the ROM, without whip.
After that I made a reboot, my phone keep reboot. Now I can't go to the recovery mode, either can I flash my device.
I really don't know what to do now.
I hope someone can help, and I posted in the right section.
Click to expand...
Click to collapse
I had that problem before too. If the "hold power button for 10 seconds then press volume down and power buttons simultaneously" doesn't work, download Quick Boot from playstore and it would allow you to choose to either Reboot, boot to recovery, or the bootloader
Sent from my HTC One X using xda premium
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
wtfshouldidonow said:
I had that problem before too. If the "hold power button for 10 seconds then press volume down and power buttons simultaneously" doesn't work, download Quick Boot from playstore and it would allow you to choose to either Reboot, boot to recovery, or the bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I hold the power button and volume down for 10 secounds, I come to the fastboot menu.
How can I download Quick Boot, when I don't have acces to my memory. I can't see what I have on my memorycard (obs. because I can't go to the recovery part), either can't connect to the computer, since I'm in a bootloop.
I'm afraid while I was doing this stuff, my battery was low. But it didn't die under the process.
Tyvm for the reply, but I can't install the quick boot.
seadersn said:
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
Click to expand...
Click to collapse
Can you please explain more?
My Skype is: Dichatz, if a awesome soul could help me there, it would be the greatest thing ever. I'm afraid of that my HTC One X has seen the daylight for the last time
Ty both for the reply.
EDIT: I followed my friends advise, and tried to erase fastboot cache, which seems not able do to. I just getting the message: < waiting for device >.
Dear God, what have I done with my phone!
Dear OP, I believe there is a solution. This situation has occurred with my device more than once. I too believed I had lost it until it resolved itself. There are several things you can do to ensure it works again. I wiped the ROM on my phone before the problem began, so I was stuck with a dead phone until I found a way to get recovery to work again. If it's possible, enter Fastboot and install a new kernel onto it, and THEN use fastboot erase cache. If that is not a viable option, make sure the USB wire is not plugged in when the device boots. By this I mean holding down the lower volume button and initializing the menu that allows you to select Fastboot, Recovery, Factory Reset and other command options. Once the device boots into the menu, you may then plug in the cable and enter Fastboot mode. If none of the above work, let the battery deplete itself until device turns off. Once you have done that, plug it into the wall charger, and then volume down and power up. If the device says something like "reading SD card", disconnect the USB and the menu will fully load. That is when you select Fastboot. Keep the device on, plug it into the pc and send your kernel commands to your device. Ensure that you also erase the cache via Fastboot. Your device should now be fully operational. I hope I was able to help.
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Thanks for replies.
Elemental_Fire said:
Dear OP, I believe there is a solution. This situation has occurred with my device more than once. I too believed I had lost it until it resolved itself. There are several things you can do to ensure it works again. I wiped the ROM on my phone before the problem began, so I was stuck with a dead phone until I found a way to get recovery to work again. If it's possible, enter Fastboot and install a new kernel onto it, and THEN use fastboot erase cache. If that is not a viable option, make sure the USB wire is not plugged in when the device boots. By this I mean holding down the lower volume button and initializing the menu that allows you to select Fastboot, Recovery, Factory Reset and other command options. Once the device boots into the menu, you may then plug in the cable and enter Fastboot mode. If none of the above work, let the battery deplete itself until device turns off. Once you have done that, plug it into the wall charger, and then volume down and power up. If the device says something like "reading SD card", disconnect the USB and the menu will fully load. That is when you select Fastboot. Keep the device on, plug it into the pc and send your kernel commands to your device. Ensure that you also erase the cache via Fastboot. Your device should now be fully operational. I hope I was able to help.
Click to expand...
Click to collapse
Yes, I was dumb, started at low battery level, even tho, everywhere says: Make sure you have more than 70 %.
I can't wipe, or install anything, since it's recovery mode that doesn't work
Atm., I charge my phone, because I need to have 10 %, I use "Stuck in fastboot with low battery. Use this BATCH file!" guide. So far it works.
amacrobie said:
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Click to expand...
Click to collapse
Thank you very much for your answer!!! I read this this guide: 9/6 Mandatory Update Official Clockworkmod Touch Recovery 5.8.4.0.
If that doesn't work, I will take closer look at your reply. No matter what, thank you very very very very much. I'm sure that reply will help some soul outthere (if not me, if it fail).
Thank you guys. You are the best. I will be right back here if I find a solution!
Tip: try 'Quick Boot' available on Google Playstore, it's a payed app but
it let you go straight into recovery mode.
Hi
Laurentius26 said:
Tip: try 'Quick Boot' available on Google Playstore, it's a payed app but
it let you go straight into recovery mode.
Click to expand...
Click to collapse
I could't turn my device on, so I could't install any programs.
Anyway, after 6 hours work, I finally got it.
I use that guide ^, so I could charge my phone to 10%, and installed new Kernel.
Thank you guys, for quick replies!
My apologies, I wasn't reading your first post properly.
Anyway congrats you have it working again.
DownClock said:
I could't turn my device on, so I could't install any programs.
Anyway, after 6 hours work, I finally got it.
I use that guide ^, so I could charge my phone to 10%, and installed new Kernel.
Thank you guys, for quick replies!
Click to expand...
Click to collapse
Can't flash cwm recovery.
amacrobie said:
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Click to expand...
Click to collapse
Hey, I am having similar problem with my htc one x here. I did some stupid stuff, tried to install jelly bean and now my device is broken.,
So the thing is, phone is stuck at HTC logo, I cant access recovery mode. And my phone now says tempered and relocked at the top so I cant get it fixed with my carrier which is rogers.
I tried installing RUU for rogers but it says image error and wrong ruu. I can't find the right one and trust me i've searched everywhere.
I can connect my phone to computer and see fastboot usb. But other than that I can't do anything with it.
I tried flashing cwm but it says failed. I'll attach image here with it.
If there is any way to fix it, please help, I just bought this device and I love it, dont wanna lose it.
Also, I read that I can add custom recovery to the phone but without recovery menu I can't do that either.
Thanks!
saagar_mistry said:
Hey, I am having similar problem with my htc one x here. I did some stupid stuff, tried to install jelly bean and now my device is broken.,
So the thing is, phone is stuck at HTC logo, I cant access recovery mode. And my phone now says tempered and relocked at the top so I cant get it fixed with my carrier which is rogers.
I tried installing RUU for rogers but it says image error and wrong ruu. I can't find the right one and trust me i've searched everywhere.
I can connect my phone to computer and see fastboot usb. But other than that I can't do anything with it.
I tried flashing cwm but it says failed. I'll attach image here with it.
If there is any way to fix it, please help, I just bought this device and I love it, dont wanna lose it.
Also, I read that I can add custom recovery to the phone but without recovery menu I can't do that either.
Thanks!
Click to expand...
Click to collapse
How much battery you think you had on your device, and how much do you think you have now?
Sendt fra min HTC One X med Tapatalk2
Htc One x
DownClock said:
How much battery you think you had on your device, and how much do you think you have now?
Sendt fra min HTC One X med Tapatalk2
Click to expand...
Click to collapse
I have been charging my device with the wall charger, eventhough I cant see the battery level I'm pretty sure it's around 80. Cuz before I go into fastboot usb when I attach my phone to computer I charge the phone first.
saagar_mistry said:
I have been charging my device with the wall charger, eventhough I cant see the battery level I'm pretty sure it's around 80. Cuz before I go into fastboot usb when I attach my phone to computer I charge the phone first.
Click to expand...
Click to collapse
To be honest I don't know what to do. Try to make a new topic, and hope for help
Good luck.
Sendt fra min HTC One X med Tapatalk2
Htc One x Cant flash into recovery thus unable to root
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
GridBreak said:
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
Click to expand...
Click to collapse
man are you sure you have international Htc One X?
I think you may have AT&T One X.
GridBreak said:
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
Click to expand...
Click to collapse
Here is the right forum for your device http://forum.xda-developers.com/forumdisplay.php?f=1538
Cannot boot
i also accidentally flashed an img into boot and now my phone is not booting and is stuck ina bootloop please help !!!!!!!!!
GridBreak said:
i also accidentally flashed an img into boot and now my phone is not booting and is stuck ina bootloop please help !!!!!!!!!
Click to expand...
Click to collapse
you should ask for help in the respective forum for your phone.
This is for Tegra 3 HTC ONE X
seadersn said:
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
Click to expand...
Click to collapse
i didnt know about adb reboot recovery, just found this via google, cheers mate!
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you
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.
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.
marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
.
Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.
So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial
Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?
marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.