ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app
Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.
resolved. thanks guys.
Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.
jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.
The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.
Related
I was running Xylon and decided to download DLHacker's latest CM10.2. I backup up Xylon, wiped system, data, cache & dalvik and installed the the 8-13 build as well as the 8-12 gapps. First boot seemed to go okay but the keyboard kept force closing to the point that I could not complete the set-up. I forced a reboot, got back into TWRP and wiped cache & dalvik and fixed permissions. Now it hangs at the splash screen, doesn't boot loop, just hangs. So I got back into recovery, wiped system, data, cache & dalvik and restored my Xylon backup. Still hangs on the splash screen, doesn't boot loop, just hangs. I go back into recovery and wipe everything again and try to install an older build of Rage HD (4.1.2) and it reboots recovery everytime I try to install it.
I am currently installing the CM10.2 build and am going to use the 3-1 gapps I have on the sd and see if that makes any difference.
Any help would be greatly appreciated as looking now it seems like that combo is hanging on the splash screen too.
I experienced something similar when flashing CM 10.2. I ended up fastbooting back to stock.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
I experienced something similar when flashing CM 10.2. I ended up fastbooting back to stock.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I think that's what is going to have to happen, can't do that from my work computer though, guess I'm phoneless for the day. That means no Freebeer & Hotwings podcast and no music. Oh well, that's why they call it the bleeding edge, sometimes ya get cut.
I plan to install the latest firmware through RSDLite when I get home, does anyone know if there an issue with installing the MR4 (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC) when I'm unlocked? Will I have any issue re-rooting or anything like that if I install the latest firmware rather than an earlier one? I never recieved MR4 OTA because I was no longer stock when it was pushed.
animez said:
I plan to install the latest firmware through RSDLite when I get home, does anyone know if there an issue with installing the MR4 (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC) when I'm unlocked? Will I have any issue re-rooting or anything like that if I install the latest firmware rather than an earlier one? I never recieved MR4 OTA because I was no longer stock when it was pushed.
Click to expand...
Click to collapse
There wont be an issue because you are unlocked. AFIK you cant root the newest firmware. If I were you id flash the last OTA that can be rooted, root it, use a root keeper such as voodoo to back it up, take the latest OTA, then restore root with the root keeper you used.
mentose457 said:
There wont be an issue because you are unlocked. AFIK you cant root the newest firmware. If I were you id flash the last OTA that can be rooted, root it, use a root keeper such as voodoo to back it up, take the latest OTA, then restore root with the root keeper you used.
Click to expand...
Click to collapse
I'll have to do a bit of research before I pull the trigger. I'm pretty sure the first 4.1.2 VZW pushed can be rooted...
To the root threadz!
You are correct. The first 4.1.2 was rootable. You could use the Droid Utility 2.0 to restore that version and root.
Sent from my DROID RAZR HD using Tapatalk 4
Finally got things fixed. I tried through rsd lite, but it kept failing. Downloaded one of the utilities and it seemed to work, but still hung on the splash screen. So after downloading a few other factory images which also failed to flash, I saw the problem. Somehow I had downloaded rsd lite 5.6. *facepalm* Probably stay stock for a little bit, thanks for the help.
Sent from my DROID RAZR HD using Tapatalk 2
My father has a Skyrocket and he didn't like how slow and clunky it was from stock, so I decided to flash a ROM that I knew well and would make his phone a more enjoyable experience. I flashed TWRP, put Carbon ROM (latest nightly) and the latest 4.3 Gapps on his SD Card, and flashed. Keep in mind I wiped data, dalvik, cache, and system before I flashed anything. Everything went well, phone booted, I got it configured and installed most of the apps he likes to use and it was good to go. A while earlier, I rebooted the phone normally, not into recovery or bootloader, just a normal reboot. The phone shut off, buzzed, and wouldn't come back to life. Pulling battery, button combinations, it would only go to the Battery Icon screen. PC wouldn't recognize, etc. Managed to get it into Odin, flashed stock, it hung at Samsung screen so I had to wipe data in stock recovery. It is running fine now on stock 4.1.2 but I'm really scratching my head at why a simple reboot soft bricked his phone. Used TWRP 2.6.0.0 btw.
That recovery is old to begin with. Second, 4.3 isn't the most stable right now
Sent from my HTC One using Tapatalk 4
Yea, use twrp 2.6.3.0. If you want 4.3 cm 10.2 is working pretty well right now.
Agreed, this is 100% because you used TWRP 2.6.0.0. 2.6.0.3 is the minimum required version for and 4.3 based ROM, and as mentioned 2.6.3.0 is the latest official release.
Thank you all very much. It didn't even cross my mind that the recovery version could be the issue. I guess I might try again later on the newest TWRP.
Sent from my MB886 using xda app-developers app
I have recently had a similar issue with a 4.3 ROM, and I am using 2.6.0.3. Only I could get into recovery after a battery pull and button combo. I just kept following the same steps of wiping flashing and it eventually it took and is running fine now(just jinxed myself I am sure).
Ok so I have quite a strange problem. Whenever I try to reboot my phone, either from holding the power button and choosing the "reboot" option on the screen, or by turning the phone off physically, and then turning it back on, my phone does not boot. When I try to turn it on, it shows the Samsung image, and then the screen turns black and nothing happens afterwards. The only way I found around this, is that I have to put my phone into recovery and then do a factory reset.
Currently, I'm running BeanStalk v4.3.1009, but I've also flashed the latest version of Slimbean and the samething happens. I used Odin to flash back into the stock Rogers GB firmware and I've gotten the phone to successfully reboot.
I then flashed Beanstalk and I was again unable to successfully reboot the phone.
Any ideas what's going on? I'm using TWRP v2.5 and then updated to v2.6 after going back to the original Rogers GB firmware, if that matters.
bluecrush69 said:
I'm using TWRP v2.5
Click to expand...
Click to collapse
This is the problem.
Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.
bluecrush69 said:
Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.
Click to expand...
Click to collapse
Flash it once with cwm. That'll clear things up then you can go back to twrp
jd1639 said:
Flash it once with cwm. That'll clear things up then you can go back to twrp
Click to expand...
Click to collapse
Can someone explain what's technically wrong with twrp 2.6.3 I've flashed a ton of these 4.3 Roms without issue. Why is everyone saying it's bad?
Sent from my XT1080 using Tapatalk
I'm running into an issue. I have at&t skyrocket (i727). I am trying to flash a rom but every time to try, it aborts. There's a message that says, "This package is for sch-i727 devices; this is a hercules"
Any advice on how to proceed?
thanks in advance.
Are you sure you don't have a t989?
jd1639 said:
Are you sure you don't have a t989?
Click to expand...
Click to collapse
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.
cov3nant said:
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.
Click to expand...
Click to collapse
In settings, about phone what model numbers shows up?
jd1639 said:
In settings, about phone what model numbers shows up?
Click to expand...
Click to collapse
If i recall, it says sch-i727 but i am having trouble restoring my backup.
cov3nant said:
If i recall, it says sch-i727 but i am having trouble restoring my backup.
Click to expand...
Click to collapse
Model says i727. I restored original stock firmware via Odin.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Same Problem
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727
swapnilps said:
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727
Click to expand...
Click to collapse
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!
Done!
FriedrichEngels said:
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!
Click to expand...
Click to collapse
Tried with latest recovery!!!
..and done!
Failed to upgrade my tab, GT-P5113, from 4.2.2 to 4.4.2 using either Omni or CM11 rom. The error indicated my device is espressor10wifi and new rom are either for espressor10rf or espressor10rfxx. How do I change to either RF or RFXXX? TIA.
hvn4179 said:
Failed to upgrade my tab, GT-P5113, from 4.2.2 to 4.4.2 using either Omni or CM11 rom. The error indicated my device is espressor10wifi and new rom are either for espressor10rf or espressor10rfxx. How do I change to either RF or RFXXX? TIA.
Click to expand...
Click to collapse
update your recovery to the latest from here: http://forum.xda-developers.com/showthread.php?t=2548476 then go here:http://forum.xda-developers.com/showthread.php?t=2571498 and follow OP directions. Report back accordingly
CSP III said:
update your recovery to the latest from here: http://forum.xda-developers.com/showthread.php?t=2548476 then go here:http://forum.xda-developers.com/showthread.php?t=2571498 and follow OP directions. Report back accordingly
Click to expand...
Click to collapse
I have a p5110. Every 4.4.2 rom I try to install I only get to the boot screen. Does it tak a long time for it to boot up the first time? Now that I tried 4.4.2 I can only revert back to a few different roms mainly CM9 and AKOP 4.1.1. No sure what I am doing wrong when I am following all the step other than just not being patient enough for it to start up. I've let it try to boot for at least 5 minutes though.
btbarr16 said:
I have a p5110. Every 4.4.2 rom I try to install I only get to the boot screen. Does it tak a long time for it to boot up the first time? Now that I tried 4.4.2 I can only revert back to a few different roms mainly CM9 and AKOP 4.1.1. No sure what I am doing wrong when I am following all the step other than just not being patient enough for it to start up. I've let it try to boot for at least 5 minutes though.
Click to expand...
Click to collapse
Not too long. Couple minutes max. You sure you are using the latest update recovery, whether it be TWRP, CWM or Philz. has to be the latest for KK Roms
CSP III said:
Not too long. Couple minutes max. You sure you are using the latest update recovery, whether it be TWRP, CWM or Philz. has to be the latest for KK Roms[/QUOTE
I'm using CWM 6.0.4.7. I used to have CM10 working on it, but now I can't even go back to that.
Click to expand...
Click to collapse
btbarr16 said:
CSP III said:
Not too long. Couple minutes max. You sure you are using the latest update recovery, whether it be TWRP, CWM or Philz. has to be the latest for KK Roms[/QUOTE
I'm using CWM 6.0.4.7. I used to have CM10 working on it, but now I can't even go back to that.
Click to expand...
Click to collapse
I dont believe (i could be wrong mind you) that you can restore previous recovery back up from updated recovery. You should just back up your apps with Titanium Backup, move the whole folder to a safe place (ie: computer) Odin back to stock and work up from there. Then put your Titanium folder back and restore user apps only. Good luck
Click to expand...
Click to collapse
btbarr16 said:
CSP III said:
Not too long. Couple minutes max. You sure you are using the latest update recovery, whether it be TWRP, CWM or Philz. has to be the latest for KK Roms[/QUOTE
I'm using CWM 6.0.4.7. I used to have CM10 working on it, but now I can't even go back to that.
Click to expand...
Click to collapse
you have to update your recovery. so that u can flash these kitkat roms... i found the recovery here: http://forum.xda-developers.com/showthread.php?t=2548257
Click to expand...
Click to collapse
Pay attention that the correct recovery is been used. It happened to me, I had a p5500 recovery on my p5113 and ran into the same issue.
Pp .
sent from my P5113 using TouchPal mind control keyboard.