Hey!
I tried to flash the Maximus rom onto my one s today and I needed quite a few tries.
Unfortunately I forgot to check if my phone is s off and it isn't. Now I flashed the rom and after I start the phone I only see the htc starting screen for a few seconds and then it turns black and flashes a little bit every 4-5 seconds.
Do you guys know how I can turn the device to s off and then flash it?
Thank you so so much!
Tom
Go to bootloader and conect the phone with youre PC. Read carefully the description. Follow the steps.
.
http://forum.xda-developers.com/showthread.php?t=2488772
http://rumrunner.us/
Thanks for the answer but the problem is that I can't start the phone to activate the developers mode or do anything else! It would have to be through fastboot or recovery! Also my computer doesn't recognize the phone, even though I was able to push something on the phone through adb sideload!
Did you make a NANDROID backup with a custom recovery? If so, restore from that.
I didn't!
tomlennart said:
I didn't!
Click to expand...
Click to collapse
What recovery do you have on there? You can flash a custom recovery on there like TWRP.
If you get TWRP on there, you can mount the sdcard and copy another ROM on there. Then do a full wipe and install the zip and then flash the boot.img to get something like CM11 on.
Alternately, you can relock your bootloader with fastboot usb, then install an RUU to bring it back to stock, then try something like moonshine.io to get S-OFF, then try maximusHD again.
808phone said:
What recovery do you have on there? You can flash a custom recovery on there like TWRP.
If you get TWRP on there, you can mount the sdcard and copy another ROM on there. Then do a full wipe and install the zip and then flash the boot.img to get something like CM11 on.
Alternately, you can relock your bootloader with fastboot usb, then install an RUU to bring it back to stock, then try something like moonshine.io to get S-OFF, then try maximusHD again.
Click to expand...
Click to collapse
I do have TWRP on there!
So, how does it work? I choose Mount, then which options do I pick? And does my computer automatically recognize the phone in the list of the connected devices or do I have to download a special program?
Which rom should I take and how exactly does it work? Is there a tutorial out there so you don't have to do all the work?
Thank you so much!!!
So reboot into bootloader. First see what HBOOT you are on. It will determine what ROM you should try.
If you have 2.15 you go with ROMS that support 2.15. If 2.16 then go with something that supports 2.16.
As far as mounting, go into TRWP. Choose MOUNT and choose Internal Storage. This will allow you to mount the internal storage on your computer.
I guess mine is 2.13 right? I don't have enough posts to post pictures so please delete the space between https:// and the rest of the link!
https:// fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xpf1/v/t34.0-12/10489061_699433320094234_38826939_n.jpg?oh=8ce1fb23d7e28d252398dd8f2d96a028&oe=53AD076A&__gda__=1403852663_8e60ad520e5b3c61a58cbf3dc20ba7c8
When I go to mount, I can't click on internal storage! I choose all I could, but the last two are "unclickable"
https:// fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xpa1/v/t34.0-12/10382441_699434953427404_7278275326706422508_n.jpg?oh=7ced00497a3f1fc8ef6afd846c75d002&oe=53AD15FF&__gda__=1403850025_68d5f9975589a6e19adacdff5a3607df
Thanks for taking up with my stupidity!
Someone chime in, but maybe you will want to upgrade your HBOOT to 2.15???
What is the carrier? Where are you located?
This _may_ be your RUU - don't run it until we know your carrier/location:
http://mobilefileserver.com/download.aspx?get=167185
PJ40IMG_Ville_U_JB_45_S_HTC_Europe_3.16.401.9_Radio_1.15.50.05.29_10.30.50.08L_release_314432_signed
Running an RUU will get you back to stock. After that, you may want to upgrade your ROM so it's compatible with moonshine.io or other S-OFF application. Once you become S-OFF you are much more free to do many things to your phone.
BTW: in your picture data might be the the choice to try. Try and mount data and see if you see your files on there.
I'm using AT&T right now, but the phone doesn't have a simlock. My location is a little bit complicated, I'm in Wisconsin right now, but the phone is from Germany, and I'll go back to Germany in about two months.
My computer doesn't recognize the phone at all, but makes the noise like you unplug something...
How would I upgrade the HBOOT?
I hope you have fastboot installed on your computer (windows?) if not:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Boot into the boot loader, make sure it ways fastboot USB
On your computer in terminal, type: fastboot devices
Hopefully it will return something.
Okay, finally I'm back in Germany and have time to try it!
I did what you just told me and it returned this:
C:\Users\Tommi>fastboot devices
HT23RW400512 fastboot
Thats good, right?
So what would the next steps be?
Thank you so much for your help!
Anyone?
Is there anyone who can help me?
tomlennart said:
Is there anyone who can help me?
Click to expand...
Click to collapse
OK you said you had TWRP. Start up in recovery, go to mount and then select internal storage.
See if the sdcard partition mounts on your computer.
If so, at that point you can put a rom on there and also the boot.img that you need to start your phone up.
No, I can't mount the internal storage!
Somewhere I saw how to fix it before but I don't remember how and where I saw it!
tomlennart said:
No, I can't mount the internal storage!
Somewhere I saw how to fix it before but I don't remember how and where I saw it!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1630459
But where do I get the stock recovery? I googled a little bit and saw that there are like a thousand different ones!
Sorry for all the stupid questions And thank you all for the help!
tomlennart said:
But where do I get the stock recovery? I googled a little bit and saw that there are like a thousand different ones!
Sorry for all the stupid questions And thank you all for the help!
Click to expand...
Click to collapse
Here is mine from my dropbox
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
Related
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium
subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.
wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...
Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium
I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?
I was stupid. Point blank.
How can I get a ROM zip back on so I can flash it again?
It just hangs at the boot screen when I try to start up, but I'm able to get into TWRP recovery. Please help..I'm kinda freakin out.
Nothing showing on the internal card to be able to flash.
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Vinsane said:
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Click to expand...
Click to collapse
have you tried flashing the stock rom with fastboot?
crazynitro said:
have you tried flashing the stock rom with fastboot?
Click to expand...
Click to collapse
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Vinsane said:
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Click to expand...
Click to collapse
you dont need any anything to be able to flash. you just need a laptop with the asus drivers installed and the latest fastboot. I'm pretty sure you cant flash a custom rom with fastboot. i havent tried it myself but i wont take the risk. you could just flash the stock rom and then later intall the custom recovery and then go ahead and install the custom rom.
I think I got it. Thank GOD for the NEW TWRP recovery.
This is what I did. I poked around TWRP and noticed that I was able to change the storage location on where it looks to install. I thought...if I can load the zip to a micro SD and flash it from there..gravy.
Of course the day as it is...the SD reader on my comp stopped working..been running around the office trying to find on that did. Finally did...placed rom zip on it..rebooted into recovery..flashing right now as we speak
Praying and crossing fingers!
It freakin WORKED! I'm baaaaaack.
The only bad part is I lost my stock backup...but that's a small price to pay to have it working again.
Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:
Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.
Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita
Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.
radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.
bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.
radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.
andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,
radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.
Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.
Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app