Database Develop

Nexus one stuck on X, can't boot to recovery.

Hi,
my nexus one completely unusable, it's been a week since i can't use it. the nexus one can't boot, it just stuck on x. it can't boot to recovery, and also when i try passimg method, it just stuck at bootloader - unzipping. anyone have suggestion to fix it ?,
thanks

You need to give us more details
Like, can you get into fast boot/h boot, using the 3 finger salute?
How did it get to this... What were the last things it did...

i can go to fastboot, i can fastboot flash recovery, system, and boot. but it doesn't change. i can still got the same issue as before.
the last thing i did was playing angry birds. after around 15 minutes playing, it just hang, and i need to pull out the battery to turn it off. starting from that point until now, my nexus one just stuck on X.

Try to remove SD card and boot without it to recovery.
Try to fastboot flash recovery stock_recovery.img (find the stock recovery and flash it), see if you can boot to stock recovery.

You may also want to try:
fastboot boot stock_recovery.img

I've been using an Evo on CM7 and GT-i9000 on ROM Kitchen builds so I thought a Nexus One would be fun.
Booted one up today and it was on Froyo... It tried to update automagic.... but now I can only get into fastboot.
I tried to fastboot flash userdata.img, system.img, recovery.img and boot.img but I'm still stuck on a big stupid X like the original poster.
I've tried to flash a cwm and amon ra img and either way no booting or recovery.
I've never been stuck like this. Even when my GT-i9000 goes into a boot loop it's easy to fix. This is totally beyond me.
I've pulled the microsd and "fastboot update signed-passion-GRI40.zip errors with
Device version-baseband is 4.06.00.12_7'
Update requires '5.08.00.04'
I cannot flash the radio.img inside
"android.d3xt3r01.tk/cyanogen/passion/radios/passion.5.08.00.04.zip"
The bar goes red and all the way to the top and just sits for 10 minutes.
I can fastboot update signed-passion-img-FRG83_0923.zip but I only get an X and lock.
Screen says:
*** UNLOCKED ***
nexusone pvt ship s-on
microp-0b15
Touch panel syn0103
Radio 4.06.00.12_7
Oct 12, 2010 14:33:16
Any ideas?

Try the radio images in the wiki...

this is what happen when i try to boot to recovery,
http://www.youtube.com/watch?v=n8DiTfYXUy4
do you think this is hardware issue ?

Hi rheza02
Did you try fastboot update with the file from HTC?
dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-GRI40.zip
I got my N1 booting today but it turns out I have bad hardware. My N1 only boots when it's really cold. hahah.
Anyway. All I did was
fastboot update signed-passion-img-FRG83_0923.zip then connect to wifi to update to GRI40

eseale said:
Hi rheza02
Did you try fastboot update with the file from HTC?
dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-GRI40.zip
I got my N1 booting today but it turns out I have bad hardware. My N1 only boots when it's really cold. hahah.
Anyway. All I did was
fastboot update signed-passion-img-FRG83_0923.zip then connect to wifi to update to GRI40
Click to expand...
Click to collapse
the link you given redirect me to htc.com/sea, do you have a new link ?,
thanks
---------------Update
i just trying your method.
and it just stuck when flashing the system.
MacBook-Pro:~ rheza02$ /Users/rheza/Downloads/1.0-FRG83-nexusone-insecure/fastboot-mac update /Users/rheza/Downloads/Applications/signed-passion-img-FRG83_0923.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: 0.35.0017
Baseband Version.....: 5.08.00.04
Serial Number........: MB0388888888
--------------------------------------------
checking mid... OKAY
checking product... OKAY
checking version-bootloader... OKAY
checking version-microp... OKAY
checking version-baseband... OKAY
sending 'boot' (2338 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2564 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (125969 KB)... OKAY
writing 'system'...
any suggestion guys ?

guys, can someone help me please ?
thanks

finally, i able to flash using fastboot update technique.
this is the log
---------------
Rheza02:~ rheza$ /Users/rheza02/Downloads/1.0-FRG83-nexusone-superboot/fastboot-mac update /Users/rheza02/Downloads/signed-passion-img-GRI40.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 0.35.0017
Baseband Version.....: 5.08.00.04
Serial Number........: MB038999823
--------------------------------------------
checking mid... OKAY
checking product... OKAY
checking version-bootloader... OKAY
checking version-microp... OKAY
checking version-baseband... OKAY
sending 'boot' (2318 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2556 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (130284 KB)... OKAY
writing 'system'... OKAY
rebooting...
and this is what happen after rebooting.
http://www.youtube.com/watch?v=n8DiTfYXUy4
anyone think this is hardware issue ?

Have you tried to cool it down? maybe put it on a stone tile for 30 minutes?

My HTC RMA was finished in one day.
Went out Fedex Tuesday overnight to Texas
Fixed Wednesday in Texas.
It's back in my hands Thursday.
No charge.

HTC G1 Soft Brick can access bootloader screen

Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49

adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7

Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the help. These files are kind of tough to find though, I'm searching still
I believe I found them here on XDA so I assume I'm flashing with recovery first the radio then bootloader.

Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I followed your instructions and I was successful. New life is now in my old HTC G1 Thank you for your patience.

that was easy bro,
RenaldoTT said:
Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49
Click to expand...
Click to collapse
If you want you can unbrick your devices by downgrading it to android 1.0 then apply the official update for the G1 from Google. It will bring you back to the stock HTC G1 1.6 but you can repeat the rooting procedure. That's what I'm doing before, specially if I flashed faulty roms or messing up with the radio and spl combos. Hope that help you.

My sd card does not read.
Then what???
Sent from my SGH-M919 using xda app-developers app

Either its not named properly, not on root of SD, SD isn't formatted to fat32, or sdcard or sdtray is bad
Sent from my Nexus 4 using XDA Premium 4 mobile app

please describe how did you>>> flash_image recovery /sdcard/cm-recovery-1.2.img
RenaldoTT said:
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7
Click to expand...
Click to collapse
I have the same problem you had. please describe how did you>>>>> flash_image recovery /sdcard/cm-recovery-1.2.img

This would be putting a recovery on root of SD card and naming it cm-recovery-1.2.img
Then booting into the os and running the command in a terminal emulator, that's it
This will only work if your ROM supports the flash_image binary but more than likely yours does.
If you need further help, please explain your problem fully and give all info about your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] soft bricked verizon non-dev moto x

I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635366

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
Are you still able to enter the Bootloader menu?

jpd_ said:
Are you still able to enter the Bootloader menu?
Click to expand...
Click to collapse
yes, I just cant boot into recovery or android.

slappydj1 said:
yes, I just cant boot into recovery or android.
Click to expand...
Click to collapse
Go ahead and flash the stock recovery img then follow the instructions from here:
http://forum.xda-developers.com/showthread.php?t=2639102
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Very helpful link here as well on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2603358
If you made a back up through TWRP, you can try restoring your phone from there too.

jpd_ said:
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Click to expand...
Click to collapse
The Verizon OTA is out. That is what got him in the situation he is in.

I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
They generally seem to show up 1 week to 1 month from when the OTA is released.

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.

Cozume said:
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Click to expand...
Click to collapse
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?

Cozume said:
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Click to expand...
Click to collapse
I tried to boot into recovery using the fastboot menu on the phone.

slappydj1 said:
I tried to boot into recovery using the fastboot menu on the phone.
Click to expand...
Click to collapse
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?

Cozume said:
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Click to expand...
Click to collapse
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed

slappydj1 said:
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
Click to expand...
Click to collapse
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.

Cozume said:
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Click to expand...
Click to collapse
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?

Cozume said:
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Click to expand...
Click to collapse
So Ill have to wait until the factory image is released?

slappydj1 said:
So Ill have to wait until the factory image is released?
Click to expand...
Click to collapse
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.

Cozume said:
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Click to expand...
Click to collapse
I was going to do a factory reset using fastboot, and I flashed the gpt.bin. after that I could not flash anything. Later I learned that wasnt the factory image but the OTA update, so I realized I messed up then.

Flash recovery FAILED (remote: no transfered data)

Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!

calbertuk said:
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
Click to expand...
Click to collapse
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.

majmoz said:
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
Click to expand...
Click to collapse
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP

calbertuk said:
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
Click to expand...
Click to collapse
I don't know what you are trying to accomplish but here is a possibility: How to : Flash HTC One Mini with out S-OFF and no need RUU Stock ROM and [ROM][M4 - 4.09.401.3] Official Stock Sense 6 Rom v2 & Firmware

Trying to Root but having Flash Issues

So im going to admit im a complete noob when it comes to rooting. And i stuck right now AND I NEED AN ADULT......
So i managed to get my boot loader unlocked on my HTC One M8, now the issue im having is flashing TWRP.
I have it saved in the same location as the fast boot file ....but everytime i give the flash command i get this
error: cannot load 'recovery.img'
I even tried the all in one tool kit to flash TWRP and i just get this message
target reported max download size of 536870912 bytes
sending 'recovery' (14934 KB)...
OKAY [ 0.519s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.560s
I have tried looking for so many different answers...but got nothing can someone help me PLZZ