Develop Bugs

[Q] Rom manager installs corrups phone

Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.

Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.

Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.

drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.

Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?

I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App

Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.

aiight sweet, I'll give that a go.
Cheers!

You're most welcome.

drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?

Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.

I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.

I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway

nvm I got in the recovery boot. Yeh the CWM-R are the same version.

drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.

drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.

HTC G2 White Screen with Andromadus ROM 1.1.2

Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!

Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).

Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium

Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse

Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....

Shot you a PM.

Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse

Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.

I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium

Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....

It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse

The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium

SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:

strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.

Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk

motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.

WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse

[Q] HTC ONE X Problem Restore Backup After Flashing JellyBean Custom ROM

Hi guys,
I'm pretty new here and sorry if I have missed a similar thread before. I have problem with my new HOX. I was flashing JellyBean. It works and after few days, I started to dislike it. Then I decided to go back using Ice Cream Sandwich. When I tried to restore back from my backup using CWM, the phone just stuck at the HTC logo screen when I reboot. Then I tried to do restore factory settings. Same thing happen again. After a while, I tried to do the "recovery.img" using my fastboot then erase cache. I thought it would help but turns out it making things worse. Now my phone can't even get to the recovery mode in CWM. Please help me if you have any suggestion on how to make my phone working again.
Thank you so much!

So you didn't even try re flash boot.img?
Sent from my HTC One X using xda app-developers app

No I did not. Do I have to do that first?
tomascus said:
So you didn't even try re flash boot.img?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Tried to re flash boot.img but still the phone stuck at the startup screen. Nothing changed

iamdavidchang said:
Hi guys,
I'm pretty new here and sorry if I have missed a similar thread before. I have problem with my new HOX. I was flashing JellyBean. It works and after few days, I started to dislike it. Then I decided to go back using Ice Cream Sandwich. When I tried to restore back from my backup using CWM, the phone just stuck at the HTC logo screen when I reboot. Then I tried to do restore factory settings. Same thing happen again. After a while, I tried to do the "recovery.img" using my fastboot then erase cache. I thought it would help but turns out it making things worse. Now my phone can't even get to the recovery mode in CWM. Please help me if you have any suggestion on how to make my phone working again.
Thank you so much!
Click to expand...
Click to collapse
extract boot.img from nandroid and flash it by fastboot.
then flash clockwork recovery
n then restore ur ics nandroid backup. I hope that works. coz I did same when my jb update failed n got stock in boot logo. now working.
and can u please say how did u do the JB update.

I fixed it with some guy help. I changed my hboot to 1.36 and install the Android Revolution HD One X 18.0. Now my phone back to life again.

[Q] Solving reboot loop 5 seconds after rom boot

Hi, I'm having some trouble getting a rom on my phone. It is the CDMA version that I unlocked and rooted and switched over to Page Plus. Everything worked great. I wanted to try the new ROMS, but every time I get them installed, the phone works for 5-15 seconds after booting (asks for wifi, google accounts, etc). It freezes for a moment, works for another second, and then reboots. This continues indefinitely.
I am absolutely sure that I have followed all the steps for the roms I am using. For example, here is what I do for the pacman rom:
Download the zip, extract the boot.img
Boot the phone into fastboot, run fastboot flash boot boot.img with the extracted img.
Load up the recovery, system reset, wipe cache, wipe dalvik, wipe system
Install the pacman v15.3
Boot again into fastboot and replash the boot.img just for good measure.
Reboot the phone, and then it hits the reboot loop.
I've tried to use another kernel (jmzone v4) as well as android open Kang and SuPrimo, but I get the same thing with each of them.
I also tried to restore my backup, but now it doesn't boot. I don't have the original boot.img, so can anyone tell me where to get that?
So, any help?
Thanks!

If you had investigated before posting, you would have seen that this is a common problem with an easy fix. Your radio version is too high, which means you took the update on stock rom.
Relock and ruu. There is a guide in the general section about bootlooping/rebooting upon boot.
We are all happy to help, but please investigate and do your homework first before just creating threads next time. It helps us and it helps you grow your knowledge of android.
Sent from my One V using xda app-developers app

Fix
I agree that you should have done your homework. I've had this problem too [link to my thread], and I'll save you some time by giving you the threads.
You're going to need to flash the RUU to get it back to stock.
You'll find links to your RUU on this thread (I used the "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe" for my Virgin Mobile CDMA phone).
Then follow this tutorial for exact steps on how to flash the RUU. It's the best that I've found.
Then try following the steps to flashing your ROMs. I've tried flashing AOKP and Paranoid with stock kernels and others (jmz's and SuperSick), but the only one that really has worked was recommended to me by another user. Try the CM10 ROM with the latest version of the SuperSick kernel (the latest I found was 12_21_12-16-04, which worked, but you'll have to look around for it). It's pretty awesome. Don't for get to click thanks to those posts that have helped you.

Lol you are a nicer person than I.
Sent from my One V using xda app-developers app

Haha I try to help the noobs, myself being kinda one :]
Sent from my One V using xda-dev app

[Q] Need some direction with Restoring

Hi All,
Yesterday I took my Tegra 3 (International) One X back to Stock ICS using RUU. Everything went smoothly after I relocked my bootloader and ran the RUU.
Then I proceeded to get all the OTA updates until I had JellyBean (3.14.707.24) with no further updates pending. Yay for Jellybean! The next thing I did was install CWM recovery and perform a nandroid backup (which didn't seem to restore later, although was created correctly).
At this point, I thought I would try using a CM10 rom to remove sense and I went ahead and installed it, flashing over the boot.img as one normally would, but it wouldn't boot. I later discovered that I needed a modded-boot.img (for new hboot 1.36), but not before I tried running the 3.14.707.24 RUU.
This RUU got stuck at sending.... and did not finish. I didn't leave it more than 20 minutes and tried twice. I also tried my ICS RUU to no avail.
Right now I have no Rom installed (from what I can tell), but I have full fastboot access and would like to know how I should proceed:
1) should I install the CM10 rom again with proper modded-boot.img (for hboot 1.36) and see if it boots? That would at least get me functional.
2) should I try another copy of the RUU for 3.14.707.24 JB? (i found one)
3) should I try a rom like Android Revolution HD which is OK to work with my new HBoot 1.36?
I don't want to do too much too fast since I know what I've done, and used to be really into this. The phone has been sitting a while since I upgraded my device and I'd like to get it working for travelling purposes. I'd be happy with a Stock Rom at this point...
Thanks for any willingness to help me
Adam

Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor

As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app

Thanks for answering
big noob said:
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
Click to expand...
Click to collapse
Thank you very much for your response!

This brings me to a next question...
Marc199 said:
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your answer!! Now I'm curious if I want to use some other ROM, but without any system, how do I get the .zip file for the rom onto my SD card for flashing.
Should I use CWM recovery and enable usb storage, or is there another way?
Thanks again,
Adam

Correct, use the recovery

Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app

Thanks!
Marc199 said:
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Click to expand...
Click to collapse
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:

THANKS!
Mr Hofs said:
Correct, use the recovery
Click to expand...
Click to collapse
Thanks so much. I'll see what happens and get back to the thread.

ALL GOOD!!
Thanks Everyone again. I'm Up and Running!
I think I was more freaked out by the RUU not working than just thinking that my phone is fine. Turned out CWM Recovery was still onboard so I just flashed a new rom using USB mounted storage. :good::good::good::cyclops:

adampollack said:
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
Click to expand...
Click to collapse
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor

Hmmm....
big noob said:
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Click to expand...
Click to collapse
Hey, Thanks for responding!
1. I figured. Thanks for validating. :good:
2. I did not use the boot.img from the nandroid backup. I've never sent a separate boot.img when restoring from Nandroid. Is that something I need to do going forward/have been lucky not having to do until now? Perhaps the ICS builds of roms had a more similar boot.img?
Adam

Yes sir, always flash the corresponding boot.img file :thumbup:

Appreciate the help
Mr Hofs said:
Yes sir, always flash the corresponding boot.img file :thumbup:
Click to expand...
Click to collapse
:highfive:
Thanks! I'm just confused because I've literally NEVER had to do this and have flashed countless roms when I was on ICS builds.
Great tip :highfive::good::highfive: