Database Develop

[Q] Need help upgrading from cyanogenmod6.1 to 7.2

Sorry if this has been asked already but I'm stuck. I'm trying to upgrade to this rom http://forum.xda-developers.com/showthread.php?t=1185027. Whenever I flash it and reboot the phone it's still on cm6.1. I saw the prerequisites and changed the radio but when I did that the phone just hung at the G1 screen so I went back to the old radio. Is there something else I need to do beforehand?
Here's what my bootloader displays
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.23.02
I did see a similar topic elsewhere and the person was directed to here http://forum.xda-developers.com/showthread.php?t=831139 but I'm still lost. I'm having difficulty flashing in fastboot.

Hi
Have you upgraded the SPL?
Sent from my HTC Dream using xda premium

No but I've tried to do that in fastboot and that's where I'm having problems. When I first get into fastboot I see that it's searching for images and after each one it says "No image!". Then it says HBOOT or FASTBOOT USB if I connect it. Is there another way to install it? I tried through recovery with dream_2708kit.zip which has the images for hboot-1.33.0013d and radio-2.22.27.08 but it fails signature and verification.

Its best to do this from fastboot (diffrent then hboot) hold down back or camera when powering on. Connect phone, should say fastboot usb. Then put these files in same folder as fastboot from sdk package (platform tools more than likley) files needed are recovery, radio and spl. Now hold shift and right click in folder, click on opent cmd here. Now type fastboot devices. Make sure you get your phone listed. Now flash recovery then radio then spl - in this order! Amonra 1.7 something, .27.08, and .13d
Sent from my HTC Vision using xda premium

I thought fastboot is the screen with the 3 skating androids which is what I see when I'm in hboot. Holding the camera button and power brings me to hboot. So I must not have fastboot installed then?
demkantor said:
Its best to do this from fastboot (diffrent then hboot) hold down back or camera when powering on. Connect phone, should say fastboot usb. Then put these files in same folder as fastboot from sdk package (platform tools more than likley) files needed are recovery, radio and spl. Now hold shift and right click in folder, click on opent cmd here. Now type fastboot devices. Make sure you get your phone listed. Now flash recovery then radio then spl - in this order! Amonra 1.7 something, .27.08, and .13d
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Fastboot and hboot is your spl. If you have 3 androids on sketboards you have upgraded to one of the engiennering spls that allows fastboot flashing (except for the .13d) after hboot checks for an .nbh file you should be in fastboot mode, connect to comp and look for fastboot usb in red. What does everthing on your screen say (the android/skateboard screen)
Sent from my HTC Vision using xda premium

On an afterthought you get the fastboot program from the android sdk package, make sure this is installed on your computer
Sent from my HTC Vision using xda premium

Is it the fastboot.exe in platform-tools folder? I thought it was finally going to work. I found that if I held on to the back button rather than camera fastboot came on but typing in fastboot devices did nothing and when I typed in the command to install the 1st file recovery it said searching for device. Sorry I'm just really frustrated. I had no problems when I installed cm6.1 years ago. I have since moved on to the HD2, had fun trying out the different android roms on that and now I'm using the Galaxy S II. I'm only trying to upgrade the G1 because I sold it on eBay and the buyer is interested in having gingerbread on there. I thought it would be easier than this.
Code:
demkantor said:
On an afterthought you get the fastboot program from the android sdk package, make sure this is installed on your computer
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

I think it's possible to flash this in recovery, but it's much, much secure to flash it in fastboot. But, if you mess up, your phone is bricked, then, the only way is JTAG. I have flashed my 1.33.0013d/2.22.28.25 combo with recovery thanks to demkantor, he showed me the files. I may need to do my homework if this is safe for you. But this combo gets, 14 mb extra RAM, at the cost of playing 3D Games. But really, when you do this, your device will work like a charm.

I typed in this command:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img and it just hangs at waiting for device. I have no problems getting it to connect when I have the phone booted up in regular mode with usb debugging checked. I'm able to type adb devices and get my phone's serial number with no problems. What am I supposed to see when I'm in fastboot and type in fastboot devices?

As mention all can be done via recovery, but it isn't all that safe. You need to cange directories, change enviromental variables, or just open the cmd in the folder fastboot is in. More than likley in platform tools. Find it, put all needed files in that same folder. Hold down shift and right click within that folder, click on the option to open cmd here. Then have your phone pluged in and in fastboot mode. Now type fastbbot devices. If your serial number comes up then proceed
Sent from my HTC Vision using xda premium

Nothing happens when I type fastboot devices, it just goes to the next command line with no serial popping up. I opened up cmd from the platform-tools folder and I have the files needed in that same folder. I really don't get what's going wrong here.

You can try changing directorys first
Or add the path in enviromental variables
Sent from my HTC Vision using xda premium

Are you using windows/mac/linux? Which os
Sent from my HTC Vision using xda premium

Windows 7

click home > right click my computer > properties > advanced system settings > advanced tab > environmental variables > new
variable name : adb
variable value is the pat ex: C:\android\android-sdk_r18-windows\android-sdk-windows\platform-tools\
make yours what it needs to be
then go to "PATH" in second box (system variables) if there isnt "PATH" add it
at the end of value add ----- ;C:\android...... the rest of your path
once done you can just open cmd anywhere your files are
fastboot and adb are in the same folder (platform-tools or whatever)
files can be anywhere on your computer
do this - open window and try adb and see what happens - then try adb devices
now you can also try fastboot, then try fastboot devices
of course in your phones settings under applications, make sure adb is checked!
or this wont do you any good

It seems as if my phone and computer aren't communicating with eachother while in fastboot. It only works when the phone is in normal mode and only then does adb devices work. I really appreciate you trying to help I know you must be getting frustrated as much as I am lol
I'm going to go ahead and try this on my old pc, the one I had used to root the phone and install cm6.1. Hopefully I'll have better luck with that than my new laptop

I'm not too easily frusterated so don't worry. You may need to remove the drivers and reinstall them so when you plug in your phone all modes are excepted. But still this is unlikley if you can use adb when phone is powered on. But still could be worth a shot to try. When you connect the phone holding power and back (or camera) do you see the phone say fastboot in red? Then when plugged in does it say fastboot usb in red?
Sent from my HTC Vision using xda premium

DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.23.02
FASTBOOT USB OR HBOOT USB, depending on which mode I'm in
<CAMERA STEP2> Hboot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
The 3 skating droids
That's all I see

And yes FASTBOOT is highlighted in red

[Q] phone not turning on after superboot

Hi
I rooted my N1 using Modaco Superboot guide. It was successful, but the phone didn't turn on after reboot and now it doesn't turn on when pressing power button. I might have used wrong superboot version.
I am able to put my N1 to bootloader mode but when I choose 'recovery' it stucks on cross logo with 2 white pixels. Or when I connect it to pc, it freezes.
My device's details:
Hboot-0.35.0017
MICROP-0b15
RADIO-5.12.00.08
Is there anything I can do to recover my phone?
I searched for solution but didn't find anything useful.

ukes said:
Hi
I rooted my N1 using Modaco Superboot guide. It was successful, but the phone didn't turn on after reboot and now it doesn't turn on when pressing power button. I might have used wrong superboot version.
I am able to put my N1 to bootloader mode but when I choose 'recovery' it stucks on cross logo with 2 white pixels. Or when I connect it to pc, it freezes.
My device's details:
Hboot-0.35.0017
MICROP-0b15
RADIO-5.12.00.08
Is there anything I can do to recover my phone?
I searched for solution but didn't find anything useful.
Click to expand...
Click to collapse
Maybe your recovery is corrupted. Just reflash via fastboot the recovery.

I can't reflash via fastboot as my device freezes when I connect it to my PC :/

ukes said:
I can't reflash via fastboot as my device freezes when I connect it to my PC :/
Click to expand...
Click to collapse
Did you use correct version of superboot? I was at modaco.com and there were several versions for the N1. In addition, is your N1 a retail version? If yes, did you follow the recommendation to unlock the bootloader?

taodan said:
Did you use correct version of superboot? I was at modaco.com and there were several versions for the N1. In addition, is your N1 a retail version? If yes, did you follow the recommendation to unlock the bootloader?
Click to expand...
Click to collapse
My N1 is not a retail version, my bootloader is unlock.
However I am not sure now if I used the correct version of superboot.

