• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root May have bricked for real

ACD168

Android Expert
Apr 30, 2010
1,885
163
I flashed Shadow ROM, and when it should of been booting up, it beeped 3 times and then flashing green notification light. I couldn't do anything but pull battery. tried to turn it on same 3 beeps and light. the only thing that works is when I pull batt, then plug the phone into a charger and it get a red light and I can get into recovery only this way but once I pull the power when in recovery bang 3 beeps and lights. it's crazy. I was s-off and it turned me to s-on. if anyone can help id really appreciated it.
 
I flashed Shadow ROM, and when it should of been booting up, it beeped 3 times and then flashing green notification light. I couldn't do anything but pull battery. tried to turn it on same 3 beeps and light. the only thing that works is when I pull batt, then plug the phone into a charger and it get a red light and I can get into recovery only this way but once I pull the power when in recovery bang 3 beeps and lights. it's crazy. I was s-off and it turned me to s-on. if anyone can help id really appreciated it.

Try putting the files you need on your sdcard with your PC and then see if you can get s-off again and flash a new another rom while plugged in and see what happens.
 
Upvote 0
If you can get to recovery you can still flash a custom recovery from unrevoke of the wiki site to get s off. I don't have a link to the site on my phone but I can update when I get home.this is what I think hapoened. I think the 3 beeps is telling you the Rom on your phone is not signed and it won't boot to protect the phone. I could be wrong but go to there page and get the update.zip and flash it.
 
Upvote 0
thats the other weird thing once into recovery it wont read any sd card no matter what format.

I just had the same problem when booting into recovery from Rom Manager which Koush just updated. Changelog says:

2.5.0.2
Fix crash bug if SD card is not mounted. Assosicate zip files with Rom Manager.

Never had a problem until the update though. Rebooted and the phone remounted the card from an error state. Reflashed clockwork and it's working for now but this is the 2nd time in a week I reflashed it. I'm wondering if this could somehow cause a problem for people cuz I have to doubt you did anything wrong with your experience...bad file, maybe but kinda doubtful. Did you check the file size? Anyway, good to hear you have another one on the way.
 
Upvote 0
I just had the same problem when booting into recovery from Rom Manager which Koush just updated. Changelog says:

2.5.0.2
Fix crash bug if SD card is not mounted. Assosicate zip files with Rom Manager.

Never had a problem until the update though. Rebooted and the phone remounted the card from an error state. Reflashed clockwork and it's working for now but this is the 2nd time in a week I reflashed it. I'm wondering if this could somehow cause a problem for people cuz I have to doubt you did anything wrong with your experience...bad file, maybe but kinda doubtful. Did you check the file size? Anyway, good to hear you have another one on the way.


Thanks man I appreciate it, I checked the MD5 and it all was well, so im baffled. I actually tried pushing for the galaxy X but they had none of it. I'm weary to root again, and hope I don't get in troble for still havein the clockwork ercovery on it. I still dont understand how this ROM made s-off turn back to S-ON. I thought only the clockwork file could do that. kinda sucks. cos now i need to have a power outlet to reboot my phone along with a battery pull.... sweet.
 
Upvote 0
So your back to the stock recovery too or still CWM? Or can you even access either at this point? And yeah, that s-on thing is effed up!! And then went back to s-off? Craziness.

I know man I was so happy to see that it went back to the s-off after being all f-ed up.. then i wiped everything, and did a back-up of my nandroid thinkging all would be fine.. nope 3 beep.. and now I'm back to s-on all of a sudden too btw... and I can't get to any recovery... unless plugged in of coarse

Well if its s on recovery won't even show up. And I don't think they will go through the phone to see why it error. I think the just plug it into a machine and just flash it back to 2.2 stock.


I hope so thanks for the response.


The 3 beeps sounds like it is going into Qualcomm diagnostic mode. Can you get into the bootloader?


i could try what would this mean if I could?? I plugged it into my brother windows vista machine to try and run the 2.2 rUU cuz I'm on win7 and it doesn't work. I saw something about what u mentioned but i think it failed or i unplugged cos i didn't realize what o twas doing then i saw and didn't know how to get it back..
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones