Related
Hi,
I'm looking for a stock ROM for the GT-i9020A as I want to switch back to the default Gingerbread that my phone came with (2.3.3, or I would also be happy with 2.3.4)
What I have done:
Unlocked bootloader
Installed ClockworkMOD
Installed Cyanogen 7
The problem is that I don't have a copy of the stock Gingerbread that I can flash on my phone. I've scoured high and low on the net, the XDA forums, XDA wiki and other forums, and I can't find it anywhere
I would prefer to keep ClockworkMOD on the recovery, but my main concern is getting back to stock Gingerbread, so I'm OK with it being removed. I can always just boot into it with 'fastboot' if I need to.
Any help would be much appreciated! Thanks
Well, I eventually found a roundabout solution that got me back to 2.3.4, and even let me keep ClockworkMOD. Hopefully this helps someone.
BE AWARE - this has only been tested on my GT-I9020A
I followed this video until just after they do the restoration (before they remove ClockworkMOD) to get my phone to GRH78 (2.3.1?). When I rebooted, my radio didn't work and I couldn't connect to my carrier. I then downloaded this file (which updates to 2.3.3), and ran it in ClockworkMOD by doing the following:
put the zip file onto the sdcard partition
booted into ClockworkMOD
selected "install zip from sdcard"
selected "choose zip from sdcard"
[selected the zip file]
Shortly after I booted into 2.3.3, I received a notification from Google to update to 2.3.4, which I did. After the update to 2.3.4, I restarted and everything was fine =)
nothsa said:
Well, I eventually found a roundabout solution that got me back to 2.3.4, and even let me keep ClockworkMOD. Hopefully this helps someone.
BE AWARE - this has only been tested on my GT-I9020A
I followed this video until just after they do the restoration (before they remove ClockworkMOD) to get my phone to GRH78 (2.3.1?). When I rebooted, my radio didn't work and I couldn't connect to my carrier. I then downloaded this file (which updates to 2.3.3), and ran it in ClockworkMOD by doing the following:
put the zip file onto the sdcard partition
booted into ClockworkMOD
selected "install zip from sdcard"
selected "choose zip from sdcard"
[selected the zip file]
Shortly after I booted into 2.3.3, I received a notification from Google to update to 2.3.4, which I did. After the update to 2.3.4, I restarted and everything was fine =)
Click to expand...
Click to collapse
the video in your link doesn't work ... i have the same prob as you
you went from
2.3.1 to 2.3.3 then ota 2.3.4?
i need help getting the first part the 2.3.1
never mind i flashed 2.3.3 from clockwork and all is well ... ota updated to 2.3.4 failed though ... is it because of clockwork?
if so where is the stock recovery.img? there is no link for it
cheers
I just got OTA notification, should I install it? I'm rooted and have custom recovery.
If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.
4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.
By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.
Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it
That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app
@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.
I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?
@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.
Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app
mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?
inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped
Doesn't seem like there will be a US LTE version again... hoping there will be a RoW version that someone will eventually create a flashable zip...
Hey Guys -
Yeah, just saw this was available for my Original Shield Tablet (rooted) few minutes ago. Aside from wiping and installing OS all over again, what's the best method to upgrade and ensuring I still have root afterwards + retain installed apps & settings?
I use an SD card in Internal mode if that makes a difference. Thanks!
Just got the Notication for the wx-un-do upgrade.
Now looking for the full ota update.
Send from my .I. .I.
Don't worry, it doesn't seem to work. OTA downloads, boots and back into system again. Asks to download ota again, version number unchanged. I've tried it 3 times already.
Whatever Nividia can do wrong, they will do wrong. It's so frequent it's no longer funny.
When you are rooted and have a custom recovery installed you need the full Ota zip file.
The incremental ota update won't work.
Snah001 said:
When you are rooted you need the full Ota zip file.
The incremental ota update won't work.
Click to expand...
Click to collapse
If you're telling me, then my device is unrooted, stock everything. Not just me, got another guy on the Shield forums saying the same thing hehe.....
on a side note, mine is a ROW LTE. Maybe those with wifi sets have better luck. But the other guy I mentioned has a wifi set, and it didn't work for him.
You have a custom recovery installed?
I search the full WiFi EU ROM. Can anybody help me
Snah001 said:
You have a custom recovery installed?
Click to expand...
Click to collapse
Stock EVERYTHING.
Have no intention to root this one because the battery replaced old version is already rooted.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
clawwulf said:
I search the full WiFi EU ROM. Can anybody help me
Click to expand...
Click to collapse
Be patient. It will come. many still asleep now.
When we have the full OTA zip then the link will be posted here immediately 4sure.
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
C'mon, RoW LTE version... can't wait
JohnK71 said:
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
Click to expand...
Click to collapse
You should be able to do a FULL OTA download, offload it - then TWRP it.
Once they post it on their site, we'll be able to flash it one way or another, just a matter of time. I'm disappointed it's only through the Mar update though...
Release notes here:
https://shield.nvidia.com/support/shield-tablet/release-notes/1
Incremental OTA works just fine on rooted tab + TWRP. Just keep in mind that it will replace your recovery for the stock one and you will loose root.
Worked fine for me. Completely stock.
Didn't work for me on stock row lte rom with multirom. Does go into mr twrp but fails install with an error 7.
Snah001's posting #24 of 2016.05.13.Fr.09:35 PM solved it all.
Before that, I ran into Failure as follows with "Upgrade" on my rooted RoW LTE.
< 1. > Hitting [[ Restart to install ]] made it into Team Win Recovery Project v3.0.0-0, where it logged the following :::
Running OpenRecoveryScript – Installing ZIP :::
Updating partition details » Done.
Full SE Linux support is present.
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file.
Skipping MD5 check : no MD5 file found.
:::
After that, I could reboot from TWRP, get another identical upgrade notification, and loop through as_many times as I'd like.
< 2. > Installing the upgrade manually from TWRP resulted in :::
Source : nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
Target : nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys
Verifying current system...
Package expects build fingerprint of :::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
or nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys;
this device has ::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_658.5732:user/release-keys
:::
Updater process ended with ERROR : 7
Error installing zip file '/data/data/com.nvidia.ota/app_download/PUBLIC92c9 4d59.zip'
Updating partition details » Done.
» Failed.
< 3. > Skipping all checks in OTA 4.1 LTE's "PUBLIC92c9fefb721b31eb2dc26fb6ac2b4d59.zip\META-INF\com\google\android\updater-script" seems no_good idea either, as I ended up without Notification Drawer and without Android Settings app. }} I had to restore a backup in TWRP to regain normal functionality.
Didn't manage to the OTA URL (somehow it's not showing in my logcat). But, I managed to grab it out and install manually with TWRP. Here it is:
Code:
https://mega.nz/#!XggijAhZ!Depd8u5nwMNt_wNcjbWmbT_6EGJB4OejmTv8eMSte9Y
EDIT: forgot to mention that this is the LTE ROW version.
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.
Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.
Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...
Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?
AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google
No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?
bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...
Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.
maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx
You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated
OK, thx :good:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Hub00 said:
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Click to expand...
Click to collapse
Try it once again... I've never received OTA updates from b560 onwards.. You could flash your way through
crashpoum99 said:
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Click to expand...
Click to collapse
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
You can try local update......And preferably Force update but it will delete all your data so backup your data And Force update........ Btw leave B584 because B588 is avaiable
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
I would try force updating using the Power+Vol.Up+Vol.Down method. Go for B588 if you want, as it's newer with the latest security patch. If the error comes after the reboot, it's most likely that force updating will fix this. Remember, force updating will delete your files!
What actually worked is downloading 'full package' in the update menu (the file was 1.56Go instead of 260 Mo). It updated overnight even with twrp. Of course, I lost gyroscope in the process...
So I'm know with B584. I will try to force update to B588 as soon as it is downloaded.
Ok, i'm know on B588 and I have gyroscope back again. Thanks for your help.
However, despite the changelog, i didn't notice any improvement with the whatsapp notifications.
Any idea why ?