Database Develop

[HOWTO] Simple Root How-To.

Well guys there are over 9000 threads here on how to root the Nexus 4.
I thought I'd make one thread that says all this in simple English and makes it quick and simple for everybody.
CREDITS:
1wayjonny - Universal Naked Driver
Koushik Dutta (koush) - CWM
Chainfire - SuperSU
HQRaja - SU & Busybox package
Click to expand...
Click to collapse
DISCLAIMER:
UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. Therefore I HIGHLY suggest you do this before you start setting up the phone/installing apps so that you don't have to redo/reinstall much.
You can re-lock and unroot the phone, but I am still going to say that this voids the warranty.
I am not responsible for what you do to your device. This is for reference only.
Please follow each step carefully (ESPECIALLY make sure to read the part before step 14 VERY CAREFULLY.)
The CWM recovery may not be 100% functional yet, but you can install zips/roms and do backups for sure.
STEPS:
1 - Download this file and unzip it to C:\Nexus4
2 - Open a command prompt (On windows vista/7, go to Start menu and type cmd and press enter. On XP & below, go to Start > Run and type cmd and press enter.)
3 - In the command propmpt, run
Code:
cd C:\Nexus4 <press enter>
4 - On the phone, go to Settings > About phone. In the About phone menu, scroll down to "build number" and tap it until it says "You are now a Developer!"
5 - Go back to the main settings menu, and the Developer options tab should now be visible. Open that tab.
6 - In the Developer options menu, check USB debugging and Stay awake.
7 - Install the driver from here.
8 - Connect the device via USB.
9 - In the command prompt, run the command
Code:
adb devices <press enter>
and your serial number should pop up. If not, try unplugging the device, reinstalling the drivers, rebooting PC, and then retry.
10 - Now run the command
Code:
adb push SUBusybox.zip /sdcard/SUbusybox.zip <press enter>
It should say something like "XXXX KB/s (1191942 bytes in X.XXXs)"
11- If it said that, run the command
Code:
adb reboot-bootloader <press enter>
12 - The phone will show up in the bootloader. Now run the command
Code:
fastboot devices <press enter>
and your serial number should pop up.
13 - If your serial number popped up, run the command
Code:
fastboot oem unlock
and your phone will ask you if you want to unlock. Select yes with the volume buttons and press power.
13 - Your phone will go back to the bootloader screen, and at the bottom it will now say LOCK STATE - unlocked
****DO WHAT IS BETWEEN THESE RED DIVIDERS IF AND ONLY IF YOU WANT OTA UPDATES TO STILL WORK. IF YOU DON'T CARE, CONTINUE ON STEP 14 BELOW THE DIVIDERS.****
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
Run
Code:
fastboot boot CWMrecovery.img <press enter>
and it should say something like
Code:
downloading 'boot.img'... OKAY [ X.XXXs]
booting... OKAY [ X.XXXs]
and your phone will boot into CWM recovery.
NOW SKIP TO STEP 17. ON STEP 18 IF IT ASKS YOU TO DISABLE RECOVERY OVERWRITE, TAP NO. STEP 19 SAYS YOU WILL HAVE CWM INSTALLED. YOU WON'T.
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
14 - Now run the command
Code:
fastboot flash recovery CWMrecovery.img <press enter>
and it should say something like
Code:
sending 'recovery' (7754 KB)... OKAY [ X.XXXs]
writing 'recovery'... OKAY [ X.XXXs]
15 - If it said OKAY twice, then press the volume down key on the phone twice and it will say Recovery mode. Press the power key.
16 - Once in recovery mode, run the commands
Code:
adb shell mount system <press enter>
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak <press enter>
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak <press enter>
adb shell umount system <press enter>
the command prompt will say nothing back to you if there were no errors.
17 - On the phone, tap install zip from sdcard (NOT INSTALL ZIP FROM SIDELOAD), then tap choose zip from sdcard. Tap 0/. Now scroll down to SUBusybox.zip and tap it. Tap yes. It will then install.
18 - Now tap Go Back and then tap reboot system now. If it asks you to disable recovery overwrite tap yes.
19 - Once the phone boots back up it will be fully wiped and you will be rooted with CWM, SuperSU, and busybox installed

Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk

jimmyz said:
Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
It didn't work for me, so I put adb commands in there to do it manually just in case.
Sent from my Nexus 4 using Tapatalk 2

No OS HTC Want To Flash Rom

