Database Info

Help: Bricked my NS4G

I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks

redsprocket said:
I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks
Click to expand...
Click to collapse
Boot into boot loader. Use fastboot to flash a recovery. Reinstall your rom of choice.

Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237

The root file on there is for ecalir/froyo only. Go into rm>download rom> superuser and download "superuser 2.3.6.3 efgh" and that should work.
Sent from my Nexus S 4G using xda premium

redsprocket said:
Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237
Click to expand...
Click to collapse
did you wipe data(factory reset) before flashing different roms? you have to. you dont need to wipe data only when updating the same rom.

Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.

redsprocket said:
Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.
Click to expand...
Click to collapse
no apologies needed, thats why we're here

[VZW] Recovery help for a noob.

Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.

knifedroid said:
Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.
Click to expand...
Click to collapse
you can only have one custom recovery installed, the other will sit as a file on your sd card and do nothing.

knifedroid said:
Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.
Click to expand...
Click to collapse
you can only have one recovery at a time, so if you ever switch to a rom that needs a different recovery than the one you have, you need to push the correct recovery, in short, yes you can only have one at a time

after unlocking phone wont boot

after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?

flameinthefire said:
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
Click to expand...
Click to collapse
Sounds like an bootloop, just odin back to stock and try again.

If you remove the battery and turn it back on, will it boot into recovery?

power+vol up+home button

Karl said:
power+vol up+home button
Click to expand...
Click to collapse
yes it turns back on but i have unlocked it and its on twp recovery which rom would work with it?

i tried flashing mr beans rom that didnt work beacuse i am on twp recovery and i tried flashing synergy rom that didnt work either so wat should i do. since i unlocked the phone can i still do odin? or will that brick my phone

guys please help!

flameinthefire said:
guys please help!
Click to expand...
Click to collapse
is there any rom that i can use for my unlocked s3

flameinthefire said:
guys please help!
Click to expand...
Click to collapse
Someone already told you what to do. Find a stock ROM, boot up Odin and flash.

the roms you tried work with TWRP... ive used TWRP since release

Karl said:
the roms you tried work with TWRP... ive used TWRP since release
Click to expand...
Click to collapse
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.

Locked or unlocked phone shouldn't matter as far as the Rom is concerned, it's been stated many times that the kexec kernels will boot fine on an unlocked phone. I would suggest starting fresh, stock ODIN, root, unlock, then flash CWM 6.0.1.0 with ez recovery and go from there.
Some people are not having any issues with the touch recoveries and others are, in my experience the CWM recovery has been the most stable and I could really care less about "touching" my recovery, buttons do the same thing. Just my 0.02
Sent from my Galaxy S III using Xda Premium

feel like an old man hearing these stories......we all know them...when we first started out flashing and **** went wrong....freak outs..panics....sweating..pacing..anger....regret.........BUT then you work through them and look back and say "**** that was easier than I thought"....and we come across them again without panic or hesitation........................dude relax........
1-grab a stock image...chose anyone you want in these forums..some are even prerooted.....i personally got competely back to stock
2-i use the one click root method..so root
3-flash cmw...any version you want as long as it is made for your model phone.....you can use e-z recovery app from market
4-MAKE A ****ING BACKUP!!! very important...
5-download e-z unlock from the play market..use...and done..now you are stock, rooted, unlock bootloader......if you plan on flashing cm10 or aokp or aosp....please make sure to read the thread "how to backup your imei" before flashing any of those roms.............boom goes the dynamite:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:.............................

King_tee said:
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Click to expand...
Click to collapse
Kexec roms don't but synergy should have. I use twrp and Synergy no problem. There isn't anything special that has to be setup for an unlocked bootloader.
Op you should be able to flash any non kexec rom. Did you do a wipe factory reset? If not you may want to give that a try

HELP!!!

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.

[Q] ROM Problem : Stuck on boot logo

This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?

confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth

CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102

I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.

Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?

k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout