I am currently on fresh 3.3 (3.29.651.5) and want to try out RLS4 (3.30). I have read that upgrading to a 3.30 rom version means that it comes with a new hboot and recovery...is this true? How do i stay with my .76 hboot and amon RA recovery?
No it will not change your hboot. But make sure you install hatch kernel #11 because your older phone will benefit from this. I also heard the. 30 is for the newer phones. I went with a .29 rom and never looked back.
Sent from my PC36100 using Tapatalk
Related
I've been gone for a while and want to get everything up to date and run a new Rom based off the 3. 70 ota. I currently am rooted via toast method with hboot. 76 an outdated amon_ra recovery and baked snack 1. 8... should I flash new recovery first or the newer hboot? Any help is appreciated and thanks in advance
Edit* also any suggestions on which Rom and kernel combo I should use? I'm looking at fresh or myns rls 4
you can just go straight to just update the rom and radio, PRI etc...dont really see the point of updating your hboot and or your recovery. i still use the very first eng. boot and the recovery from toastch root method.
I was just wondering if anyone has installed a rom that was made from 3.70 and then tried to go back to a rom that was 3.30. i want to know if it can be done or has anyone had problems doing it. thank for all the info.
First Post!!!
I love this new Rom! It is by far the fastest and most aesthetically pleasing Rom I have ever used. Keep up the good work dev! Can't wait for your updates!
Seriously though, to answer your question, I have updated to 3.70 and then rolled back to 3.29(originally came on my 0003 Evo) with absolutely no problems. I even updated to 3.70 then unrooted back to 3.29 and got the update via OTA and then rerooted. It shouldn't be a problem as long as you use the RUU of the Rom that is compatible with your hardware.
I have not had problems. Doesn't mean others haven't. If you updated your radios then maybe. I haven't gone back to a 3.30 since the switch.
zone23 said:
I have not had problems. Doesn't mean others haven't.
Click to expand...
Click to collapse
so you have gone from 3.70 back to 3.30. i am asking because a friend of mine tried and all the phone does is boot loop. the only roms that work is 3.70
1975jamie said:
so you have gone from 3.70 back to 3.30. i am asking because a friend of mine tried and all the phone does is boot loop. the only roms that work is 3.70
Click to expand...
Click to collapse
Have your friend try flashing the wipe everything zip from calkulin. Also does he have hardware 004? 3.30 was only rolled out to 0004 Evo's. If not have them try a 3.29 Rom.
No I will have to let him know. Do you happen to have the thread info.
Sented from my Evo 4G using Myn's Roms. Chat on gtalk [email protected]
1975jamie said:
so you have gone from 3.70 back to 3.30. i am asking because a friend of mine tried and all the phone does is boot loop. the only roms that work is 3.70
Click to expand...
Click to collapse
The reason it bootloops is because the 3.30 roms use HTC kernel #17. When u flashed the 3.70 you probably also updated your PRI to 1.90_003, which requires HTC kernel #15 or a custom kernel (e.g., netarchy 4.3). So the kernel is what's causing bootloops for your friend.
Tell him to wipe everything then flash the 3.30 rom. Then before rebooting flash the custom kernel. It'll boot fine gauranteed.
Basically the PRI 1.90_003 cannot use any HTC kernel before #15 (which came with the 3.70 update). So any HTC kernel prior will cause bootloops.
Sent from my sweet HTC EVO running Myn's Warm TwoPointTwo RLS 4.95 (RLS 5 Beta)
What happen was he was using a myns rls 4 and then installed an rom with 3.70. When he tried to go back to myns everything went wrong.
Sented from my Evo 4G using Myn's Roms. Chat on gtalk [email protected]
Here's the thread you can find the tool on: http://forum.xda-developers.com/showthread.php?t=785271
Androidious said:
The reason it bootloops is because the 3.30 roms use HTC kernel #17. When u flashed the 3.70 you probably also updated your PRI to 1.90_003, which requires HTC kernel #15 or a custom kernel (e.g., netarchy 4.3). So the kernel is what's causing bootloops for your friend.
Tell him to wipe everything then flash the 3.30 rom. Then before rebooting flash the custom kernel. It'll boot fine gauranteed.
Sent from my sweet HTC EVO running Myn's Warm TwoPointTwo RLS 4.95 (RLS 5 Beta)
Click to expand...
Click to collapse
Androidious is right. Use calk's wipe everything then try flashing Myn's. If that doesn't work your friend may need a custom kernel, or download the HTC #15 Kernel and flash that.
My first guess on this stuff is he is using Clockworkmod recovery and its not clearing his Dalvik cache. As it has been stated many many times that it doesn't work. This may not be the case but is my first guess.
Thank you everyone for all the info.. Been a great help..
Funny...I'm currently having the same or a similar problem...I wanted to try the new 3.70 based ROMs, but now I can't go back to my NAND of myns 4...I've tried the wipe zip and I even tried to roll back my radio...I'm literaly stuck at the slash screen
I've been having this issue too, except I've tried installing new roms with htc kernel 15 and with netarchy kernels and all roms still boot loop for me with the exception of Ava and Evio. Maybe the link was bad? Does anybody have a link for htc # 15?
zone23 said:
My first guess on this stuff is he is using Clockworkmod recovery and its not clearing his Dalvik cache. As it has been stated many many times that it doesn't work. This may not be the case but is my first guess.
Click to expand...
Click to collapse
+1 on this one
Sent from my gingerbread Evo using XDA App
I had this same problem.... I had to go back to step one to rooting my phone again since it wouldn't let me restore my phone.
Sent from my PC36100 using Tapatalk
So this is the story.
For one reason or another, messing around with Titanium I lost com.htc.dialer.
I wanted to replace it so I flashed the PC36IMG from root and started the whole rooting guide again, keeping AR v1.8.
Then following the guide, I flashed another PC36IMG which is SprintLover's Rom.
Everything works fine now except that whenever I try to flash Myn's Rom again, or any other rom, it just freezes at the splash screen.
the only way I get back is by restoring the NAND backup I did of Sprint Lovers. Not even the NAND I did of Myn or any other Rom works.
I've been pulling my hair out for this one but I can't seem to figure it out.
Android Version - 2.2
Baseband - 2.15.00.11.19
Kernel Version - [email protected] #15
Build - 3.70.651.1. CL294884 release-keys
Software - 3.70.651.1
PRI-1.90_003
PRL - 60662
Thanks!
BTW if this turns out to be something I missed on the search and it was something really easy...don't flame me that much xD
I was getting the same problem, until I flash fresh and got it to work, i think the problem was our current PRI doesn't match MYN 3.3 software since that PRI version came out with the 3.7 software which is what fresh is based off of
Sent from my PC36100 using XDA App
zeau2004 said:
I was getting the same problem, until I flash fresh and got it to work, i think the problem was our current PRI doesn't match MYN 3.3 software since that PRI version came out with the 3.7 software which is what fresh is based off of
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That is correct. Also, I believe in regards to RLS4, that the htc #17 kernel that it comes with is NOT compatible with the newest radio (which you have) Best way around that is to flash a custom kernel, pretty much any one of nets, ziggys, or ms's sbc kernels. So I would try downgrading your PRI to 1.77, flash RLS4, then while still in recovery, flash the kernel. It should work then.
The other option is to wait for RLS5, which should be out relatively soon. That is based on the 3.70 software, and your current radios and PRI will be needed to run with RLS5 anyways. Good luck, and by the way, it's worth it. Myn's ROM is, in my opinion, by far the best sense ROM.
if you flash a custom kernel after flashing myn's ROM, then reboot. you will be fine. stock HTC#17(stock kernel on RLS4) does not play well with PRI 1.90.
-or-
just wait a few more days for final version of RLS5 to come out based on the latest OTA (3.70)....
Thanks everyone =D
I flashed CM6.1 for now after flashing the Eng Hbootand I'll just wait for RL5. It was such a hassle having a half broken phone on my first day back to University with no PC to hook up and change the files...not going to play around with it till the weekend xD
First of all, I apologize if this is in the wrong place or has been answered, but to the best of my searching and hours of tinkering and trying, I have found nothing.
I. Just want. CM6 B2 Blue Beast w/Snap v7. I have rooted my evo but it is newer with HBOOT 2.10 Radio 2.15 and 0004 hw version. I rooted it with Unrevoked and did Unrevoked forever, and from what I understand you can't get the ENG bootloader needed for CM6 if you have my hardware.
For the love of god. If anyone can help me I would love you forever.
I have been through a crazy bricking from flashing all kinds of PC36img's and I am mostly adb illiterate but finally got an RUU working and got back to stock and re-rooted.
Please help meeeee!
You try downloading rom manager from the market and use it to flash armon recovery? Then just flash the zips and you are ready to go.
Sent from my Htc Evo using Tapatalk pro
xxwckdxx said:
You try downloading rom manager from the market and use it to flash armon recovery? Then just flash the zips and you are ready to go.
Sent from my Htc Evo using Tapatalk pro
Click to expand...
Click to collapse
I'm trying to install the old CM6, not CM6.1+
I get the Status 7 error talking about bootloader .76
but yes, I have tried using Rom Manager
EDIT: CMB2 (not CM6, but still not CM6.1+)
First let me apologize if this has been answered before, but I could not find my specific question nor answer.
I am on baseband 2.15 and am trying to downgrade to 2.05. When I try to flash the radio in zip format, I get an error stating that my os is to new and that everything after 1.5 will not be able to flash this specific radio. This is not the same as downgrading from 2.15.x.x to a lower 2.15x.x. So please don't point me to this type of example.
Does anyone know, step by step, how to get this done?
Thank you in advance.
Edit: hboot 0.97
Radio 2.15.00.09.01
S-off
Rooted via unrevoked forever
Newer versions of the stock ROM may not work well or at all with older radios.
You may need to rollback to 2.2 to use the older 2.xx radios. 2.05.00.06.10 came out with the 2.2 froyo rollout. The newer gingersense ROMs probably can't be used with such an old radio.
Why do you need to roll back to 2.05 anyway?
MultiDev said:
Newer versions of the stock ROM may not work well or at all with older radios.
You may need to rollback to 2.2 to use the older 2.xx radios. 2.05.00.06.10 came out with the 2.2 froyo rollout. The newer gingersense ROMs probably can't be used with such an old radio.
Why do you need to roll back to 2.05 anyway?
Click to expand...
Click to collapse
Need to get my radio to a point where the nvm is writable.
Edit: update, got the radio to downgrade by using rom manager with clockwork recovery 2.5.0.7 and flashed radio update.zip
It was an amend error. An old version of Clockwork - as you did - or Amon Ra would be needed to flash it. Next time you flash radios (or anything that gives you that error) you'll either have to find an edify version or downgrade/switch recovery again.
Sent from my PC36100 using Tapatalk