Some how I formatted the system and have no OS and cant mount storage in the recovery gives a error. When I try to fastboot flash i get this error.
sending 'zip' (1025039 KB)...
OKAY [ 36.272s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 36.314s
any help is appreciated if fixed will donate to the helper

Can't fastboot flash a Rom. (Gee if it were that easy
You have to sideload a ROM .
- put your Rom in your SDK folder
- in recovery, select ADB Sideload. Phone will set itself to sideload mode
Make sure phone is detected (adb devices)
Type command on your computer
Adb sideload /path/to/rom.zip
Sent with pigeons.

HTC One > STUCK AT BOOTLOADER + PC DOES NOT RECOGNIZE

Hey guys, I'm frustrated as hell here, please help me out, I've raged too much for my own health.
What happened:
1: I had CYANOGENMOD installed and all was good
2: Didn't like it, and wanted to try out stock android, so I followed a video with the title : (Restore your HTC One to Sense 5 (Stock or Factory ROM)) by Sakitech
3: Once the video dude told me to write down in the CMD : fastboot oem lock , that's when this problem started, I've been trying to find a fix for this since 7 AM and it's already 6:22 PM, I haven't gotten up much at all except to eat and ****, so please don't think I haven't done my share of searching around.
I have:
-Attempted to "push" adb and fastboot but there's no device to push to because my PC does not recognize the HTC ONE, I've tried on a PC with Windows 8.1 + a PC with Windows 8 + a PC with Windows 7 + an iMac , none worked.
In the bootloader, when I go to Fastboot mode I can see (Fastboot usb) sometimes, only when I'm really lucky.
-Tried to go to recovery mode, but the bootloader only restarts and does nothing else.
-----------------------------------------------------------------------------------------------------------------------------------------------
FINAL SOLUTION:
1)Go to the XDA troubleshoot FAQ and follow the 2ND question in order to get your PC to recognize your phone.
2) Follow this:
bored_stupid said:
Download TWRP 2.6.3.3,(most stable) http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the recovery in your adb/fastboot folder, then press shift key/right mouse button and open command prompt here
enter bootloader and connect your phone to PC
fastboot devices
if it comes back with some numbers
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if successful, enter recovery and reflash your custom rom
Click to expand...
Click to collapse
3) Go to MOUNT and check Data only (IN TWRP) Then use a windows 7 PC and push a rom to your phone via recovery ( Have your rom renamed to ROM and put it in the folder containing ADB, then simply shift-rightclick and click on "Open command window here" then write this command down: adb push rom.zip /sdcard/ -The CMD window won't be showing you any progress, so just wait 5-10 mins until it gives you a small line of feedback containing the amount of KB/MB it has sent to your Phone.
4) Wipe both Cache's in the TWRP "Wipe" menu, then simply flash your ROM.
If the first time you restart your phone it's stuck at the splash screen, just restart again and it should work.
Huge thanks to bored_stupid and nkk71 for the help, I greatly appreciate it.

Aitelqadi said:
Hey guys, I'm frustrated as hell here, please help me out, I've raged too much for my own health.
What happened:
1: I had CYANOGENMOD installed and all was good
2: Didn't like it, and wanted to try out stock android, so I followed a video with the title : (Restore your HTC One to Sense 5 (Stock or Factory ROM)) by Sakitech
3: Once the video dude told me to write down in the CMD : fastboot oem lock , that's when this problem started, I've been trying to find a fix for this since 7 AM and it's already 6:22 PM, I haven't gotten up much at all except to eat and ****, so please don't think I haven't done my share of searching around.
I have:
-Attempted to "push" adb and fastboot but there's no device to push to because my PC does not recognize the HTC ONE, I've tried on a PC with Windows 8.1 + a PC with Windows 8 + a PC with Windows 7 + an iMac , none worked.
In the bootloader, when I go to Fastboot mode I can see (Fastboot usb) sometimes, only when I'm really lucky.
-Tried to go to recovery mode, but the bootloader only restarts and does nothing else.
WILL BE EDITING THIS LATER ON TO ADD WHAT I TRIED AND WHAT HAPPENED WITH THIS PROBLEM.
Click to expand...
Click to collapse
Do not follow Videos from youtube etc. Most are out of date and do not take into account your particular phone, ie, whether its rooted or not, S-On/S-off...
First of all get your phone recognized by your PC
take a look here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Also unlock your bootloader again

bored_stupid said:
Do not follow Videos from youtube etc. Most are out of date and do not take into account your particular phone, ie, whether its rooted or not, S-On/S-off...
First of all get your phone recognized by your PC
take a look here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Also unlock your bootloader again
Click to expand...
Click to collapse
I've unlocked the bootloader successfully, updated my HTC drivers just like in the FAQ, BUT, I cannot access my sd-card/phone files and the phone is stuck on the cyanogenmod splash screen and every now and then it restarts by itself.
/EDIT/
P.S. I was able to get into recovery mode, I have ClockworkMod Recovery v6.0.4.3

Aitelqadi said:
I've unlocked the bootloader successfully, updated my HTC drivers just like in the FAQ, BUT, I cannot access my sd-card/phone files and the phone is stuck on the cyanogenmod splash screen and every now and then it restarts by itself.
Click to expand...
Click to collapse
You need a working OS to do that.
Download TWRP 2.6.3.3,(most stable) http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the recovery in your adb/fastboot folder, then press shift key/right mouse button and open command prompt here
enter bootloader and connect your phone to PC
fastboot devices
if it comes back with some numbers
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if successful, enter recovery and reflash your custom rom

bored_stupid said:
You need a working OS to do that.
Download TWRP 2.6.3.3,(most stable)
Put the recovery in your adb/fastboot folder, then press shift key/right mouse button and open command prompt here
enter bootloader and connect your phone to PC
fastboot devices
if it comes back with some numbers
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if successful, enter recovery and reflash your custom rom
Click to expand...
Click to collapse
Done, how do I reflash my custom rom if I don't have one (I wiped everything before when I was attempting to fix this), also my phone is still not recognized on the PC, also I'd like to put stock 4.4 android.

Aitelqadi said:
Done, how do I reflash my custom rom if I don't have one (I wiped everything before when I was attempting to fix this), also my phone is still not recognized on the PC, also I'd like to put stock 4.4 android.
Click to expand...
Click to collapse
you can use an OTG cable and a USB stick with a rom on it or use a windows 7 PC and push a rom to your phone via recovery.. have to go to work now.. but will help soon. Good luck
PS.. by the way.. your phone will only be recognised in fastboot or through your recovery using adb. Until you have a working rom installed
Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2

bored_stupid said:
you can use an OTG cable and a USB stick with a rom on it or use a windows 7 PC and push a rom to your phone via recovery.. have to go to work now.. but will help soon. Good luck
PS.. by the way.. your phone will only be recognised in fastboot or through your recovery using adb. Until you have a working rom installed
Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Ok so I'm trying to push insertcoin Sense 6 ROM , I have the ROM in the folder containing both fastbood and ADB, and I renamed the ROM to ROM and I'm using the command adb push ROM.zip /sdcard/, but whenever I press enter nothing happens in the CMD, but I see the ROM file almost instantly in the recovery sdcard, but I cannot use it, whenever I try to install it it fails, I'm guessing it's being copied but weirdly there;s no feedback in CMD ?

Aitelqadi said:
Ok so I'm trying to push insertcoin Sense 6 ROM , I have the ROM in the folder containing both fastbood and ADB, and I renamed the ROM to ROM and I'm using the command adb push ROM.zip /sdcard/, but whenever I press enter nothing happens in the CMD, but I see the ROM file almost instantly in the recovery sdcard, but I cannot use it, whenever I try to install it it fails, I'm guessing it's being copied but weirdly there;s no feedback in CMD ?
Click to expand...
Click to collapse
the push will take 5 to 10 minutes without showing progress until it's finished, check below:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.

ublelyQ for
Alright was able to pull it off, will be editing the main post now.

895 99852933
nkk71 said:
the push will take 5 to 10 minutes without showing progress until it's finished, check below:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
God, it seems like whenever I fix a problem another one pops up....
I got my ROM installed and all was well, until I wasn't able to call/send messages, I put my sim card in another phone to check if that was the problem, but it wasn't. I also tried two different ROM's just to make sure, Insertcoin Sense 6 and Android Revolution HD .

Aitelqadi said:
God, it seems like whenever I fix a problem another one pops up....
I got my ROM installed and all was well, until I wasn't able to call/send messages, I put my sim card in another phone to check if that was the problem, but it wasn't. I also tried two different ROM's just to make sure, Insertcoin Sense 6 and Android Revolution HD .
Click to expand...
Click to collapse
APN problem?

nkk71 said:
the push will take 5 to 10 minutes without showing progress until it's finished, check below:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
nkk71 said:
APN problem?
Click to expand...
Click to collapse
Aren't APN's only for mobile internet?
EDIT
And I have the APN settings set according to my ISP, the problem is here that I cannot call at all, the phone detects there is a sim card, but it's not able to use it.
When I call it says "Out of Service Area" and drops the call almost instantly. If I remove the Sim the phone tells me that I removed the sim, same thing happens when I insert the sim.

Aitelqadi said:
Aren't APN's only for mobile internet?
EDIT
And I have the APN settings set according to my ISP, the problem is here that I cannot call at all, the phone detects there is a sim card, but it's not able to use it.
When I call it says "Out of Service Area" and drops the call almost instantly. If I remove the Sim the phone tells me that I removed the sim, same thing happens when I insert the sim.
Click to expand...
Click to collapse
OH GOD YES YES. Found the solution, man I was literally jumping up and down from happiness.
Had to go to Network Operators > Select Automatically. Thanks for the help again.

