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...
Related
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
Hello Everyone,
Im new to this forum as a poster, I do have read quite a few tutorials on here on how to unlock/root/s-off my device but now Im stuck again and can't seem to find a solution.
I have a HTC Sensation Z710e and I'm running CyanogenMod 10.1-20130309-Albinoman887-pyramid. Now whenever I watch a movie I there are no troubles BUT when I scroll in the movie or pause it or whatever I get an error. I looked it up and found out my version is an unstable one. So a friend of mine explained to me I could update via Goo.im, and here's the problem. It says there are no updates for my device even though that friend of mine updated to 10.1-20130601-Albinoman887-pyramid in the same way.
I did get a message like 2 weeks ago there was an update available for my device but when I clicked the notice nothing happened.
Now my biggest question is, is there some way I can download an update zip in stead of the 10.1-20130601-Albinoman887-pyramid Rom and have to start all over again with all my apps, or am I just ****ed and need to start backupping what I want to backup and start over again?
Thx for any and all insights,
Marius
well if the rom is just an update from the same rom, get it from another repo (download it from your phone or pc) and flash it with TWRP/CWM
It should work, I've done many rom upgrades without wiping my system.
Daniel120201 said:
well if the rom is just an update from the same rom, get it from another repo (download it from your phone or pc) and flash it with TWRP/CWM
It should work, I've done many rom upgrades without wiping my system.
Click to expand...
Click to collapse
So you're saying I should just "install from sdcard" with my 4EXT and it will not wipe all my settings? Even though its a completely "new" ROM but just an update of the one I have right now? I dont have to invoke something like "update"?
I did already download the file with Goo.im (that did work ) and it was about 157mb, that gives me the feeling its a completely new ROM, that's why Im a bit hesitant
Thx for the info though
MariusJP is right, there's no need for a wipe when you are flashing an update, but it may depend from ROM to ROM and from update to update. Just flash it and look for problems. If there are problems you'll have to wipe.
You should do a Backup via CWM before flashing any new software especially when it's not a stable one.
Flashing this update won't wipe your settings and data.
Sent from my GT-I9100 using xda app-developers app
Sent from my HTC ChaCha A810e using xda app-developers app
Just like Daniel said, because its an update of the ROM Im using it just updates. I was just afraid it would reinstall everything but it didnt
Thx for all the help
If I buy the S3 from a verizon store today brand new, will I be able to root it and unlock the boot loader still or will it come with a firmware too new?
Sorry if this was answered before. Tried searching but couldn't find results. If they are out there then I blame iOS 7 and my iPhone that needs replacing
I'm not sure what, if any, updates they've had in the last few months but I just got my s3 in August. I did take an update on it and had no issues with using casual to root & unlock. Perhaps someone may have a more recent experience.
Sent from my Slim GS3
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Rooting is a great idea- I'm loving 4.4 on the s3.
clembrowning said:
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
fbiryujin said:
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
Click to expand...
Click to collapse
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
MisterSprinkles said:
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
Click to expand...
Click to collapse
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Ah crap. Thanks for the warning. I decided to order a Verizon Moto X Dev Edition. Can't wait for that to arrive.
Thanks to everyone for the info/advice.
KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Macrodroid said:
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I have no problem getting the recovery installed. The custom recoveries are just *non-functional* because they can't mount any partitions. The error logs' are pretty clear, and every custom recovery I've tried behaves exactly the same.
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
Hello!
Im not really new to rooting and custom roms. Had the Nexus 4 until about a year ago, so been away from Android for about a year! Got the Nexus 5 a couple weeks ago, but been too busy to get around to doing anything with it. So, well, now its time! Ive unlocked the bootloader, and installed ClockworkMod Recovery (Only cuz thats what I used to use, and I like it! The installation goes fine, and the recovery works fine! So, I restart my phone so I can see if the phone is working fine before I install a rom. Everythings fine! So, I resart and go into recovery and that's where the problem is! When I go into recovery, it shows a picture of a Android under service. Well, I did some research, and from what I can tell it looks like there is no custom recovery on the phone. I repeated this a couple times, same problem! can anyone help me out? Someone here mustve faced this problem too... or maybe Im just screwing up somewhere and I dont realize it.
-AGZ
It happens with stock lollipop and maybe some aosp ones too. Flash latest SuperSU from recovery or delete recovery-from-boot.p (I think in system folder)
Sent from my Nexus 5 using XDA Free mobile app
AGZ98 said:
Hello!
Im not really new to rooting and custom roms. Had the Nexus 4 until about a year ago, so been away from Android for about a year! Got the Nexus 5 a couple weeks ago, but been too busy to get around to doing anything with it. So, well, now its time! Ive unlocked the bootloader, and installed ClockworkMod Recovery (Only cuz thats what I used to use, and I like it! The installation goes fine, and the recovery works fine! So, I restart my phone so I can see if the phone is working fine before I install a rom. Everythings fine! So, I resart and go into recovery and that's where the problem is! When I go into recovery, it shows a picture of a Android under service. Well, I did some research, and from what I can tell it looks like there is no custom recovery on the phone. I repeated this a couple times, same problem! can anyone help me out? Someone here mustve faced this problem too... or maybe Im just screwing up somewhere and I dont realize it.
-AGZ
Click to expand...
Click to collapse
Fastboot boot cwmrecovery.img
Flash supersu in recovery
Then
Fastboot flash recovery cwmrecovery.img
Btw, I recommend you use twrp
Sent from my Nexus 9 using XDA Free mobile app
+1 for TWRP, CWM is practically ancient.
Live boot TWRP, flash SuperSU, then use Flashify (root) to install TWRP.
bm19981217 said:
delete recovery-from-boot.p (I think in system folder)
Click to expand...
Click to collapse
This. This is the key for maintaining your custom recovery after a reboot.
a maguro wrote this.