Hey everyone so I took my phone out of my pocket and it was stuck in a boot loop. I tried taking the battery out, volume up + power + home, volume down + power + home but nothing. I've tried booting it also without a battery.
I have Quantum running on my phone, and have never had any problems. The occasional restart but now my phone won't even get to the home screen. I get just a boot loop with normal sounds, and then my LED begins to flash. Then it just loops again ..
Don't really know what to do.
UPDATE: Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
DELETED - irrelevant information.
StoneyJSG said:
DELETED
Click to expand...
Click to collapse
Why ?
Rovon said:
Why ?
Click to expand...
Click to collapse
Will your computer detect it if connected? (Odin, Heimdall, adb)
dawgdoc said:
Will your computer detect it if connected? (Odin, Heimdall, adb)
Click to expand...
Click to collapse
Yes computer is detecting it with Odin.
Rovon said:
Yes computer is detecting it with Odin.
Click to expand...
Click to collapse
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
dawgdoc said:
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
Click to expand...
Click to collapse
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Rovon said:
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Click to expand...
Click to collapse
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Rovon said:
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Click to expand...
Click to collapse
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
jason2678 said:
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
Click to expand...
Click to collapse
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Rovon said:
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Click to expand...
Click to collapse
So I keep getting a bunch of errors with TWR. I tried installing AOKP but got stuck at a boot screen again, and after trying to wipe my phone I get an error message saying "Failed". Now I'm trying install Quantum again but get an error message saying "Zip file is corrupt". T__T
Going to try another rom..
Update: I've tried Quantum again and it finally installed but now I'm stuck in a bootloop again. This is so frustrating ...
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
dawgdoc said:
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
Click to expand...
Click to collapse
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Rovon said:
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Click to expand...
Click to collapse
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
dawgdoc said:
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
Click to expand...
Click to collapse
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Rovon said:
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Click to expand...
Click to collapse
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
mrrocketdog said:
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Hmm .. that command didn't seem to pull anything up for me.
Rovon said:
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
Hmm .. that command didn't seem to pull anything up for me.
Click to expand...
Click to collapse
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
jason2678 said:
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
Click to expand...
Click to collapse
Alright I'm downloading this now. Assuming this works, should I do an OTA update then root or am I safe to root the device from odin as soon as this bootloader is installed?
Related
Hello. First post because I'm usually pretty good at finding solutions to my problems just searching. I can't find the solution to my current issue and I hope you fine folks can give me some advice.
Issue arose while clean flashing my d2att to the most recent Task650 AOKP build using the latest TWRP. Did my nandroid to internal sd like usual, factory reset, and format system. Done this 100 times with no issues. This time, TWRP crashed while formatting system and phone vibrates, reboots, hangs on the new kernel splash screen for Task650s Rom. Pull the battery, replace, then boot recovery with the volume home power method. TWRP splash screen shows, screen goes black, vibrates twice, then reboots back into previously mentioned kernel splash and hangs.
So I can't boot recovery and I can't boot my phone. I enter download mode and try to Odin the most recent twrp tar. Same. I try a previous twrp tar. Same.
I think I can use a rooted stock image to get back up and running, but I don't want to lose the contents of my internal sd.
How can I fix this with minimal data loss? Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
CZ Eddie said:
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
Click to expand...
Click to collapse
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
GhastlyTT said:
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
Click to expand...
Click to collapse
Odin won't delete /data only a factory reset in stock recovery will
Hello, I have a rogers i747 and I installed the newest CM build today and my internal storage would no longer show up. Afterwards I tried to use a recovery in TWRP and now my phone won't install data or system from any files that I try to flash. The phone will go into recovery mode and it will also go into downloading mode but I have no idea what to do. I can't seem to use any of my recoveries or even flash a new ROM onto the phone.
..
Are you entirely sure internal storage is gone? If you didn't know, the storage is nested into an emulate /0 folder. If you can get the phone to boot go ahead and look around in File Manager or Root Explorer for that folder. Everything you had on internal storage should be located there.
Onto the crazier things you're mentioning...
You should only have one "recovery". Unless of course you mean to say backups that you've saved in the event something goes wrong. Unfortunately with some recoveries the blob files for the backup stack up over time and get too large to be restored. I think updating the recovery might fix that, but I never had to mess with any of that stuff. I usually ended up returning to completely stock software to fix the issues I had the first few times I caught problems no amount of wiping would fix.
Before you do anything crazy go ahead and boot into recovery (hold volume up + home button + power until you see the samsung logo and it boots into twrp or cwm depending on what you're using), clear cache, clear dalvik cache in advanced and then reboot system now. Some issues are taken care of by that, some aren't.
Failing that, try a full wipe of your phone and reflashing the ROM assuming your files haven't been corrupted/deleted somehow.
If that doesn't work you'll need to use Odin or Kies or whatever to return to completely stock and reroot and all that nonsense.
Good luck.
I ended up having to flash a stock rom with Odin and it ended up working again. Not sure what happened but none of my backups would load and the phone was saying that storage was in use but the files weren't accessible and the backups wouldn't write to the internal storage they would say successful but do nothing. If I install twrp and try to flash cm again is there a chance that this same issue will occur again? And does anyone have an idea of why this occurred in the first place? I have never had an issue flashing between roms or using recoveries in the past. Just afraid of permanently bricking my phone at this point by installing a custom rom again. Never had issues before the new cm.
Sent from my SGH-I747M using xda app-developers app
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
DroidJay123 said:
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
Click to expand...
Click to collapse
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Mr.Rageface said:
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Click to expand...
Click to collapse
Yes it is recognized once in Download mode...sorry about that. What can I do to get it up and running? I am not new to flashing, etc so it's got me really upset that I cant get it to boot. What could possibly go wrong?
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
http://fs1.d-h.st/download/00023/E5R/I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 You can download that file and put it in the PDA section once you run Odin and run it from there. This will put your phone back to the Stock Rom 4.1.1 and you can restart from there if you want.
Mr. Rageface
xXFl4sh said:
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
Click to expand...
Click to collapse
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
DroidJay123 said:
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
Click to expand...
Click to collapse
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Mr.Rageface said:
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Click to expand...
Click to collapse
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
DroidJay123 said:
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
Click to expand...
Click to collapse
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Mr.Rageface said:
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Click to expand...
Click to collapse
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
DroidJay123 said:
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
Click to expand...
Click to collapse
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Mr.Rageface said:
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Click to expand...
Click to collapse
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
DroidJay123 said:
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
Click to expand...
Click to collapse
BTW, how can I confirm I have the most recent bootloader version? It looks like my phone's current baseband version is i747UCDLK3. I did download the boot_CWM_i747UCDMG2.zip file and put it on the internal storage. Do I just want to flash that file to update my bootloader?
Thanks again!
-Jay
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Mr.Rageface said:
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Click to expand...
Click to collapse
Thanks for the information. The phone that has been all screwed up and the reason I posted a thread in the first place is my gf's GS3. I have her's rooted again and running. I am going to update her baseband version and then install a custom ROM so she's up to 4.3.1. As far as mine goes, I have been fine. I myself also still have the outdated bootloader version. Is it ok to just flash that update for the bootloader without it doing anything wrong? I'm asking this since I'm rooted and running a custom ROM with no current problems. In other words, I don't want to end up saying "it wasn't broke, why did I mess with it" ? I did bookmark that thread you referenced in your last message. Damn that thread is LOADED with just about everything one would possibly need to know about Android and making it their own.
So my g/f accepted the OTA update today (not knowing obviously) and she got updated to 4.3 via AT&T, unfortunately!! I attempted to flash the latest Liquid Smooth ROM and I continue to get a FAILED message during installation. It mentions a bunch of bootloader numbers ( I am assuming the only ones this ROM is compatible with?) So is there any way to roll the bootloader back to a compatible one or just go a different route for the custom ROM?
Also, I attempted flashing the file to update my baseband yet when I so into the device, it doesn't show as having the updated version? Is there a different way of doing it or maybe a different file?
I'm not to sure about the troubles that may come about since your gf went with the 4.3 OTA but If I am not mistaken it will need to be downgraded before you try doing anything else to it and if it is not showing that you updated your bootloader on your phone I recommend grabbing the App called Root Checker to double check then look for another file, tho unless it failed it should have updated it or messed up your phone one.
First Yes i have searched and i found several posts but none had enough information or ended up with directing the op to the de-brick thread I feel its not bricked and I don't want to run into more problems.
Here is how it goes down
using 4.2.1 Rom
using CWRM 6.0.3.1
I tried to encrypt my phone (don't ask me why as if i could go back in time i wouldn't have tried it)
So first it would only boot to the screen that says encryption failed factory reset and try to encrypt again and has a restart button at first nothing worked even the Rom UI would crash at this point and the restart (software button) on the screen was unresponsive. I then went into recovery and tried to load a recovery and it could not mount /data as it read as it was secured. So i went and formatted it and was successful with restoring a backup Although as soon as it booted again it brought me right to that same screen?
I am going to try to start over with a new Rom installation while i wait for a reply.
I just hope i can get it done simply without Odin or connecting it to my PC as i tend to not have good luck with that. IDK whats up with my PC.
Anyway if a simple Rom install fixes it ill be happy but something is still there saying i want to encrypt it or IDK what is causing it to go to the encryption failed page when I have formatted all but /sdcard (i was afraid to unless I'm told) I know everything else is fine /system /data /cache are all replaced by the Rom so i know its OK to format them but /sdcard is all the data on the phone so I'm not afraid of losing music ringtones pictures etc if i do need to format /sdcard but i want to be told i should first
also please ask me for any in formation you may need i want to fix this and also i need to go find a Rom so also a Rom suggestion is fine too (if its going to help otherwise I'm going to find a basic 4.2.1 Touchwiz based Rom and flash that
Please Flash UVDMD5 version of Root66 via Odin.
Perseus71 said:
Please Flash UVDMD5 version of Root66 via Odin.
Click to expand...
Click to collapse
THANKS I tried flashing a fresh ROM after formatting everything now im in a boot loop and as it not bricked (soft bricked anyway) i was hoping a new route66 via Odin would be my main option.
Now as far as it goes on updating to 4.3 what file should i flash via Odin? should i use T999_UVDMD5 to get it working again then use T999_UVUEMJC to update to 4.3 (how i went from ICS to JB so would it be the same to KK ,4.3,) or can i just do a single Odin to T99_UVUEMJC so I u can be ready to use 4.3 roms. I just want to make sure because if I don't' have to use a 4.13 route 66 ROM to com back from this boot loop can I skip the step of using Odin to UN soft brick my 4.1.2 and go straight to 4.3.
I just want to know the best way to go about eventually being able to load 4.3 roms on this phone more because they are easier to find (as in more developed at this time) and to be update
I appreciate all your help and in case any ROM devs are reading this I love your work each and every one of you make this place better i wish i had the (first smarts) and second the time to mod for myself but over the years you guys are just awesome and i wish i was at any of your levels (all who post or even mod for themselves) as if i knew what you did i would not be in the predicament either and if i can fix it i will be pleased with myself as i bet most or all devs could fix this issue in 5-10 min where you can see Ive been at it days! Thanks in advance for any future help and most of all so far thank to you Perseus71 for helping me start
Never EVER flash UVUEMJC. Let's first get you back working with UVDMD5. Once that's achieved, I will get you 4.3 by another way.
For now, If you are right now on that bootloop/softbrick with just the UVDMD5, then great. If not go back to recovery, factory reset and wipe the cache and Re-flash UVDMD5 via Odin. This time, in Odin, make sure to uncheck Auto Reboot.
Once Odin has succeeded, Flash a custom Recovery such as TWRP via Odin. After that is done, reboot to recovery. Wipe Dalvik and Cache and then reboot normal.
[Q] Encryption Unsuccessful (Android 4.1)
I have partitioned my phone incorrectly. Phone is asking for a reset..
I deleted the /data and /sdcard because I formatted the internal storage and every time I reboot, I get a Encryption Unsuccessful message and it tells me to reset phone. I did but same message. What should I do??
Here's my phone: Cherry Mobile Omega HD (IQ6A) / Xolo A1000 / Alps H100
Android JB, Custom ROM, Rooted, TWRP
5"
8Gb External
Wrong Device forum Bud.
Hi, I have been trying to flash a new ROM to my Note II.
It was on Official Stock 4.3 ROM and I flashed succesfully another 4.3 ROM based on stock with some Note 3 features using Philipz Touch.
Then I switch Philipz to TWRP in order to install DN3 V4 ROM and I made the wipes and format /data and I start flashing the ROM, and since that moment It stucks on the first screen.
When I try to flash a stock 4.3 ROM using Odin, It seems to flash correctly, but when I try to boot, it stucks again.
I can enter to recovery and download mode, I can install some ROMS using TWRP but when it finishes it shows "Unable to mount /data" and if I try to boot, It always stucks on fisrt screen.
I hope you can help me.
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Still the same
biokiller said:
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Click to expand...
Click to collapse
I really appreciate your help, but I can't fix the problem yet.
With CWM I can't make a factory reset, when I try to make it, it restarts the phone and it stuks on the first screen.
I have flashed stock ROMS with odin and it says PASS but when the phone boots It always stucks on the first screen.
Fear not.
I am fairly confident this will work, but read the whole post first
You tick erase all nand as well as the usual two options. Then boot into recovery (should give warnings about unmountable /data) and wipe data / factory reset. Then reboot and it should work / odin a stock rom as normal.
If that doesnt work / or instead you get the correct pit file and flash it as well as the rom and have four options ticked: pit, erase all nand + normal two.
If someone gave me their phone with the same symptoms as yours and said: fix it right now that's what I'd do. I'd also warn them I really need to do more research before doing this and using these two options in odin could brick the phone forever.
I hope this gives you lines of inquiry. I found many mixed messages with the erase nand option, most said nothing of merit except don't do it, some said you must wipe data first (which u can't), some said exactly what I've repeated, some say a pit is enough, others had many steps and files ive never heard of to solve the same issue. There is a large thread in the S3 forum about this, even got mentioned on xda proper. My brief cookie crumbs journey did not return any note 2 threads.
Remember one thing, before using odin, double check every detail. Battery, cable being used, files being used (right ones, md5s), right options ticked, computer is in good health, internet is off, Kies is not running. (I'm sure ive missed some)
Solved
I install again the stock kit Kat firmware and the problem was the same, but this time I boot stock recovery and there I made factory reset and that's it. Problem solved and Note boot normally.
Thanks for your help
With or without erase nand in odin?
No, I just flashed normally as all the stock firmwares
I see, thought you'd rule that out. Disappointing really. Glad ur sorted anyway. Remeber wiping data is important when changing roms, even if it's not always absolutely necessary.
Did you try TWRP or Philztouch ? Did you flash 4.3 stock rom?
Sent from my GT-N7100 using Tapatalk