[Q] A Unique Problem...:confused:

Hello fellow One users,
I have browsed threw most if not all the HTC One problems on the site and google to try and figure this thing out as i KNOW how people hate Duplicated Threads... Anyways i hope someone can help me with this situation.. Thanks
I received this phone from a friend, ive attached pic showing the state he gave it t me in... According to him he was able to get the phone into Bootmode .. when he gives it to me AFTER TRYING TO RUN A RUU without S-OFF ...
Heres my problem... Basically the phone will not power on, into anything... I try to power on i get this... either a red flashing LED inside the top speaker... or a solid RED led when plugged into the power outlet .... Then ill try to boot into Bootmode and i get this ... Home and Back buttons flashing with no LED on, after the Home and Back buttons flash 10 times i then get a solid red LED , plugged in or not... ive even trying to just charge the device ( I had it charging for a week CONSTANTLY ) no results .. i even try to run a RUU ( for luck i guess ) but no cigar... all i get is an error saying the device has less then 30% battery .. i don't know how it can tell that even tho my PC actually doesn't even see the phone EVER connect.
If anyone can give me ideas and solutions on how to go about fixing this please do as i have tried almost everything. I am very familiar with android and electronics so please don't noob me.
Thank you and i do apologize if i do respond with Noobish questions and the HTC One is a newer device to me.
Thanks
**UPDATE**
Got it to boot into bootloader and it also boots to the HTC screen as shown below.... now i try to run adb commands but the PHONE IS NOT AUTHORIZED...What do i do now??

RED light solid = Not enough battery - at least 30% is required other the security measures will prevent you from flashing RUUs.
Device unauthorized? Try to check and uncheck the USB Debugging option in the device, if possible. If not, you can plug in and out the USB and the device should show up a messagebox to ask you if you authorize the computer, but for that Debugging must be checked AFAIK.
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
Click to expand...
Click to collapse
If ADB does not work, you can still use fastboot commands.

davebugyi said:
Try to check and uncheck the USB Debugging option in the device, if possible.
If ADB does not work, you can still use fastboot commands.
Click to expand...
Click to collapse
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- RUU will not work with S-On and UNLOCKED bootloader, with S-On you need to relock bootloader for RUU to work -> but don't do that yet!!
2- for future reference: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?

nkk71 said:
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?
Click to expand...
Click to collapse
I am running Windows 8 64bit with the latest adb version. also all i have are USB 3.0 ports
and ive tried to run the command "fastboot getvar all" but it just says waiting for device when the device is in fastboot usb mode...

Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks

Shotgun4 said:
Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks
Click to expand...
Click to collapse
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44

nkk71 said:
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44
Click to expand...
Click to collapse
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?

nkk71 said:
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?
Click to expand...
Click to collapse
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
Ok thanks, I'll let you know how things go
Sent from my LG-D801 using XDA Free mobile app

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...

Shotgun4 said:
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...
Click to expand...
Click to collapse
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)

nkk71 said:
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)
Click to expand...
Click to collapse
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Click to expand...
Click to collapse
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a <name of ROM>.zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly

nkk71 said:
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a .zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly
Click to expand...
Click to collapse
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""

Shotgun4 said:
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""
Click to expand...
Click to collapse
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Finally after 6 hours of sitting at my laptop, browsing the internet for answers ... it was so simple ...
1. adb wasnt working because when the device was connected in recover mode, Windows 8 had installed the "My HTC" drive ... To fix it all i did was uninstall that driver "My HTC".. refresh Device Manager and look under "unknown Devices" ... and install the Samasung OEM adb device driver in its place ...BOOM working adb!?
Next i followed your steps to push the rom via adb and it finished successful.
C:\Users\Peter\Android>adb devices
List of devices attached
FAXXXXXXXXXX recovery
C:\Users\Peter\Android>adb push rom.zip /sdcard/
4739 KB/s (1017950778 bytes in 209.742s)
C:\Users\Peter\Android>adb shell md5sum /sdcard/rom.zip
06c863ce41b0d5001290737a31e198a1 /sdcard/rom.zip
C:\Users\Peter\Android>
3. i check the "md5sum" and got "06c863ce41b0d5001290737a31e198a1" ... File i pushed was Android_Revolution_HD-One_9.4...
4. Flashed and device is now working perfectly :victory:
Thank You so much and for being so patient with me aha ... you deserve a thanks and a donation for all your help :highfive:
Also gained S-Off using Revon

Root Assistance RP2 Android 9 pie, latest updates.

Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)

Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk

blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin

In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock

blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.

Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445