I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time
SonicAndreev said:
I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time
Click to expand...
Click to collapse
Try installing the stock rom clean. It might help.
Shubho20 said:
Try installing the stock rom clean. It might help.
Click to expand...
Click to collapse
I have already tried. It doesnt help.
SonicAndreev said:
I have already tried. It doesnt help.
Click to expand...
Click to collapse
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.
ConradP said:
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.
Click to expand...
Click to collapse
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...
SonicAndreev said:
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...
Click to expand...
Click to collapse
This phone is harder to master with custom roms then my previous LG G2.
ConradP said:
This phone is harder to master with custom roms then my previous LG G2.
Click to expand...
Click to collapse
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.
SonicAndreev said:
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.
Click to expand...
Click to collapse
Yes, I totally agree.
And I am waiting for the Nougat release - after the beta I am missing some options - like dualscreen.
hey bro just unlock bootloader....(because this error for only bootloader lovked)
sahildutt said:
hey bro just unlock bootloader....(because this error for only bootloader lovked)
Click to expand...
Click to collapse
What? Explain your problem more.
Related
Hello guys.
I recently upgraded from EVA-AL10C00B195 to Nougat Beta B322 It was probably for L29. But after upgrading, there isn't a camera app and google apps do not work. So decided to go back to stock MM rom but I cant install TWRP and root the phone. I have a full TWRP backup of the phone from before upgrade. Is there a TWRP for P9 on Nougat?
I don't mind the data on the phone, is there a way for me to go back to stock rom? Any help would be appreciated. Thanks!
You need to grab a full marshmallow stock rom,unzip it to the dload folder on the external sd card(it should contain an update.app file).
Then hold down both volume keys and power button and it should reflash stock rom and bootloader.
I tried that with EVA-AL10C00B183 FULL rom.
At 5% it gives error:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Would've been great if it worked this way. Anymore ideas?
It looks like you downloaded an update package and not a full rom
nuttzo33 said:
It looks like you downloaded an update package and not a full rom
Click to expand...
Click to collapse
It was a full rom package. Which one do you recommend? I will try that. http://hwmt.ru/oth/HWFF/info/view.php?find_model=EVA-AL
n0my said:
It was a full rom package. Which one do you recommend? I will try that. http://hwmt.ru/oth/HWFF/info/view.php?find_model=EVA-AL
Click to expand...
Click to collapse
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-eva-al10-b161-t3418276
nuttzo33 said:
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-eva-al10-b161-t3418276
Click to expand...
Click to collapse
Same error as before:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Hmm,Im not sure,it should work.
Try
1.Factory reset of the phone through the main menu and not through twrp.
2.Make sure you have the right rom in the dload folder on the external sd.
3.Make sure you don't have a dload folder and rom anywhere else like the internal memory of the phone.
4.If that fails try relocking the bootloader if it's unlocked and try again.
If that doesn't work then I don't know what it is,maybe try signing up for the beta and see if you can get another update which has a functioning keyboard.
Factory reset fails everytime. But when the phone boots up, the settings are reset. I don't have twrp after the nougat update.
The rom was in external sd inside dload folder.
There isn't a dload folder anywhere else apart from external sd that contains the stock rom linked.
I've unlocked the bootloader and it's the same result.
Where can i sign up for the beta? I don't think there will be beta for chinese AL10 rom.
Here you are:
http://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091
Thanks for the help guys but non of this worked for me. I kinda bricked it.
I went ahead and spent a lot of money on DC-Unlocker. It basically formatted the phone and flashed a small factory image. After that, the instruction said I needed to install a full stock firmware for the phone. After which I had to repair the IMEI and also had to get it SIM unlocked even though my phone was factory unlocked.
It costed me 15 euros for formatting and flashing factory firmware. Plus 8 euros to repair IMEI. Plus 4 euros to get SIM unlocked. Total: 27 euros! Now I am back to stock rom with everything stock and working.
Moral of the story, don't install nougat beta if it isn't for your phone. EVA-AL10 in my case. Just wait for your turn.
n0my said:
Hello guys.
I recently upgraded from EVA-AL10C00B195 to Nougat Beta B322 It was probably for L29. But after upgrading, there isn't a camera app and google apps do not work. So decided to go back to stock MM rom but I cant install TWRP and root the phone. I have a full TWRP backup of the phone from before upgrade. Is there a TWRP for P9 on Nougat?
I don't mind the data on the phone, is there a way for me to go back to stock rom? Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
n0my, please have a look at my thread that I just closed off: http://forum.xda-developers.com/p9/help/issues-twrp-root-access-flashing-t3509877 I had the exact same problem, but I'm all good now!
i cannot find rollback package for eva-al10, this ****ing variant make me mad, goddam huawei, no more phone from this brand from now on.
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
Here's my situation:
My phone's original build number is VTR-L29-C63C6 but I flashed the Oreo update for European units which is 8.0.0.046(01BN). So there are quite a few features that's not working for me and I wanted to flash my region's update instead. But whenever I'm on the process of having the TWRP installed, I always get an error message saying: FAILED (remote: partition length get error). Currently stuck due to this. I hope someone could help me out here on how I could flash the TWRP again on my phone. Would really appreciate it. Thank you!
Rb101093 said:
Here's my situation:
My phone's original build number is VTR-L29-C63C6 but I flashed the Oreo update for European units which is 8.0.0.046(01BN). So there are quite a few features that's not working for me and I wanted to flash my region's update instead. But whenever I'm on the process of having the TWRP installed, I always get an error message saying: FAILED (remote: partition length get error). Currently stuck due to this. I hope someone could help me out here on how I could flash the TWRP again on my phone. Would really appreciate it. Thank you!
Click to expand...
Click to collapse
Ok PM AND I'll help you
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
It works on the Android O build here:
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
I have a similar problem.
I had VTR-L09C02B159 which I've rooted and tried to put the VTR-L09C900B311 Oreo on. Due to inexperience I've ended up with 8.0.0.046(01BN) version I don't know how to get rid of.
After a lot of searching I've managed to put TWRP back on using the method quoted above but I'm stuck here.
Ideally, I'd like to rebrand my phone to C432 and I'd be happy to rollback to Android 7 for now. I feel like I could rollback if I was on C432, or rebrand if I was on Android 7, easily, but no clue how to do both. Any ideas how to proceed?
Thank you
Hi guys,
I have a sunmi v2 android PDA, and i want to remove blocked OS.
I can't find bootloader, or i dont know how to enter on it, also i want to install a recovery mode to flash a new ROM.
Someone can help me please with this problem?
Thank You.
Hi, I have the same problem. Did you find a way to do it?
Can you tell me please?
Thank you
I have V.1.. Firstly, are you guys able to allow installation of apps from "Unknown Sources"?
Just wondering if you ever managed to load android onto the V2 and remove the Sunmi OS? I have managed to enable dev mode and allow untrusted sources but on installing google play services and store all I get is crash reports and have to factory reset.
Thanks
J
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
wesleybr90 said:
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
Click to expand...
Click to collapse
To enable untrusted sources I had dev mode on but under security > device admin > unknown sources. I don't know if you need to enable dev mode to turn that on but if so go to about > build number > tap until it enables. I'm not really a software guy and was hoping someone on the internet would have a solution to rooting the device and maybe ADB it, I did ask a software engineer friend of mine and he did some research on them, these things talk to Sunmi's servers on boot with the current FW so they are heavily locked down, so progress wise for me is it's been in a drawer since January and I'm hoping someone will have a way to root the thing :S
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Noob Sailbot said:
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Click to expand...
Click to collapse
Thank you for the update, Im following this thread to see how this goes. Im trying to unlock my Sunmi V1 too
I managed to brick it, stuck at boot looping... Somehow I redownload boot and system from my backup with SP flash tool and got it working back again...
So I tried using ASSAYED Kitchen and remove some Bloatware, rebuild it, and upload it back to device, used two files: System.img and boot.img... This bricked my device.
What am I doing wrong? This must surely be my error. Do I need to do something to recovery partition?
UPDATE:
Managed to install custom recovery TWRP, made it myself using Carliv Image Kitchen
UPDATE 2:
Even thou TWRP seems working, It does not mount any partitions: /data, /system... Invalid argument...
Does anyone know how to fix it easy way? because I cant find too similar custom TWRP to Sunmi...
Any custom system.img that I flash with SP tool does not want to boot, never, and even if I only open ASSAYED Kitchen, do nothing and repack it. Is the only way to install it with TWRP?
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Noob Sailbot said:
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Click to expand...
Click to collapse
I am also looking forward to the results you have done
So amazing!!
I am slowly loosing interest in this. Whatever I do it is just endless loop...
When I modify package-restrictions.xml and settings_secure.xml files I got GooglePlay and Maps and stuff, but first time you connect the device to internet, SunmiBaseService overwrites them with options used for this DeviceID.
I renamed this SunmiBaseService to something else, got this working, but then since the whole thing runs on this sunmi backbone you can't install any apk's. I can normally install apks using USB and enabled BaseService.
It would be best if I could have just normal Android on this thing since it is unusable if you block BaseService, and if you would do any system upgrade on some point in time it would overwrite and install this service by itself. Like I said, it is endless loop. Even after contacting sunmi my region cant't have this for private use.
I can provide all files used in this process, my scatter files, my TWRP recovery and else...
The question is is it possible to port clean Android to this device, like we install new windows on a PC?
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Velcis Ribeiro said:
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Click to expand...
Click to collapse
No, I tried everything I know. Only thing that I did not do is replacing sunmibase service with some kind of android base service or paying some youtube guy 20$ for unlocking, but I doubt it would work correctly. Couse after you, in some point in time, update software or something I highly doubt it would work after that.
{Mod edit: Quoted post has been deleted}
I am going to upload files that I have, but I need few days to do so.
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
Can you share the files again please, the links don't work anymore. Thank you
My buddy has toast loaded on an old device and was looking to replace the os so his kid can use the tablet. Sunmi t2
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
I am after these files also if you still have them
Would it be possible for you to re-upload the files?
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.
awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.
Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader2. Flash any latest OSS ROM (this is just to remove MIUI)3. Use MiFlash and fastboot method to install old versions (re-lock if you want)Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.