Hey guys,
Hoping someone here might be able to help me get rid of the bane of my existence right now. I've been reading all over and using various methods other people seem to have had success with but nothing is working for me.
I have a Samsung Galaxy Victory 4G from Virgin Mobile. I'm also responsible for 2 others that are having the same issue.
A while back I had rooted all our devices and put TWRP on them but have total stock rom.
A few weeks ago we all started getting this system update prompt that lets you install now or later. If we tried to install it with TWRP it just boots into TWRP. So I put the stock recovery back on and took the prompt and let it reboot. It begins installing but halfway through I get a red yield sign and it stops and reboots the phone. If we go this route the prompt usually doesn't show up again for days.
So I went and tried custom recovery and custom rom next. Didn't get the update on the custom rom until the next morning when I woke up. Went and got a perfect custom recovery/rom package for the phone and went total stock. Same issue as before where it gets halfway through and fails.
I've tried navigating to the root/cache folder as another thread suggested and renaming the update stored there but the update has never shown up in that directory.
Basically now, periodically this prompt continues to pop up, sometimes very frequently on the foreground of whatever you're doing on the phone and constantly reminds/annoys the hell out of us.
I'd take a screenshot but it hasn't reappeared in 2 days since I last took the update and it failed.
Appreciate any help from anyone!
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had not thought to try going stock with no root. That is the only thing I haven't tried. Will report back. Thank you
Related
My phone got stuck in what appeared to be recovery mode while trying to flash Jelly Bean using this guide:
http://www.android.gs/update-verizon-galaxy-s3-to-vralg7-ics-update-rooted-and-deodexed-firmware/
The phone seemed to flash took about 8 minutes then just went blank. Nothing. After about 10 minutes of waiting still nothing. I finally tried to get it to respond by hitting up/down/power and home buttons and still nothing. I then pulled the battery figuring I had bricked it anyway. After pulling the battery I restarted the phone and it came on but in a stock configeration. Not bricked but lost my root and cannot seem to get the phone to restore from Titanium Pro back up (not rooted any more). Any help getting things back the way they were would be appreciated.
drzcharlie said:
My phone got stuck in what appeared to be recovery mode while trying to flash Jelly Bean using this guide:
http://www.android.gs/update-verizon-galaxy-s3-to-vralg7-ics-update-rooted-and-deodexed-firmware/
The phone seemed to flash took about 8 minutes then just went blank. Nothing. After about 10 minutes of waiting still nothing. I finally tried to get it to respond by hitting up/down/power and home buttons and still nothing. I then pulled the battery figuring I had bricked it anyway. After pulling the battery I restarted the phone and it came on but in a stock configeration. Not bricked but lost my root and cannot seem to get the phone to restore from Titanium Pro back up (not rooted any more). Any help getting things back the way they were would be appreciated.
Click to expand...
Click to collapse
Section 5 of my guide...use the prerooted jellybean version. This will wipe your internal so back up what you dont want to lose.
By the way what you linked is for an ICS update not the jb leaks. Listen to droid style. I woke audio recommend getting your files, etc from here in XDA or rootz wiki. I see a lot of problems of people following these random guides online.
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
By the way what you linked is for an ICS update not the jb leaks. Listen to droid style. I woke audio recommend getting your files, etc from here in XDA or rootz wiki. I see a lot of problems of people following these random guides online.
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
I've noticed this as well. It seems every week or two someone is having major issues and they stem from using these rooting guides from sites I've never heard of.
Sent from my SCH-I535 using xda app-developers app
droidstyle said:
Section 5 of my guide...use the prerooted jellybean version. This will wipe your internal so back up what you dont want to lose.
Click to expand...
Click to collapse
After this happened I read more, a lot more about rooting and decided I wasn't rooted now.
Trying to root again produces an (amb?) error which I can't get past.
drzcharlie said:
After this happened I read more, a lot more about rooting and decided I wasn't rooted now.
Trying to root again produces an (amb?) error which I can't get past.
Click to expand...
Click to collapse
Do you have a super su app n the phone because what you linked is supposed to be pre rooted
Sent from my SGS3 running Eclipse 2.1
No Super SU, though I had it previously. I've checked in my applications list and it's not there.
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2046439
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
wingtytn said:
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
Click to expand...
Click to collapse
I think i actually locked it after i finished the install. And then restarted, do softbricks occur when you re-lock your bootloader?
Also another question..is there any way to check the /system /data partitions from inside the phone (terminal app maybe?) are correctly set to r/w over r/o (i don't like unplanned installs )
Soft bricks always occur on a locked bootloader. There are file managers that can do that like solid explorer.
jmxc23 said:
Soft bricks always occur on a locked boot loader. There are file managers that can do that like solid explorer.
Click to expand...
Click to collapse
Ah dully noted in the future the boot loader will be left unlocked! and thanks for the app recommendation i downloaded it and checked all my permissions I'm slightly less terrified to restart my phone now
thanks for all you help
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Didn't unlock bootloader?
I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.
Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app
recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.
No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app
So, today I received an update. 4.4.3.
I downloaded (from Android). After that, I needed to reboot to install ...
But It didn't install anything! It just rebooted ... and now, after 20-30 seconds, the system is rebooting itself!
What happened? What can I do?
(Rooted phone)
You can't do OTA updates on a rooted phone. The only solution I would suggest would be to manually flash the stock .IMG Zip and Radio files
Sent from my Nexus 5 using XDA Premium 4 mobile app
Unfathomable said:
You can't do OTA updates on a rooted phone. The only solution I would suggest would be to manually flash the stock .IMG Zip and Radio files
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What you mean I can't?
I shouldn't receive or If I update, it'll crash?
Generally speaking when doing a OTA update on a rooted device it will either unroot the device and push the update, not push the update through because a custom recovery is installed, or not boot at all or softbrick with a bootloop.
Sent from my Nexus 5 using XDA Premium 4 mobile app
@Unfathomable .... Be careful with the advice you give posters in the forum. What you claim about rooted Moto G phones being unable to take OTA updates is total rubbish.
My XT1034 was fully rooted, all I did was replace the custom recovery with the stock recovery and then the OTA downloaded and updated my device to 4.4.3. The phone was still rooted with read/write access to all folders, files and apps and all I had to do was flash back my custom recovery.
Maybe you are quoting what happened to your device which wasn't a Moto G ....In which case you shouldn't be quoting it in this forum.
I was speaking in a general term. I'm very familiar with the moto g in fact and from the situation If the device will not boot the only solution would be to revert to stock.
I quickly deleted the cache folder ... and "it worked". Not rebooting anymore.
Well I apologize that neither of our responses were helpful lol I was under the impression you were running a custom recovery. I'm glad you fixed it though!
Marcos Schroer said:
So, today I received an update. 4.4.3.
I downloaded (from Android). After that, I needed to reboot to install ...
But It didn't install anything! It just rebooted ... and now, after 20-30 seconds, the system is rebooting itself!
What happened? What can I do?
(Rooted phone)
Click to expand...
Click to collapse
This is why XDA practically begs you to search the forum before posting a problem. Several things you all should know:
- The phone was rebooting because the recovery could not update and the phone sees the update files in /cache when it finally boots, and of course it restarts to apply the update...and will keep doing so until the update is complete. We've treated why this happens just a few days ago so I won't bother. Look it up in General.
- Moto G can receive OTA updates whether unlocked, rooted, whatever, so long as the stock ROM is running. Applying the update, well.....
- The stock recovery is actually not the best choice if you've tweaked your stock ROM. It will always cause the constant reboots if it sees something wrong without telling you why.
Look up the ANDROID 4.4.3 IS OUT post (or something like that). Read through, educate yourselves, then try out what has been suggested. It's easy...
So, I've had my rooted G2 for awhile. Automatically updated to D800-20Y a few weeks ago. Decided I wanted to try CM out and used Autorec to get a custom recovery. Everything seemed to work great, booted into recovery and I keep getting error #30 can't make a folder for TWRP backup. Obviously this is during me trying to backup my current setup. What is going on here? I don't want to try to flash anything until I have a backup. Help is appreciated!
mungerank said:
So, I've had my rooted G2 for awhile. Automatically updated to D800-20Y a few weeks ago. Decided I wanted to try CM out and used Autorec to get a custom recovery. Everything seemed to work great, booted into recovery and I keep getting error #30 can't make a folder for TWRP backup. Obviously this is during me trying to backup my current setup. What is going on here? I don't want to try to flash anything until I have a backup. Help is appreciated!
Click to expand...
Click to collapse
I just got " Forced" the D800-20y update last night it kept my root but was wanting to install TWRP also. Did you ever get anywhere with this issue? Where you able to backup?
Sent from my LG-D800 using XDA Premium 4 mobile app
vxkillswitchxv37 said:
I just got " Forced" the D800-20y update last night it kept my root but was wanting to install TWRP also. Did you ever get anywhere with this issue? Where you able to backup?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I ended up flashing the device with fresh software and traded it off for an s4. I didn't want a device that was going to update on its own without my consent. Never had an issue with Samsung and updates before