My g1 is stuck at original 1.0 firmware&i was trying to root it but my pc died. I got as far as going into the terminal and doing the script with devblock&im trying to find a way to undo it via a terminal script so i can atleast get ota updates from tmobile again.
All help is greatly appreciated
you are going to have to un root...but that will require a pc.
actually you can find the OTA for cupcake on the t-mobile forums along with instructions on how to manually update it but you are going to HAVE TO UN ROOT before you do that otherwise you will BRICK.
here is the link for the t-mobile forums and the thread that i was talking about.
http://forums.t-mobile.com/t5/Opera...A-Android-15-Cupcake-Manual-Update/m-p/100646
That's a part of the issue. I would just finish downloading the zip files to get to the latest cm update but any zip file I download it says its corrupted when I try to apply it from the sdcard
Related
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Fixed!
Found this thread after a search and reading a thread on the G3.
http://forum.xda-developers.com/showthread.php?t=2451696
Tsip85 said:
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
mach01 said:
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
Click to expand...
Click to collapse
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Glad it helped. As for a recovery switcher, you might want to consider using a simple one of the Play Store. They are convenient and easy to use. This thread is really great: http://www.xda-developers.com/simple-recovery-switcher/
Hope this helps.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Would you mind sharing that link I need to find my bosses g2 please help
chazla86 said:
Would you mind sharing that link I need to find my bosses g2 please help
Click to expand...
Click to collapse
Yes...check the link I posted on the second post.
Forgive me here. I have a VZW dev edition.
Currently running 4.4.4 stock rom. I had it rooted before and I think I recently lost root. Forgot why but I didn't really need it.
EDIT: I remember now. I did a factory reset. Did I lose root?
anyways the OTA that came a few weeks ago the small one will not install. I have enabled my apps again that I had disabled. I do not remember if I did a tether hack before which was just replacing a file. Bootloader is unlocked still.
So after the OTA downloads and reboots the android shows up the bar starts to move and then red exclamation mark.
Update unsuccessful.
What do I need to do? I also do not want to wipe data.
The OTA alert is annoying me to no end.
It sounds like the pre-flash validation checks are failing for some reason.
A few things don't add up in your post...
You have a Dev Edition, so to root you unlock the bootloader, flash TWRP, boot into it, and when it prompts you too, allow it to root (or if you don't get rooted, install SuperSU while booted to TWRP). IN that state, a Factory reset doesn't remove root. So did you root by some other method? If so, that is why the OTA is failing.
Next.. you say you did a tether hack that was just replacing a file. Did you put the ORIGINAL file back? If no, that will cause the OTA to fail.
The only way to really know exactly why is to NOT install the OTA, instead just download it. Move the OTA zip from /cache to your /SDCard (which takes root) after it finished downloading. Again Do NOT install it the "normal way". Make sure you have a working STOCK Recovery on your phone. Manually boot to stock recovery and apply the update zip via the menu options. When it errors, it will pause and tell you why, what caused the issue. You need to correct it and try again.
One final option... See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 you can take some time and read the first post... then skip to Post #2, and use the Requirements section, and Option 2.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
Hi. I'm currently on C432B166 and have previously contact Huawei and was told that the update rollout will run until the end of June for the UK.
I would like to update manually but not sure what i need to do and what i need to download. I do not want to root my phone or anything like that. I do not have access to a computer for anything. So my only way is to do everything via my phone. I would be very great full in any help or guidance offered. Thanks in advance.
boroleigh said:
Hi. I'm currently on C432B166 and have previously contact Huawei and was told that the update rollout will run until the end of June for the UK.
I would like to update manually but not sure what i need to do and what i need to download. I do not want to root my phone or anything like that. I do not have access to a computer for anything. So my only way is to do everything via my phone. I would be very great full in any help or guidance offered. Thanks in advance.
Click to expand...
Click to collapse
Harder without a pc... But not impossible, especially if you don't want to root.
You'll need to download the c432b182 update, & install using the dload method. Then the c432b361 update the same way. The phone should auto update itself at that point to b378
I'm not going to post links to the updates as they can change, but not too difficult to find in the stock firmware thread and elsewhere.
The dload method is easy as well... Extract the update zip you downloaded. Copy the extracted dload folder and all contents to your microSD card, turn off the phone and turn it back on holding both volume buttons.
You should be able to use the firmware finder app as well, don't use it myself, but don't think it needs root.
Greetings,
I have a phone with unlocked bootloader and root access. I sent it to a repair shop recently, and it seems that during the repair Huawei's OTA Updater has been set to "Download Update Automatically". Right now it has already downloaded a firmware update and is prompting me to restart my phone to complete the update - I do NOT want that.
I searched through sites to see how can I stop the update process.
1) The website (https://************/huawei-update-...kely-isnt-intentional-easy-way-to-fix-inside/) suggested to disable Huawei OTA Manager via /system/app/HwOUC, but I couldn't find that folder at all.
2) I am currently attempting to delete the downloaded update by removing /data/ota and /data/update/HwOUC, as listed in (https://forum.xda-developers.com/p10/help/ota-file-location-t3857535), but I am still afraid to reboot my phone now.
May I ask if there is any other step which I should do, to ensure the update is NOT applied?