Does anyone else has any suggestions how to make my device work?
Thanks

not for your device but im sure it can be done if u ask developer hasoon2000 when ever my amaze 4g goes poop i use that to fix it here the link to the Toolkit http://forum.xda-developers.com/showthread.php?t=1493905 i suggest asking in that thread for help my best advice and sorry i couldn't help you i try to tho

[Q] Assistance needed: bricked my HTC One, hard.

So, here's the deal: I accidentally flashed an International/ATT/T Mobile rom in haste.
Upon doing so, my phone boot loops at the boot loader. I couldn't boot into recovery or into the rom at all.
I tried to go about "unbrick/unrooting" the phone -- I relocked my bootloader but am stuck now not being able to access the phone in ADB or through the RUU.
I am really at a loss at where to go from here. What info can I provide for some guidance?

First you sure you cant get adb to workk with computer? You need to try and run the ruu. If not im not sure. Does you bootloader say s-on or off and is it locked or unlocked
Sent from my HTCONE using xda premium

HTC_M7 said:
First you sure you cant get adb to workk with computer? You need to try and run the ruu. If not im not sure. Does you bootloader say s-on or off and is it locked or unlocked
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
ADB works with the computer, I've used it before. The RUU runs, but when it doesn't see the device, and neither does adb when I use adb devices.
The phone is currently:
*** TAMPERED ***
*** LOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013,18:47:36:-1
Ugh.

Check-
fastboot devices
If it recognizes the phone flash a custom recovery.
fastboot flash recovery name_of_file.img
boot to recovery and now use adb
Put a SPRINT hboot in your adb/fastboot folder
adb push name_of_hboot.img /sdcard/hboot.img
adb shell
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
Then reboot to bootloader and run the ruu
---------- Post added at 04:29 AM ---------- Previous post was at 04:26 AM ----------
18th.abn said:
Check-
fastboot devices
If it recognizes the phone flash a custom recovery.
fastboot flash recovery name_of_file.img
boot to recovery and now use adb
Put a SPRINT hboot in your adb/fastboot folder
adb push name_of_hboot.img /sdcard/hboot.img
adb shell
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
Then reboot to bootloader and run the ruu
Click to expand...
Click to collapse
Disregard......your locked....... Try to unlock it again (likely won't work)
fastboot flash unlocktoken Unlock_code.bin

Fastboot Devices just gives me another clean prompt.
Fastboot device gives me a (waiting for device)... =(
I've noticed when I plug in the "Fastboot" on the bootloader goes away... thoughts?
EDIT: fastboot flash unlocktoken Unlock_code.bin gives me (waiting for device) as well.

Try the tool located here. http://forum.xda-developers.com/showthread.php?t=2236814
I would try flash recovery, sideload Rom and finally RUU. Good luck.

Will this undo s off? I'm going to return phone due to it shutting off randomly.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Try the tool located here. http://forum.xda-developers.com/showthread.php?t=2236814
I would try flash recovery, sideload Rom and finally RUU. Good luck.
Click to expand...
Click to collapse
I haven't tried this yet, as I'm at work now -- however I think there's a bigger issue: neitehr Fastboot or ADB see my phone.
Anyone else have any ideas about how to force this thing into connectivity?

loxish said:
I haven't tried this yet, as I'm at work now -- however I think there's a bigger issue: neitehr Fastboot or ADB see my phone.
Anyone else have any ideas about how to force this thing into connectivity?
Click to expand...
Click to collapse
The One tool actually worked, holy cow. I've got recovery again and am going to flash a new rom.
Thanks guys.

Okay.
Here is where I'm at now.
I'm unlocked and have TWRP 2.5.0.0 installed.
However, when I go to start the sideload, it just sits there at "Starting ADB Sideload feature..."
Any ideas? I need to sideload this rom so I can boot the phone.

loxish said:
Okay.
Here is where I'm at now.
I'm unlocked and have TWRP 2.5.0.0 installed.
However, when I go to start the sideload, it just sits there at "Starting ADB Sideload feature..."
Any ideas? I need to sideload this rom so I can boot the phone.
Click to expand...
Click to collapse
Further update: ADB Sideload finally worked, gave me "100% Sideload Complete" on the computer and the "lock" button was up on the phone -- but the screen was unresponsive, couldn't unlock it... when I unplugged it from the computer, the screen went black and it is completely unresponsive now. No power, nothing, no backlight.
Ugh.

loxish said:
Further update: ADB Sideload finally worked, gave me "100% Sideload Complete" on the computer and the "lock" button was up on the phone -- but the screen was unresponsive, couldn't unlock it... when I unplugged it from the computer, the screen went black and it is completely unresponsive now. No power, nothing, no backlight.
Ugh.
Click to expand...
Click to collapse
Now that your computer sees the phone, you could try the ruu again. Hopefully that will get things up and running.
Sent from my HTCONE using Tapatalk 4 Beta

Well, seems I doomed myself there because it doesn't now. It did, before I tried to sideload and now the phone is, insofar as I can tell, completely dead. ****...

loxish said:
Well, seems I doomed myself there because it doesn't now. It did, before I tried to sideload and now the phone is, insofar as I can tell, completely dead. ****...
Click to expand...
Click to collapse
Has anyone ever seen this?
I tried to sideload the Slim rom and the unit is now completely black.
The odd thing is: It's still on, however it's not responding to any button pressing. I can tell it's on because 1) it's warm on the back for an extended time and 2) if I plug it in, the drivers show up.
I suppose I should just let the battery die.
Ugh.

loxish said:
Has anyone ever seen this?
I tried to sideload the Slim rom and the unit is now completely black.
The odd thing is: It's still on, however it's not responding to any button pressing. I can tell it's on because 1) it's warm on the back for an extended time and 2) if I plug it in, the drivers show up.
I suppose I should just let the battery die.
Ugh.
Click to expand...
Click to collapse
Put the phone under a bright light and press/hold the power button. This isnt a joke either.

