Develop Bugs

AT&T galaxy s3 softbricked

I was trying to install one of drewgarens touchwiz roms. touchwiz milestone 5 firefly i believe. not the most recent one because i was too lazy . boy was that a mistake. everything was going smoothly until it booted and it got stuck on boot. I thought no big deal just go into recovery and use a backup. until i did so and recovery was gone and there was only download mode. I have spent the whole afternoon trying to fix it and none of it has worked. I tried flashing the stock rom and it as well got stuck on boot. I looked at all the AT&t relevant ones and also the international versions. so all in all is there anyway to fix this and has anyone had the same issue? i was flashing from cyanogenmod 10 m1 to the drewgaren rom btw. I can also go to download mode. I tried to flash stock but it still gets stuck on boot. log. I flashed the ATT boot logo and it did not work. all of which were flashed through odin.
any thanks in advance is greatly appreciated.

I think you can flash back to stock with just download mode + odin

Randomacts said:
I think you can flash back to stock with just download mode + odin
Click to expand...
Click to collapse
I already tried that. It still get stuck on the Boot logo

stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
I can't help you but I wish you luck.

stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Unplug your device. Hold the power button to turn it off. Hold volume up, home, and power. It should go to recovery. If you do the same thing with volume down instead of up, you can get into download mode.
Sent from my SAMSUNG-SGH-I747 using xda premium

Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.

jethro650 said:
Sounds like you need a recovery...try this
http://forum.xda-developers.com/showthread.php?t=1746665
[SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]
Follow the instructions and you should be able to flash the recovery and continue on with what you were doing. Remember to wipe really good when going from aosp back to any stock based ROM. They are completely different and will cause boot loops if you don't wipe.
Click to expand...
Click to collapse
I cannot enable usb debugging

Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.

jethro650 said:
Crap...there are Odin flashable versions of cwm floating around you'll need to find one of those. If you haven't found one I'll post one up when I get home.
Click to expand...
Click to collapse
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
Ok here we go Odin cwm--> https://dl.dropbox.com/u/28590257/Odin recovery/CWM-Recovery-LTE-SGS3-v4.tar.md5
Newest twrp --> https://dl.dropbox.com/u/28590257/Odin recovery/twrp2.3.1install.zip
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.

jethro650 said:
K I made it home lol. I'll attach a Odin flashable cwm, it's an older one but it'll get you a recovery, I hope. I just tried it on my phone with Odin, 3.07 both with usb debugging enabled and disabled on my phone and it worked both times. Crap keep getting errors uploading right to xda servers, I'll drop box it in a minute.
I'll add the newest twrp for you lol. Flash the cwm with odin, should work and then the twrp is a zip you can flash in cwm.
Hope this helps get you a recovery.
Remember in Odin use only PDA and only have auto reboot checked.
Click to expand...
Click to collapse
This may sound like a stupid question but what boxes do i tick in odin?

After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:

jethro650 said:
After your hooked up and Odin is open under the options on the left side check only Auto Reboot. On the right under files check PDA and use that button to browse your computer and find the cwm you downloaded from my dropbox. Then just hit start on the bottom of the Odin window and let it finish, your phone should reboot when its done. It will get stuck again like you described in your first post but pull the battery, put it back in and boot into recovery using vol up,home and power buttons. That should (if everything flashed OK) put you into cwm 5.5.0.4. Once there wipe data/factory reset then restore the back up you mentioned in your original post, that should get you running again.
---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------
If something has happened to your backup then you could try the stock rooted stuff here , just pick the one for your carrier and follow the instructions. :highfive:
Click to expand...
Click to collapse
I was able to get it into recovery but i realized i did not have my sd card in so i turned it off and put my sd card in. unfortunately i was not able to get it back into recovery i tried flashing it again with the sd card in and no luck

That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?

jethro650 said:
That's odd. Couple of stupid questions on my part just to make sure, you had the right button combo, and, you released the buttons soon as the splash screen came on? Can you still get into download mode? Oh and did you do the wipes while in recovery?
Click to expand...
Click to collapse
oh my gosh THANK YOU SOOOMUCH. I was worried i would have to take it to at&t ill be sure to press the thanks button.

I take it you got your phone working lol. Glad I could help a little. Little advice, anytime you switch to a different type of ROM (aosp to stock based or the other way around) make sure you wipe data/factory reset before flashing anything. It will save you problems in the long run.
Oh and could you go back and edit your original post and just add solved in brackets to the title for people in trouble looking for info.

stuart26 said:
I already tried that. It still get stuck on the Boot logo
Click to expand...
Click to collapse
Depending on which stock ROM you flashed with odin you should now have a recovery, if not then something isn't right. The full bone stock ROM should have the factory 3e recovery, and the root injected stock ROM should have some version of CWM recovery. A factory reset will most likely fix your boot loop, if there is no recovery flash the rooted stock ROM that matches your device from this guide.
Edit - Didn't see there was a second page 0_o

[Q] After CWM upgrade cannot start or restore phone

I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message

Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"

I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium

I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse

stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?

In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.

Same here, stay away from that update! Bad things!

This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?

Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...

I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP

I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.

J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.

[Q] ClockWorkMod - Stuck in Odin Mode!

Hello Everyone,
I'm hoping someone can help me out.
I installed ROM Manager on my phone, and (honestly not sure why!) but I did. When I launched the application, it told me that v. 6.0 was available if I wanted to update - Stupid me, updated ClockWorkMod to v6.0.
Well, everything was fine.. until I decided to use the ROM Manager Backup option - When I rebooted, it got stuck on
"Could not do normal boot"
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFI_LSB: 0X30
WRITE PROTECTION: Enable
Downloading....
Do not turn off target!!
I'm not sure what to do at this point. I've tried VOL UP + HOME + POWER - but it goes right back to this spot. I've pulled the battery waited for 5 mins - then tried the same VOL UP + HOME + POWER - still nothing.
Any help would be greatly appreciated.
Thanks,
Jay

Don't press the home button is the first thing I can think of.
Power + Volume up = Custom Recovery
Power + Volume down = ODIN/Download mode
To get into Recovery mode:
Pull battery
Insert battery but Don't turn phone on.
Press Power + Volume up buttons and hold them until you see the custom recovery prompt in blue lettering in the upper left corner of the S4, and then immediately release the buttons. You should enter into Recovery.
I don't use CWM so I'm not that familiar with its installation, etc. But there are a few threads that go into CWM in detail.

Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..

JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is method of choice, but sometimes the Recovery doesn't take, so Method #1 is then recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28

TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?

mgbotoe said:
TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?
Click to expand...
Click to collapse
TWRP looks to have worked for me.
But I can see what you mean. I no longer get stuck in ODIN MODE - but I was having issues after dropping a ROM on my phone. Even after successful setup of the ROM, if I decided to reboot just for giggles. It would freeze on Samsung S4 Logo.
Well, I have since fixed this issue:
I believe the reason why I was getting stuck on Samsung S4 Logo on reboot was because in addition to wipe data/wipe cache/wipe dalvik - I also formatted the internal_sd - this is just a theory but my internal_sd regardless of me dumping a ROM on there, after reboot would do nothing - When I went in recovery - internal_sd showed 0MB. Thus, stuck boot screen. Nothing to boot too.
FIX: Installed STOCK ROM, and KERNEL - Confirmed, that reboot works after setting up phone. My understanding is that it installs all the necessary folder structure required. Got the STOCK ROM from: http://galaxys4root.com/galaxy-s4-stock-firmware/
Then followed this root process and recovery:
http://galaxys4root.com/galaxy-s4-ro...g-twrp-method/
Once I did that, booted to recovery did the normal (wipe data/wipe cache/wipe dalvik) then dropped ALPHA ROM on my phone, along with Infamous KERNEL, and everything is great. Reboots like a champ now. -- Still using TWRP, but v. 2.5.0 - (no issues as of yet! )

Glad to see all working out for you

JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!

sincity said:
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!
Click to expand...
Click to collapse
Install ODIN 3.07 to your pc
Install drivers for your device onto your pc
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Please read the above thread in the link carefully.
If your device is stuck on a screen, what were you doing prior to get to that state.
First, boot into custom recovery and Wipe cache and dalvik cache, reboot, and see if that helps.
Either way, you should have ODIN on your pc

Biker1 said:
Install ODIN 3.07 to your pc
Install drivers to your device.
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
Thanks a million... I'll give it a try! Wish me luck!

sincity said:
Thanks a million... I'll give it a try! Wish me luck!
Click to expand...
Click to collapse
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
---------- Post added at 11:58 PM ---------- Previous post was at 11:43 PM ----------
JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
If you go with TWRP, don't use Goo Manager as that will install 2.6.0.0 which has some issues for some, as you probably know.
Install TWRP 2.5.0.2 with ODIN, which I did many months ago, and have had zero issues.
You can install with Mobile ODIN also I believe.

