I am having a brutal time with recovering my rooted, soft bricked Droid Charge. More than a while ago while trying to root it, I bricked it, but followed the step by step tutorial on this site and fixed it with ease. But recently, it magically soft bricked. I tried EVERYTHING to recover it, including all the step by step tutorials on here to recover a Droid Charge. I have it to the point where it boots (which takes forever). It'll boot to the main screen then basically freeze and shut down. I re-flashed the rom, pit, recovery, etc, etc ... and that's about as far as I can get.
Is my phone pretty much shot? Does the usb port matter? All the files were successful in Odin, but I was using Windows on a duel booted Macbook. But either way, it's stressing me out, especially now that I'm stuck with a lag-fest BlackBerry that makes me want to throw myself out the window. Can anyone help?
_Silky said:
I am having a brutal time with recovering my rooted, soft bricked Droid Charge. More than a while ago while trying to root it, I bricked it, but followed the step by step tutorial on this site and fixed it with ease. But recently, it magically soft bricked. I tried EVERYTHING to recover it, including all the step by step tutorials on here to recover a Droid Charge. I have it to the point where it boots (which takes forever). It'll boot to the main screen then basically freeze and shut down. I re-flashed the rom, pit, recovery, etc, etc ... and that's about as far as I can get.
Is my phone pretty much shot? Does the usb port matter? All the files were successful in Odin, but I was using Windows on a duel booted Macbook. But either way, it's stressing me out, especially now that I'm stuck with a lag-fest BlackBerry that makes me want to throw myself out the window. Can anyone help?
Click to expand...
Click to collapse
what is phone model dude?
Related
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Well early today I was running ics 4.0.4 on my g2x and I got tired of it, so I decided to restore my backup of my original rom/settings.I forgot I had switched my micro SD card to the one I had in my droid incredible 2, and I ended up restoring my dic2 back up. From there the phone would just stay at the LG screen, so I started to look around. I tried using nvflash, but it stayed the same, then I tried the flash.bat, when I turned the phone on it still stays on the LG screen but with the blue loading bar underneath, and when I try to put it into recovery mode it says S/W Updates. I don't know what to do, I'm a newbie to this stuff although I was able to root it myself. I don't care if I have to unroot my phone or go back to my original rom, I've been looking for something like this for hours and can't find anything. Please help, Thanks!!
When you used nvflash, exactly what steps did you take?
follow this guide http://forum.xda-developers.com/showthread.php?t=1248644
when you plug your phone in to use NV flash, find the device in the device manager, uninstall the driver and check the delete box, unplug the phone then start the guide.
you cannot hard brick a tegra device with flashing so you should be able to recover.
Hi, I'm a super newbie with a nice gs3 who have been toying around with rooting and roms for a bit.
recently, I noticed that my clockworkmod folder was taking up great amount of space in my phone memory (approx. 4 gigs)
so I decided to delete the folder and re-root my phone.
After re-rooting, all my phone now does is stay on for a bit, freeze, go to a black screen, and then turn back on.
It has repeated this cycle for infinite times now.
I've tried the to reboot into recovery mode by pressing vol.up+power+home, but all it does is stay on the samsung reboot logo.
I've also tried to soft un-brick the phone with odin, but the process always fails and it doesn't even seem to be able to start the process.
It seems to be able to recognize the device, but won't do anything else further and keeps telling me it has failed.
My decision to delete the clockworkmod folder was a super stupid decision.
Have I hard bricked my phone? Is it soft brick? Or have I just completely sabotaged my phone to a whole new degree?
I have no idea what has happened and desperate for a fix while crying in the corner of my room.
Please help!!!
Sounds like you just deleted a nandroid by deleting the clockwordmod folder. That shouldn't effect the phone functioning at all. What do you mean by "re-rooting?" Deleting that folder wouldn't effect root not sure why you tried to re-root. It sounds like something went wrong during the "re-root" process. What method did you use when trying to do that?
You soft brick your phone. I believe You didn't have to root an already rooted phone. In Odin you must click PDA(must be checked also) and choose your stock ROM. Your phone must be in download mode for you to even start the process. I will also like more details like root method and what version android your running.
ok. i successfully rooted this kindle with "root with restore by Bin4ry." i am pretty sure i was on version 7.2.1. i made an attempt at installing a second bootloader with TWRP using seokhun's noob-proof tutorial, step by step. bam, brick. maximum bootloop. i then went to use KFHD System.img restore tool, to no avail. KFFA, no-go. i made a factory cable to get it into fastboot, and it works- the only life it shows is fastboot screen or bootloop with the kf logo. only in fastboot with a regular usb does adb recognize a connection. now, my main goal is to just recover from this brick and carry on. i have scoured the forum and got the same thing every time. is it a permanent brick?
i'm not a complete noob, i have plenty of experience rooting and flashing several models of htc androids. this is just super confusing, cuz i can usually fight thru stuff like this. any guidance is appreciated!
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.