Related
I have an AT&T N1 that I bought second-hand a few weeks ago:
Android version 2.3.3
Baseband version 32.41.00.32U_5.08.00.04
Build number GRI40
There is no "lock" at the bottom of the screen when I boot the phone.
I have not received the OTA update to 2.3.4. I have tried the "checkin" procedure, but nothing. Menu/About phone/System updates says "Your system is currently up to date."
I followed widely available directions to manually upgrade to 2.3.4, but it didn't work. I saw several messages, ending with:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
After reading through other threads, I am starting to think that I have a ROM that is somehow not stock or is carrier specific. Is my thinking right?
At this time I just want to get the regular, stock updates. Should I follow the directions in other threads to restore my phone to stock in order to get the regular stock updates?
A little more info:
Kernel version 2 [dot] 6 [dot] 35 [dot] 7 [dash] 59423 [dash] g08607d4 android [dash] build [at] apa28 #1
Follow the "Using PASSIMG.ZIP method" guide in the following link to bring the phone back to FRG83 (Android 2.2.1). After reboot, you should get the 2.3.4 update.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
mwandaw said:
I have an AT&T N1 that I bought second-hand a few weeks ago:
Android version 2.3.3
Baseband version 32.41.00.32U_5.08.00.04
Build number GRI40
There is no "lock" at the bottom of the screen when I boot the phone.
I have not received the OTA update to 2.3.4. I have tried the "checkin" procedure, but nothing. Menu/About phone/System updates says "Your system is currently up to date."
I followed widely available directions to manually upgrade to 2.3.4, but it didn't work. I saw several messages, ending with:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
After reading through other threads, I am starting to think that I have a ROM that is somehow not stock or is carrier specific. Is my thinking right?
At this time I just want to get the regular, stock updates. Should I follow the directions in other threads to restore my phone to stock in order to get the regular stock updates?
Click to expand...
Click to collapse
How are you trying to flash the update manually? Do you have a custom recovery? If so, you need to turn signature verification OFF...
Unfortunately, I cannot include links to outside websites in my replies. However, I can tell you that there are instructions on AndroidCentral [dot] com to manually update. The name of the post or article is "Nexus One's Android 2.3.4 update is here; we've got your update instructions".
Basically, the article has a link to a zip file with an awfully long name. I'm supposed to rename that to update [dot] zip and move it to the SD card in my phone. Then I'm supposed to get into the bootloader, select recovery and eventually select Apply sdcard:update [dot] zip. I did all of that without any trouble, but then I got messages below:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
I tried turning off signature verification, but then the error message said something about a missing file.
I would be glad to wait for the OTA update, but at this point (three weeks since the announcement) I doubt that it will happen.
I would appreciate any advice.
What is the error about the missing file? Because assuming you just have a stock install, it should work fine. If you don't have a stock install and your carrier put a custom version on there, you won't be able to update using this. You would either have to do the passimg method mentioned above which will put you to the stock firmware and you should then be able to receive the update.
Otherwise, you will have to wait until your carrier comes out with an updated version.
It Worked!
I followed the "Using PASSIMG.ZIP method" guide recommended by madballs. It worked quickly and easily. About ten minutes after installing the stock Android 2.2 I received a message that a system update was available, and 2.3.4 installed without any trouble.
Hopefully, from now on I'll receive updates OTA quickly and without hassle.
Thanks!
mwandaw said:
I followed the "Using PASSIMG.ZIP method" guide recommended by madballs. It worked quickly and easily. About ten minutes after installing the stock Android 2.2 I received a message that a system update was available, and 2.3.4 installed without any trouble.
Hopefully, from now on I'll receive updates OTA quickly and without hassle.
Thanks!
Click to expand...
Click to collapse
You should not run into any problems from now on. When the next update comes, you can apply it manually or wait for the OTA. In addition, if at any time you try rooting your phone and flash a custom recovery and ROM, you can always use the PASSIMG method to go back to completely stock. There is a thread in the development section that linked a PASSIMG.zip file for to go to 2.3.4 directly. Never tried that file myself though. Enjoy your N1!
http://forum.xda-developers.com/showthread.php?t=1094018
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
nazeer786 said:
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
Click to expand...
Click to collapse
first read this post so you understand how ota update works
Unlocking the bootloader wipe /data partition including preloaded htc app in /data/preload. In some ota updates, these app are patched. If the updater script of the ota can't find these files (or they don't match because they were modified) the ota installation will abort --> red triangle.
Same for the thousand of system files, if some are missing or modified, ota installation will abort.
You need to know which file(s) is causing the ota install to fail. See this post how to find which file is missing or have unexpected content.
then you need to find each missing/modified files and push them to the right location and setting permission correctly (rw-r--r--).
i.e if the updater script reports (from stock recovery):
Code:
check /data/preload/calculator.apk failed, error, No such file or directory ()
calculator.apk is missing
this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
i.e if the updater script reports:
Code:
"/data/preload/calculator.apk" has unexpected contents
calculator.apk have unexpected content (corrupted or modified file)
in this case again this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
you must do it for all files that are causing the ota installation to fail
or in some cases, it will be simpler just to use a ruu, a guru reset rom or a nandroid backup to restore your phone and then do the ota update.
or you can use a custom rom with latest version.
Thanks alot
alray said:
first read this post so you understand how ota update works
Unlocking the bootloader wipe /data partition including preloaded htc app in /data/preload. In some ota updates, these app are patched. If the updater script of the ota can't find these files (or they don't match because they were modified) the ota installation will abort --> red triangle.
Same for the thousand of system files, if some are missing or modified, ota installation will abort.
You need to know which file(s) is causing the ota install to fail. See this post how to find which file is missing or have unexpected content.
then you need to find each missing/modified files and push them to the right location and setting permission correctly (rw-r--r--).
i.e if the updater script reports (from stock recovery):
Code:
check /data/preload/calculator.apk failed, error, No such file or directory ()
calculator.apk is missing
this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
i.e if the updater script reports:
Code:
"/data/preload/calculator.apk" has unexpected contents
calculator.apk have unexpected content (corrupted or modified file)
in this case again this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
you must do it for all files that are causing the ota installation to fail
or in some cases, it will be simpler just to use a ruu, a guru reset rom or a nandroid backup to restore your phone and then do the ota update.
or you can use a custom rom with latest version.
Click to expand...
Click to collapse
Thank you , I will look at the options above , I just have one more question , I read somewhere that ota's are most of the time just patch files , so is it possible that probably later on there is a whole new system update , not patches , if that's the case then I suppose the ota will not look for any modifications as it will simply just install the new version ?
nazeer786 said:
Thank you , I will look at the options above , I just have one more question , I read somewhere that ota's are most of the time just patch files , so is it possible that probably later on there is a whole new system update , not patches , if that's the case then I suppose the ota will not look for any modifications as it will simply just install the new version ?
Click to expand...
Click to collapse
ota updates always patch existing files. If you want to do a full installation, you might want to use a RUU.
nazeer786 said:
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
Click to expand...
Click to collapse
Try this stock Rom http://forum.xda-developers.com/showthread.php?p=53773615#post53773615
Thanks for this , I will try this Rom out , but first I will have to install a custom recovery
Sent from my HTC One using XDA Free mobile app
nazeer786 said:
Thanks for this , I will try this Rom out , but first I will have to install a custom recovery
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
if you choose to flash a rom, I recommend you to use twrp recovery version 2.6.3.3. older version don't work with newer rom, and newer version of twrp have some bugs, so better to use 2.6.3.3
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Hardley97 said:
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Click to expand...
Click to collapse
Here's my advice, go back to stock again,the LG flash tool. When that completes, use Freedom Tools (its in Development) and use ioroot25 (link is in the aforementioned thread) to root device. Then use Freedom Tool to install twrp. I've used it many times and never had a problem. Re-download cm rom (perhaps bad download) and flash in twrp. I would suggest using a more current twrp (start with 2.7, DL newest twrp, flash, reboot recovery) then flash cm. Let me know how it goes!
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Hardley97 said:
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Click to expand...
Click to collapse
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
njstein said:
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
Click to expand...
Click to collapse
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Hardley97 said:
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Click to expand...
Click to collapse
Dude, I'm sorry for not reading closer to begin with, but ya, you're trying to flash a JB rom with a KK recovery. 2.7 and up are for kk only. I'm so sorry...
Did you flash a gapps zip with Beanstalk? Did you do a completely clean install?
If you still want to flash a 10.2 cm you're going to have to find the appropriate recovery, and there I'm of no use since I entered this phone on kk and don't know anything about its jb history. Also don't know about the USB tether part either (I don't use it) so you're probably going to have to do some searching, flashing, and experimentation.
But bright side is we've figured out why you couldn't flash the cm rom. Either stay on kk or above, or start scrolling through the dev section looking for jb recovery...
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Hardley97 said:
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Click to expand...
Click to collapse
So glad it worked for you and you're up and running!
Nah, bro, I'm good. Give it to the devs, they deserve it. Giving knowledge through experience is what xda is all about, pass it on when you can. Thank you, though!
Android newbie trying to do a 6.20.651.3 update on a HTC One M8 Sprint variant. I’ve tried the direct download method, I get to 1.06gb, download successful, verified, unzipping update then reboots and flashes up some errors and goes into TWRP recovery.
I have also had a few goes at it from Windows running RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.EXE that fails as well with an error 155: unknown error: cannot update Android phone, please get the correct ROM update utility and try again or just hangs there on 0% for 30 mins.
Device has s-off and is rooted - at least Root Checker app says it is but it can also report not properly installed. I've just tried the direct download method once more having used the Root Check app to confirm that it is rooted but with same result.
Can anyone give me a few pointers in terms of what I have to do to get this to work. Help much appreciated.
You won't be able to take the OTA update with TWRP installed. As for running the latest RUU, you have to have the latest firmware installed first. You'll also need the latest version of TWRP if you want to flash a MM ROM. Check OMJ's RUU thread in Android Development for more info.
An alternative to taking the OTA or running the RUU would be to update your firmware & TWRP recovery, then flash a stock rooted MM ROM.
Thanks for your response. It has given me some understanding of the different types of update. I checked my TWRP and it is 2.8.7.0, which is the latest, and tried a firmware update using the firmware update utility from here
http://forum.xda-developers.com/showthread.php?t=2729173
and downloaded one of the non-Harman extracted firmware versions, renamed to rom.zip, put it in required folder and ran ARUWizard.exe and it is stuck on updating (0/1) sending, has been for 15 mins so I can assume that this will not work.
Any ideas? There are four variants: full, full signed, with / without recovery, boot. Am I running the wrong firmware?
Download the modified MM firmware (no boot or recovery) and place it on your external SD card and rename the file 0P6BIMG.zip (make sure the file doesn't have an extra .zip extension on the end). Reboot to the boot loader and update your firmware when prompted. As for TWRP, there is a newer version available. Check the last couple of pages of the TWRP thread in Original Development. It's version 2.8.9.0.
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
mp
check your mp
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Download the file linked below. Once you've done that, click the link in my signature for the M8 hboot guide. Scroll down to the section on firmware updates (it's in the very first post) and follow my instructions in my guide to update your firmware.
https://www.androidfilehost.com/?fid=24391638059059964
So im currently trying to unlock my bootloader and i now have the permission from Xiaomi. However i can't flash any of the developer roms, not through the useless updater app no matter what version i try or what name i give the file. It just says "Can't verify update" and then there's nothing more to it. It appears there are no other methods so what exactly am i doing wrong?
Download the latest global dev rom and update it from updater app...
It will wipe all data including internal...
Then try to unlock...
I also had this problem when I wanted to flash another MIUI ROM. Use the fastboot method as described here: http://en.miui.com/a-234.html
This has worked for me.
Same here, but mine does not even want to fast boot. Feels as if I'm stuck with this stupid Miui 7 version.
TROiiDA said:
So im currently trying to unlock my bootloader and i now have the permission from Xiaomi. However i can't flash any of the developer roms, not through the useless updater app no matter what version i try or what name i give the file. It just says "Can't verify update" and then there's nothing more to it. It appears there are no other methods so what exactly am i doing wrong?
Click to expand...
Click to collapse
Have you used the Mi Unlock tool to unlock your bootloader before you tried flashing the update?
I start updating global beta miui 9 on Redmi 3s prime through updater app its start decrypting and finally it said your data will erase as i forgot to make backup i cancel it...after making backup when i started again it said cant verify package ..plzz help me