[Q] Only LTE and can't get recovery - Verizon Samsung Galaxy S III

A while back I flashed cm10 but the data wasn't working and I went back to stock through odin. Since then I have only been able to get 4g lte and receive texts, I can't send texts and can't call. I lose data when ever I go out of verizon lte range. I also can't root it like I had been able to before. This is because I can't get into recovery. I tried to flash cwm through odin, but when I try to go into recovery I get the screen saying it's booting into recovery and it vibrates a second time and boots normally. I have looked for solutions but can't find someone this this same exact problem.
Any help would be greatly appreciated, thanks!

mattmcs2 said:
A while back I flashed cm10 but the data wasn't working and I went back to stock through odin. Since then I have only been able to get 4g lte and receive texts, I can't send texts and can't call. I lose data when ever I go out of verizon lte range. I also can't root it like I had been able to before. This is because I can't get into recovery. I tried to flash cwm through odin, but when I try to go into recovery I get the screen saying it's booting into recovery and it vibrates a second time and boots normally. I have looked for solutions but can't find someone this this same exact problem.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Dial *2767*3855# it will do a complete factory reset, but your problem will be solved. I ran into the same problem and spent forever trying to find a fix. Cyanogenmod 10.1 currently is not working for me (and what seems like all verizon users) I keep hoping each update will fix it, but nothing does. If anyone finds a complete fix let me know.

Still not working
trevod523 said:
Dial *2767*3855# it will do a complete factory reset, but your problem will be solved. I ran into the same problem and spent forever trying to find a fix. Cyanogenmod 10.1 currently is not working for me (and what seems like all verizon users) I keep hoping each update will fix it, but nothing does. If anyone finds a complete fix let me know.
Click to expand...
Click to collapse
It doesn't do anything it just keeps dialing, still don't know what to do. Can someone help?

Try this guide first if you haven't already: http://forum.xda-developers.com/showthread.php?t=2066275. If that doesn't work, then follow section 5 here: http://forum.xda-developers.com/showthread.php?t=1762709. Then you should be able to do the dialer reprovision code.

BigErnM said:
Try this guide first if you haven't already: http://forum.xda-developers.com/showthread.php?t=2066275. If that doesn't work, then follow section 5 here: http://forum.xda-developers.com/showthread.php?t=1762709. Then you should be able to do the dialer reprovision code.
Click to expand...
Click to collapse
One quick question before I start, how will I wipe data after I odin if I can't get into recovery?

mattmcs2 said:
It doesn't do anything it just keeps dialing, still don't know what to do. Can someone help?
Click to expand...
Click to collapse
The reprovision code only works on ICS VRALF2 and VRALG1 based roms.
mattmcs2 said:
One quick question before I start, how will I wipe data after I odin if I can't get into recovery?
Click to expand...
Click to collapse
Not sure what you mean. Odin wipes the data from your previous rom when you Odin stock images. Depending on which .tar that you use, it will either leave internal storage alone or it will format it also. You won't have a custom recovery to wipe data with btw.

I had same problem after restoring a bad back up from twrp.
I highly reccomend the unbrick method over at the android development thread.
http://forum.xda-developers.com/showthread.php?t=1840030
It will make it so you reboot your phone. And you'll get stuck in boot loop. Pull battery and then you'll be able to access stock recovery. Wipe data. And cache. And reboot.
If you used root66 in the unbrick method you will be rooted with a LOCKED boot loaded. So unlock it and reinstall your favorite recovery
Hit that thanks button if it works for you
Sent from my SCH-I535 using xda app-developers app

I flashed a prerooted stock Jelly Bean file and it worked, then I unlocked the bootloader and installed cwm recovery. I'm planning on flashing a nightly version of CM10.1, but I tried to do a nandroid backup first. It was taking a long time and then it said "error while making a backup image of /data." Does anyone know why?
I also still only have 4g and can't send texts or call. Should I flash a radio file? (I don't know what that does)

SlimSnoopOS said:
The reprovision code only works on ICS VRALF2 and VRALG1 based roms.
Not sure what you mean. Odin wipes the data from your previous rom when you Odin stock images. Depending on which .tar that you use, it will either leave internal storage alone or it will format it also. You won't have a custom recovery to wipe data with btw.
Click to expand...
Click to collapse
I flashed a prerooted file through odin and then unlocked bootloader and installed cwm recovery. I still only have 4g lte and can't send texts or call. Then I flashed a couple of different modems and it didn't change anything. Any advice?

mattmcs2 said:
I flashed a prerooted stock Jelly Bean file and it worked, then I unlocked the bootloader and installed cwm recovery. I'm planning on flashing a nightly version of CM10.1, but I tried to do a nandroid backup first. It was taking a long time and then it said "error while making a backup image of /data." Does anyone know why?
I also still only have 4g and can't send texts or call. Should I flash a radio file? (I don't know what that does)
Click to expand...
Click to collapse
Here is what I HIGHLY recommend.
1.Flash stock unrooted ROM through Odin.
2.Dial that number to stock reset. (*2767*3855#) let phone reset and reboot.
3. Check your data and text/ calling.
If good. Go to step 4. If not, I'd follow the unbrick method and then repeat step 1.
4. Flash root66.tar through Odin
5. Unlock boot loader.
6. Download latest version of CWM and flash through Odin.
7. Back up current ROM and go from there.
flash-a-holic on my Verizon Galaxy S3
young and flashing.

michaeldizzowns said:
Here is what I HIGHLY recommend.
1.Flash stock unrooted ROM through Odin.
2.Dial that number to stock reset. (*2767*3855#) let phone reset and reboot.
3. Check your data and text/ calling.
If good. Go to step 4. If not, I'd follow the unbrick method and then repeat step 1.
4. Flash root66.tar through Odin
5. Unlock boot loader.
6. Download latest version of CWM and flash through Odin.
7. Back up current ROM and go from there.
flash-a-holic on my Verizon Galaxy S3
young and flashing.
Click to expand...
Click to collapse
Thank you! I got my phone working now!

Related

Need Help Fixing Someone's Cappy

Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then

HELP!!!

So I was rooted on synergy r72 then went to jellybean...tried flashing back to clean rom and s*it hit the fan...I ended up Odin back to stock and started from square 1...unlocked and rooted I made a nandroid and tried to flash clean rom once again...it installed but when it got to the boot animation it looked strange and the screen where it said Samsung had a bunch of different colors and then it rebooted...battery pulls didn't work...restored my root66 from Odin but can't flash any new roms! Any ideas what is going on!?!? I would greatly appreciate the help!
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Brian Gove said:
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Click to expand...
Click to collapse
Yes... I haven't done anything differently from when it worked prior to this
Sent from my SCH-I535 using xda app-developers app
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Did you try downloading the file again? It could have corrupted. Just a thought. Make sure your bootloader is still unlocked(You can tell because it will boot by the first 'Samsung' screen in a split second then go onto the 'Samsung Galaxy SIII' screen.). And before you flash cleanrom wipe everything, data, cache, davlik. Run the fix permissions too just to be sure.
pschatz12 said:
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Click to expand...
Click to collapse
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
buhohitr said:
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
Click to expand...
Click to collapse
This. If you ODIN back to stock, you need to unlock again.
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
pschatz12 said:
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
Click to expand...
Click to collapse
Please list the steps you took step by step so we can see what's going on here. Don't embellish, don't exaggerate, tell us what you did and what you didn't do. Based on your steps you shouldn't be bootlooping. I would follow droidstyle's guide step by step in each category that is relevant (going back to stock, unlocking, flashing ROMs, etc.). Follow each step closely in whatever ROM you're flashing as well. Don't take shortcuts.
You sure you're unlocked? Maybe try unlocking again. It doesn't seem to bother anything if unlock an unlocked phone. If that makes sense...
+1 to listing your exact steps to help troubleshoot.
mustbepbs said:
This. If you ODIN back to stock, you need to unlock again.
Click to expand...
Click to collapse
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Brian Gove said:
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Click to expand...
Click to collapse
I swore that it did. Are you sure?
http://forum.xda-developers.com/showthread.php?t=1842830 - Yes it does. It rewrites the aboot.img to the secure one.
Positive, I tested it out and that's why droidstyles guide has changed.
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Boot loop sounds like a kernel issue. Are you sure you're not using a TW kernel on AOSP, etc?
Also have you tried redownloading the files that are giving you problems? Try redownloading the kernel to see if that makes a difference. If you're successful in flashing ROMs then I think a fresh download might fix your issue.
pschatz12 said:
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Thats a wired problem I would try going back to the stock rooted image again
Wontfinishlast said:
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Click to expand...
Click to collapse
Ziggys kernel was flashed successfully and synergy r72 running successfully... Do you guys think I should try dirty flashing clean rom? Idk what else to try... From synergy I can do a full wipe and try install clean rom but I doubt it will work
Sent from my SCH-I535 using xda app-developers app
cleanrom doesn't come with their own kernel baked into it already??? Why would they make you flash the ROM then the kernel..... And if you're getting the bootloop after installing the kernel then it's as mustbepbs said, re-download the kernel file.

[Q] Firmware Update Not Completing

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

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app
joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.
sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2
mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!
The phone will not install a Verizon update with a custom recovery installed.

[Q] How do you unroot GS3?

How do you unroot the GS3 and get back to stock unrooted? I am currently just stock rooted. I'm just done with flashing and don't want to worry about something happening to my phone while I'm rooted, and am sick of it not being able to take the VZW update on a daily basis. I understand there is an unroot in the superuser app, is it as simple as clicking that and it will unroot by itself? Is there more I need to do? Thanks for your help!
Bump
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
buhohitr said:
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
Click to expand...
Click to collapse
Thank you. Once you perform either or these methods, can you still root again in the future if you decide to?
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Bump
irl5fan said:
Bump
Click to expand...
Click to collapse
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
irl5fan said:
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
Click to expand...
Click to collapse
You're right, try to search for it in Google. I didn't bookmark anything.
Sent from my HTC6525LVW using Tapatalk
irl5fan said:
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Click to expand...
Click to collapse
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
Sent From V500
Using XDA App
unroot gs3
LiamAtkins90 said:
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
irl5fan said:
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
LiamAtkins90 said:
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
Click to expand...
Click to collapse
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
irl5fan said:
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
Click to expand...
Click to collapse
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
LiamAtkins90 said:
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
irl5fan said:
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
Click to expand...
Click to collapse
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
My model number is SCH-I535. I have used Odin before, but I'll take a look at the guide just to make sure. Thanks for your help!
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
ShapesBlue said:
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
No problem, glad I can help.
Verizon edition Models tend to get overlooked as oppose to International variants which is a shame, I think both should get equal recognition. Not just Sammy Verizon, most Verizon models and also Google Play Edition Model Phones/Tablets get pushed aside.... Crying shame.
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
Everything worked out great, flashed the stock firmware and was able to take the OTA. Thank you so much for your help, it's greatly appreciated!

Categories

Resources