Related
I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?
rrhutch said:
I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?
Click to expand...
Click to collapse
i have the same problm :crying:
Need more info than that.
For example... Are you rooted or stock?
If rooted, there are a couple of reasons off hand I can think of you could be having a problem.
If you're stock, well... All I can think of is wave your hands in the air, and wave them like you just don't care. Pretty sure that won't fix the problem though, but if it does, report back! xD
I'm rooted.
Sent from my DROID RAZR using xda app-developers app
exactly the same problem
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
I'm in the same situation.
I'm going to try http://forum.xda-developers.com/showthread.php?t=1849994
when I get home tonight to see if this fixes it.
Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
ytdong said:
Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
Click to expand...
Click to collapse
you should've sync your snote data with drive or dropbox!!! any firmware update 101 is to back up all your data
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.
Thank you! but I've been on stock recovery so I never flashed cwm or made a cwm backup. How can I restore to a backup after I flash the cwm recovery?
Nefariouss said:
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.
Click to expand...
Click to collapse
if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it
Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
khanh1289 said:
if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it
Click to expand...
Click to collapse
ytdong said:
Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
Click to expand...
Click to collapse
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
This worked for me as well. Thanks a lot, Vincent9756!:good:
Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse
Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse
Worked for me. Thanks!
rrhutch said:
Worked for me. Thanks!
Click to expand...
Click to collapse
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?
Kikoshi said:
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?
Click to expand...
Click to collapse
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.
Z a p i x said:
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.
Click to expand...
Click to collapse
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!
Kikoshi said:
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!
Click to expand...
Click to collapse
Yeah, there will most certainly be kernel and recovery uploads.
the only issue you might run into is CWM not sticking. If it doesn't reflash CWM in ODIN with reboot unchecked. Then after you flash it, boot into CWM. When you select reboot, it should offer to prevent stock recovery from replacing it.
and you're welcome, glad to help
Guys u might think this is a dumb question but how do i flash stock recovery with odin like were do insert the file i know how tp put in dl mode and get my comp to see my tab in odin and i did flash the prerooted injected stock uealgb recovery to get root i just dont know were to put the files in odin some help would be greatly appreciated, cause i need to flash this first before i do the ota update correct ? If not i will bootloop ? So rootkeeper alows me to keep root acess after ota? Thanks guys
Sent from my GT-N8013 using xda app-developers app / jelly powered samsung infuse 4g
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update? Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
tylerlawhon said:
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update?
Click to expand...
Click to collapse
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
Click to expand...
Click to collapse
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
I'll check my wife's phone tonight. If she gets the ota I will pull it from the cache and extract the boot loader and recovery and rezip it and see if it will flash via twrp
SlimSnoopOS said:
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
Click to expand...
Click to collapse
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
tylerlawhon said:
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
Click to expand...
Click to collapse
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
SlimSnoopOS said:
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
Click to expand...
Click to collapse
Hmmm sounds interesting. I doubt I'd be able to use EZ unlock like I did on ICS... I guess I'll wait for a recovery flashable file.
What OTA?
cammykool said:
What OTA?
Click to expand...
Click to collapse
4.1.2 ota being pushed starting today. According to Google+
Is this basically the same thing as the VRBMA2 leak?
pettigrew95 said:
Is this basically the same thing as the VRBMA2 leak?
Click to expand...
Click to collapse
Yes, it's a final version of VRBMA2 leak which is VRBMB1
Damn.... on the day i root... oh well glad i did!
vzw probably blocked our current methods.
The OTA de-odexed is already posted courtesy of beanstown over here:
http://forum.xda-developers.com/showthread.php?t=2177798
I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.
lexluthor said:
I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.
Click to expand...
Click to collapse
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798
pettigrew95 said:
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798
Click to expand...
Click to collapse
I'd rather have the odex version though. You think someone will post that?
OK I took it from cache. Does anyone remember what all I need to delete after I extract it so it doesn't update boot loader. Recovery for sure...here's where I am before i rezip
Razr HD Maxx on Verizon.
I am rooted, unlocked bootloader, Team Win recovery, stock OS.
3 times I attempted to install the latest update (9.18.79.en.US). Each time it reboots into Team Win recovery. I then reboot the system and once the desktop loads, it reboots immediately into Team Win recovery. I can never get into the OS anymore because it immediately displays "Powering off" and loads the Team Win recovery screen. So, each of the 3 times I attempted to install, I ended up reverting back to my backup.
What am I doing wrong? Do I need to remove Team Win? Is the update not compatible with my current setup? Or, do I need to do it manually? i.e. download the update and install it using Team Win recovery.
Thoughts? Thank you in advance for reading and attempting a resolution. If I end up figuring it out, I'll post an update. :good:
Fix for Reboots
Too Fix Just go on Teamwin Recovery and select wipe Data>Advance Wipe Data> and only wipe cache and dalvik cache..
that should fix y;our reboots..
as for the update.... no sure yet
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
thanks to both responses.
quick update: i located the downloaded update via /cache. i attempted to install it when TWRP came up. "Failed". I wiped cache/dalvik, and that did not work either. It fixed the boot problem initially, but then it just prompted for the update again and the reboot cycle repeated. except I was in a factory state with my apps. (i.e. i had to go through the initial prompts of setting up my phone.)
So, I will attempt to do the following:
deeje00 said:
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
and see what happens.
Thanks again.
Installing new Razr HD Verizon update
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Andrewl62 said:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Mr-Glass said:
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I have stock recovery on my phone, re-enabled/unfroze all stock apps, temp unrooted with voodoo and it still won't install
Any thoughts?
woodjc01 said:
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
Click to expand...
Click to collapse
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
Your welcome. Glad I could help.
forgot to give an update. i got the update to work with the stock recovery. i'm on newest stock os build with unlocked bootloader, root, and stock recovery. :good:
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
My update failed to install as well. I'm rooted but NOT unlocked. Can someone point me in the right direction regarding how to restore bloatware apps? I made the rookie mistake of completely removing some of them a while back. I sincerely apologize if a solution has been posted already, as I was not able to find one so far.
s_u_n said:
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
Click to expand...
Click to collapse
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
iBolski said:
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
Click to expand...
Click to collapse
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
s_u_n said:
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
Click to expand...
Click to collapse
But that's what this OTA was - the 4.4 upgrade. I guess I'm a little confused on what you were asking exactly.
Glad you are on KK now, though. And, you can go back to JB if you want to since your bootloader is unlocked.
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk
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.