[Q] Help needed, stuck after failed attempt to update ROM - HTC One X

Hi
I recently tried to update a stock handset from 3 to the Android Revolution HD 18.2 ROM, but have failed and now cant get it to boot at all.
I have CID: H3G__001 and HBOOT 1.12, i think i may have jumped the gun and not updated my hboot but could be wrong.
I am using a mixture of Hasoon2000 v2.3 tools and some adb commands found while searching for solutions, but nothing i try seems to restore it.
When i first rooted / unlocked it, i installed TWRP 2.4.1.0 from Hasoon's tool, and did a backup.
I have tried restoring from this backup but all i get is stuck at the 3 logo, rather than the HTC one.
I tried to re-lock the bootloader and reboot, clear all the cache but still nothing....
I have spent hours now searching for possible solutions before finally calling out for help, as i think i am now likely to do more damage than good.
I even tried to download a full backup from Matt's collection http://forum.xda-developers.com/showthread.php?t=1975140 but this failed to install
HELP !!!! Phone is now dead

Hi.
You need to update your hboot in order to flash ARHD 18.x.
Your backup failed to boot because you didn't flash the boot.img of it. Get the boot.img at /sdcard/TWRP/ and flash it.

TToivanen,
Thanks for such a fast response.
I have tried searching for the correct files to use to update my hboot, but the list from http://forum.xda-developers.com/showthread.php?t=2153777&highlight=hboot just confuses me as i cant seem to work out the correct one to use (if any).
Do you know where i could get the right hboot for my cid ?
If i update the hboot and re-flash the ARHD 18.x. - if this fails again, will i still be able to recover to stock using TWRP recovery and your method of locating the boot.img from the sdcard/TWRP ?
Many thanks, its just i have been going round in circles for ages and gave my other phone to a friend so now desperate to get back up and running again.

I think you have more succes in this thread
http://forum.xda-developers.com/showthread.php?t=1927048
And yes you can always return to a backup or another rom ....

Oké so download the firmware.zip from the link above and do these fastboot commands. Note that you will need the original Unlock_code.bin because this method involves locking and reunlocking the bootloader. Search for it in your email inbox.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do two or three times if it fails)
fastboot flash unlocktoken Unlock_code.bin
fastboot flash recovery openrecovery-twrp-xxxx.img

Thanks all, managed to un-brick it, now time to play and see what it can do.
Updated hboot by following the instructions http://forum.xda-developers.com/showthread.php?t=1927048
Then went back to install the Android Revolution HD 18.2 ROM and boot.img and all working again.
Not sure if its the best ROM for this device but i thought its a reasonable place to start. Going to install Titanium backup first and also do a full nand backup just in case something goes wrong, or i feel brave enough to try a different ROM.
Thanks again.

You're welcome!

Related

Unbricking HTC One X... Pls Help Me

