[SOLVED] How do you enter recovery mode for TWRP ? (Bootloop) - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.

TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?

Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.

TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.

Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen

TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?

Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.

TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.

Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?

TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.

Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol

TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.

Related

[Q] bootloop and red triangle in recovery mode HELP NEEDED!

Dear guys from XDA,
I think I messed up real good this time. My rooted HTC Desire with a 2.2 ROM wasn't taking the update which I wanted to do. To fix this I tried to manually update my phone by downloading the update on my computer and run it via Recovery mode. I used the option install zip from sd card.
Unfortunately by doing so, I did not realize I deleted my ROM and replaced it with an update. Now I'm stuck with a phone in bootloop and red triangle when trying to access recovery mode to install my older ROM (which I usually did when I messed it up).
I know I can press the volume up button and reboot but then I get stuck into a bootloop. Eventually I have to pull the battery out and I'm back at the beginning. Can't do anything anymore.
I tried many tutorials but I could not fix this, also I'm not really into the 'techy' stuff so can you guys be real clear in your help.
sounds like you're just missing a ROM on your phone. Can't you just download the ROM you want, put it on your SD card and flash that to get back up and running? Or restore a NANDroid backup?
...assuming you mean you rooted your phone and then failed at flashing a ROM..but it sounds like you might mean you attempted to download and OTA update after being rooted?
Download a ROM, put it on your SD card, boot into Recovery (vol. down + power), wipe all data, cache, dalvik, then install the new ROM from the SD card.
Hi,
thx for your reply. I am indeed missing a ROM. The problem is that I can't access the option 'install zip from sdcard' in my recovery mode. I am now trying to rename a ROM as update.zip so I can install that. Any further suggestions?
ErwinVermeulen said:
Hi,
thx for your reply. I am indeed missing a ROM. The problem is that I can't access the option 'install zip from sdcard' in my recovery mode. I am now trying to rename a ROM as update.zip so I can install that. Any further suggestions?
Click to expand...
Click to collapse
Can you get into fastboot ? (back button + power)
paul.c said:
Can you get into fastboot ? (back button + power)
Click to expand...
Click to collapse
Yes i can enter that. Does that help me?
ErwinVermeulen said:
Yes i can enter that. Does that help me?
Click to expand...
Click to collapse
Install HTC Sync, download the RUU which most resembles your original RUU from here: http://forum.xda-developers.com/showthread.php?t=695667.
Connect your phone via USB in fastboot, and run the RUU.exe you've downloaded. You should be fine.
yes it helps you
you can run a RUU now
just plug phone with usb cable to PC, boot into fastboot mode and execute the RUU.exe
it will go back to stock, you will lose root and custom recovery but at least it will boot up, so you can root again etc.
Thx guys! that did it for me! Really easy job! You have no idea how relieved I am right now. Some tech-guys at my local computer shop told me to send it back to the manufacturer cuz the ROM needed to be synced with the motherboard. I already thought it was a weird story.
Again, thx XDA!

[Q] Phone stuck in boot loop, not recognized by Odin

