Hey guys. I recently had my Atrix 2 soft brick on me. I can (and have) search this site and google on how to use RSD Lite or "MacGyver" it. But the only processes that I am seeing in performing myself all leads to flashing it first. Now to my knowledge, that simply means that I will be wiping the thing clear and instal a new ROM (either stock or custom). But does that mean that I can't access the data thats still there before its formatted? I think I still have contacts on there that I still need to get off. Any info you can give will be appreciated. Thanks guys, later.
Sowden said:
Hey guys. I recently had my Atrix 2 soft brick on me. I can (and have) search this site and google on how to use RSD Lite or "MacGyver" it. But the only processes that I am seeing in performing myself all leads to flashing it first. Now to my knowledge, that simply means that I will be wiping the thing clear and instal a new ROM (either stock or custom). But does that mean that I can't access the data thats still there before its formatted? I think I still have contacts on there that I still need to get off. Any info you can give will be appreciated. Thanks guys, later.
Click to expand...
Click to collapse
Contacts? you know google backs them up right?
But either way, only thing you can do is get crap off your sdcard. data on phone, is gone if not backed up to the cloud or sdcard.
MotoMudder77 said:
Contacts? you know google backs them up right?
But either way, only thing you can do is get crap off your sdcard. data on phone, is gone if not backed up to the cloud or sdcard.
Click to expand...
Click to collapse
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Sowden said:
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Click to expand...
Click to collapse
depending on what you did to "brick" your phone, it might be possible to fix it w/o FXZ'in back.
But if you must FXZ, and cant boot the phone, your SOL. sorry man.
IMHO, In this day and age, your gonna have to use the cloud. New devices are all leaning that way. Look at it like a safety measure incase crap like this happens.
break phone, crap is gone, SDcard screws up, all your pictures and files are gone.
The times of storing contacts on SIM cards is long and gone.
MotoMudder77 said:
depending on what you did to "brick" your phone, it might be possible to fix it w/o FXZ'in back.
But if you must FXZ, and cant boot the phone, your SOL. sorry man.
Click to expand...
Click to collapse
Well, I really didn't do anything wrong. I was working real late with it trying to get an app to coralate with my phone and my tablet. Just let it run out of batteries, and since I was busy, I figured I could charge it back later. Little did I know it wouldn't turn back on again. I am attempting to charge it manually right now, but if that doesn't work, then my last resort will be to take it somewhere locally to try to bring it back. Unless there is someone on the boards here that does a repair over local screen control (logmein.com type thing) (um, anyone on here does that? I had a guy work on my tablet once the same way). Thanks man for you're help.
Edit: Due to my n00bness, I realize that this thread has mutated into something that should go into the "Think you bricked your phone?" thread. Apologies.
So your phone just died?
What happens when you attempt to charge it? With a wall charger, not usb.
Do you get the led lit up?
Sent from my MB865 using Tapatalk 2
Alright, so heres my story. I own two different batteries for my phone. One that came with it that I think I fried the life on it by charging it with an USB OTG (I used it as my entertainment system at the time). The other one I got at batteries+Plus. That was the one I have been using currently. With my newest battery (Batteries+Plus) attached to my phone, I can get it to my "M" splash screen and freeze when I plug it in to the wall. That one I have to work at getting AP Flash on, but I can get that open. It gives me the dreaded "Battery Low - Cannot program" sign. And oddly enough it doesn't give me a selection screen like it usually does, I have been trying to charge that battery manually and checking it with a voltage meter. It seems that its not holding the charge correctly. So I then theres my old battery (that came with the phone). With that attached, I can get past the "M" screen to the "AT&T" splash screen before it freezes. That I don't really have to work hard to get to the AP Flash recovery while plugged into the wall. It is really no help either. I can connect it to my laptop and it says that its USB Transfer ready (but I can't get that with the other battery). They both start the splash screen immediately when I plug it into the wall, I haven't had my phone brick on me like this, so I hope I'm making some kind of sense. Thanks for listening to my story man.
Sowden said:
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Click to expand...
Click to collapse
Just flash the system partition only.
You have to have some command line skills, which is not hard...
1) get your phone back to being charged.
2) get the phone into fastboot mode.
3) connect your A2 to your computer
4) download the correct fxz file for your region.
5) unzip the fxz and save the system.img file in same dir you have the android SDK installed in
6) run cmd.exe
7) cd to the directory you unzipped the fxz system.img file to, from the command line
8) run the following:
Code:
fastboot flash system system.img
fastboot reboot
That should save all your data, since it is stored in /data and not /system.
That should save you from a bootloop if you were on stock, if not you are kind of SOL, unless you can do some install script hacking to only flash /system for the ROM you are on without clearing /data.
jimbridgman said:
Just flash the system partition only.
That should save all your data, since it is stored in /data and not /system.
Click to expand...
Click to collapse
Oh, alright, because in order to flash your phone correctly you have to flash system.img, data.img, and (something else? I've seen it done in a video I just can't remember what it was) right? Alright, I should just google Atrix 2 AT&T USA SFZ and I should find my right one? Thanks for your help guys, I'm going to try to avoid taking it to a shop tomorrow.
Wait a second, sorry to ask another question. If I just update the system img, as you said, can I apply a Gingerbread kernel
and still have it operate the same, or should I find a matching ICS as it was on my phone? Thanks.
Sowden said:
Oh, alright, because in order to flash your phone correctly you have to flash system.img, data.img, and (something else? I've seen it done in a video I just can't remember what it was) right? Alright, I should just google Atrix 2 AT&T USA SFZ and I should find my right one? Thanks for your help guys, I'm going to try to avoid taking it to a shop tomorrow.
Click to expand...
Click to collapse
No you do not have to flash all the partitions. Since all your data sits in its own partition, you can save it by only flashing the system partition and not using RSD, which WILL erase the /data partition, which you want to keep.
I would advise you to take a backup of just your data and save it to your sdcard in case this happens again, if this works for you.
The fxz files are in the developer section or here:
http://sbf.droid-developers.org/edison/list.php
You must know which region and version of android you were on before.
jimbridgman said:
Just flash the system partition only.
That should save all your data, since it is stored in /data and not /system.
That should save you from a bootloop if you were on stock, if not you are kind of SOL, unless you can do some install script hacking to only flash /system for the ROM you are on without clearing /data.
Click to expand...
Click to collapse
Yeah, no dice. I flashed the system.img and the boot.img and I still got the same thing. I guess I'll take it to some local store to see if they can do something to help recover it. Thanks for your help, and I guess that a "cloud" situation is a new reality I will have to consider. Thanks guys, later.
Related
I TRIED THE HBOOT 2.2 ROOT GOT BRICKED AND USED THE FIX FROM "Monarky"
THANKS DUDE AND IT WORKED SO IVE PUT TOGETHER
A SHORTER FIX I ACTUALLY DID THE WORK MYSELF SO ALL YOU HAVE TO DO IS REPLACE THE ATTACHED FILE WITH THE ONE ON YOUR SD CARD
AND RELOAD BOOTLOADER AND IT SHOULD UNBRICK BUT ITS GOING TO SWITCH YOUR "PRI VERSION" BUT IT WORKS
ALL I ASK FOR IS A SIMPLE THANKS
FIX - http://www.megaupload.com/?d=2KA69REH
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
he was probably referring to being stuck at the RUU update screen
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
s0xpan said:
he was probably referring to being stuck at the RUU update screen
Click to expand...
Click to collapse
well yea the red triangle
I haven't downloaded what you cooked up there, but if included radios or the wimax partition, you really need to warn people that they could lose 4G.
If you "brick" your phone, you should only use the RUU from Sprint to fix it. If the phone isn't recognized by the RUU, then extract the PC36IMG.zip from it and use the fastboot command line to flash.
-- Brian
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
Nope, your wrong. Back when I used to mod PSPs, if you flashed a firmware incorrectly, you'd either get a semi-brick or a brick. A semi-brick is when you can't get into the OS, but you can access some sort of recovery menu/method. A brick is when it won't turn on at all or it will turn on but won't do anything (or freeze at splash screen).
mlin said:
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
Click to expand...
Click to collapse
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post. I don't think you understood what I said. Though you could get the phone into bootloader, the screen was not on. The only reason you would even know the phone was on was if you had it hooked up to your comp when you powered up. There was no method you could use that would allow anything to be written to the internal memory. There was a hardware problem with some of the evos, where in they have a TON off bad blocks. This prevented the os from being rewritten. I have meet a few other guys on xda who have the problem with bad blocks. So, how would you define this, if not as a brick? It wasn't hung up somewhere. It was totally unusable. After spending 2 hours on IRC, we decided it was totally unfixable. Took it to a sprint repair center the next day and, funny enough, they agreed. They couldn't even access it enough to tell that I had an unlocked bootloader. Yes, they replaced it.
tejasrichard said:
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post.
Click to expand...
Click to collapse
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
mlin said:
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
Click to expand...
Click to collapse
No big deal, man
The whole thing is pretty silly, anyway. My only point was you could be bricked and still have your charge light comer on. No hard feelings here.
Tejasrichard is right. I got one of the bad blocks phone, brand new too. I guess ill use it for a spare touchscreen
Bootup Problem
So I have an evo that when powered up only displays the startup white HTC EVO 4G screen for 5 sec....turns off for 3 or 4 sec then back on and same in a continuous loop. I can access regular android recovery with the white screen and androids on the bottom. When I choose recovery from the options on that page it does nothing but the white HTC EVO 4G screen boot looping over and over.
Things I have tried:
New SD Card
PC36IMG - tons of them from many methods
Flash a new recovery
The computer does recognize the phone but I can't find it anywhere?
Any help ?
PM me please.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
X2!.................
After trying this method my phone stills only boots to the white screen
I know we're going to get at least one person who says their phone is bricked. Here's how to unbrick it (links to stock rom/kernel, etc) for Virgin and Sprint versions:
http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps!
You'll need to know how to install and patch SWUpdate for the Moment so it works for the Intercept. Not hard at all.
Did I miss something? How did we go from the EVO to the Moment/Intercept? Anyhow I'm having the same problem as whoisjlk in post #14. Please if anyone has a solution I would greatly appreciate it and even donate. PLEASE PLEASE PLEASE...thanks in advance.
Wow I guess I posted in the wrong section LOL.
Ok, I have an Evo that I would like to recover from the dark side.
I rooted my HTC EVO 4g using Unrevoked, it worked fine, then I decided to flash a new rom, followed all the steps and I backed up my stock and wipe data/factory reset and Davik, now my phone doesn't read the sd card.
Took the sd card out and did a FAT32 format (4 times already), downloaded the new zip to it and still not reading.'
Bought a couple different SD cards.
Can't do a restore because the sd card and is not recognized.
As soon as I check install zip from card it reads
ClockworkMod Recovery v2.5.0.1
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(No such file or directory)
E:Can't mount /sdcard
Now I know Amon RA Recovery is way better.
I had S-OFF, after wipe all data have S-ON and don't know why.
This is what I tried:
All kinds of PC36IMG (Recoveries, ROMS, Unrevoked S on and S off)
ADB doesn't work.
Phone is not found, when try to update drivers using Windows 7 it says that Qualcomm-CDMA-Technologies-MSM driver is not found, but my other EVO and the ones that I rooted have no problems.
Phone boots into HBOOT and Recovery.
After opening HBOOT PC36IMG gets recognized but not updated.
In recovery when try to flash from SD has the message E: Can't blah blah
If I try to reboot the phone, it just goes to a black screen with a flashing LED or gets stock on white screen forever.
Any ideas?
I would like to fix it, already have a working phone, and I don't need this one, is just to put all the help together and maybe some one that has a similar problem can avoid all the troubles and follow a single post and not spend hours searching just to find the wrong answers.
Otherwise is going to be just for spare parts and that doesn't help many.
Thanks in advance.
If you have an idea, lets try it, PM or reply here.
So I installed the stock JPU rom to my captivate and then did my 3 button fix combo cause it wasnt working. After that I went and flashed SetiroN 1.46 14*0mhz kernel with Odin.
It restarted the phone to a black screen and since then it has show the same thing.. My jig does not work, hair dryer does not work, different battery does not work, letting the battery sit for various amounts of time doesn't work. From what Setiron told me it seems to be a JPU bootloader issue?
Has anyone else come across this?; or know of a different fix ? I have everything saved on my internal sd and have absolute no access to getting those files out
.edit: sorry if this is in the wrong section
grkmaster said:
So I installed the stock JPU rom to my captivate and then did my 3 button fix combo cause it wasnt working. After that I went and flashed SetiroN 1.46 14*0mhz kernel with Odin.
It restarted the phone to a black screen and since then it has show the same thing.. My jig does not work, hair dryer does not work, different battery does not work, letting the battery sit for various amounts of time doesn't work. From what Setiron told me it seems to be a JPU bootloader issue?
Has anyone else come across this?; or know of a different fix ? I have everything saved on my internal sd and have absolute no access to getting those files out
.edit: sorry if this is in the wrong section
Click to expand...
Click to collapse
If you flashed the LOW package (which contains bootloader) and your bootloader got corrupted... you should send it to Samsung or ATT. There's nothing you can do except buyng a Riff Jtag box which can flash a new bootloader. But that is around 200$
icezar1 said:
If you flashed the LOW package (which contains bootloader) and your bootloader got corrupted... you should send it to Samsung or ATT. There's nothing you can do except buyng a Riff Jtag box which can flash a new bootloader. But that is around 200$
Click to expand...
Click to collapse
Im pretty sure it might have said low in the end.. Damn.. not worth spending that money at all. Thanks for the response.
Two things.. so usually try staying away from new bootloaders which contain LOW just to be safe.. and also there is no other way to get the files out right from the internalsd?
grkmaster said:
Im pretty sure it might have said low in the end.. Damn.. not worth spending that money at all. Thanks for the response.
Two things.. so usually try staying away from new bootloaders which contain LOW just to be safe.. and also there is no other way to get the files out right from the internalsd?
Click to expand...
Click to collapse
sorry mate, if you cant boot it, you cant access the files.. the internal SD is a chip on the MB, if you find a way to take it out and solder it on a usb drive board... then you could take those files out but that's waaaaaay to dangerous. Better send it back
icezar1 said:
sorry mate, if you cant boot it, you cant access the files.. the internal SD is a chip on the MB, if you find a way to take it out and solder it on a usb drive board... then you could take those files out but that's waaaaaay to dangerous. Better send it back
Click to expand...
Click to collapse
yeah im fine.. luckily i did a backup maybe the last time i did a master clear like a week ago so im ok.. i ust like saving my text msgs but thats pretty much the only thing im losing and the rest ill just redownload..
Time to invest on a 32gb external for just these purposes lol .. appreciate the help
So yesterday my phone fell from about OptiPlex height right onto the USB port with a cable plugged in. The plugged torqued a bit, and the result is that it won't connect to any computer, though it seems to charge fine.
I want to see if T-Mo will replace it, but I figure I should get Valhalla off it first. My questions are 2:
1) Is there a way to get it back to stock, including recovery, without USB?
2) Does T-Mo really check that I haven't rooted and ROM'ed the phone?
Does anybody have any experience like this to share?
brutuspa said:
So yesterday my phone fell from about OptiPlex height right onto the USB port with a cable plugged in. The plugged torqued a bit, and the result is that it won't connect to any computer, though it seems to charge fine.
I want to see if T-Mo will replace it, but I figure I should get Valhalla off it first. My questions are 2:
1) Is there a way to get it back to stock, including recovery, without USB?
2) Does T-Mo really check that I haven't rooted and ROM'ed the phone?
Does anybody have any experience like this to share?
Click to expand...
Click to collapse
Obtain a micro SD to SD converter
Place the micro SD into the converter, plug it into your computer
Open the SD and place the ROM zip onto the SD
Put the SD back into your phone
Boot to recovery, flash ROM from zip
Here is a stock zip i found for you: http://forum.xda-developers.com/showthread.php?t=1062847
Also I know this isn't going to help too much, but I once "bricked" an optimus (I now know it wasn't bricked, but I was dumb n00b and deleted the launcher XD) and returned it within the 14day window... they never even asked a question...
tehgyb said:
Obtain a micro SD to SD converter
Place the micro SD into the converter, plug it into your computer
Open the SD and place the ROM zip onto the SD
Put the SD back into your phone
Boot to recovery, flash ROM from zip
Here is a stock zip i found for you: http://forum.xda-developers.com/showthread.php?t=1062847
Also I know this isn't going to help too much, but I once "bricked" an optimus (I now know it wasn't bricked, but I was dumb n00b and deleted the launcher XD) and returned it within the 14day window... they never even asked a question...
Click to expand...
Click to collapse
Thanks for the link, I'll definitely grab that ROM.
However, how can I Odin it without a working USB? I can deal with any CWM ROMs, but I'd be returning the device without stock recovery and rooted. I am probably being overly paranoid, but I could get by using the phone without USB, just flashing whatever GB or, dare I say, ICS ROMs that our benevolent devs make available.
See my dilemma?
Wait, so is the problem your USB cable or the actual USB plug on your phone?
If it's the former, you could get any Micro USB cable. I found that my SGS4G can charge with the BlackBerry cables.
bkoon1218 said:
Wait, so is the problem your USB cable or the actual USB plug on your phone?
If it's the former, you could get any Micro USB cable. I found that my SGS4G can charge with the BlackBerry cables.
Click to expand...
Click to collapse
No, it's the latter. Sorry, in trying to brief I wasn't clear.
Ordinarily to return a phone I assume I would need to track down a stock image, Odin it, and then SuperOneClick unroot, if necessary. I would imagine both of those steps would require a working data connection via USB. Mine only charges, it now doesn't connect on three computers that used to mount it with no problem.
I can pull the MicrosSD or transfer via WiFi and load anything through CWM (ICBINB, Valhalla, KI*, KJ*...) and have been. But if I want to turn it over to T-Mo for a replacement, I imagine it has to look like I haven't rooted and ROMed it with every GB release that has seen the light of day the past 2 months. Even if I CWM a stock KB5 or KD1, I'll still have a warranty-violating Recovery and it will be rooted.
brutuspa said:
Thanks for the link, I'll definitely grab that ROM.
However, how can I Odin it without a working USB? I can deal with any CWM ROMs, but I'd be returning the device without stock recovery and rooted. I am probably being overly paranoid, but I could get by using the phone without USB, just flashing whatever GB or, dare I say, ICS ROMs that our benevolent devs make available.
See my dilemma?
Click to expand...
Click to collapse
That link is a cwmable zip of stock without root. I would think that'd do the trick, no?
Sent from my SGH-T959V using XDA App
My bad, I assumed it was Odin only.
brutuspa said:
My bad, I assumed it was Odin only.
Click to expand...
Click to collapse
Unless I misread something... :X
Sent from my SGH-T959V using XDA App
I'll let you know after Titanium finishes. Wish me luck
tehgyb said:
Unless I misread something... :X
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
It's an Odin ROM, from what I'm reading. I haven't taken the time to download it and check myself though.
bkoon1218 said:
It's an Odin ROM, from what I'm reading. I haven't taken the time to download it and check myself though.
Click to expand...
Click to collapse
OK, I'll hold off on that then.
For what it's worth, T-Mobile pointed out that I had "weird" software on my phone, and said they couldn't help. I tried to say yes, but if I revert to stock what could you do? They didn't go for it.
Sent from my SGH-T959V using XDA App
brutuspa said:
For what it's worth, T-Mobile pointed out that I had "weird" software on my phone, and said they couldn't help. I tried to say yes, but if I revert to stock what could you do? They didn't go for it.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Damn, that really sucks. You really shouldn't admit to rooting and flashing custom ROMs, since that already voids your warranty. Reverting back to stock doesn't legally unvoid your warranty, I believe.
Sorry, but I think you just might be SoL in this case.
If you have insurance, a crazy idea could be to purposely hard brick your device and say that your phone completely screwed up after you dropped it. You should probably get more suggestions about this idea first though.
Another less crazy idea would be for you to open up your phone and see if you can set it back in place properly.
bkoon1218 said:
Damn, that really sucks. You really shouldn't admit to rooting and flashing custom ROMs, since that already voids your warranty. Reverting back to stock doesn't legally unvoid your warranty, I believe.
Sorry, but I think you just might be SoL in this case.
If you have insurance, a crazy idea could be to purposely hard brick your device and say that your phone completely screwed up after you dropped it. You should probably get more suggestions about this idea first though.
Another less crazy idea would be for you to open up your phone and see if you can set it back in place properly.
Click to expand...
Click to collapse
Technically I didn't admit anything. She said "let me take it in back and try it on our computer". 5 minutes later she was showing me the About phone screen and calling me out for it. I'll try a different T-Mo store, and hope she didn't note my account.
Then my troubles got worse, but now are better.
I ended up hosing the whole thing. I couldn't get back to recovery - only download. Then I tried Odin, while jiggling the USB, and was able to get it to connect and accept KD1, but it failed halfway through. I kept monkeying with the USB and saw a little flash and then it powered off completely. Battery pull got it back to the failed firmware - try Kies prompt, but Odin could see it. Pushed KD1 again while not even breathing on the phone and it finished.
I now have a phone that looks stock. It definitely has a bad USB. I know a shop that replaced my Blackberry Curve's USB for about $70. That will be my next step if T-Mo marked my account with a scarlet letter.
Let's see how long I can stand stock
PS at least my WiFi works better than GB
PPS A different store arranged for a replacement for a $20 processing fee. It arrives Thursday.
i get the unlocked warning screen then it goes black, i'm unlock but cant flash cwm i try and get error cant load cwmrecovery.img anyone have any ideas? thanks
Need a little more info than that. What did you do to it?
Sent from my XT897 using Tapatalk 2
is there a way to go back to stock
Yea, using RSD, look in the dev forum.
Sent from my XT897 using Tapatalk 2
i check but i think they were having problems with files
perrotype3 said:
i check but i think they were having problems with files
Click to expand...
Click to collapse
Yeah, RSD system img is still having problems. There are a couple of threads here with nearly stock system recoveries for TWRP.
http://forum.xda-developers.com/showthread.php?p=32409538
http://forum.xda-developers.com/showthread.php?p=32514141
-Saint
You can get un-stuck from this spot .. it took me longer than I would have liked, but with the patience of other folks here and my unwillingness to quit, i got it back and working. The stock images are here. The key is that you need them on the external SD card to flash them back on using TWRP, which was the problem I was having. I eventually used a whole different laptop altogether with a micro-sd to SD adapter to move them over.
If Id have waited one more day, a few generous fellows found a way to unlock the bootloader without having to contact Sprint, then if it really bricks then wouldnt have it on record. Still quite a feat.
Herby6262 said:
You can get un-stuck from this spot .. it took me longer than I would have liked, but with the patience of other folks here and my unwillingness to quit, i got it back and working. The stock images are here. The key is that you need them on the external SD card to flash them back on using TWRP, which was the problem I was having. I eventually used a whole different laptop altogether with a micro-sd to SD adapter to move them over.
If Id have waited one more day, a few generous fellows found a way to unlock the bootloader without having to contact Sprint, then if it really bricks then wouldnt have it on record. Still quite a feat.
Click to expand...
Click to collapse
If you really can't fix it, pm me.
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.