So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Burkejt1 said:
So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Click to expand...
Click to collapse
The fix is listed in boreds rezrom thread in one of his first couple posts. It even says mainver fix...
Sorry didn't read all the way. Lol my bad. Been awake 30+ hours now.
So two things you can do. Put the micro SD card into another phone or computer and temp remove the ph98img.zip file.
Two is pull the micro SD card out about halfway and put the battery in so it touched the contacts and turns on but don't put pressure on the micro SD card. Boot into hboot then lift the battery while pushing it against the contacts and push the microsd in and then volume down to recovery and power to chose and your in the recovery.
Sent from my ADR6425LVW using XDA
Got it, thanks a ton!
I like the SD card halfway in trick because I don't have a micro sd to computer adapter that did the trick for me
Mirror for that mainver file...
Burkejt1 said:
So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Click to expand...
Click to collapse
Hey bud same issue here do you happen to have a link to that file...the op's link in that thread is 404 ...thx in advance
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Hey all I'm trying to flash rom REZOUND - Stock Root Deodexed 3.11.605.1.zip with PH98IMG from http://www.theandroidsoul.com/htc-rezound-ics-leak-3-11-605-1/. I was able to change the mainver in the ph98 file and that updates just fine but when I try to flash the rom itself it flashes okay but then it reboots to the white screen that says htc and doesn't go past that. Not sure what I missing, any help would be great! Thanks in advance.
I would stick to roms that have support threads for them so that when you have questions, you can ask the relevant people using that rom rather than asking a general question from people who most likely are not using what you are trying.
There are lots of ROMS for the Rezound located in http://forum.xda-developers.com/forumdisplay.php?f=1392 that have support threads.
chickltt7 said:
Hey all I'm trying to flash rom REZOUND - Stock Root Deodexed 3.11.605.1.zip with PH98IMG from http://www.theandroidsoul.com/htc-rezound-ics-leak-3-11-605-1/. I was able to change the mainver in the ph98 file and that updates just fine but when I try to flash the rom itself it flashes okay but then it reboots to the white screen that says htc and doesn't go past that. Not sure what I missing, any help would be great! Thanks in advance.[/QUOTE
Sounds like the kernel isn't flashing , are you sure its not failing installation and your just not seeing the error message ?
What main ver do you have ? there is a new tool on the developement forum that will automatically reset your mainver so you don't have to mess with changing the PH98IMG file . Otherwise not sure what your doing wrong.
Click to expand...
Click to collapse
Agreed. It sounds like you don't have the right boot image flashed for your ROM. try flashing it via fastboot and you should get a clean boot.
Hi, I'm new so I can't post in the dev threads. Here's my situation, I'd really appreciate anyone's help. Here's my current config:
S-OFF
HBOOT 2.11.2005 (just went back from 2.21)
Amon Ra 3.15
I'm having awful sdcard (both) issues and/or stability issues. What I've tried so far:
HBOOT 2.21 and Scott's Cleanrom 4.4. I can actually read the sdcards fine, but the rom reboots my phone and always gives me sim card errors. I've reflashed umteen times, wiped, wiped, erased davik again and again.
Restored original nandroid backup. Rom boots fine, can't see the sdcard(s)
So, I'm trying to go back to a GB rom (Cleanrom 1.7.5) but when I flash that rom, even with hboot 2.11, it can't see data on the sd cards. I've tried flashing "Old firmware patch.zip" but still can't read the cards.
On a related note, I can seem to talk to the phone fine via windows and adb (I have the htc drivers installed) but when I'm in what I think is "fastboot usb" any commands I run just say "waiting for device".
If I can get the phone back to GBE 1.7.5 I'd be super happy, as I have a titanium backup of it and I need this phone to be a phone again
Thank you.
You posted in the right place, the development forum is for developers to post their work, not our questions or plea for help. My guess is you need the old firmware patch you can find with many roms. All of Scotts roms put it on the SD card for you. Go look in the new CleanRom 4.4 thread and read the instructions on how to install. If that doesnt work find the appropriate RUU and flash that as per instructions.
EDIT:
http://forum.xda-developers.com/showthread.php?t=1508118 Go to this thread and in the very first post there is Instructions about halfway down for old firmware and a download for the patch. Download the patch, put it on your sd card and flash in Amon Ra. Should be good after that. In the future use the search function ar read through some other threads to see if someone else is having the same problem you are.
Actually I've been reading and searching for hours trying to find the right bit, so please don't assume that.
I reflashed RUU and then Scott's GB rom and it looks good again.
Thanks for the help.
tehsquishmeister said:
Actually I've been reading and searching for hours trying to find the right bit, so please don't assume that.
I reflashed RUU and then Scott's GB rom and it looks good again.
Thanks for the help.
Click to expand...
Click to collapse
I don't mean to assume but with your 2 posts and join date I will stay with my assumption that you haven't read enough. If you decide to try something you see in the forum make sure you read the entire thread from front to back to understand what you are about to do. I'm sure you were having a well documented issue which is why developers actually put it in the instructions to flash the patch immediately after you flash a Rom. But you should know that since you have been reading for hours. I don't mean to be a **** just telling it how it is.
sent from my Clean Rezound
No worries, don't care.
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
Hey guys, Im in urgent need of help here.
I'll give you an exact account of what i did.
saved apps via Ti. Back.; uploaded the new ICS radios and debloated, deodexed rom from my computer to my tbolt, renamed the radio from my computer; booted into 4ext, nandroid, wiped EVERYTHING, booted into bootloader; bootloader detected the new radio and I confirmed its update
Next thing that happened was that the HTC splash screen appeared as normal but disappeared, leaving a blank screen with dim backlight. Pulled battery and tried to reboot 10+ times to no avail. Same thing happens everytime. ADB doesn't recognize the phone but i CAN boot into bootloader. The problem is that everytime I boot into bootloader, the radio begins to update, leaving with the only option to reboot. Thus, I cant get into recovery.
I've spent the past couple hours trying to do my homework on this but its not looking too hot. I need this bad boy, so help is much appreciated.
Doug
You need to take the radio off the sd card, so you can boot to recovery and actually flash the rom.
Sounds like you haven't flashed a rom yet, so it has nothing to boot into.
With the radio image (PG05IMG.zip) on the root it will not go to Recovery.
So you will need to find a card reader to rename the radio file, since you wiped prior to flashing the radios.
The preferred process would have been to flash the radios, boot to your current rom, rename the radio file from within the current rom.
Then boot to recovery and flash the new rom.
I somewhat outlined this in the OP of the rooted rom thread where you should have gotten the download from.
santod040 said:
You need to take the radio off the sd card, so you can boot to recovery and actually flash the rom.
Sounds like you haven't flashed a rom yet, so it has nothing to boot into.
With the radio image (PG05IMG.zip) on the root it will not go to Recovery.
So you will need to find a card reader to rename the radio file, since you wiped prior to flashing the radios.
The preferred process would have been to flash the radios, boot to your current rom, rename the radio file from within the current rom.
Then boot to recovery and flash the new rom.
I somewhat outlined this in the OP of the rooted rom thread where you should have gotten the download from.
Click to expand...
Click to collapse
Makes sense.I dont know why I read "wipe everything" before the rest of your thread and thought that meant to do so before reflashing radios.
Got a $10 reader and was able to change the radio file and boot into recovery. Flashed the rom as usual and it looks lke everythings working.
Thanks for the help man.