Earlier I reflashed back to the stock rom for my Galaxy S III, and after I flashed a new install of cyanogen mod I can't get my phone out of the boot loop. I can still access download mode but Odin and my computer won't pick up on it, and I can still access Clockword Mod. Is there anything to do or am I out of luck because my computer doesnt recognize my phone
Do you have an ext SD card ? Place a ROM on the ext card.
Did you wipe cache in stock recovery after flashing back to stock ?
Sent from my SAMSUNG-SGH-I747 using xda premium
re: bootloops
iamblue337 said:
Earlier I reflashed back to the stock rom for my Galaxy S III, and after I flashed a new install of cyanogen mod I can't get my phone out of the boot loop. I can still access download mode but Odin and my computer won't pick up on it, and I can still access Clockword Mod. Is there anything to do or am I out of luck because my computer doesnt recognize my phone
Click to expand...
Click to collapse
Try this, usually in a case like yours there is at least a 50% success rate.
Reboot the phone into recovery and do a "Factory Reset".
After doing that reboot the phone and see if it boots completely.
If the phone boots up completely, you will also be able to go into download mode.
You may want to shell out less than $5.00 including shipping for a USB JIG on eBay or other places.
With a JIG all you do is turn the phone off or remove your battery, wait 20 seconds - replace battery and plug the little JIG into the usb of the
phone then wait a 2-3 seconds more or less and like magic you will be in download mode ready to Odin flash(tar) a proper Touchwiz Jellybean
I747 4.1.2 stock rooted rom which are very much un-like all these CM10/AOSP/AOKP roms which are all just experimental.
Once you have flashed the stock rooted jellybean 4.1.2 TAR rom you will be able to flash any custom Touchwiz Jellybean
custom rom of your choice unless you still want to go ahead and flash another experimental CM/AOKP/ASOP rom.
Good luck!
Not to nit pick, but the latest stock Jelly Bean for the I747 is 4.1.1, not 4.1.2. Also, most of the stock rooted roms don't include custom recovery. They usually include the stock 3e recovery. To get a custom recovery, just dl Rom manager for cwm, or goo manager for twrp, and they can install a recovery for you that will have you ready to flash.
Which version of stock did you flash?
jperry73 said:
Remove Kies and install the Samsung USB drivers for ODIN to recognize it.
Click to expand...
Click to collapse
Yup.
Was just going to ask if the OP was successful in connecting the S3 with ODIN in the past.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iamblue337 said:
Earlier I reflashed back to the stock rom for my Galaxy S III, and after I flashed a new install of cyanogen mod I can't get my phone out of the boot loop. I can still access download mode but Odin and my computer won't pick up on it, and I can still access Clockword Mod. Is there anything to do or am I out of luck because my computer doesnt recognize my phone
Click to expand...
Click to collapse
hi, umm did you get your matter resolved man? i am stuck with the same problem. please assist.
shaq64 said:
hi, umm did you get your matter resolved man? i am stuck with the same problem. please assist.
Click to expand...
Click to collapse
What bootloader and modem are currently on your phone?
What ROM were you on and what were you flashing when the troubles started?
Since you can get into download mode, can you get into Recovery Mode? If you can, try putting CM11 on a MicroSd card and flash it from CWM.
iamblue337 said:
Earlier I reflashed back to the stock rom for my Galaxy S III, and after I flashed a new install of cyanogen mod I can't get my phone out of the boot loop. I can still access download mode but Odin and my computer won't pick up on it, and I can still access Clockword Mod. Is there anything to do or am I out of luck because my computer doesnt recognize my phone
Click to expand...
Click to collapse
dawgdoc said:
What bootloader and modem are currently on your phone?
What ROM were you on and what were you flashing when the troubles started?
Since you can get into download mode, can you get into Recovery Mode? If you can, try putting CM11 on a MicroSd card and flash it from CWM.
Click to expand...
Click to collapse
My sgs2 is stuck in a boot loop, computers won't recognize the usb connection, and my sd card won't mount on philz touch 5 V6.0.3.7 My SD card is, however, recognizable if I plug it directly to my computer using an adapter.
so I rooted my phone using CWM. After that, my computer stopped recognizing my phone. I tried everything to fix it including factory resetting my phone, formatting cache, data, system, and sd card all under the CWM boot menu (hold volup+home+power). Soon afterwards, my phone got stuck in a boot loop. On startup, it hangs on the white "Samsung" logo. While trying to fix the issue, I noticed that my sd card won't mount.
I've tried this method, but it requires that I either have usb access or access to my phone. I've tried formatting the SD card in my computer. I've tried using different computers. I've tried using different usb cords. I've tried searching Google and these forums for a solution. i have uninstalled the samsung drivers countless times and rebooted with no success.
I need to figure out a way to flash the stock rom back to my phone. In order to do this, I need to get my usb to recognize or manage to have phil touch 5 v 6.0.3.7 mount the sd card. If I can do this, the rest is easy. Does anyone has any ideas on what can be done? please please assist!
shaq64 said:
My sgs2 is stuck in a boot loop, computers won't recognize the usb connection, and my sd card won't mount on philz touch 5 V6.0.3.7 My SD card is, however, recognizable if I plug it directly to my computer using an adapter.
so I rooted my phone using CWM. After that, my computer stopped recognizing my phone. I tried everything to fix it including factory resetting my phone, formatting cache, data, system, and sd card all under the CWM boot menu (hold volup+home+power). Soon afterwards, my phone got stuck in a boot loop. On startup, it hangs on the white "Samsung" logo. While trying to fix the issue, I noticed that my sd card won't mount.
I've tried this method, but it requires that I either have usb access or access to my phone. I've tried formatting the SD card in my computer. I've tried using different computers. I've tried using different usb cords. I've tried searching Google and these forums for a solution. i have uninstalled the samsung drivers countless times and rebooted with no success.
I need to figure out a way to flash the stock rom back to my phone. In order to do this, I need to get my usb to recognize or manage to have phil touch 5 v 6.0.3.7 mount the sd card. If I can do this, the rest is easy. Does anyone has any ideas on what can be done? please please assist!
Click to expand...
Click to collapse
Did you find something ? I just have the same problem...

[Q] Soft Bricked....can't unbrick or revert to stock rom...any thoughts?

I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works

Problems downgrading from 4.3

Hello! I have been flashing roms/kernels for awhile now. I have tried probably 12-15 different roms and beanstalk has been my favorite for awhile now.
Anyway, i decided to revert back to stock so i could update and try stock 4.3. First thing i did was flash stock 4.1.1(i think thats what version it was) firmware with odin. Everything went fine and phone booted up and worked perfectly. So i proceeded to update via software update in the settings menu. My phone updated flawlessly and before i knew it i was on stock unrooted 4.3. Needless to say I did not like the changes, so i decided to go back to the older version.
So, i flashed the stock 4.1.1 firmware with odin again and it was a pass. I then tried to turn my phone back on and it would hang at the samsung logo. So i figured i would restore my old beanstalk backup. I tried to restore it and there was an error. So i rebooted my phone and it hanged on the samsung logo again, only this time there is that little blue cyanogenmod guy there like it used to be when i was running beanstalk. I tried flashing different stock firmwares and now they all fail with odin. I rebooted into recovery and did a data wipe many times and i still cannot boot or flash anything with odin.
I can still get into cwm recovery and download mode. Im thinking that the older stock rom i flashed caused problems because i was on 4.3. Something wrong with the bootloader maybe?
Any help or advice to get this fixed would be great. I still feel there is hope because i can reboot into recovery and download mode.
well nvm, my phone is really screwed now. I read another post and it said to flash a boot image file. I flashed the file and tried to reboot and now the phone wont come on and i cant get into recovery or download mode. =-( now i officially have a paper weight
be there... done that
scorey03 said:
Hello! I have been flashing roms/kernels for awhile now. I have tried probably 12-15 different roms and beanstalk has been my favorite for awhile now.
Anyway, i decided to revert back to stock so i could update and try stock 4.3. First thing i did was flash stock 4.1.1(i think thats what version it was) firmware with odin. Everything went fine and phone booted up and worked perfectly. So i proceeded to update via software update in the settings menu. My phone updated flawlessly and before i knew it i was on stock unrooted 4.3. Needless to say I did not like the changes, so i decided to go back to the older version.
So, i flashed the stock 4.1.1 firmware with odin again and it was a pass. I then tried to turn my phone back on and it would hang at the samsung logo. So i figured i would restore my old beanstalk backup. I tried to restore it and there was an error. So i rebooted my phone and it hanged on the samsung logo again, only this time there is that little blue cyanogenmod guSD there like it used to be when i was running beanstalk. I tried flashing different stock firmwares and now they all fail with odin. I rebooted into recovery and did a data wipe many times and i still cannot boot or flash anything with odin.
I can still get into cwm recovery and download mode. Im thinking that the older stock rom i flashed caused problems because i was on 4.3. Something wrong with the bootloader maybe?
Any help or advice to get this fixed would be great. I still feel there is hope because i can reboot into recovery and download mode.
Click to expand...
Click to collapse
I would first download a fresh version of a rom and the corresponding version of GAPPs and on your computer. Transfer you files onto you misco SD card via the SD card slot on the computer. Boot your phone into recovery and flash them from the /sdcard1 option. Should flash successfully. Then reboot. I always keep spare ROM versions on my removable card for such emergencies. Also, keep a current ROMbackup there as well. Good luck.
Walknmemfs said:
I would first download a fresh version of a rom and the corresponding version of GAPPs and on your computer. Transfer you files onto you misco SD card via the SD card slot on the computer. Boot your phone into recovery and flash them from the /sdcard1 option. Should flash successfully. Then reboot. I always keep spare ROM versions on my removable card for such emergencies. Also, keep a current ROMbackup there as well. Good luck.
Click to expand...
Click to collapse
i tried doing this http://forum.xda-developers.com/showthread.php?t=2549068
but thats not working either. cant get the phone to do anything. wont come on in download mode, recovery...wont come on at all.
debrick
scorey03 said:
i tried doing this http://forum.xda-developers.com/showthread.php?t=2549068
but thats not working either. cant get the phone to do anything. wont come on in download mode, recovery...wont come on at all.
Click to expand...
Click to collapse
hey try another debrick image if you want i can email the one the worked for me,after going in download mode flash cyanogenmod 11 forget about downgrade or stock 4.3 you are stuck just like me your phone wont reboot without the sd card so you gona have to flash modem and bootloader manually here is wher to get it bootloader = http://www.androidfilehost.com/?fid=23212708291681451 modem= http://www.androidfilehost.com/?fid=23212708291681456 put both zip files in the internal storage rebot to recovery remove debrick sd card then flash both zip files wipe cache and dalvin and try to reboot it worked for me .
xjunior said:
hey try another debrick image if you want i can email the one the worked for me,after going in download mode flash cyanogenmod 11 forget about downgrade or stock 4.3 you are stuck just like me your phone wont reboot without the sd card so you gona have to flash modem and bootloader manually here is wher to get it bootloader = http://www.androidfilehost.com/?fid=23212708291681451 modem= http://www.androidfilehost.com/?fid=23212708291681456 put both zip files in the internal storage rebot to recovery remove debrick sd card then flash both zip files wipe cache and dalvin and try to reboot it worked for me .
Click to expand...
Click to collapse
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
image
scorey03 said:
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
Click to expand...
Click to collapse
download the image here and unzip it then burn with win32diskimager , drive.google.com/file/d/0B4b7I4izs-CwdWFUdFQ2YTNZSU0/edit?usp=sharing remove the battery put it back hold home power and volume down at the same time .
---------- Post added at 07:53 PM ---------- Previous post was at 07:32 PM ----------
scorey03 said:
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
Click to expand...
Click to collapse
assuming you have the [email protected] galaxy s3
download the image here and unzip it then burn with win32diskimager , drive.google.com/file/d/0B4b7I4izs-CwdWFUdFQ2YTNZSU0/edit?usp=sharing remove the battery put it back hold home power and volume down at the same time .it wont work for other models [email protected] only but the process is the same only need to find the right file for your phone.
that one didnt work either
scorey03 said:
that one didnt work either
Click to expand...
Click to collapse
It's kind of been a known issue since the day the OTA came out that downgrading the bootloader from the one that comes with 4.3 will hard brick your device. No known fix.

[Q]I can get into TWRP, can't reflash 4.3, hangs @ ATT logo.$5 Paypal if you can fix!

Hello all,
I flashed and rooted my SGIII about 6 months back using these threads
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showpost.php?p=47747640&postcount=1
Everything was running fine until Saturday, I noticed my phone kept shutting off in my pocket. Once i got home and started doing diagnostics, i couldn't really tell what caused it, i uninstalled the realtor.com app i had downloaded Saturday during the day just in case and wiped the cache of a bunch of apps I had before the problem started. The problem still exists, the phone will randomly flicker 3 or 4 times, the shutdown menu shows up then goes away, then it turns off and i have to boot it back up manually.
Anyone else had this issue?
It seems as though these threads come pretty frequently here lately, I am going to suggest a power button, it is a fairly common failure. On a good working phone if you push and hold the power button for 10 seconds it will turn the phone off, but not before popping up the power/reset menu.
Good luck hope you get it fixed quickly and perhaps I'm wrong?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Starting to think this is hardware related, i did a complete factory reset and same issue occurred. Now I have to take it back to stock and see if I have a case for a replacement.
Since i updated and rooted as I did, am I screwed?
now it seems to be soft bricked.. this is fun
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
audit13 said:
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
Click to expand...
Click to collapse
Yea I did, I'm currently searching how to do this process post-4.3 update
update: so i can get into TWRP just fine, cannot reflash 4.3 update, getting an error no MD5 file found, and "assert failed: apply_patch_check ("system/app/Bo.. it cuts off from there.. then says E:Error executing updater binary in zip
if i reboot it just hangs at the ATT logo
what I have done so far was backed up before this brick started, then factory reset, data and all cache, since the factory reset I haven't gotten past the ATT logo.
Not going to sleep tonight until this is solved, I know someone can help me since I can still get into TWRP
Was thinking of trying to ODIN back to 4.1.1 then flash 4.2 then flash 4.3 but I am pretty sure that will hard brick it right?
$5 paypal to whoever fixes this for me!
wellppp think i bricked it
serstylz2 said:
wellppp think i bricked it
Click to expand...
Click to collapse
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
JEdad26 said:
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Click to expand...
Click to collapse
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
serstylz2 said:
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
Click to expand...
Click to collapse
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
JEdad26 said:
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Also would have probably worked if I had any life at all from this thing. I think this was destined to break, I believe hardware failed.
It broke when I tried flashing d2att_I747UCUEMJ2_bootloader_modem after flashing boot_CWM_I747UCUEMJB
UPDATE: Able to get back into Download mode, TWRP and it still hangs at the ATT logo. Was able to do that by sticking a debrick dump img on my sd card and doing that method. Now I am trying to fully follow thru with that thread (http://forum.xda-developers.com/showthread.php?t=2549068) but I still have never seen a stock 4.3 that i can flash via ODIN, i asked them where I can find that. I may try these directions in the meantime (Also, I tried to update to TWRP 2.6.3.1 and ODIN froze on the checking .md5 step so, maybe that's the issue to begin with?)
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2a....3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/show...1&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Welp I'm finally back up.. here's what I had to do
First, had to get a debrick img from http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Then carried out these steps
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
booted to Recovery, then basically whipped through these steps
"You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below."
My original problem came when i removed the debrick SD and inserted the file SD, i wasn't mounting so i was confused for a min. Then the ROM i was trying to flash was the "update43" from the OTA 4.3 update thread, that does not work, ended up using the "almost Stock" from here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
And I was good after that. Basically I just went a long way to do what the tuts had already said to do, and the screen flickering is also gone along with the random reboots i was getting.
Very thankful for this forum and you all

Categories

Resources