trying to update my rooted nexus one, but it dose NOT go well for a few times. it got a following message;
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
how can i fix it?
thanks in advance.
When you say rooted do you mean there is a custom ROM installed? If so then you won't be able to update with an update file you will need to do is with a whole ROM file such as passimg. So check out passimg (look at my sig) then you should be prompted for an upgrade as soon as you boot up.
no, my one is just gingerbreaked. im trying to update it to 2.3.6 or 7.
thanks,
Rooted phone won't update.
you may or not update rooted phone. we all know that.
you may or not update a rooted phone. we all know that. i don't need this kind of reply. let me clarify my question.
E:failed to verify whole-file signature
E:signarure verification failed
Installation aborted.
what do these message mean? and can i fix it?
thx
The message is self-explanatory.
The file doesn't pass signature check.
Which means - it's either corrupted or wrong.
what you say is what the message say.
it won't be a solution.
ykom said:
what you say is what the message say.
it won't be a solution.
Click to expand...
Click to collapse
You're not asking the right questions we're only trying to help
Sent from my Nexus One using xda premium
Once u rooted ur phone, U can't simply update the OTA version... neither manually..
Now to update to the latest android official, U need to "UNROOT" ur phone first and then u'll get what u want. How to "unroot," Read 'Dude Random21's' Signatures.
U can't have an official android and custom ROM running simultaneously on ur phone
ykom said:
what you say is what the message say.
it won't be a solution.
Click to expand...
Click to collapse
The solution should be obvious:
Download the correct and non-corrupted update, and apply.
You're not giving any information about your error, besides the error itself, and expect the forum to help you. For example, if you're doing it through custom recovery which you installed instead of the stock Android recovery - it won't be able to read Google original update files, since they have different signatures, and you'll need to turn off the signature check in the recovery. On the other hand, if the message appears on stock recovery - it can only mean a corrupted or wrong download.
what obvious? you don't decide what i think. i would. please don't bother yourself. i think that i got a right rom update, and no corruption.
however, i agree that there is NOT enough info. please take a look at a screen shot. it has not received new autoupdate recently even when it is not rooted, so may try to get it manually.
what ota or any rom update anybody recommend? and address to get it.
thanks,
The reason is that you are not running stock Android. Your carrier has a custom version on there, so you will have to wait until they release an update for your phone (or you can use the PASSIMG method to possible get you back to stock Android).
Since you are not running stock Android (verified by seeing your build number... official builds from Google use a 5 character Build Version like GKW74), you cannot use the official updates files from google. They will show that the signatures do not match, because it isn't able to update a non-Google release.
thanks to bassmadrigal,
that is what i was guessing. so now i have a choice.
Related
I think it comes with 2.32.651.2 OTA update, which I can't do because on a Sense ROM, going to 'About Phone' > 'System Updates' > doesn't work for my situation.
Does anyone have this file? Or guide me on how to get PRI 2.65_003 manually (not OTA)?
Resolved!
0 - create backup
1 - install ClockWork 2.5.0.7 (#2 wouldn't install with my 3.0.2.4)
2 - install NFX Sprint 2.31.651.7 STOCK ODEX with A2sd Update3
3 - update PRL manually with ##PRL# (since ##PRL# is removed with #4, I think?)
4 - install OTA_HeroC_Sprint_2.32.651.2 (thanks to jasonmaloney) <~~~ this was my missing link
5 - install RegawMOD Hero Rooter v1.3 (to root/install clockwork 3.0.0.5)
6 - create backup of Sense rom
7 - restore back aospCmod!
...and wipe, wipe, wipe.
General consensus on this is you'll have to nandroid, run a RUU (.7), accept the 651.2 OTA, re-root (unless you're s-off ), re-flash your recovery and then restore nand backup.
I just googled "2.32.651.2 OTA update."
vayman said:
General consensus on this is you'll have to nandroid, run a RUU (.7), accept the 651.2 OTA, re-root (unless you're s-off ), re-flash your recovery and then restore nand backup.
I just googled "2.32.651.2 OTA update."
Click to expand...
Click to collapse
Thanks but like I said in the OP, I cannot 'accept the 651.2 OTA'. It fails, same with the PRL update.
wesssider said:
Thanks but like I said in the OP, I cannot 'accept the 651.2 OTA'. It fails, same with the PRL update.
Click to expand...
Click to collapse
Have you tried accepting the OTA while on the RUU or just on a rooted "Sense" ROM? If you haven't tried the RUU route it may be worth a shot. But as far as I know and as 24601 posted in the aospCMod thread, that 651.2 is only available OTA.
vayman said:
Have you tried accepting the OTA while on the RUU or just on a rooted "Sense" ROM? If you haven't tried the RUU route it may be worth a shot. But as far as I know and just as 24601 posted in the aospCMod thread, that 651.2 is only available OTA.
Click to expand...
Click to collapse
Again OTA's fail. I need to do it manually. Isn't the 2.32.651.2 OTA patch stored on the phone before its applied. If so, thats all I need.
wesssider said:
Again OTA's fail. I need to do it manually. Isn't the 2.32.651.2 OTA patch stored on the phone before its applied. If so, thats all I need.
Click to expand...
Click to collapse
Sorry to keep harping on the OTA, but you didn't mention that you tried RUU. So I'm just going to assume that you have. As far as the patch being stored on the phone, that I don't know. Maybe someone who knows will reply.
vayman said:
Sorry to keep harping on the OTA, but you didn't mention that you tried RUU. So I'm just going to assume that you have. As far as the patch being stored on the phone, that I don't know. Maybe someone who knows will reply.
Click to expand...
Click to collapse
Yes, I have tried RUU. It's all good, I appreciate your time looking into this for me.
wesssider said:
Yes, I have tried RUU. It's all good, I appreciate your time looking into this for me.
Click to expand...
Click to collapse
No problem man. Happy to help, and if I find anything I'll let you know. Not sure what nfinite is up to these days but as far as I know he was the only one that made a stock ROM based on 651.2. Maybe send him a PM and see if he can be of any help. May be worth a shot.
vayman said:
No problem man. Happy to help, and if I find anything I'll let you know. Not sure what nfinite is up to these days but as far as I know he was the only one that made a stock ROM based on 651.2. Maybe send him a PM and see if he can be of any help. May be worth a shot.
Click to expand...
Click to collapse
Good idea. Sent nfinitefx45 a PM.
wesssider said:
Good idea. Sent nfinitefx45 a PM.
Click to expand...
Click to collapse
I would also suggest you send member oostah a PM, he has all kinds of crazy stuff, like a verizon radio image, and a PRL from the evo - he knows how to do it manually (I think) and some good ones to try. I would HIGHLY recommend you get an unlocked bootloader - aka "s-off" - BEFORE you do this stuff.
il Duce said:
I would also suggest you send member oostah a PM, he has all kinds of crazy stuff, like a verizon radio image, and a PRL from the evo - he knows how to do it manually (I think) and some good ones to try. I would HIGHLY recommend you get an unlocked bootloader - aka "s-off" - BEFORE you do this stuff.
Click to expand...
Click to collapse
Hmmm, didn't think about oostah. Good suggestion Duce!
Definitely +1 on S-off too!
il Duce said:
I would also suggest you send member oostah a PM, he has all kinds of crazy stuff, like a verizon radio image, and a PRL from the evo - he knows how to do it manually (I think) and some good ones to try. I would HIGHLY recommend you get an unlocked bootloader - aka "s-off" - BEFORE you do this stuff.
Click to expand...
Click to collapse
Another good idea. Sent oostah a PM.
I'm s-off.
wesssider said:
Again OTA's fail. I need to do it manually. Isn't the 2.32.651.2 OTA patch stored on the phone before its applied. If so, thats all I need.
Click to expand...
Click to collapse
OTA_HeroC_Sprint_2.31.651.7_2.27.651.6_release5iou1d929vcwrqa7.zip
OTA_HeroC_Sprint_2.32.651.2_2.31.651.7_releasezkc856o9ps7466v8.zip
jasonmaloney said:
OTA_HeroC_Sprint_2.31.651.7_2.27.651.6_release5iou1d929vcwrqa7.zip
OTA_HeroC_Sprint_2.32.651.2_2.31.651.7_releasezkc856o9ps7466v8.zip
Click to expand...
Click to collapse
I just tried flashing the 2nd link, it tells me
E:No signature (175 files)
E:Verification failed
Is it because I'm using Amon_RA 1.7? I downgraded from CWM 3.0.2.4 just to flash nfx's stock 2.31.651.7 ROM
edit: is it meant to be flashed through fastboot?
tried it and it says FAILED (remote: 12 signature verify fail)
c00ller said:
I just tried flashing the 2nd link, it tells me
E:No signature (175 files)
E:Verification failed
Is it because I'm using Amon_RA 1.7? I downgraded from CWM 3.0.2.4 just to flash nfx's stock 2.31.651.7 ROM
edit: is it meant to be flashed through fastboot?
tried it and it says FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
These are the OTA updates you get when running stock. They're probably not going to work on other ROMs. They're signed by HTC, so you either need to use the stock recovery or turn off signature verification.
Resolved! Updated OP.
0 - create backup
1 - install ClockWork 2.5.0.7 (#2 wouldn't install with my 3.0.2.4)
2 - install NFX Sprint 2.31.651.7 STOCK ODEX with A2sd Update3
3 - update PRL manually with ##PRL# (since ##PRL# is removed with #4, I think?)
4 - install OTA_HeroC_Sprint_2.32.651.2 (thanks to jasonmaloney) <~~~ this was my missing link
5 - install RegawMOD Hero Rooter v1.3 (to root/install clockwork 3.0.0.5)
6 - create backup of Sense rom
7 - restore back aospCmod!
...and wipe, wipe, wipe.
Yeah, I dealt with this last night tho the only advantage to having the latest PRI/PRL for me seems to be that I can say I have them. I didn't go the same route exactly as you, I used ruu and then did an ota. However it does seem that the pri will not update unless you upgrade from the *.7 to the *.2, as I had flashed the .2 many times by itself.
~maybe I set it too high...
jasonmaloney said:
These are the OTA updates you get when running stock. They're probably not going to work on other ROMs. They're signed by HTC, so you either need to use the stock recovery or turn off signature verification.
Click to expand...
Click to collapse
How do I turn off sig verification?
How to find the stock recovery:
http://forum.xda-developers.com/showthread.php?t=897887
aiwetir said:
How do I turn off sig verification?
Click to expand...
Click to collapse
In ClockWork Recovery, choose install zip from sdcard > toggle signature verification?
wesssider said:
In ClockWork Recovery, choose install zip from sdcard > toggle signature verification?
Click to expand...
Click to collapse
Thanks! I found that but forgot to come back here and edit my post.
I just got a Google nexus one second hand with firmware version: 2.1-update 1 and build number assion-userdebug 2.1-update1 EPE55 26105 test-keys.
I've tried to update the firmware to 2.2 or 2.3 manually but none of the packages I've found worked. Installation aborts. I don't know if it's because of this weird build number...PLEASE I NEED HELP...I've googled and tried everything!! And nothing works.
http://forum.xda-developers.com/showthread.php?p=30111868
Sent from my Nexus One using xda premium
Okay, i refer to the other thread you gave me but i'm not sure if it will solve my problem. The question in the other thread is a bit different from mine...I do get the triangle in the exclamation mark..it's just that the packages i've tried does not want to install. I get two errors
E:Failed to verify the whole file signature
E:signature verification failed
Installation aborted.
did you follow all i said ?
normally it should work
Sent from my Nexus One using xda premium
No I have'nt tried it as yet...can you explain what passing.zip will do? And will the rom work regardless of my build number? I just want to know if it is safe...I don't to cause any damage to the phone. By the way..thanks for your responses.
Hey i downloaded the rom, i followed your instructions but nothing happened.
Then i tried to opened the zipped folder and could not. It says that the folder is either invalid or corrupted.
So i'm not sure if that's the reason why nothing happens when i load in the phone.
Try to download it again, or try this one (don't mind the RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release.exe).
I downloaded it twice already, and it said the same thing. The file is either invalid or corrupted. Thanks for your quick reply...I just really need this 2.1-update1 firmware to update. lol
Is the download you gave me, a .rar file? I've downloaded it..what to do next?
sheffdwayne said:
Is the download you gave me, a .rar file? I've downloaded it..what to do next?
Click to expand...
Click to collapse
Yes, it's a rar. Extract the PASSIMG_Passion_Google_WWE_3.10.1700.1_GRJ22_release_signed.zip, rename it PASSIMG.zip (make sure it's not PASSIMG.zip.zip - hidden extension) and copy it to the root of your µSD card.
Power off your Nexus One and then press power button + volume down. You will enter in bootloader and all you have to do is wait.
Okay, i went through all your instruction..but nothing happened when i went to the boatloader. I saw the sd checking, and at PASSIMG.zip, it says no Image!. I'm wondering if it's because my hboot is the older version. My version of Hboot is 0.33.2012 (PB9910000)
sheffdwayne said:
Okay, i went through all your instruction..but nothing happened when i went to the boatloader. I saw the sd checking, and at PASSIMG.zip, it says no Image!. I'm wondering if it's because my hboot is the older version. My version of Hboot is 0.33.2012 (PB9910000)
Click to expand...
Click to collapse
Measure its in ur main SD dir so it can pick it up.
Sent from my Nexus One using Tapatalk 2
Yes it's in my main Sd card. But it still doesn't pick up. I don't know why.. I don't know why my N1 refuses to update.
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
mystborn said:
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
Click to expand...
Click to collapse
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
mystborn said:
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
Click to expand...
Click to collapse
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
nkk71 said:
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
Click to expand...
Click to collapse
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
mystborn said:
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
Click to expand...
Click to collapse
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
nkk71 said:
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
Click to expand...
Click to collapse
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
mystborn said:
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
Click to expand...
Click to collapse
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
nkk71 said:
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
Click to expand...
Click to collapse
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
mystborn said:
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
Click to expand...
Click to collapse
That did the job, now I am running 4.3
mystborn said:
That did the job, now I am running 4.3
Click to expand...
Click to collapse
Congrats mate, I thought I saw an earlier post with something like "OTA Check Tool"? What's that?
Anyway, glad it worked out :good::good:
You may want to change the main thread title to include [SOLVED] for other to know
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
mystborn said:
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks, I'll check that tool out when I get a chance, but like you said, it doesn't seem very accurate (at least yet).
And yes, I do believe you had an interesting approach at flashing an OTA
Can anyone help me? There is a problem with my update center app. I dont know the time when my phone or update center app became like this. I just want to update my kitkat to lolipop, but when I do that, my app wont start the download
1. I open my update center app
2. Open software update
3. Click on "Continue Update"
4. A black mini box show up that say " new update is downloading. Check in notification panel"
5. Checking my notif panel and I got nothing
SS on atachment
Please help meee
Sory for bad english
Click to expand...
Click to collapse
PROBLEM SOLVED GUYS
No need to flashing, just connect to computer, use lg mobile tools, then update through computer,,
Im really happy, I have lollipop now, thanks for the suggetion btw
Did you modify your phone in any way? It is or was rooted?
Anyway, you can either install Lollipop via KDZ (I am not sure if it update your system or make a "clean install" instead, install a fresh system and delete your data). Or you can install Kitkat stock ROM via KDZ and then apply OTA update, if you prefer (same remark as above applies).
lfom said:
Did you modify your phone in any way? It is or was rooted?
Anyway, you can either install Lollipop via KDZ (I am not sure if it update your system or make a "clean install" instead, install a fresh system and delete your data). Or you can install Kitkat stock ROM via KDZ and then apply OTA update, if you prefer (same remark as above applies).
Click to expand...
Click to collapse
No, im not so interest with root, so i never do that
Yeaa, its says that many people prefer flashing to updrage but I will use it when I very frustrated with this things
Install Kitkat stock ROM via KDZ? How to do that? Is it also flashing?
Sorry, what "same remark as above applies" means? *not to good in english
optrune said:
No, im not so interest with root, so i never do that
Yeaa, its says that many people prefer flashing to updrage but I will use it when I very frustrated with this things
Install Kitkat stock ROM via KDZ? How to do that? Is it also flashing?
Sorry, what "same remark as above applies" means? *not to good in english
Click to expand...
Click to collapse
Try using CCleaner to perform cleanup of junk files that often remain in the space meant for the update. Just a guessing here, no guarantees that it'll work, but you have nothing to lose. Needs no root. So give it a try.
problem solved guys, thank youu
Hello!
I have a Huawei Mate 9 (MHA-L29C432B190). Yesterday I tried to root my Phone to play Pokemon Go with fake gps. After I managed to root my phone, I couldn't boot into TWRP Recovery Mode anymore.
Because I still had some files I needed to flash I installed Flashfire from the PlayStore. I think after I flashed the newest Magisk version(The flash failed because of Error:1), my device got unrooted. But I think my device is still partly rooted because I can't get into Pokemon Go. Everytime I try to start it I get stuck the loading screen. So right now I can't flash anything to get my root back and I don't have the root to use alternative flash applications. I also tried to start return my phone to stock back with a update.app But it can't be installed. I also can't use "fastboot flash recovery twrp.img" I always get " Writing 'recovery'...FAILED (remote:command can't be used/allowed)". And also after some reboots my oem unlock got turned off and I can't turn it on anymore.
I don't have any ideas anymore what to do. I thought I could root my device, so I could unroot properly with superuser. I tried some other application like KingRoot oder OneClickRoot but both of them don't have a rooting method for the Huawei Mate 9 yet. Btw I don't have a backup because of my naivety.
I hope you guys can help me . I appreciate any ideas
Thanks in advance
In summary what do u want???
Sent from my iPhone using Tapatalk Pro
abuk91 said:
In summary what do u want???
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.
Kyranix said:
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.
Click to expand...
Click to collapse
Do a Google search for:
"Return to stock (your model number)"
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work
Kyranix said:
Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work
Click to expand...
Click to collapse
What did you find? What have you tried?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model
Kyranix said:
What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model
Click to expand...
Click to collapse
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)
Kyranix said:
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)
Click to expand...
Click to collapse
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.
Kyranix said:
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.
Click to expand...
Click to collapse
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
And can you please tell me how to do it then. You can also send me a guide
Kyranix said:
And can you please tell me how to do it then. You can also send me a guide
Click to expand...
Click to collapse
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda
Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck
Kyranix said:
Well thats because I already had problems to post this thread because I am new to xda [emoji14] But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck
Click to expand...
Click to collapse
Even new members(less than 10 posts) can post in device specific Q&A fora, new members are only blocked from posting in "development" fora and threads.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE