I cannot get the ROM to load... What am I doing wrong, I flash the radio from the GB section of the radio page... then go to load the ROM and it gets stuck on the HTC quietly brilliant page...
I flashed ROM first, then pulled battery to get to HBOOT, and flashed radio from GB thread.
turpintb said:
I flashed ROM first, then pulled battery to get to HBOOT, and flashed radio from GB thread.
Click to expand...
Click to collapse
That's how I did it also and worked fine.
Try restoring one of your system backup files, and start over.
Did you make sure to check the md5 of the radio and Rom.?
Flash the radio first, boot all the way into Android, remove the new radio from /sdcard, reboot to recovery wipe everything, flash new Rom. Reboot enjoy.
Sent from my ADR6400L using XDA Premium App
Related
I am going to download and install the new radio. But I noticed that in the original post the file is around 400mb. I was looking through the das bamf 1.5 thread and the new radio file to download there is only around 25mb. That is a huge difference. I am planning on using das bamf 1.5 as I currently run 1.4 and it is stable.
So what's the difference between the 2 radio downloads? Or are they the same? Please help me understand
Thanks.
Jcase posted the full update (rom and radio) whereas bamf 1.5 is only the modified rom and the separate 25mb file is the radio itself.
Sent from my ADR6400L using XDA App
Thank you kind sir I kinda of thought that. Thanks for the clarification.
So from what I understand the process is something like this
-Put file on root of SD card (named properly)
-Reboot into recovery and wipe data/cache davlik cache.
-turn phone off. Reboot into hboot, allow radio update procedure.
-ok now here is where I need some clarification. I think here I want to boot back to recovery but is it ok to boot into my current Rom (das bamf 1.4) to move/delete the radio update, then boot into recovery?
I was going to ask next if the 25mb radio file was rooted, but I think root is not relevant in the radio aspect. Right?
Thanks!
-boot into recovery and flash das bamf 1.5.
You asked if it is ok to boot back into your 1.4 ROM, but it will not be there because the step before you wiped your date which is the rom.
Sent from my ADR6400L using XDA App
Duh...oh yeah. Can't believe that skipped my mind.
So what is the best way to get to recovery after the radio install.
I can't seem to remember if the phone auto rebooted after the radio install or if I have the option to reboot into recovery.
DeathGrind said:
Duh...oh yeah. Can't believe that skipped my mind.
So what is the best way to get to recovery after the radio install.
I can't seem to remember if the phone auto rebooted after the radio install or if I have the option to reboot into recovery.
Click to expand...
Click to collapse
If it doesn't auto reboot then pull the battery. Hold the volume button down and power on the device which will boot into fastboot then boot into recovery. Remember to rename or delete the radio file after you have installed it if not you'll be prompted to install the radio everytime you're in fastboot and you wont be able to get into recovery.
Is it bad to flash the rom then do the radio after the rom is setup?
I was trying to avoid pulling the battery. As my case is a pain to take off, not to mention the battery door is a pain too. But it will need to be done if I wipe first.
I would like to know if I can flash the new radio over das bamf 1.4. That way I can boot into the OS and use a file explorer to delete/move the radio image, then if needed I could boot into fastboot with the update prompt. Butt if I am already booted into the OS then I could just boot directly to recovery bypassing the need to boot to fastboot, wipe and install das bamf 1.5 then.
Thanks.
Alright this Is what I did...I downloaded the newest MR2 Gingerbread Radio...then downloaded BAMF remix 1.7. Went into hboot flashed radio...rebooted then went to Rom Manager rebooted to recovery and flashed BAMF Rom...did wipe data before flashing Rom. I then recieved a couple of error messges followed by (bad). Then I did a system restore, I just rooted a couple of days ago and did a nand backup of everything stock. Now I don't have data, everytime I go into hboot it goes to the "do you want to update" part and to top It all off while freakin out trying to fix my screw up I lost Rom Manager so I don't have CWM. I came from stock radio and BAMF Remix 1.7 before all of this.
As you all can tell I'm new to the Thunderbolt. Did alot of reading these forums and watching Youtube before attempting this. I've "googled" for the past hour before coming to you guys...hope someone can help. Thanks in advance.
caspersfi said:
Alright this Is what I did...I downloaded the newest MR2 Gingerbread Radio...then downloaded BAMF remix 1.7. Went into hboot flashed radio...rebooted then went to Rom Manager rebooted to recovery and flashed BAMF Rom...did wipe data before flashing Rom. I then recieved a couple of error messges followed by (bad). Then I did a system restore, I just rooted a couple of days ago and did a nand backup of everything stock. Now I don't have data, everytime I go into hboot it goes to the "do you want to update" part and to top It all off while freakin out trying to fix my screw up I lost Rom Manager so I don't have CWM. I came from stock radio and BAMF Remix 1.7 before all of this.
As you all can tell I'm new to the Thunderbolt. Did alot of reading these forums and watching Youtube before attempting this. I've "googled" for the past hour before coming to you guys...hope someone can help. Thanks in advance.
Click to expand...
Click to collapse
The MR2 radio is for Ginger roms and new froyo leak. Bamf remix 1.7 is an older froyo leak. Try a bamf Ginger rom.
Also, don't post questions in development section. There's a q&a section for this stuff.
And research before flashing things. You should understand what's going on before modding your phone.
Sent from my ADR6400L using XDA Premium App
You can't use a gingerbread radio with a froyo ROM. You need to re-flash a froyo radio in bootloader. After that READ the whole post before you flash away and wreck your phone
Can we change the word noob to "dumb and lazy"?
Sent from my ADR6400L using XDA Premium App
I'm sorry guys I meant I tried to flash the BAMF 2.0-5 and this happened..I'm sorry for posting here I'll move along.....thanks
We will live. good luck!
Sent from my ADR6400L using XDA Premium App
If you want to use the MR2 Radio, download a gingerbread based rom. If you would like to use a gingerbread based rom, download the MR2 Radio or the Alpha leak (I would recommend the MR2 radio).
If you can't get into CWM through hboot, put your SD card in a card reader or another phone, and delete the PG05IMG.zip file. If you have the MR2 radio flashed right now, Remove the PG05IMG.zip file, and put a gingerbread based rom on your SD card. Now that the radio is off your SD card, you can access recovery through hboot. Now just flash the GB rom.
caspersfi said:
I'm sorry guys I meant I tried to flash the BAMF 2.0-5 and this happened..I'm sorry for posting here I'll move along.....thanks
Click to expand...
Click to collapse
Casper, delete the Radio (PG05IM file) from your SD card. Boot into recovery and Clockwork mod should pull up. Manually install Das Bamf 2.0 vers 5 file again. Sometimes you get errors using ROM Manager.
Richpopski123 said:
Can we change the word noob to "dumb and lazy"?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Depends on you.
Sent from my ADR6400L using XDA Premium App
Quick question. I couldn't find the answer searching. I am upgrading from bamf 1.6.3 to 1.8.6 and will also be upgrading to the mr2 radio. Should I flash the Rom and then the radio? Or vice versa? Thanks.
Flash the ROM first. You won't have service. Then flash the radio from bootloader.
Really, though, it doesn't matter. The thing to avoid is getting into a bootloop where the ROM won't boot completely, but the radio is still named pg05img.zip on the root of your sdcard, so you can't get into recovery and fix the ROM.
As far as I'm aware, the only side effect of having a mismatched radio/ROM combo is that you'll have no service. Can someone verify this?
Ok Thanks guys. I have everything downloaded currently and on the root of my sd card. So going to flash the rom, then rename radio file, and flash the radio.
Ok, I flashed rom then radio and everything looked good. I did a restart after restoring everything with titanium backup and now its stuck on the Thunderbolt screen. What should I do? It's been like this for 15 minutes.
coder_t2 said:
Ok, I flashed rom then radio and everything looked good. I did a restart after restoring everything with titanium backup and now its stuck on the Thunderbolt screen. What should I do? It's been like this for 15 minutes.
Click to expand...
Click to collapse
If everything went well before TB, reflash, and don't restore any system apps. Some suggest not using TB to restore data either. Makeva nandroid before restoring anything.
Sent from my ADR6400L using XDA Premium App
Did you restore system data too? sometimes that can bugger things up. I usually only restore system settings that are in green, if any.
You can always just wipe and reflash the rom.
Ok. I just pulled out the battery and rebooted and all was fine. I did restore system settings that were in green. So I guess that may have been it.
Sent from my ADR6400L using XDA App
I would like to add that's the H BOOT not CWM. I know its common sense for some but Ive seen this cause issues in some of the other threads.
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
Hi guys, I've been ripping my hair out trying to figure this out. I've been at it literally all day. I am trying to install the ZR3D ROM on my phone, and I'm using 4ext, and it gets as far as the wallpaper screen, and then bam. Reboots itself. I've wiped it clean using "format all partitions except SD card", loaded the ROM, went to the boot loader, and flashed boot.img, but it still keeps getting stuck in an loop. Any help would be greatly appreciated.
Thanks.
I take it since your flashing boot img from fastboot your s-on correct? Are you flashing the stock kernel that came with the Rom or a custom? Try flashing a different kernel with smart flash enabled in 4ext. If that don't work it could be the Rom. If that's the case try flashing a different one. If I may make a Rom suggestion try the common sense v1.7. Let me know how it goes.
dasaybz said:
Hi guys, I've been ripping my hair out trying to figure this out. I've been at it literally all day. I am trying to install the ZR3D ROM on my phone, and I'm using 4ext, and it gets as far as the wallpaper screen, and then bam. Reboots itself. I've wiped it clean using "format all partitions except SD card", loaded the ROM, went to the boot loader, and flashed boot.img, but it still keeps getting stuck in an loop. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Boot loops are not boot.img related issues.
Firstly, ensure that you have the right firmware / hboot version for whatever combination of rom & kernel that you're using.
Verify the MD5sum for the zip before flashing.
If you experience force closes, then wipe & reflash.
So a kernel cannot cause a boot loop? Hmmmm
Thanks I reloaded a different rom and it worked fine.
Sent from my PG86100 using xda app-developers app
dasaybz said:
Thanks I reloaded a different rom and it worked fine.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
No problem. It's courtesy to hit the thank you button when someone has helped you by the way.