So im on das bamf 2.0 with the mr2 radio flashed, i could load the rom and use my phone.But then i decided to unroot the phone, so i flashed the stock rom which worked before and took me back to being on stock and unrooted.But, now when i flashed it said Main Version is lower, in red letters. I now have no root with s-on as well. My phone wont boot because apparently one of the boot images i flashed didnt want to get unflashed. I cant do anything in the bootloader that wont end up with it rebooting the bootloader. I do not have usb debugging on because of the fact that i it FLASHED the pgio5mg or whatever it is that you call it, flashed = turning off usb debugging. Should i try to get a new one from big red? what if they get on to me and not give me a new phone thanks to it saying security warning?
Is there any way for me to be able to use my phone again, whether its getting rooting again or downloading an official gingerbread rom, if thats even out yet?
PLEASE HELP IM ONLY 2 MONTHS IN MY CONTRACT!
Also, at the top of bootloader it says SECURITY WARNING.
u have the wrong radio for the stock phone. u need the MR1 radio. since u still have the PG05IMG on your card it is stuck in boot loop. u need access to a card reader so u can remove that file. that will take care of the boot loop. then just install the MR1 radio.
also if u go to verizon as is, they will not honor your warranty.
lostnuke said:
u have the wrong radio for the stock phone. u need the MR1 radio. since u still have the PG05IMG on your card it is stuck in boot loop. u need access to a card reader so u can remove that file. that will take care of the boot loop. then just install the MR1 radio.
also if u go to verizon as is, they will not honor your warranty.
Click to expand...
Click to collapse
You just saved me from a life time of nightmares! But that didnt work, pio5mg or not im stuck in a fruit loop!
The first step after flashing pg05img.zip is to remove it from your sdcard.
Sent from my CM7 ThunderBolt using XDA Premium App
That didnt worrrrrrrk, i flashed the default froyo rom which is , like 23 MB, and it loaded it, but nothing happened it just returned me to bootloader menu!
As long as there is no file named pg05img.zip on the root of your sdcard, you can get into recovery from hboot. Are you able to get into recovery?
From what I understand, if you have the wrong radio for your ROM, the only side effect is that you'll have no signal from verizon. It sounds to me like you just need to reflash the ROM to get the phone to boot properly.
XxJakems28xX said:
That didnt worrrrrrrk, i flashed the default froyo rom which is , like 23 MB, and it loaded it, but nothing happened it just returned me to bootloader menu!
Click to expand...
Click to collapse
The default FroYo ROM and NO ROM for that matter is 23MB! Should be 300ishMB for Sense based ROMs.
Mustang302LX said:
The default FroYo ROM and NO ROM for that matter is 23MB! Should be 300ishMB for Sense based ROMs.
Click to expand...
Click to collapse
^^ what I was about to say.
The radios are close to 23MB but not the roms.
BTW, @OP, doesn't sound like you followed the directions when going back to stock as the security warning was one of the disclaimers.
http://forum.xda-developers.com/showthread.php?t=1009423
sorry i meant to say the defualt froyo radio is around 23 mb, i will try to flash this huge rom again, but now i have to wait like three hours cuz every time i try to flash the rom it says BATTERY VOLTAGE IS TOO LOW, and i cannot go to recovery it just takes me back to the hboot crap. I never read that tutortial guess i shouldve, i couldve sworn all you had to do was flash the defualt rom, DANG IT, i think that since i was on gingerbread this piece of shi doesnt want to flash the froyo rom, the fact that im now unrooted it doesnt want me to downgrade, god im never rooting again!
I rooted my phone by using the 3 click method by the unrevoked teem or whatever they are, i downgraded using the downgradepgoi5mg zip file found inside the folder, i dont know if that hepls but i hope it does.
Related
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Well you shouldn't panic. Which radio did you flash? I would flash the MR2 one from this link http://forum.xda-developers.com/showthread.php?t=1154010 . If that doesn't work, I would download the rom directly from Synergy here http://androidfilehost.com/XxXViRuSXxX/roms/synergy/thunderbolt/
From recovery, wipe everything manually (Wipe data/cache/dalvik) than flash the file from where it is on your SD card. If you need specific instructions feel free to ask.
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Sure hope he's just confused...
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Lol I saw that, I decided not to say anything, I guess you have the sharper tongue than me
Ya pretty scary. I'm hoping he meant he rooted his phone and when he said unrooted, he meant "stock" froyo build on his phone.
Sounds like he is able to boot up, just not get any signal.
I'm guessing he is not too skilled in the ways of Android yet.
Lol just found something interesting. Synergy isn't even on rom manager? I was checking to see if the version ofcsynergy he was using was a previous froyo build, and I can't even find it on rom manager
He probably meant that he used Rom Manager to load the rom rather than using recovery.
haha weird
OK, so I was tired when I wrote my initial post, and I probably didn't make a whole lot of sense. Let me be a bit clearer.
For reference, no, I'm "not too skilled in the ways of Android yet". I've been living with Froyo, anxiously awaiting Gingerbread, and then got fed up and read about all the benefits that come with rooting. Now that an easier method has presented itself - the Revolutionary method, as opposed to opening a command prompt and doing the adb stuff, which I can do - I rooted a friend's phone - but decided to not take the plunge myself - I decided to go ahead and give GB a shot.
So let me break down what happened:
- My phone was unrooted previously, running the same software it came with. I'd done a few OTA updates that Verizon provided but had never gone into my phone. That's why I called it "stock", sorry if that terminology confused people. I just meant it was the OS that came on my phone - Android 2.2 w/ HTC Sense and all that jazz.
- I ran the Revolutionary method posted in the "Thunderbolt Android Development" forum. Worked fine. Ran Recovery and installed Superuser permissions as the documentation said. Worked great. Have a phone where if HBOOT launches, it says -Revolutionary- at the top, and it's got -S OFF. My phone technically is rooted.
- The Synergy mod was also posted in the "TB Android Development" forum. I downloaded that and installed it using ROM Manager (Install ROM from SD). Worked fine ... but then had no signal. Every other aspect of the phone seemed to be working. My radio just wasn't working.
- Downloaded an updated radio from the TB Android Dev. forum, ran that, it said it was updating the radio. Rebooted the phone after the update ... still no signal.
I "solved" this problem by flashing the leaked HTC/TB Gingerbread build, the latest one that was like 400 MB, and when I booted my phone up again I had Gingerbread on my phone with HTC Sense 2.1, and I had signal. So I'm living right now with a fully working phone, but I wanted to dip my foot into custom ROMs. So now I have a backup method just in case the radio thing doesn't work again, but what can I do to install a custom ROM and ensure that I get signal?
Thanks for the response, xebryus - and to everyone else, sorry I was a little confusing. Everybody starts from somewhere, right?
-BT7
Download the GB ROM you want, boot into clockwork (please don't install VIA ROM Manager). In clockwork using you Volume keys to move and the Home button to select....
Select Wipe Data/Factory Reset
Select Wipe Cache
Select Advanced
Select Wipe Dalvik
Select Go Back
Select Mounts and Storage
Select Format /system
Select Go Back Until you are at the first screen
Select Install from SD Card
Select Choose ZIP
Go to the folder where you downloaded the ROM
Select ROM
Select Yes.
When it is done Reboot.
Enjoy!
Sent from my SHIFTAO5P using XDA App
Hey, at least you didn't brick your phone, so kudos for you for getting that far.
As others have stated there are basically two kinds of radio versions out there. One that work with Froyo builds and ones that work with GB builds.
So depending on the rom you are loading, you just have to make sure you have the right radio to match the rom(the rom thread should tell you what radio it requires). From what you were saying, it sounded like you just had the wrong radio.
Anyways, couple of things you want to make sure you do. Any check to make sure the checksum is correct on the radio (so that it's not corrupt) otherwise you could have some major issues. Also, once you flash the radio and you get your phone back up, make sure to either rename or delete the PG05img file from your SD root, otherwise, again a major hassle.
Check out the noob thread at the top of this forum also. It has great info there that will help you on your journey.
Good Luck.
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
RevosFTS said:
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
Click to expand...
Click to collapse
When the TB first came out, it seemed that people were having issues with using rom manager to flash roms (alot of force closes, things in general not working correctly). So many experienced people said to use recovery rather than rom manager to flash anything on the TB.
I guess that idea just kinda stuck after that.
Ok thanks. I will still use recovery anyhow I am more used to it. Plus I'm kinda old school I love adb haha
Sent from my ADR6400L using XDA App
I have downloaded Synergy Rom and have no problems except that I am not able to get the radio to flash. I am on verizon and chose the MR3.5 radio. I did a battery pull and then pressed the power and volume down button to enter HBoot but I do not have an option to Upgrade. What am I doing wrong any help is appreciated. I need help quick, thanks!!!
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Did you rename the .zip and have it on the root of your SD card?
Sent from my ADR6400L using XDA App
HarlyFan said:
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Click to expand...
Click to collapse
Nope..402w is still MR1. Sounds like you are already in bootloader so at this point if it isn't updating then more than likely the file is named incorrectly as stated above.
Radios HAVE to be named PG05IMG.zip (3rd character is a ZERO, not the letter "O"). It HAS to be in the root folder of your SD card. Now, turn the phone OFF.
Next, hold down the VOL-DOWN button. Keep it held down. Is it still held down ? If so, push and hold down the POWER button. When the screen turns on, you can release both. This menu will automatically look for 3 or 4 files with certain names. One of the names (files) it looks for is .... PG05IMG.zip. When/if it finds it, it will check it and ask you if you want to load it. Tell it to load it and then leave your phone alone. It will update it and reboot like normal (if successful).
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
killgorian said:
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
Click to expand...
Click to collapse
What exactly are you trying to do? Completely unroot the thing and put S-On? I'd like to be sure before I dole out instructions. And why such an old RUU? Why not the 1.70 RUU. And how was the Tbolt rooted and S-Off'd before?
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
killgorian said:
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
Click to expand...
Click to collapse
I hope wiser minds than mine chime in, but I don't think flashing an old RUU would be wise if Revolution was used. Revolution replaces the hboot and I don't think flashing a new RUU replaces it. I'm not sure what bad would come of it, actually.
It sounds to me like you just need to flash a new ROM. I don't know what radios you have, but you probably have newer ones since those are the radios of choice for newer ROMs. I'd try that first. If that doesn't do it, then I think what needs to happen next it to figure out what hboot you have. If it was done via the jcase method, then flashing an RUU should work fine. If not, well... I'm not an expert on that front, but there are threads on that subject. I wish I could dish out a real simple answer, but I'm not sure it so simple.
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Absolute_Zero said:
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Click to expand...
Click to collapse
Thanks for confirming. If you can hold volume-down while powering it up and get into ClockworkMod, flashing another ROM is just a matter of a few button pushes.
Exactly what I thought. I've loaded custom roms on the a855 and Eris before, but the above file won't load. I'm wondering if the bl is locked but it has clockwork, so I'm confused...
That's an entire RUU. That's why. Go get just a ROM and flash through clockwork.
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
killgorian said:
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
Click to expand...
Click to collapse
A full RUU contains a LOT more than just a ROM. It must also be flashed differently; through the bootloader and not recovery. An RUU contains a new bootloader and radios, as well as a ROM. If you'd flashed that RUU correctly through the bootloader, you probably would have lost S-Off and root, or ended up with a device that did even less desirable things... like bootloop.
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Edit: Nevermind, it seems to be good to go. Thanks again for the help.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
in the rom thread most devs put what radios are compatible and a link to the radio. Not sure how new plainjane is, but most of the newer radios work with all the custom roms.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
If you used Revolution or updated to the patched bootloader, it's designed to not allow flashing over. That's probably why it failed.
hi guys
I recently bought a 2nd hand Vibrant for a really good price.
As far as i see the Vibrant is already rooted with 2.2.1 Lidroid, and CWM installed.
The battery usage is amazing with this rom, but I still fancy to install some custom GB roms.
I have some questions:
1. I would like to check if I am already on GB bootloader, please guide me to check?
2. If I am not on GB bootloader, I know I must first install it.
I wonder if Vibrant has some stock GB firmwares like captivate does? The stock camera is a must for my case ><
Am i correct if I follow this method from here
http://forum.xda-developers.com/showthread.php?t=1156832
3.Or actually I can simply flash any custom GB roms directly from where I am (Lidorid 2)
THX
Okay you know if you're not gb bootloaders when you turn on ur phone there's weird rainbow lines
If not then you are
And if you are then yea you can flash any rom
Sent from my GT-I9000 using xda premium
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
j4371 said:
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
Click to expand...
Click to collapse
I've run CM7, and CM9 (ICS) on Froyo boot loaders. For me it just makes the kernel screen flash and show again, then goes on to ROM booting. I'm running a Froyo boot loader right now.
Is lidroid a t959 rom or a t959v?
You need to have a t959 to be in the vibrant 3g section, otherwise you'll probably want the galaxy s 4g section.
Sent from my Sensation using Tapatalk 2
there is a Lidroid version for T959 - I have a Odin flash with it. I use it instead of JFD.
Want to know if you have the GB boot loaders? Easy -
Hold the Volume up button and the power button at the same time. If it goes to download mode....you got the GB bootloaders.
T959 Vibrant does not have Samsung 2.3 support. Samsung forgot about us after Froyo. There Froyo OTA upgrade bricked so many phones that they wont chance it again.
For 2.3 Gingerbread you will have to download a I9000 port found in our Development section. That said the ICS packages are very nice for Vibs too.
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Yup, you'll need to go back to stock. There are plenty of write-ups on how to do it.
Also, NEVER restore a 2.2 backup after you install 2.3 or higher. The file systems and partitions are different. Odin back to stock, install lidroid again, and then try to restore your backup.
j4371 said:
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Click to expand...
Click to collapse
Get into download mode by while it's off, holding VOL-UP + Vol-DOWN and plugging in USB.
y vibrant revived!!
Thx everyone
After this, I am thinking to ask my colleagueto make one JIG for me.
I'd like to confirm it's same as SGS, i.e. 3 X 10kohm in series
its been a while since i last used Amaze. i had installed Energy ROM (gb) and exchanged Amaze for Galaxy S2. he tried factory resetting it and said he is stuck in boot screen. I will be getting that phone in few hours and i want to revert that back to Stock rom with ICS. How do i revert back ????
simple guidelines would be perfect.
Thank You.
hlimbu00 said:
its been a while since i last used Amaze. i had installed Energy ROM (gb) and exchanged Amaze for Galaxy S2. he tried factory resetting it and said he is stuck in boot screen. I will be getting that phone in few hours and i want to revert that back to Stock rom with ICS. How do i revert back ????
simple guidelines would be perfect.
Thank You.
Click to expand...
Click to collapse
Info is needed to work with, bootloader version, s-on or s-off, what did he do to get stuck on the boot screen?
he tried factory resetting the phone.
hlimbu00 said:
he tried factory resetting the phone.
Click to expand...
Click to collapse
Factory resetting doesn't cause a phone to bootloop or get softbricked, just saying.
Anyways, if you have a custom recovery installed, you could just simply wipe the device and reinstall whatever rom it was.
To go back to complete stock, look for the most recent GB stock ruu file in the dev forum, download it and place it on your sd card. Rename that file PH85IMG, reboot into bootloader, follow all on screen instructions to restore to stock. If the device is s-on, you will need to lock the bootloader before placing that PH85IMG on the sd card.
Or you can look for the most recent ICS leaked ruu zip file to go straight to ICS instead of GB, instructions to use this file remains the same as GB.
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...