Konfuzion said:
Put the phone under a bright light and press/hold the power button. This isnt a joke either.
Click to expand...
Click to collapse
I've actually heard that. I will give it a shot.

This worked! Brilliant!
Now, at this point I've got a rom loaded, have recovery access/etc, the only issue is that the rom turns the phone off after about 10 seconds.
Going to try to reflash it from sideload. Is there no way to mount the storage through recovery?

loxish said:
This worked! Brilliant!
Now, at this point I've got a rom loaded, have recovery access/etc, the only issue is that the rom turns the phone off after about 10 seconds.
Going to try to reflash it from sideload. Is there no way to mount the storage through recovery?
Click to expand...
Click to collapse
I know I sound like a broken record, but if that doesn't work, try the ruu. When my phones have been messed up from flashing ROMs, that fixed them.
Sent from my HTCONE using Tapatalk 4 Beta

coal686 said:
I know I sound like a broken record, but if that doesn't work, try the ruu. When my phones have been messed up from flashing ROMs, that fixed them.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Awesome, will do -- do I need to lock the bootloader again?

loxish said:
Awesome, will do -- do I need to lock the bootloader again?
Click to expand...
Click to collapse
yes, to run an RUU-yes

HTC ONE stuck on Bootloader screen HELP PLEASE!!!!!

Im really frinking out my phone is stuck on Bootloader screen i root everything was good and for some stupid reason i decided to updated it to 4.3 and after i run it and it restart i just keep going back to bootloader screen try recovery but it will just got back to same screen when you plug into the computer it does detect ti just fine but i don't know what to do this is what is on my screen. i try RUU but is say i have the wrong version (31.1)
and the phone is like completely wipe out. some HELP ME PLEASE , I don't have insurance nor warranty and the phone is like 1 month old
Sprint HTC one
***tampered***
***Relocked***
M7_WIL PVT SHI P S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot

Please help. Im in the same situtation
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!

I got mine fixed!!!
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect

blacky305 said:
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
Click to expand...
Click to collapse
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!

blacky305 said:
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
Click to expand...
Click to collapse
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??

Cubanflow2992 said:
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
in the same boat...