Biker1 said:
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
Click to expand...
Click to collapse
Ok I figured it out... I really appreciate your help! My blood pressure went down! LOL!
Yes my cell was rooted... I used GX4EX by:
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***

[Q] goto TWRP from a wiped device

Hi All,
Repost since I posted this question in the wrong forum before. Sorry for the spam.
I tried to flash my E980 (already rooted and running Carbon ROM nightly build 10/10/2013) with the latest ROM nightly build 10/24/2013.
When in TWRP 2.5.0.0, I wiped everything except the external SD, added 10/24/2013 build image, gapps, and modem zips and hit install rom.
The flashing stopped due to error saying the MD5 signature of the build image zip is bad.
Now I am left with a device with no OS installed. When I power it on, after the initial LG logo flash, nothing happens.
Would you please tell me how to get back into the recovery mode? Thanks a lot.
I have re-downloaded the ROM zip and put it in the external SD.
At this stage, do I have to use LG flash tool to flash the factory ROM first, then do root,...? Or can I flash the custom ROM directly.

Flash the ROM in cwm directly
Sent from my GT-P3100 using xda app-developers app

Do this
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.

StarkV5 said:
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.
Click to expand...
Click to collapse
Volume up
Sent from my Optimus G Pro using XDA Premium 4 mobile app

StarkV5 said:
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.
Click to expand...
Click to collapse
StarkV5, thanks a lot!
It is "volume up + home + power". Returned to TWRP 2.6.1.0 recovery and flashed 20131104 CM10.2 today. Everything works smoothly except that the screen touch issue in TWRP. The touch calibration was spot on during the first use after TWRP install. After a reboot, the touch is so off. It is like working with a 960*540 screen, i.e. the top left quadrant of the E980 screen.
Thank you (and Neroga too) again!

[Q] its bad

Tried Cyanogen 10.2 d2spr
Sprint Galaxy s3 L710
Android 4.3
Odin 1.85
Got superuser and used goomanager w twrps
made backups
Tried to flash cyanogen and i got error missing md5
tried a fix where you edit the updater-scripts in the cyanogen zip and that didnt work
Then I read that switching to cws would fix the problem, I read that you can d/l the cws zip and use twrps to flash it
Basically I was way over my head and shoulda kept the restore to stock option because that WAS working
Phone wont boot normal. volumeup and power and menu just flashes"recovery booting" or something really fast in the top left corner and shuts back off
Idk... Odin doesnt recognize the phone anymore
Definitely dont know what im doing anymore

thecuddy said:
Tried Cyanogen 10.2 d2spr
Sprint Galaxy s3 L710
Android 4.3
Odin 1.85
Got superuser and used goomanager w twrps
made backups
Tried to flash cyanogen and i got error missing md5
tried a fix where you edit the updater-scripts in the cyanogen zip and that didnt work
Then I read that switching to cws would fix the problem, I read that you can d/l the cws zip and use twrps to flash it
Basically I was way over my head and shoulda kept the restore to stock option because that WAS working
Phone wont boot normal. volumeup and power and menu just flashes"recovery booting" or something really fast in the top left corner and shuts back off
Idk... Odin doesnt recognize the phone anymore
Definitely dont know what im doing anymore
Click to expand...
Click to collapse
Can you get into download mode or are you just plugging into the computer; Odin won't recognize your phone unless it is in download mode first. Also, I find Odin 3.07 to be a bit better than 1.85.

Mr. Struck said:
Can you get into download mode or are you just plugging into the computer; Odin won't recognize your phone unless it is in download mode first. Also, I find Odin 3.07 to be a bit better than 1.85.
Click to expand...
Click to collapse
it doesnt do anything when i try to get to download mode.
If its plugged to the computer or wall, it will boot loop without a samsung screen
Not plugged in boots to samsung screen with blue text top left and shuts off right after. can barely read the blue text its so fast

thecuddy said:
it doesnt do anything when i try to get to download mode.
If its plugged to the computer or wall, it will boot loop without a samsung screen
Not plugged in boots to samsung screen with blue text top left and shuts off right after. can barely read the blue text its so fast
Click to expand...
Click to collapse
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?

Mr. Struck said:
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?
Click to expand...
Click to collapse
ok. i wasnt holding that one long enough. so now use odin? <3