Hi Gentlemen,
I am new to rooting Androind phones since been using iphone all this years. Right now, I think my HTC One X is bricked. This is what I've done to cause it in this situation:
1) After installing Clockwork Recovery and Super SU. I installed the super wipe.
2) Run super wipe and proceeded to install Android Revolution ROM but the installation was unsuccessful. Not much reason was stated. So I proceeded to reboot the phone and now it just hang at the splash screen.
I've done alot of read up and research the forum how to unbrick my phone but I'm clueless and don't know what to do anymore. I can still get to bootloader screen and that's the furthest I can go.
Pleasse help me.
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
After doing step 2, I receive this respond:
... INFOLock successfully...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Is it something wrong?
amigo_s said:
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
I did try doing that but this error pops out:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Pls help me
I take it you did the right thing and made sure you have the right RUU for your phone before you attempted to root?
Hmmm managed to get myself stuck in the same situation here a well as wouldnt go back into recovery. Have relocked bootloader but whn I try to reflash RUU it wont recognise the phone even though it shows in device manager correctly and I can control via fastboot commands but doesnt show when using adb devices.
Any ideas whey RUU cant see the phone?
it defo the correct Ruu?
Mod or Die
Hi.My problem is when I want flash stock terminal give something like that sending 'recovery' (5786 KB)... FAILED (remote: (00120000))
whats the problem?
ps1
right now its
sending 'recovery' (5786 KB)... OKAY
writing 'recovery'... FAILED (remote: battery low)
MacBook-Pro-xxx:fastboot xxx$
when i try to charge phone automaticlly starts
snowwhite007 said:
it defo the correct Ruu?
Mod or Die
Click to expand...
Click to collapse
I presume so as is EUROPE RUU of which I can only find 2, hav the other one downloading currently, but the dialogue it comes up with says about no connection via USB and surely even the incorrect RUU would dectect the phone but fail on authentication wouldn't it?
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Remember to Flash Stock Recovery before relocking your bootloader.
wen you are done whit that enter bootloader and press Fastboot then run the RUU file...
DaDoctor!
ya i was one of the first to say that lol but i dont care anymore hehe im just trying to help ppl but sometimes ill get wen seeing ppl posting that exact same thing you have done to alot of pll
Managed to get the RUU to recognise my phone, needed HTC Sync installed even though everything else was working ok without, but although I can now flash RUU's I get a customer number error which I guess Im getting as my phone was a branded T-Mobile one.
Therefore am I correct in saying that unless I can get RUU 1.26.110.5, which is the RUU I need, or get recovery working again by some mircale then Im screwed and now have a rather expensive paper weight?
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
I FOUND THE SOLUTION !!!!!!!!!!!!!
First Sorry for my French !
So, flash stock recovery first, lock the recovery.
Go to fastboot, and click on the Power Off, screen goes black and the phone is OFF.
Put the charger and the usb on the phone, WAIT 1 or 2hours, led still red, DON'T POWER ON !
When is done, go fastboot, launch RUU, IT'S DONE, battery is good !
Works for me
Swannsin said:
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
Click to expand...
Click to collapse
Cool well done for getting back into recovery....how did you manage it? As for getting rom back did you not do a backup of the previous rom before wiping? If not you may be stumped for the time being as USB mount does not work on any of the custom recoveries so far.
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Ok managed to get mine booting back into CWM Recovery as well now but dont think about sending back to HTC as the CWM guys are working on USB Mount & ADB as we speak so dont think it will be to long. Ill look into fatboot commands now and see if there isnt soemthing we can use.
There's always a way..........
DaDoctor said:
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Click to expand...
Click to collapse
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
snowwhite007 said:
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
Click to expand...
Click to collapse
Backups are only half of the story. When you cant get into recovery to restore the backups that you HAD made and then when trying to reflash the RUU to resotre your phone it then wipes the backups but then allows you back into recovery where you now have no backups nor the ability to mount USB or push anything to the SD so and still in the same siutation just with nice blue writing now thats just plain sods law......LOL!
---------- Post added at 09:24 PM ---------- Previous post was at 09:16 PM ----------
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Think we are fairly screwed until either USB/ADB is working in recovery or S-Off is available in which case any RUU should work I believe. Worth hanging on rather than paying HTC in my opinion.

Back to Stock HTC Euro Rom

I have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
monkeyphonix said:
I have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
Click to expand...
Click to collapse
You can go back; it's only if you'd done an official update (OTA or RUU) that you'd be stuck, because they also update the bootloader and you can't downgrade that.
Since you've got backups I would just restore the backup of the T-Mobile ROM, flash the boot.img which is in the nandroid backup folder, then (if he's wanting it completely stock), flash the stock recovery and lock the bootloader again.
Alternatively, if you can find a T-Mobile RUU you can just lock the bootloader then run the RUU to write everything back to stock, but it seems a waste of time downloading a full RUU when you've got a backup of the software you want already sitting there.
Hey thanks, will give that a try..cheers
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
monkeyphonix said:
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot as well?
Does that have to be done on my pc ? I just flashed the boot.img then the actual backup. Via the phone
Unless you're s-off you can't write to the boot partition from recovery, so you need to do it from your computer using fastboot. Exactly the same as when you're flashing a ROM.
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
monkeyphonix said:
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
Click to expand...
Click to collapse
Interesting; I'm impressed your ROM's been working, seeing as you've seemingly been using the stock 1.26 boot.img with the 1.29 ROM.
Anyway, it's a similar (red identical) process to the one you used to unlock the bootloader. Assuming you've still got the fastboot executable on your PC from when you unlocked, and a copy of the boot.img from the backup you're trying to restore:
1) copy boot.img into the same folder as the fastboot binary
2) turn your phone on in fastboot mode (turn it off, hold vol-down and power on and it should boot into bootloader; select 'fastboot' from the menu if it doesn't automatically load into fastboot mode)
3) connect the phone to the PC via USB (the text on the phone should now say "fastboot USB")
4) on your PC open a command prompt and navigte to the folder containing your boot.img and the fastboot binary
5) run the following command: fastboot flash boot boot.img
6) run the following command: fastboot erase cache
7) run the following command: fastboot reboot
I've just reverted back to stock recovery instead of the original boot for some reason, been at a wedding and am a bit very drunk still, so I really need to get the stock boot.img file from somewhere don't I.
Edit, I found it in clockwork folder by connecting to pc and it is 8mb from April.
I did what you said and it all worked, great thanks. I am now back on stock boot.img abd back to tmobile 1.26....but still with the clockwork recovery and still rooted.
I know how to revert back to the stock recovery as I just did it by mistake...should I be d-rooting it or whatever you call it...and will I have wiped out my sim unlock I paid for ?
Also it is offering me an update of 28 or so mb, is this safe to install ? I am on 1.26 right now. Or do I want to get rid of clockworkd and revert to stock recovery first ?
The 28mb update will be the 1.28 update; you would need to restore the stock recovery and lock the bootloader again to install that (it will just download and fail if you try to install it now).
If the person you're selling it to wants it completely back to stock, then flash your stock recovery, then go back into fastboot (same process as before) and use the command fastboot oem lock to lock the bootloader again. Then accept the update and it'll be back to stock and updated to 1.28.
No idea about SIM-unlocks, sorry. I imagine it would still hold (otherwise everyone who's flashing ROMs, updates or backups would need to keep re-doing it), but I'm honestly just guessing at this point so don't take any of that as anything conclusive.
Ok I did all that and relocked it just about to do the update. Thanks very much for your help.

[Q] htc one x rebooting

please help me! I tried to flash a new rom and after doing the 'fastboot flash boot boot.img' command it keeps restarting. The phone is booting to the lock screen and i can only see the wallpaper, and after 2 seconds it restarts.
Details please. What ROM did you flash and what ROM did you come from? What guide or method did you follow to install the new ROM? What backups do you have available? If none, then what is you CID and Mainver number to see someone has provided a nanadroid backup for you to use.
capusniac said:
please help me! I tried to flash a new rom and after doing the 'fastboot flash boot boot.img' command it keeps restarting. The phone is booting to the lock screen and i can only see the wallpaper, and after 2 seconds it restarts.
Click to expand...
Click to collapse
P.S. i tried to do nandroid restore, and a factory reset but it won't help
It could be because of incompatibility with the current system and/or userdata
Did you:
1) flash the right system.img for this boot.img. it should be provided with the ROM
2) do a factory reset / erase userdata
To install system you do:
Fastboot flash system system.img
To erase userdata:
Fastboot erase userdata
You can also send me the result of the logcat untill the device reboots if adb debugging is enabled
Can you specify also which ROM are you using
Sent from my Galaxy Nexus using xda premium
requiem11 said:
Details please. What ROM did you flash and what ROM did you come from? What guide or method did you follow to install the new ROM? What backups do you have available? If none, then what is you CID and Mainver number to see someone has provided a nanadroid backup for you to use.
Click to expand...
Click to collapse
i don't know what rom it had on it because the phone wasn't mine. I tried to flash http://forum.xda-developers.com/showthread.php?t=1745176
cid: htc_orang309
i saved the nandoid back up on computer
Verify djodjoni's suggestions and instructions. Post what you've learned.
I thought I recognized your username. You've posted recently. hboot 1.36 but ICS rom loaded, so you are looking for a jellybean rom that works with your new Hboot that some dodgy repair shop loaded. I take it you've opted for ViperX. Is this right?
requiem11 said:
Verify djodjoni's suggestions and instructions. Post what you've learned.
I thought I recognized your username. You've posted recently. hboot 1.36 but ICS rom loaded, so you are looking for a jellybean rom that works with your new Hboot that some dodgy repair shop loaded. I take it you've opted for ViperX. Is this right?
Click to expand...
Click to collapse
yes, and it was at the gsm because of the same problem, but previously it stopped at the htc logo
where i have to put the boot.img file to flash it? i want to be sure not to harm my phone even more
I'm not using the ViperX ROM, I'm actually using stock, but great instructions for flashing roms is available here:
http://forum.xda-developers.com/showthread.php?t=2069904
i flashed the rom but after the htc and venom boot animation it stops at the htc logo and not entering lock screen like earlier
Can somebody help me solve this problem?
Ur doing smth wrong. what exactly are you doing there? Step by step.
Also can you do adb shell?
yuhuu
i solved the problem. I found another cid orang309 nandroid back up and it worked!!!
when i tried to restore with my back up, where was the same problem. But now it works fine.
Also i had android version 4.0.3 which they installed at gsm repair, and it was laggy, but now i have 4.0.4 and works just fine)))
btw you don't know when we'll receive 4.1.2? because when i bought it, it had 4.1.2

[Q] Bricked HTC One need help please

