I flashed back to stock 2.1 on my samsung vibrant.
the phone boots up fine at first, then all of a sudden i get a wierd screen and the phone reboots automatically. i dont know what the problem is. can anyone please help me with this problem.
the phone is continuously rebooting for the past half and hour. and i have no idea what to do now.
PLEASE HELP ME WITH THIS.
im posting a photo of the "wierd" screen below. the quality is crappy, but i cant help it.
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
erad1 said:
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
Click to expand...
Click to collapse
yes i did try flashing a 2.3 ROM,but it didnt work properly, so i tried flashing the stock 2.1 again using ODIN...it got installed, but later all these things started happening.
i even flashed the 512 PIT file that came along with the stock 2.1, but still no use.
can u please post the link to the kernel you are talking about and also how should i flash the kernel?
thanks for your reply.
hey the problem is solved. i installed eugene's 2.2 leaked build and my phone is back to normal now...!!!!
thanks for all your help. i really appreciate it...!!!
Glad to hear you got it...just be careful to know which bootloaders you are on, GB or FROYO... unless you have alot of problems with a ROM its not really necessary to ever flash back to stock...I flash rom to rom without any issue as long as you:
1. wipe cache partition,
2. then wipe dalvik cache and then
3. factory reset all from CWM...
4.then flash whatever .zip ROM you like.
Flashing back to stock FROYO/ECLAIR from GB with an odin rom you must be sure the stock rom either includes both PBL and SBL or no bootloaders at all and then your good.
Hi, new Android user here.
I was trying to root my Nexus S phone yesterday and I'm having problems. There is a lot of rooting guides out there and I used one from xda and also one from unlockr.com. Managed to root the phone ok (I think), but everytime I flash a custom ROM, the phone won't start at all, it just sits at the boot up screen and repeats itself.
So I'm thinking, I should just start over again. So I flash the stock ROM from xda back to 2.3.1. Everything seems ok, the phone starts up... but it's always stuck on airplane mode and the phone itself doesn't even show stuff like IMEI, mac address anymore.
So now I figure I've probably messed the phone up enough and need help lol. How do I go about reflashing the stock ROM and getting my Nexus back to out of the box condition (Stock ROM and no custom bootloader)?? Any guides or step by step instructions would be very helpful.
Thanks
Did you wipe before flashing roms?
Sent from my Nexus S c",)
Maybe flashing the KB2 modem would help that but the 9020a came stock with 2.3.3 and not 2.3.1 so that could be it...I'm not sure but that software wasn't meant at all for ours so it could be part of the problem. But if I was you I'd take a look at this thread wich has all the stock software for your phone. Make sure you wipe everything in clockework and then flash the stock rom. http://forum.xda-developers.com/showpost.php?p=13123996&postcount=39
dsixda uploaded the stock backup and the stock recovery, you can read more at that link, good luck hope it helps
You can download the full stock ROM from the link below:
http://goo.gl/8P8vl
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
jungbum said:
You can download the full stock ROM from the link below:
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
Click to expand...
Click to collapse
that did the trick. thanks everyone, now time to try rooting and flashing ROM again!
hrm lol now trying to update it to 2.3.4, it downloaded the update, but on reboot i get the white triangle with ! in it :\
this phone is so messed now
edit: well now everything is ok again, wiped data, flashed with CM7 and now it says 2.3.4, go figure.
i been on jellybean rom but wanted to go back to gingerbread.i have used odin to go back to gingerbread then flashed custon gb rom but everytime i get a bootloop no matter which gb rom i flash. however i can easily flash back to jellybean why cant i go back to gb i always full wipe and after i odin im on the red bootloader that gb bootloader right can i please get some help thank you
Which Odin pack are you flashing?
maybe try heimdall one click uclb3 stock
Sent from my sweet & buttery Infuse
same thing happened to me. i Odined twice. that did the trick
tyronekndrck said:
i been on jellybean rom but wanted to go back to gingerbread.i have used odin to go back to gingerbread then flashed custon gb rom but everytime i get a bootloop no matter which gb rom i flash. however i can easily flash back to jellybean why cant i go back to gb i always full wipe and after i odin im on the red bootloader that gb bootloader right can i please get some help thank you
Click to expand...
Click to collapse
I'd recommend going back to stock and starting from there its better. At least thats what I do
So I was rooted on synergy r72 then went to jellybean...tried flashing back to clean rom and s*it hit the fan...I ended up Odin back to stock and started from square 1...unlocked and rooted I made a nandroid and tried to flash clean rom once again...it installed but when it got to the boot animation it looked strange and the screen where it said Samsung had a bunch of different colors and then it rebooted...battery pulls didn't work...restored my root66 from Odin but can't flash any new roms! Any ideas what is going on!?!? I would greatly appreciate the help!
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Brian Gove said:
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Click to expand...
Click to collapse
Yes... I haven't done anything differently from when it worked prior to this
Sent from my SCH-I535 using xda app-developers app
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Did you try downloading the file again? It could have corrupted. Just a thought. Make sure your bootloader is still unlocked(You can tell because it will boot by the first 'Samsung' screen in a split second then go onto the 'Samsung Galaxy SIII' screen.). And before you flash cleanrom wipe everything, data, cache, davlik. Run the fix permissions too just to be sure.
pschatz12 said:
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Click to expand...
Click to collapse
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
buhohitr said:
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
Click to expand...
Click to collapse
This. If you ODIN back to stock, you need to unlock again.
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
pschatz12 said:
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
Click to expand...
Click to collapse
Please list the steps you took step by step so we can see what's going on here. Don't embellish, don't exaggerate, tell us what you did and what you didn't do. Based on your steps you shouldn't be bootlooping. I would follow droidstyle's guide step by step in each category that is relevant (going back to stock, unlocking, flashing ROMs, etc.). Follow each step closely in whatever ROM you're flashing as well. Don't take shortcuts.
You sure you're unlocked? Maybe try unlocking again. It doesn't seem to bother anything if unlock an unlocked phone. If that makes sense...
+1 to listing your exact steps to help troubleshoot.
mustbepbs said:
This. If you ODIN back to stock, you need to unlock again.
Click to expand...
Click to collapse
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Brian Gove said:
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Click to expand...
Click to collapse
I swore that it did. Are you sure?
http://forum.xda-developers.com/showthread.php?t=1842830 - Yes it does. It rewrites the aboot.img to the secure one.
Positive, I tested it out and that's why droidstyles guide has changed.
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Boot loop sounds like a kernel issue. Are you sure you're not using a TW kernel on AOSP, etc?
Also have you tried redownloading the files that are giving you problems? Try redownloading the kernel to see if that makes a difference. If you're successful in flashing ROMs then I think a fresh download might fix your issue.
pschatz12 said:
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Thats a wired problem I would try going back to the stock rooted image again
Wontfinishlast said:
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Click to expand...
Click to collapse
Ziggys kernel was flashed successfully and synergy r72 running successfully... Do you guys think I should try dirty flashing clean rom? Idk what else to try... From synergy I can do a full wipe and try install clean rom but I doubt it will work
Sent from my SCH-I535 using xda app-developers app
cleanrom doesn't come with their own kernel baked into it already??? Why would they make you flash the ROM then the kernel..... And if you're getting the bootloop after installing the kernel then it's as mustbepbs said, re-download the kernel file.
I have a ****ed up bootloader (tried to flash CM9 and everything went to hell). I CAN NOT ODIN as my USB port is ****ED. I can get to the recovery screen but can't see ****. Can someone PLEASE give me a stock GB (2.3.6) ZIP rom that I can flash via CWM.