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

Root Bricked, but why?

Slick

Slick

Well-Known Member
I was reading through the android forums when i thought (I dont have a nandroid backup ) So i booted in to CWM and tried to back it up. It said an error occurred so i did not think much of it and rebooted my phone. its in a boot loop and wont turn on. Any idea on how to fix it and/or why this happened?
 
Not sure why it happened, (perhaps you tried to save the backup to your phone instead of SD and didn't have enough space?)but you could probably download and install one of the several choices of ROMs or stock backups that are floating around here to fix it.
Make sure you have the correct version of CWM for your phone and software version, and make sure the ROM or backup is compatible as well.
I.e. you wouldn't want to try to flash a stock ICS backup onto a newer JBOOB.
 
I believe that one should work. You don't need to flash it with Odin though, just save it to your SD and install with cwm.

Before you do that though, which version of cwm are you using?
 
sanjuro77 said:
I believe that one should work. You don't need to flash it with Odin though, just save it to your SD and install with cwm.

Before you do that though, which version of cwm are you using?
Click to expand...
CWM v6.0.3.6

Also when i boot into CWM it says warning: no file_contexts
 
I used my dads old S3 and put my sd card in it then plugged then usb into the my computer and dragged the file on. I installed the zip from external sd card and the same thing still happens.
 
Did you try wipe cache and delvic cache . And I've always factory data reset before flashing rom. Might want to give it a shot.
 
M0NSTER said:
already tried. Sucks being without a phone :(
Click to expand...


I hear ya. I soft bricked mine once for three days before I got it working again. But as long as you've got recovery mode and download mode it can be fixed!

Did your phone come out of the box with ICS or JB?
This might be a silly question, but when you used Odin to flash CWM, did you remember to pull the battery after and then boot directly into recovery? I only ask because the phone would have rewritten the stock recovery if it just booted normally the first time.
Also, is it a proper bootloop or is it just stuck on the Samsung logo? Sometimes after flashing things it can take up to around 20 minutes to boot the first time.
 
sanjuro77 said:
I hear ya, man. I soft bricked mine once for three days before I got it working again. But as long as you've got recovery mode and download mode it can be fixed!

Did your phone come out of the box with ICS or JB?
This might be a silly question, but when you used Odin to flash CWM, did you remember to pull the battery after and then boot directly into recovery? I only ask because the phone would have rewritten the stock recovery if it just booted normally the first time.
Also, is it a proper bootloop or is it just stuck on the Samsung logo? Sometimes after flashing things it can take up to around 20 minutes to boot the first time.
Click to expand...


I cant recall what it came with only because there were problems with my phone and i had to keep sending the old back and getting the new one about 5 times. And its stuck on the samsung logo. Also i did pull the battery after and then boot directly into recovery. Ill try letting it sit for 30 min. Thank you so much for helping and replying quickly!:D
 
If it didn't work-
If your phone came with JB, then that older ROM *might* not work (i could be mistaken). It was for ICS Reverbs that had been updated to JB.
You might try downloading SuperBoy's latest Party Time JB and try flashing that, if I'm not mistaken that was built from stock JB. Also try downloading it directly to your SD card if you can, sometimes Windows file transfers can corrupt the ROM.
 
sanjuro77 said:
If it didn't work-
If your phone came with JB, then that older ROM *might* not work (i could be mistaken). It was for ICS Reverbs that had been updated to JB.
You might try downloading SuperBoy's latest Party Time JB and try flashing that, if I'm not mistaken that was built from stock JB. Also try downloading it directly to your SD card if you can, sometimes Windows file transfers can corrupt the ROM.
Click to expand...
Tried the party time rom still no luck.
 
Well damn. I've only got a couple other ideas - you can try reflashing CWM, I guess there's a possibility it didn't flash correctly...or try using TWRP recovery instead of CWM.
Then there's Tyler1998's Odin-flashable stock backup, I think the thread it's in is called "I'm making stock jellybean backup".( I'd link to it but I'm on the app) If you go that route, read the instructions carefully, it's a bit more involved than the average backup.
It is also actually a stock ICS backup but if it works you should still be able to upgrade to JB.
 
Make sure your not mixing the international with a regular. Just try a custom such as CyanogenMod or pacman and maybe mokee
 
superboy4444 said:
try flashing a different recovery...i have a pretty good idea its a recovery issue
Click to expand...

This recovery has proven to be universal for ICS 4.0.4 and JB 4.1.2:
http://androidforums.com/reverb-all-things-root/765187-recovery-cwmt-6-0-3-6-jb-md6-mi2.html

This one is a Touch UI and was used prior to 6.0.3.6:
http://androidforums.com/reverb-all-things-root/701566-recovery-touch-cwm-v6-0-3-0-a.html

This link has both the original 6.0.2.3 CWM (also referred to as Test8), as well as a link for the STOCK 4.0.4 <3e> recovery:
http://androidforums.com/reverb-all-things-root/730331-recovery-support-mirrors-dead-links.html

And of course here's the T.W.R.P. 2.6.1.0 link:
http://androidforums.com/reverb-all-things-root/782256-recovery-twrp-2-6-1-0-a.html

Peace,
Sox
 
the problem here is not recovery or anything it is corrupted data partition which is about the only thing that'll cause a bootloop other than a mismatch on system data like when flashing a new rom that isn't stock based... to fix your problem try this if you're familiar with adb

adb shell

$ su

# cd /data

# rm -rf system

# reboot

(note: you dont have to type the $ or the # these just specify the level of permissions you have ($=user #=root))
just do a factory reset if you aren't familiar with adb or it doesn't work, you'll lose your apps but have your phone back, if that doesn't work you'll most likely have to format your data partition which will destroy any files that aren't on your removable storage... I know it sucks but sometimes you gotta do what you gotta do....
hope you can get your phone back

EDIT: also just an FYI, your phone is NOT bricked if it has adb or odin mode or is playing a boot animaition or has recovery... just so you know
 
I already factory rest and i wiped cache partition. Also i tryed what soxtober05 suggested but i cant put the files in the recovery location because my phone is boot loop and wont turn on.

Also should i just install this from recovery?
This recovery has proven to be universal for ICS 4.0.4 and JB 4.1.2:
[RECOVERY] CWMT-6.0.3.6 for JB MD6/MI2
 
You must log in or register to reply here.
Back
Top Bottom