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.
Related
For anyone who wants it, here's the STOCK PRE & Post-OTA recovery images. (I just added PRE-OTA if for some reason it's needed down the road.)
If you plan on flashing it back over the ClockWork recovery image, make sure S=OFF otherwise the flash won't complete successfully.
You can turn S=ON back after the flash.
THIS IS NOT A FLASHABLE ZIP - I only zipped it to get it to upload as an attachment! You will need to do a Fastboot Flash to install (there may be other methods but Fastboot is what I used).
Below are instructions I am borrowing from the Amen-Ra recovery installation from the N1 - they will apply the same here!
via fastboot
Code:
Copy recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding volume down, then select fastboot)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery.img
via terminal app
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
I hope this proves to be useful to at least 1 person!
Thanks a lot!
MYT4G (Glacier)
sounds like a good way to restore...now all we need are some roms
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Great contribution
c_licious said:
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Click to expand...
Click to collapse
Actually I merely extracted them from the stock Rom here on xda and from the ota update file someone posted but nobody has figured out how to apply. Both have been tested on my phone.
I figured I would make it easier on everyone who simply wants to download the recovery as opposed to the entire rom or update.
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
kitsunisan said:
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
Click to expand...
Click to collapse
Check this thread out - I was just reading it, should help out!
http://forum.xda-developers.com/showthread.php?t=843428
Nevermind, wasn't paying attention when I posted, thought it was something else. Still, will come in very handy for me, I just got my replacement today, and replacing clockwork recovery was the last thing I needed to do.
JWhipple said:
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Click to expand...
Click to collapse
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
You got the first one after reverting back from being rooted?
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Not sure - but if you want to "appear" to be 100% stock w/ OTA update, probably best to set it to S=ON.
The thing is though, my understanding is that if even if you use the unroot, you still will have persistent root unless HTC or Google somehow patches the exploit that was used to get root in the first place. So, you'll have root but won't be able to change anything on the ROM unless you turn S=OFF again. I ran the unroot and S=ON and still have the ability to do everything (other than mess with the ROM) that your standard Rooted phone would be able to.
jjlean said:
You got the first one after reverting back from being rooted?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
JWhipple said:
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
Click to expand...
Click to collapse
I got the first OTA before doing s=off (needed the OTA to make it work at the time - did it first day).
I am trying to find out about the second OTA, about which there is practically no information available. I would I assume I have to have the first one installed to get the second (but what is it?).
Again - thanks for posting the original stock recoveries - have a feeling I may need one down the road (like when 2.3 finally comes out and I have a reason to go back to stock).
I've yet to see anyone say that they have actually received a 2nd OTA... Go figure?
Would I be able to use this recovery image to get my phone back up an running again?
I was messing around trying to apply the custom animations and somehow ended up getting my phone stuck in a constant reboot mode.
I have done some research and think that I am on the right track, but can someone verify this for me?
I have permroot with S-OFF, factory reset from the bootloader menu does not get me anywhere, but the phone is recognized through the "fastboot" prompt.
Would I just place the recovery image in the root of the sd card and run these commands?:
fastboot erase recovery
fastboot flash recovery.img
Thanks in advance for any help
From terminal im getting image not found? Do I have to mount or something?
Also... From pc ....Put .img in a place where fast boot can see it, where is thay
Sent from my HTC Glacier using XDA App
Ok guys, the absolute easiest way to do this... This is dependent upon you having S=OFF.
1) Install the android SDK....
2) In my case, fastboot is in C:\sdk\tools as I installed the SDK to C:\SDK. For fastboot to see the image file, I placed the image file (after extracted from the .ZIP) into the C:\sdk\tools folder.
3) Shut down the phone. Turn it back on while holding down the VOL-DOWN button.
4) On the bottom of the screen you'll see:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
5) FASTBOOT should already be highlighted. Press the POWER button.
6) If your USB isn't already plugged in, do it now.
7) Give the PC max of 30 seconds to recognize the bootloader mode.
8) From a DOS prompt, navagate into the C:\SDK\TOOLS folder.
9) Type "FASTBOOT DEVICES" (less the quotes) and press ENTER. If your phone is recognized it should show the serial info of your phone.
10) Type "FASTBOOT FLASH RECOVERY RECOVERY.IMG" (again, less the quotes) and press ENTER .
11) You should see the send and receive. If you do, SUCCESS.
I was able to do all of the steps listed, but I keep getting stuck at a boot loop.
Fastboot recognized my phone, flash recovery from fastboot says that it is successful, but still no luck.
Sent from my HTC HD2 using XDA App
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.
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
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!
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
UPDATE: used fastboot to flash stock firmware. Now i have bootloader and twrp recovery but no rom to flash or nandroid to restore. I cant move any nandroid TO the device for some reaodn. Ive tried for about a half hour now. And the one rom that I tried to adb sideload failed to install
bigbuckin said:
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
Click to expand...
Click to collapse
Did you run a Sense RUU? You'll need to to resize your partitions.
When the previous owner converted to GPE, he ran a GPE RUU that makes the system partition too small for Sense.
You need to run an AT&T RUU to convert back properly.
Here is a link for the official HTC/AT&T RUU download.
The full instructions are there as well for manually updating.
Read them.
The download is at the bottom of the page.
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
bigbuckin said:
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Click to expand...
Click to collapse
bigbuckin said:
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
Click to expand...
Click to collapse
This thread has everything you need.
You'll want option 1. When you boot into bootloader, you'll have to select hboot to start the flash. I don't know why he left that out of his instructions.
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
bigbuckin said:
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
Click to expand...
Click to collapse
Petty much.
Boot into bootloader, select hboot, press vol up to flash, press power button to reboot after the flash. Done.
You'll get prompts for the volume up and press power button.
No need to do anything but rename it, put it on extSD, and go to hboot.
You're amazing. I've spent countless hours troubleshooting this and never came across this thread. I'll update when finished to confirm it worked for me
Oh, I forgot to add, when you done with the flash make sure you delete the renamed file from your extSD. If you don't, every time you boot to hboot it'll try to update again.
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
bigbuckin said:
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
Click to expand...
Click to collapse
http://forum.xda-developers.com/att...u-m8att-4-4-4-s-off-onlynewest-t3015680/page2
Scroll to post #17, and read the next few.
You need to run it twice.