Related
When the ota hit my droid 2, I couldn't update because I deleted all those stupid apps like vznav, blockbuster, amazon mp3, etc and couldn't upgrade without reverting my cell to stock. I hear that if you have a rooted droid 2 with just some rooted apps and haven't deleted anything, you can use the ota or skip reinstalling 2.2.20.
I understand this is a common issue right now so here is how I did it successfully.
First Download these files as they are ABSOLUTELY necessary.
Motorola drivers for omap 3630
RSD lite 4.7 & patch (4.8 and 4.9 didnt detect the device on my pc)
2.2.20 firmware (stock at launch)
2.3.20 firmware (latest)
2. Install RSDLite by double clicking the RSD Lite.msi file you just downloaded.
3. Once RSD Lite is installed, copy the pst_flash.ini file you downloaded with the RSD Lite install file and paste it into C:\Program Files (x86)\Motorola\RSD Lite OR C:\Program Files\Motorola\RSD Lite depending on where your computer put it when installing. Allow it to overwrite the existing pst_flash.ini file.
3. Unzip the drivers folder you downloaded (32 bit OR 64 bit), then double click the Motorola Consumer Driver Installer application and install the drivers.
4. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
5. Open the RSDLite program by right clicking it and selecting Run As Administrator.
6. Click on the “…” button next to the filename box and select the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file you downloaded earlier.
7. Once it is selected, hit Start and wait for it to finish flashing the phone.
8. Once it is done, click on the “…” button next to the filename box again and this time select the BL_D235_cdma_droid2_Consumer_replacer_HSPart.sbf file you downloaded earlier.
9. Once it is selected, hit Start and wait for it to finish flashing the phone.
10. Once both have been flashed, your are back to the stock Android 2.2 firmware.
11. Load in recovery mode and reset to factory default.
You can either upgrade now over the air or you can load the sbf for 2.3.20.
1. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
2. Open the RSDLite program by right clicking it and selecting Run As Administrator.
3. Click on the “…” button next to the filename box and select the VRZ_A955_2.3.20_1FF_01.sbf file you downloaded earlier.
4. Once it is selected, hit Start and wait for it to finish flashing the phone.
5. Bam you have 2.3.20, now you can do a recovery factory reset and do your thing.
From what I have seen on the web, you can't use this sbf if you installed the OTA cause it will brick your phone but you can reflash this sbf if you upgraded using this sbf.
I do not know if you can just take your rooted phone with deleted apps and flash the 2.3.20 over your current 2.2.20. I do know the process I used worked without a hitch.
Edit: Hey guys, after the patch I noticed bad battery life and my battery monitor wouldn't open. Apparently you will need to boot into recovery and wipe the cache partition. All the links work.
Thanks for taking the time to write this up ! Much appreciated =)
Sent from my DROID2 using Tapatalk
so does this mean if i'm on 2.3.20 and want to go back to stock( and reflash to 2.3.20 is impossible??.... I'm doing this because i went directly from fission 1.2.1(stock band) to 2.3.20 and just want to make sure whether i have the latest kernels
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
is there a way to go from 2.3 to 2.2, like the original kernel and radio, baseband that most people were running like a month ago. im trying to sbf form 2.3 to the older one and i keep getting errors is there any way i can go back?
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
zibrah3ed said:
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Thanks for the reply. now i can stop trying lol, it was driving me crazy.
bladearronwey said:
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
Click to expand...
Click to collapse
I gotcha, well it works exactly as stated so it was safe and is safe to do it the way I flashed. I will edit the sticky though to remove irrelevant info. Also reflashing the 2.3.20 sbf after flashing once yielded no errors. I'll edit the op.
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
JonandRoid said:
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Make sure you use the FULL FLASH and not the system only file
Renegade8100 said:
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
Click to expand...
Click to collapse
Im using RDS 4.9 there was no inf files that came with .9 so idk what you're talking about. I know 4.7 required a patch but idk if the new ones require it. I have fission 2.0.1 and my phone didn't brick because I have it up and running right now but I still don't have the new baseband mine is still .05...
Sent from my DROID2 using XDA App
JonandRoid said:
I still don't have the new baseband mine is still .05.
Click to expand...
Click to collapse
There's a tutorial on my "[TOOL] Ubuntu livecd" thread on how to update the baseband only, after flashing 2.3.2. Just go to the bottom of the OP and it will all be there. (I'd quote it but I'm on my D2 not my computer)
Sent from Newk's DROID2 using XDA App
No files
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
This should help you out.
http://www.mydroidworld.com/forums/...rld-present-droid-2-2-3-20-triple-threat.html
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
The update file in my tut still works for me. Update.zip
All the links should work. I just uploaded the 2.2.20 to include the drivers and rsdlite
bladearronwey said:
Make sure you use the FULL FLASH and not the system only file
Click to expand...
Click to collapse
FYI, I did the full flash for 2.3.20 because the automatic update kept failing. Not sure why it didn't work - I had rooted the Droid2, "removed" a few annoying apps by renaming the adk and odec files to .bak. I unrooted it and tried the auto update again but it failed. Not sure what was making it fail, but rather than put all the apps back and try letting the phone do its thing, I used the method above - just using RDS Lite to flash to 2.3.20 without doing the previous steps.
It worked fine, but I had to dial *22899 to re-activate the phone afterward.
So far so good, but I'm not sure that rooting the phone and messing around with it, to the tune of a few good hours of my life, was worth a little bit of battery life, especially considering the 2.3.20 is supposed to fix the two problems I had with the Droid, namely poor battery life and email sync problems after inactivity.
thanks for the how-to! i flashed straight over from a rooted 2.2 phone to the new version as well.
i did experience force closes on the battery monitor as well, and clearing the cache did not fix that. i cleared, rebooted, and when it still didnt work, i flashed the phone once more and all is well. did not need to clear cache a second time. im a rookie still at all this, so bear with me if my reply seems obvious- or doesnt make sense.
i also had to reactivate the phone with the *# referenced above.
thanks again!
Had no problems updating from 2.2 to 2.3 using only the 2.3 SBF. Worked great and kept all other settings intact.
To fix the battery monitor force closing issue; just plug your phone into the charger while it's on! Fixed the issue right up for me!
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed
After searching around and not being 100% sure on how I should go about fixing this particular bootloop I decided to post a thread. Bootloader unlocked, phone unlocked, FRP unlocked, and TWRP installed. Can't seem to get the phone recognized when plugged in no matter where I'm at and hisuite recovery doesn't work, nor does the erecovery or whatever it's called. I had the phone running just fine with supersu but after installing my usual Xposed/Busybox and rebooting I got caught in a bootloop. (might have been caused by being on Oreo and having some problems with a version made for Nougat or something). I've seen there are various ways to exit the loop and at this point I'd be open to any but I do notice some posts saying they almost bricked their phone while doing so. Currently on my microSD I've got a hwota update I was going to try to use. I've got no backups in TWRP either because I'm irresponsible (my fault). What can I do to just wipe the phone, reinstall any version of android and get back to where I was at. I'm a little new to this as I've only ever rooted my tablet. Thanks for the help and all the info I've taken from this forum before and hopefully now. Forgot to mention I don't know my full device number only MHA-L29 in the US.
Ok Well after laying in bed and thinking about it I wound up running HWOTA8 from TWRP since I could access that. Seemed to just bring me back to eRecovery, and I factory reset my phone. I'll reinstall TWRP and flash supersu then make a backup and try again. Not sure what happened but I seemed to be in a pretty good spot since I could access TWRP even though my phone wouldn't show up on my computer while in fastboot/Recovery mode.
edit: oh I got a new problem now. I'm on testkeys firmware, camera, sim, and bluetooth work but I can't update from 7 back to 8. I'll do more testing around before bothering to unlock bootloader or install TWRP.
I've been trying to follow the guide in this thread but to no avail. I just get software install failed and then I have to start again.
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
KittyCat5eUTP said:
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
Click to expand...
Click to collapse
What is your full build number? Please, post screenshot.
5[Strogino] said:
What is your full build number? Please, post screenshot.
Click to expand...
Click to collapse
Model: MHA-L29
Build: NRD90M test-keys
EMUI version: 5.0.1
Android version: 7.0
I believe I was originally on some variant of MHA-L29C567 since I'm US based and its the dual sim version
I've tried using HWOTA a few times to either upgrade/update or rebrand and no matter what I choose when my phone restarts to install I just get software install failed. Usually I'll have to run through first time setup again. I've read that some people said this particular issue had to do with the update zips but mine seem to be named correctly so all I can think of doing is getting another firmware and trying again with that.
haha okay so I found out I was putting the update zips in the wrong folder. I fixed that and re ran HWOTA. update started/finished and my phone started booting and restarting a lot then went into erecovery. I'm downloading the update package right now and it's slow as hell but it's moving. And that failed leaving me to boot a few times and then get back to erecovery. I'll try getting into fastboot or recovery.
Edit: Well that seems to have resolved itself now. After having the erecovery fail I wiped/factory reset and booted the phone into oreo 8.0.0.321 with all the apps and updater. Thanks to everyone who dropped in and I'll be getting emails if someone replies that needs help too. I'm not very knowledgeable but I can give it a shot.