Using UpdateMe on my GS3, I downloaded Free GS3 3.0 to my phone (I was running the previous version). Went into TWRP, installed it (backed up and wiped all caches and system before hand). Rebooted, and it worked fine. Then, I went back into TWRP to install a mod for the batter percentage indicator that I had previously used on the old version of Free GS3. Installed it, worked without a hitch. Except, now my phone won't boot. It flashes the samsung logo then the galaxy s3 logo, followed by blank screen. That's it. I think the problem is that my version of TWRP isn't the latest version (I couldnt' find out how to update it anywhere). Now, I have no idea what to do. Somebody please help, I just want to use my phone again.
Go back into recovery wipe cache and dalvik and reflash the rom. Do not use the mod again.
Sent from the future via Tapatalk 4
The problem is the mod. The MD4 update changed a lot of things, you're just gonna have to wait for Clark44 to update the battery mod.
Related
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).
Hi, all. Just like the title says. I'm stuck in a bootloop and not sure what to do.
TWRP 2.5
Went from Docs deodexed T999L ROM to SlimBean 2.2
then...
I was making a backup of SlimBean 2.2 on TWRP 2.5 I believe and that went fine. I then went to do a factory reset but it gave me some kind of error that data wasn't found or was found. It was all confusing to me. So I decided to upgrade to the latest TWRP 2.6.3.1 from Doc's signature (I think that was it). I rebooted into the new TWRP and when I went to do a factory reset, it rebooted constantly. So I went into recovery again, and I was able to clear, dalvik, cache, and system, but freezes and reboots when trying to clear data.
Stupid me, I then flashed TWRP 2.5 again, and now I can't get into the recovery settings. It was show the blue TeamWin logo, but then reboots, shows the Galaxy S3 T999L logo, then the SlimBean boot screen, then reboots, repeating this over and over again.
So basically I have no working custom recovery, no operating system, but I can get into download mode.
Not exactly sure where to go from here. I rooted using the recovery method about a month or so ago. Do you think I can just go through the root process and flash TWRP 2.6.3.1 from Odin?
Thanks in advance!
Edit:
A little bit more, I was running Stock 4.1.2 before the rooting process and never did the official 4.3 update.
Also, in Doc's T999L info thread, could I essentially just revert back to stock using Odin? Or will my non-wiped data be a problem?
Aha! Never mind, everyone. I looked more into it and reverted back to stock using Root66 in Doc's thread.
Anyway, hope this helps anyone in the future if you come across this.
Have a good holiday, yall!
Edit:
So good news bad news, I could finally boot into TWRP 6.2.3.1, but doing a factory reset I still got this: "error: opening data/lost+found"
So I ended up formatting the data. All is well now and that error doesn't show up anymore.
Hope this helps!
Hey guys,
I was running liquid smooth ROM along with Agni kernel. Some of the apps were FC so I wanted to refresh the ROM by wiping and flashing it back. I mistenly hit softreboot instead of recovery. The phone got stuck on the loading liquidrom screen forever.
Went into recovery, made a backup, wiped everything out. Restored the backup.. still stucked on loading screen.
Went back into recovery, wipe everything, I mean everything, even external SD.
When a came to boot the phone, recovery told me there was no ROM installed.. duh!
So I grabbed the stock firmware from sammobiles and went with Odin to flash it. But I'm getting stock on NAND write start. I tried a second computer, with lastest Kies installed. Same stuff.
Is there a reason why the stock firmware just won't flash?
I'm gonna need help on this one cause I'm out of ideas.
Thank you
DanKicker said:
Hey guys,
I was running liquid smooth ROM along with Agni kernel. Some of the apps were FC so I wanted to refresh the ROM by wiping and flashing it back. I mistenly hit softreboot instead of recovery. The phone got stuck on the loading liquidrom screen forever.
Went into recovery, made a backup, wiped everything out. Restored the backup.. still stucked on loading screen.
Went back into recovery, wipe everything, I mean everything, even external SD.
When a came to boot the phone, recovery told me there was no ROM installed.. duh!
So I grabbed the stock firmware from sammobiles and went with Odin to flash it. But I'm getting stock on NAND write start. I tried a second computer, with lastest Kies installed. Same stuff.
Is there a reason why the stock firmware just won't flash?
I'm gonna need help on this one cause I'm out of ideas.
Thank you
Click to expand...
Click to collapse
Please see this thread I started yesterday: http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page1. Many of us are having the same issue, and I was able to fix my Android last night.
Please spread the word.
Do anyone know what to do here. I got a note 2 from my aunt for fixing her S6, I figured I would use this as an extra device to play around with but I absolutely HATE TouchWiz so I wanted to put CM12.1 on it, now I've done this probably thousands of times before, this phone is screwed, I can't figure out why. Even on my old Note 2 it worked, can't get this working, no idea why.
My aunt has done all the OTA updates since she bought it brand new so it was running 4.2.2 DNF4, I did a system restore to get rid of all her stuff, once it booted to the welcome screen to set it up I rebooted into download mode, used odin to flash the latest twrp, all good, wiped the phone, flash the latest cm12.1 nightly and latest opengapps, wipe dalvik, reboot, reboots back into twrp, nothing I can do, I tried this a few times with different builds and even different roms, nothing works, twrp is screwed and will not let me leave once it boots, I have to pull the battery.
So I flashed back to stock touchwiz 4.4.2, rebooted back to download, flashed CMR, figured it must work better since it's right on the download page for CM12.1, wipe it, flash the files, reboot, stuck in a boot loop at the cyanogenmod face, sits there for hours, nothing happens.
Tried the exact process using cwm and philz, nothing works, I literally can't flash anything AOSP, I've tried other roms and only stock touchwiz will boot past the boot screen, and stock touchwiz has no problem running if I run CMR, CWM, or Philz, but TWRP doesn't work on anything, it will not let me leave if I boot into recovery unless I pull the battery and let it boot normal.
Any ideas at all? I'm getting completely fed up with this phone and I'm going to throw it in the garbage if I can't figure this out, I've wasted the same amount of time that if I spent this much time at work, I could have bought a used Nexus 5 by now lol
I used DN3, U HAVE TO WIPE 3X WITH OLDER TWRP, FLASH PHILZ, dont WIPE , THEN INSTALL ROM.ITS ALL REALLY A PAIN.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
How old are we talking for TWRP? As in a different version of 2.8.x or like 2.7.x or maybe even 2.6.x?
EDIT:
I followed your instructions and that actually worked.. I used the latest TWRP for 2.7 which was 2.7.1, I'm going to play with this a little more tomorrow and see what the latest version of twrp is that I can use without getting stuck in a boot loop, thanks a lot for that info.
The only issue I've run into now is I got Error 12 while trying to flash GAPPS so currently there are no GAPPS installed.
Glad you're running. GAPPS very touchy on some roms, Go to ROM thread for that stuff.
I'm just running regular untouched CM12.1 nightlies, any GAPPS should work but the recovery is telling me it's out of date and can't use it stbin or something like that?
However, I found out that once CM12.1 is installed, and before it's set up, I can reboot back into download, flash with odin TWRP 2.8.5 which is the newest I've found that works. and it will let me flash the latest GAPPS, the phone still boots back to the setup/welcome screen, and then I can set it all up as if everything was fine.
It's quite the work around but at least I was able to get it all working.
I also tested this again using DNF4 and it also works using this twrp to wipe and philz to flash method.
Thanks again.