So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
volumebmx15 said:
So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
Click to expand...
Click to collapse
It depends on what you are trying to do. You said you wanted to flash a new recovery, so go ahead and do it.
http://forum.xda-developers.com/showthread.php?t=2416431
If you want to revert back to stock, go ahead and do that too.
http://forum.xda-developers.com/showthread.php?t=2475216
But I say your best bet is to just push a ROM in recovery. Are you S-Off?
Also, what commands are you doing to push a ROM? Is the E: drive where your SDK toolkit located?
Karn101,
What ROM and RECOVERY would you suggest I flash?
I had the TWRP 2.6.3.4 touch recovery installed but for some reason it would not allow me to install the following 2 ROMS
1. Google Edition HTC One VZW [KITKAT]
2. Inverted-EclipticONE-KitKat-v1.2
When I did this I kept getting the E: Error executing updater binary which really had me as a loss.
To answer your question I am S-OFF it says UNLOCKED M7_WLV PVT SHIP S-OFF RH @ the bootloader screen.
HBOOT Version is 1.54.000
Also when I was pushing a ROM I was using some commands I found in a guide here: http://forum.xda-developers.com/showthread.php?t=2354259
I followed some of the steps on here with no luck...
Also I attempted to flash several recoveries from Fast boot with the Fastboot flash recovery recovery.img in the command promt. It shows that the files was sent but the phone just get stuck at the bootloader saying loading recovery at the top in blue font.
Can you walk me through each step on this? I need to get a recovery on there first them push a ROM to the device and install it via the recovery.... I am assuming that would be the easiest method.
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Tigerstown said:
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Click to expand...
Click to collapse
I suggest this as well.
also
"brick" means phone is dead. you're phone turns on..
not a brick.
what i did once when i couldnt flash RUU was it should work S-On and well Its got to work on S-Off
1-Download TWRP recovery also the System.img and boot.img
2-Rename TWRPRecovery6.3xx.img to Recovery.img
3-Flash recovery in fastboot fastboot flash recovery Recovery.img
4-boot into recovery via fastboot fastboot boot recovery.img
This will boot your device into the custom recovery
5-press Backup
6-swipe to confirm
7-after it's done making a backup
8-navigate back to the home screen
9-press Advanced
10-press Mount
11-check the box next to USB-OTG
This will allow to mount your sdcard into the computer and you can copy the system.img from the RUU
12-open folder TWRP open folder BACKUPS ETC ETC until you get to the folder with the backup you just made
13-delete the system.ext4.win delete the system.ext4.win.md5
14-copy the system.img here abd rename it to
15-system.ext4.win
16-then unmount
17-then navigate back to the home page in the recovery and
18-press Restore
19-then choose that backup and swipe to confirm
20-also recommend fastbooting the boot.img
this is what i did when i couldnt get any rom to flash any roms via recovery nor a i could do a RUU saved my phone.

Need help reviving my One

I'm in a pickle and I hope someone will be kind enough to try to help me.
I can get into HBOOT and TWRP recovery OK. I don't have a ROM on the phone to flash. I have one Nandroid but it fails (not enough space).
I have Minimal ADB and Fastboot (version 1.0.31) on my Windows 7 Pro machine. I can get fastboot to recognize my device, but not ADB.
How can I get a ROM .zip into the phone?
major_works said:
I'm in a pickle and I hope someone will be kind enough to try to help me.
I can get into HBOOT and TWRP recovery OK. I don't have a ROM on the phone to flash. I have one Nandroid but it fails (not enough space).
I have Minimal ADB and Fastboot (version 1.0.31) on my Windows 7 Pro machine. I can get fastboot to recognize my device, but not ADB.
How can I get a ROM .zip into the phone?
Click to expand...
Click to collapse
You can flash my NuSenseSIX rom like you would the firmware in the stock thread.
I included an android-info.txt file, so it will actually flash like firmware or an RUU would.
So I would say try that.
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip NuSenseSIX-KitKat_m7vzw_RC5.0_041114.zip
You can rename the file if you want for ease or just copy and paste the above.
Thanks, Santod. I had Hawknest's build on the phone, which kept failing during the data restore. So in desperation, I tried a restore minus the data partition. That did the trick. I still need to figure out why ADB isn't working. It was working fine last time I needed it .
Sent from my HTC6500LVW using Tapatalk
Santod: Well, I am a first-class idiot. My phone was fine, running EclipticSix. But I just had to try flashing the NuSense ROM in RUU mode.
Didn't work. Or I have screwed it up. In any case, I'm back where I started, only now I don't have a nandroid on the phone, or anything else, for that matter.
I followed the usual pattern for flashing NuSense:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
All I get is the HTC splash screen. When I go back into recovery, it tells me there is no OS installed.
I'm in the process of downloading the decrypted 2.10.605.1 RUU posted in your stock thread.
I have the same RUU with encryption also. The phone is S-Off but no superCID. Can I flash the encrypted RUU or should I wait for the decrypted one to download?
Sorry to keep bugging you; I know you have bigger fish to fry. But thanks in advance for any advice.
EDIT: Back in business. I flashed the decrypted RUU and she is up and running. Whew.

Categories

Resources