Mr. Struck said:
To be clear, you are holding Volume Down (not Volume Up, which is for Recovery Mode), Home Key, and Power Button all at the same time until the main Download screen appears?
Click to expand...
Click to collapse
Ran odin and now i can get it to boot to cwm instead of twrps. should i go for the install again or call it quits. i dunno what exactly went wrong or how to go about the install from this point. thank you

thecuddy said:
ok. i wasnt holding that one long enough. so now use odin? <3
Click to expand...
Click to collapse
You need a couple of things first. You will want to use Odin to push the latest version of Philz Touch, as it is a much better recovery than either CWM or TWRP. There is an option in Philz to restore TWRP backups, so as long as the backup you made earlier was of a proper working ROM (I would assume of your stock version), then you can use Philz to restore it. If you aren't comfortable switching recoveries right away, use Odin to push TWRP again. Basically, I want to make sure you have a working custom recovery in place before proceeding any further. Also, don't use a third-party to download/install ROM's, you need to be downloading from the official source. If you are wanting to run Cyanogen, go to their website and download directly from them.
Philz Touch XDA Thread by CNexus
http://www.cyanogenmod.org/
Once you have pushed the recovery onto your phone (make sure the Reboot option is unchecked in Odin, otherwise it will boot up too soon), pull your battery out for about ten seconds, replace, and then use the button sequence for Recovery Mode, make sure to hold the buttons past the vibration until the actual screen pops up.
---------- Post added at 12:35 AM ---------- Previous post was at 12:26 AM ----------
thecuddy said:
Ran odin and now i can get it to boot to cwm instead of twrps. should i go for the install again or call it quits. i dunno what exactly went wrong or how to go about the install from this point. thank you
Click to expand...
Click to collapse
If you received an MD5 error on the first install, you most likely have a bad download, so you probably won't be able to flash it with CWM either. I am assuming that when you made your backup, you used TWRP, in which case you cannot restore that with CWM, you will need either Philz Touch or TWRP. We need to get you booted back into a working system before proceeding, as you should have no OS installed currently if you wiped everything properly before attempting to flash Cyanogen.

I feel like Im going to have three different recoveries on the phone if I do that. I don't understand what im doing fundamentally. All I can do right now is follow instructions. And I'm scared now lol. How do I increase your thanks meter ahah Maybe I should do more research. Should what I was trying to do work in the first place?

thecuddy said:
I feel like Im going to have three different recoveries on the phone if I do that. I don't understand what im doing fundamentally. All I can do right now is follow instructions. And I'm scared now lol. How do I increase your thanks meter ahah Maybe I should do more research. Should what I was trying to do work in the first place?
Click to expand...
Click to collapse
Only one recovery can exist at a time, so whatever one you pushed or flashed most recently will be the current one. Which one did you have on the phone when you made your backup? That will be a good starting point.

Mr. Struck said:
Only one recovery can exist at a time, so whatever one you pushed or flashed most recently will be the current one. Which one did you have on the phone when you made your backup? That will be a good starting point.
Click to expand...
Click to collapse
Started with twrps. Got md5 error. Reverted to backup. Then got cwm zip and booted to twps and tried to install it. Then problem.

thecuddy said:
Started with twrps. Got md5 error. Reverted to backup. Then got cwm zip and booted to twps and tried to install it. Then problem.
Click to expand...
Click to collapse
So as I mentioned earlier, you will need to get either TWRP back as your recovery, in order to restore the backup you made with it, or you will want to switch to Philz, which is the best recovery option available anyway, and use Philz to restore your TWRP backup. I think for starters you will want to use TWRP just to get back up and running, and then switch to Philz soon so that you aren't too overwhelmed tonight.
http://techerrata.com/browse/twrp2/d2spr
Choose the tar file for either version 2.6.3.0 or 2.6.3.1 and use Odin to push it onto your phone (2.6.3.1 is the newest version, but doesn't install properly on some devices; 2.6.3.0 should work for our purposes if 2.6.3.1 doesn't install properly for you). Then follow my instructions a couple of posts back about booting into recovery after using Odin.

Ill have to do this tomorrow. I pushed the tar through with odin and the phone is running at stock with supersu. Im not sure if my recovery is cwm or twrp now. But I have spent all day doing this. Ill continue tomorrow thnx again.

thecuddy said:
Ill have to do this tomorrow. I pushed the tar through with odin and the phone is running at stock with supersu. Im not sure if my recovery is cwm or twrp now. But I have spent all day doing this. Ill continue tomorrow thnx again.
Click to expand...
Click to collapse
You should now have TWRP as your custom recovery. Feel free to PM me if needed tomorrow for any advice going forward.