Related
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Experienced all. Tsk. Should have stayed away from the Marshmallow upgrade thread.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Uh-oh... Another Mate 7 phone bricked by the Marshmallow beta B511 update...
I guess you'll just have to wait for the full official marshmallow update (no longer beta) for your TL09 phone for your region, or at least, wait for the official TL09 marshmallow to lollipop downgrade package for your region. When Huawei releases one or both, then you can install one or both via forced update (power + volume up + volume down) and have a functioning phone again.
For now, there's nothing you can do but wait and wait... unless you know your way around rooting, unlocking bootloaders and custom ROMs. There are actually quite a lot of Mate 7 owners in the similar situation as you. If only you can BAND together with a common cause/objective, your 'bricked by Marshmallow B511' group could somehow be a FORCE to reckon with that Huawei cannot ignore. Your group can petition Huawei with emails to release at least the 'marshmallow to lollipop downgrade package' for other non-China regions NOW, or the EARLIEST humanly possible...
You may want to read other users similar experiences with their bricked mate 7 phone (by installing the beta marshmallow b511 update) here: http://forum.xda-developers.com/mat...-marshmallow-b511-t3304178/page2#post65176950
It will make you feel much better knowing you are not alone. Alternately, you can just vent out your frustrations to Huawei in another thread. Not sure if its allowed in XDA though.
Those with bricked mate 7 phones:
Can you try and see if this suggestion works?
=========== (quoted from http://www.carbontesla.com/2016/01/download-ascend-mate-7-b511-marshmallow-ota-zip/) by wissam marrash
wissam marrash • a day ago
Guys I have mt7-l09 and its working with marshmallow, yes it drains more battery and some lagging in some areas but this should happen because its a beta and incremental release. For people who got spoil their phone while installing, you should read the requirements very well before downloading this rom. Its clearly mentioned for B326 and for un-rooted phones. so before you install you should install the B326 (you can download using this link: http://m.huawei.com/pkmobile/c... make sure to choose mt7-l09 or mt7-l10 and after installing the B326 install marshmallow beta.
For people who wants to downgrade, yes you can but you have to choose a full release like the B326-B327-B328.
N.B. ONLY Marshmallow BETA rom, Don't unzip the after downloading, its not like the other updates. You should copy the zipped file as is to inside "dload" folder.
Just a tip, some releases are not supporting 4G lte especially when it marked Europe.
For people who keep rebooting, try to connect you phone to pc or take out the memory card and use card reader and access your files and then delete the files from the "dload" folder and then download using your pc any full release rom (b326 or b327 or b328) and extract it and then copy the "UPDATE" file to the dload folder and then turn off the phone and then boot your phone while holding Vol up + Vol down + Power buttons at same time to automatically trigger the update installation and should go smooth.
Hope my comments will help
==============
Here are the links to full ROMs:
TL10: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62450&key4=MATE7
L09: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62371&key4=MATE7
reboot
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
maksudbek said:
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!
Just wondering if I'll be able to take an OTA update from 6.0 to 6.0.1 whenever it is available? I received a message saying a software update was available and when I told it to install it, it rebooted into TWRP, checked the current software for about 3 minutes, then rebooted? Upon looking, I am still on 6.0? I had the system check to see if there was still an update available, but it said there was nothing. Maybe it was just a radio update? I am anxiously awaiting the update so that I may install Xposed. Any input would be greatly appreciated :good:
AT+T US Unlocked
Rooted/S-off
6.0
1.10.502.3
You can't take OTAs with rooted phones and twrp. The OTA looks at the system partition and if anything is changed...it will not install.
You have to either take a backup somebody made with the OTA/stock basically. Flash it via TWRP. Or RUU back to the lastest for your phone. Then, take all OTA updates, then TWRP, Format Data, then SuperSU again, reboot...start/restore phone.
There is no easy way without Dev support/Custom Roms to get latest bases/OTAs right now without wiping/starting over somehow.
This is why having devs creating Roms is really a luxury. Because they already have the proven installer/Rom customized. They will then take OTAs/new bases, roll that into their Rom, and you just do an update/flash, like Viper, and not lose anything, and no need to wipe.
Likely never to happen with this phone since Devs really only work on the Mainline/Flagship M models, like M8/M9/M10 etc...
I just rooted my Honor 8 running B360 and was successfull. But apparently there are some strange things, for example, the settings menu to configure the smart key is gone. Also, I noticed something strange when I went into my build.prop to get the Google Assistant. The line ro.build.tags is set to test-keys, which was in my build number when I ran into some problems while rooting. Is this right or should this be something else? Also ro.build.description includes NRD90M test-keys which was the exact build number when I ran into these problems. This sounds strange as my current build is FRD-L09C432B360..
I ran into that issue when I tried to install nougat for the first time, basically, stuff is missing, and I'm not sure why.
The solution is a long one unfortunately.
You'll have to reflash the update.app from a marshmallow version (the only full one I found for my device was b162. Make sure it's full so you miss nothing.)
Then use the Charles update method, or just wait until the update rolls out and do the normal update, don't root it and install twrp, because it will not install properly.
Then you should be on nougat and good to go.
I have yet to root on nougat, because I'm waiting to see if they'll roll out any patches for small bugs, and waiting to see if a better root method is released.
Good luck either way!
SolarisSixth said:
I ran into that issue when I tried to install nougat for the first time, basically, stuff is missing, and I'm not sure why.
The solution is a long one unfortunately.
You'll have to reflash the update.app from a marshmallow version (the only full one I found for my device was b162. Make sure it's full so you miss nothing.)
Then use the Charles update method, or just wait until the update rolls out and do the normal update, don't root it and install twrp, because it will not install properly.
Then you should be on nougat and good to go.
I have yet to root on nougat, because I'm waiting to see if they'll roll out any patches for small bugs, and waiting to see if a better root method is released.
Good luck either way!
Click to expand...
Click to collapse
Before you answered here, I tried to reflash update_data_full_hw_eu.zip and then boot, but it was stuck at the Honor logo. Then I rebooted into TWRP and install both update.zip and update_data_full_hw_eu.zip. I was again stuck at the Honor logo, but after booting into the stock recovery and doing a factory reset the phone booted as clean in B360. Then I spent litterally 5 minutes rooting with TWRP and phh's SuperUser. (http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/) I now have root on Nougat, and I have not seen any features missing yet. It still says NRD90M and test-keys all over my build.prop but I guess that is supposed to be there.
FreeLineTM said:
Before you answered here, I tried to reflash update_data_full_hw_eu.zip and then boot, but it was stuck at the Honor logo. Then I rebooted into TWRP and install both update.zip and update_data_full_hw_eu.zip. I was again stuck at the Honor logo, but after booting into the stock recovery and doing a factory reset the phone booted as clean in B360. Then I spent litterally 5 minutes rooting with TWRP and phh's SuperUser. (http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/) I now have root on Nougat, and I have not seen any features missing yet. It still says NRD90M and test-keys all over my build.prop but I guess that is supposed to be there.
Click to expand...
Click to collapse
I might give this a go - do you know which update.zip and eu you flashed? I have heaps of different versions
JoshSnitz said:
I might give this a go - do you know which update.zip and eu you flashed? I have heaps of different versions
Click to expand...
Click to collapse
This is a very old thread..
I picked up two Honor 6X BLN-24 models, the serial numbers are within a couple hundred of each other, so I'm assuming they're from the same batch. Right now they're both on Nougat, but one looks like it has a partial install of Nougat and the other has a "normal" install. Here's what happened:
1) The partial install phone - I unboxed it, connected it to WiFi, did a check for updates; it found the Nougat update, so I let the system update itself, rebooted, had Nougat B360. Flashed TWRP, which is working fine on the phone.
2) The "normal" install phone - instead of updating straight to Nougat, I installed TWRP first and had a bunch of issues with the wrong TWRP .img file; that's a separate issue. Got Nougat installed eventually on the phone but ended up with the "Test Keys" build issue. Ended up doing the rollback to MM, then did the check for updates, it found the Nougat update and I let it install. Phone has Nougat, build shows as B360.
Thought everything was fine and didn't really take a good look at the phones since I had to do other stuff to do before migrating to the Honors.. Now I'm ready and I'm noticing that one phone - the one that went to Nougat straight out of the box - doesn't have a bunch of apps that the second phone has, like the FM radio, CNN, Lyft, News Republic. Outside of the FM radio, I don't care about the other apps, but something else is missing - the System Update option in Settings. There may be other stuff missing, but the System Update thing is problematic.
So I figure my options are:
1) Rollback the phone that's missing things to MM, then retry the update, or
2) Try a dirty flash of the Nougat B360 update and data files.
3) Flash the smaller update_data file for the B360 build that contains most of the apps (but doesn't look like it has the FM radio)
Or is there another option?
Go with option 2. If no success then I would suggest for option 1.
Need couple of favours as you did rollback. Do you have the rollback package file? If yes, please share.
If you are rooted, use Huawei mutli tool and backup the oeminfo file. I need both these files so that if anyone messed up with their phone we will be able to revive and also address the nrd test keys issue and the best we can do is to debrand from other variant to US variant.
Thanks beforehand.
I had similar issues my phone was showing as nrd test keys and the backup of twrp also indentify phone as nrd test keys. When I checked updated update it was showing no update. My phone wassoft bricks so i download and updated package for build no b 340 and in build no it was showing nrd test key
Later i flashed zip shared in volte fix thread on xda as I was not having volte.
After flashing all thing went good test key issues resolved also so u can try that zip also.
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
You can use it if it matches with your last build no
WetWilly said:
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
Click to expand...
Click to collapse
Thanks downloading now. Yes then you can use this file for rollback.
Here's the latest update. - I tried the dirty flash method and it wouldn't work. AT ALL. I'm getting the "software failed update" at 5% message that several others have received. I downloaded the BLN-24C567B360 FullOTA package from three different sources; all had the same hash and *none* of them would work using the dload method. I ended up flashing the MM rollback package (which worked perfectly via the dload method) then flashed the MM firmware (also worked perfectly using the dload method). The phone booted into MM, it found the 2.35GB Nougat update (which is the same size of the Nougat .zips I downloaded), and it installed the update. It also installed the FM Radio (a system app) and the US package of apps that for some reason it didn't install when it upgraded to Nougat fresh out of the box.
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash. Thankfully the rollback worked. FYI, rolling back to MM relocks the bootloader. At this point I'm just keeping both the rollback and MM packages saved together on an SD card; flash rollback, pop card, rename folders on PC, pop card back in 6X, flash MM, reboot, find update, OTA to Nougat. Easier done than said, actually.
I am curious about why none of the B360 Nougat update.app files will flash on either phone. I don't think it's coincidental because the e-Recovery via WiFi doesn't find a package, and if I try System Recovery in HiSuite it says "no recovery available; take device to a Service Center".
WetWilly said:
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash.
Click to expand...
Click to collapse
If you get this issue again, try to format data inside TWRP.
itisiryan said:
If you get this issue again, try to format data inside TWRP.
Click to expand...
Click to collapse
I actually tried that. I ran into this same issue previously when I had TWRP installed, and TWRP's wipe data didn't work. Ultimately had to do the rollback to MM/roll-forward to Nougat and re-unlock the bootloader.
I can't figure out why my two phones won't flash Nougat using the dload method. The only logical reason is the upload.app file signatures, but I haven't found any alternative Nougat files for BLN-24C567B660.