I'm trying to apply the July update but am getting "Installation Problem" error when the update runs.
I was previously rooted with Magisk but did a full wipe and reload back to stock in mid June. I do not have TWRP or any other custom/rooted apps any more.
Is there anything else I should check? All other usual suspects work fine like Google Pay etc.
Thanks ahead of time
Verify your image D/L checksum is correct. Switch USB ports. Use a new USB cable (A>C and not C>C). Make sure you have the current platform tools. Different computer. Start with the easy stuff like platform tools and cable.
I went ahead and downloaded the OTA to sideload. It worked fine but I wish it was working through the regular real OTA process. We'll see how August goes though I expect that will be the big Q update...?
Bootloader locked, stock ROM, stock everything else should work just fine but who knows
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Hey guys, I just got a T-Mobile SGH-T869 and it came with Honeycomb on it.
I've been able to root it (which was as dumb as flashing a ZIP on the stock recovery), and I've flashed the CWM 5 I found (here). However, I'm unable to flash CM10 from that, so I'm looking to figure out what's wrong or the missing step.
Any suggestions?
Just to follow up on my own issue, I figured it'd be a good idea to update my SGH-T869 to ICS, because HoneyComb is kinda terrible.
For this device, at least for now, the "official" ICS update isn't being made available over the air, only available via the Samsung Kies program.
Its totally free and you can get it for Mac or Windows here http://www.samsung.com/us/kies/
The procedure to update was seriously as dumb as "Install Kies, then plug in your device".
Kies should auto-detect and in the case of my SGH-T869, it immediately offered to update the firmware. However, Kies requires your battery to be charged up before it'll let you proceed, so initially it didn't allow me to flash (my battery was down to around 43%).
After updating this way, everything was back to stock and I had no root anymore.
I re-obtained root by downloading the two attached files. The attached CWM is a "temporary" touch-enabled version. Flashing it from the stock recovery boots you into CWM but after you reboot, its gone. I booted to that and then flashed the attached root.zip, which re-established root on my tablet.
So, sort of progress. Next step: figure out how to get CM10 on this bad boy, since the stock ICS kinda blows
I’ll make this short.
I was successfully rooted. But I couldn’t update to 9.5.6.
I updated but it keeps failing. I switch to slot A and I was on 9.5.6 but WiFi didn’t work and apps would crash randomly, and it was laggy. I would go back to slot b and WiFi worked and everything was great but I’m on 9.5.3. And I would try to update again and it would fail and sometimes I would have to have in fastboot and reflash twrp to reboot to restore. I restored the device multiple times, removed root but it still happens. I used to always use android but I was on iOS for years and I’m used to jailbreaking and Apple IOS. Please help me. How can I restore and start from scratch? Or how can I fix this? It’s very annoying. I have my info backed up so I don’t care what I have to do. I love this phone but I had the Verizon iPhone bug when people call me and I answer it fails on there end. Or else I would deal with 9.5.3. All help is greatly appreciated.
You need to read the threads better, it's already been explained that wifi can end up being disabled because the rooted boot.img is older than your current rom version. Flashing one of the kernels available usually fixes this. You can also extract the boot image from the rom you downloaded and patch that boot.img file using Magisk, then when you apply that everything should work correctly.
From reading your post it would appear you're on T-Mobile (US) so you would need to download the 9.5.6 package and then extract the boot.img, then patch that using Magisk and push it to the phone using fastboot, once you reboot everything should be rooted and working.
I've recently been playing around on my shield tablet with a couple of different roms and rooting, but I ended going back to stock - albeit with root and twrp installed. I downloaded the stock image from Nvidia's own download site and everything well and now it wants to install 5.4 over OTA. I figured that was fine, I'd have to re-root and, possibly, reinstall twrp, but that's not a hassle so I went ahead with the update.
Unfortunately, when it rebooted to install it actually rebooted into twrp. I figured that was OK, since I could just flash the update manually. I found it from /data/data/com/nvidia.ota/ and went to flash it. It failed, however, with error e3003 - complaining about the update file being older that the existing system file. The only solution I could find on googling was to make suer you went through the updates systematically and in order. Since my tablet had been restored to 5.2 I tried flashing the 5.3 update, but it gave me the same error.
I'm now somewhat stumped as to how I can actually go about getting my tablet back up to date again...
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?