For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
Cubanflow2992 said:
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
---------- Post added at 03:46 AM ---------- Previous post was at 03:18 AM ----------
khigdon1 said:
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
Click to expand...
Click to collapse
I did a **** load of stuff to try to fix it, even let my roommate go at it for a day. Numerous things were done beforehand but I would often get the same error. The thing that did the trick was following Indirect's forum.
I had my phone unlocked, went in to recovery, the first two adb commands did some stuff. The third command I received an error however recognizing the command, I just rebooted the phone through the TWRP menu. I then went into fastboot where I relocked the phone. After locking the phone I ran Sprint_HTC_One_m7wls_1.29.651.7_RUU and my phone was fixed. Hopes this helps

Did you guy type exit after the echo command?

bigdaddy619 said:
Did you guy type exit after the echo command?
Click to expand...
Click to collapse
I closed out the window after the echo command. I later reopened a new command window to lock the phone in fastboot

blacky305 said:
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
is never goes to back screen when i turn my phone on like i would regularly it goes to the bootloader screen i select recovery and i goes to the TWRP ... i just bot a OTG USB cable and i place the custome rom the usb and plug ti into my phone but i will not load it
Click to expand...
Click to collapse

Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app

mrlakadaddy said:
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i got this one
eForCity Micro USB OTG to USB 2.0 Adapter compatible with Samsung© Galaxy S III / S3

[Q] Stuck in HBOOT loop

Hi,
I know that the boot loop scenario is pretty common, but my problem seems bizarre. I recently installed cyanogenmod successfully but I was unhappy with it so I decided to remove it and install a clean version of Sense 5.5. I obviously screwed up somehow.
The problem is that the phone doesn't want to boot up to the normal home screen. Whenever I power the phone on it automatically boots onto the FASTBOOT screen. From there I get a number of different problems, I shall list which options work and which do not; FASTBOOT works, RECOVERY does not (reboots back to FASTBOOT), FACTORY RESET does not work (reboots back to FASTBOOT), SIM LOCK does not work, IMAGE CRC works, SHOW BARCODE works.
When I use FASTBOOT USB I am unable to see my device on my computer also, so I am unable to look inside my SD card or use abd commands.
Here is what the top of HBOOT reads;
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013,00:29:38.0

It seems your boot loader has been relocked. It must have been unlocked for you to install cyanogenmod right?
Which method did you use to install a clean version of Sense? I'm not too familiar with running RUUs but if you want the phone to stay rooted then I would flash a new recovery using fastboot.

I'm running into a similar problem, my HTC One is just like yours, my computer doesn't even read it as a media device and says that there's something wrong (duh), tried running up ADB, redownloaded drivers and I still have no luck.
Sent from my SM-N900T using Tapatalk

JasSingh93 said:
It seems your boot loader has been relocked. It must have been unlocked for you to install cyanogenmod right?
Which method did you use to install a clean version of Sense? I'm not too familiar with running RUUs but if you want the phone to stay rooted then I would flash a new recovery using fastboot.
Click to expand...
Click to collapse
It must have been unlocked. I used ClockworkMod, I deleted the cache and then installed the Sense ROM from my SD card.
I tried to run a RUU but I couldn't because my phone is not being recognized by my computer.

@ hrogers .. Try to load a custom RECOVERY from TWRP and/ or an RUU. executive from HTCguru
Sent from my HTC One using XDA Premium 4 mobile app

dayze0 said:
@ hrogers .. Try to load a custom RECOVERY from TWRP and/ or an RUU. executive from HTCguru
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unable to do that due to no connection between phone and computer.

hrogers123 said:
Unable to do that due to no connection between phone and computer.
Click to expand...
Click to collapse
You should be able to send commands to the phone using fastboot USB. Have you checked you have the correct drivers installed and correctly set it up? Tried using a different PC maybe?
Also try starting from scratch, deleting all the PC fastboot files and drivers and re-setup.
I've never had any problems with fastboot, it usually never fails.

JasSingh93 said:
You should be able to send commands to the phone using fastboot USB. Have you checked you have the correct drivers installed and correctly set it up? Tried using a different PC maybe?
Also try starting from scratch, deleting all the PC fastboot files and drivers and re-setup.
I've never had any problems with fastboot, it usually never fails.
Click to expand...
Click to collapse
Wow i'm a dumbass, completely forgot about fastboot commands. Will do that now to see if it fixes the problem.