Hello there. I'm new and I have a problem upgrading to 5.0 from kitkat. I barely know anything about cellphones and my friend was helping me out before this happened.
So the background story was this:
My cellphone (Moto G LTE XT1040) was not showing the push notifications so after digging, I looked for some solutions that required a rooted cellphone, so I did it.
I unlocked the bootloader and installed a custom recovery (TWRP), then I installed SuperSU to make the cellphone root and tinkered around with the solutions to the push notifications issue, and left the cellphone untouched after.
Just this week, I recieved the upgrade to android 5.1 and before installing it I unrooted the cellphone, uninstalled SuperSu, flashed it with stock recovery and then a factory reset it. That should clean everything, but it turns out that after 2 failed tries, It doesnt install the upgrade. The cellphone shuts down and it shows that it tries to install the upgrade but the bar fills up until around 15% and a quick error message displays and it restarts normally.
Should I just install the stock rom (the 500 mb file) so all functions and settings go back to true default?
Thanks beforehand and sorry for the bad english
HTML:
Anyone?
Related
Hello there. I'm a noob and now I'm stuck in the web of the consequences of my sudden stupidity.I have been trying to update my AT&T HTC One X for the last 4 days. I had already unlocked the bootloader and installed the Supersu through the TWRP. but when I was trying to install the rom it wrote failed and I had two variants. Go back or press reboot. So I touched the reboot button and discovered that I had to install all the stuff I once had again, I noticed that I wasn't asked to connect to a wifi. so I carried on after checkin once again. Then I opened my settings through the status bar and it was written "Error" under the Wifi switch and I couldn't use any downloaded applications, they turned up to be not responding as soon as I opened them. I booted into recovery mode once more and tried to restore my backup through the TWRP.But it didn't show any files.. PLEASE help!
Okay, so just today I was looking through some articles and saw that Android 4.4.4 was able to be downloaded for the Moto G, I have a rooted Moto G, so I know that I can't install the OTA updates without reverting back to stock.
So it was early in the morning, I was still tired and not thinking strait; and I forgot that I couldn't install the OTA updates without reverting; So I made an idiotic mistake and used the settings update method to download the new version..... so now I am stuck in a boot loop because when ever I get to the Clockworkmod recovery, it says it can't complete it and it reboots my phone. Then the phone detects the phone didn't update and it goes into recovery. This just keeps happening over, and over, and over again,
See, the thing is, I would revert back to the stock, but I can't install the stock onto the internal SD because the phone reboots before I can actually get the stock zip onto the phone... so I'm stuck at this point, and I really don't know what to do... and I really don't think there is much I can do at this point.
Here Is My Phone Info:
Model: XT1031
Clockworkmod Recovery Version: v6.0.4.7
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
meekrawb said:
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
Click to expand...
Click to collapse
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
xLOLxTSNOOPS said:
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
Click to expand...
Click to collapse
Leave it plugged in for a few hours and then fastboot flash the stock firmware for your model number.
Unless someone else knows an easier way to get you going.
I have the shield tablet LTE version and after connecting to WIFI it immediately installed all OTAs upto the hotfix also. So here I am sitting with lollipop in my tablet and I decide to go for rooting and CWM installation.. After rooting using adb/fastboot and installing CWM image, I decide to disable ATTall access because I read that it stops the portable hotspot from working. So, did that and then process after process started crashing. First it started with background data not being enabled (playstore wouldn't open) , NVidia hub crashing, google text to speech crashing, etc.
So, I went to cwm and did factory reset. At the initial stages itself where it asks for language setup, the google text to speexh crashes and I cannot click next or proceed forward.
I flash the Lollipop OTA once again thinking it would overwrite the system but it didn't.. and the same issue keeps happening..
Now what do I do?
Regards
Alden
An update to the mess i was in...
I tried recovery mode at the fastloader boot menu and I got the robot lying down with a red exclamation mark sign. I pressed vol + key and it opened the original recovery I think. I wiped user data from this menu and rebooted. and now it has come to the original screen setup and so far no process crashes...
What could have caused this entire mess?
I am not sure what would cause your issues but i believe your best bet is to download the full rom image for your tablet and flash it via fastboot. That should get you back up and running. (Be warned doing this will erase everything on your tablet!! SD card will be untouched)
By fullmrom u mean the one from the nvidia developer website right?
Yes that is the one! I am currently at work so I cant post a link to it but if you need it ill try to post it once im off, in about 30-ish minutes. Good luck! (p.s. last resort is RMA)
Is your shield up and running once again? Just wanted to get an update. =]
Thanks javydawg, I didnt use the one on nvidias developer website as i simply did not have enough data left in my Internet plan .. its 2.3 gb in size... after recoVery i was left with lollipop so i flashed a 750 mb file tht i gt from these forums and updated it to the latest version.. i still haven't pinpointed the reason for my earlier trouble but will shout out if it happens again... have to be careful cos not sure if RMA is possible for me in India...
I got a Moto G First generation (X1032) with lollipop 5.1
A few weeks ago I had the option to do a update, after I installed the update my phone was restarting and it now gets stuck in a bootloop. I can still come to the bootloader.
When I connect my phone to my computer it won't install, so I can't acces my phone.
My phone needs to startup in order to install it, but that's not possible because it will get in a bootloop.
My phone was rooted, but I fully unrooted it before I did the update.
Is there anyway to survive my phone? Already tried factory reset, but that won't do.
Thank you for your time.
Davoz said:
I got a Moto G First generation (X1032) with lollipop 5.1
A few weeks ago I had the option to do a update, after I installed the update my phone was restarting and it now gets stuck in a bootloop. I can still come to the bootloader.
When I connect my phone to my computer it won't install, so I can't acces my phone.
My phone needs to startup in order to install it, but that's not possible because it will get in a bootloop.
My phone was rooted, but I fully unrooted it before I did the update.
Is there anyway to survive my phone? Already tried factory reset, but that won't do.
Thank you for your time.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
My guess is that you need to flash again the stock ROM.
You ended up into a bootloop because you may changed some system files, and for each update the installer is checking that.
There are two situations:
- The update process will went good but you will be stuck into a bootloop
- The update process will be interrupted directly from the recovery
Here is a good guide about how to get back to stock.
Good luck!
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet