Related
"Cyanogendmod.Org / Install CM for z3c / Unlock Your Xperia Z3 Compact" <--- That's the URL somehow.
Followed this instruction. Got myself the 12.1 .zip and .img.
I get error installaing the .zip and the .img isn't even an option:
The old rom is infinitly loading in that blue/purple wave line.
I then turn the phone off by holding down the power button until the phone restarts.
My history:
>Pressing up and down on the button rockers.
>Cyanogen Recovery starts.
>I choose "Wipe data/factory reset".
>I choose "Apply update".
(Apply from ADB doesn't work as it seems as ADB has no access for USB debugging. That's why install it from an external SD)
>Install "cm-12.1-20160918-NIGHTLY-z3c.zip" or its copy that I named "update.zip".
Error message:
[CAN'T POST PICTURE BECAUSE XDA HAS VERY FUNNY MEME RULES XDDD]
Private message maybe...? Can I send you guys URL pics via PM?
How can I get out of this loop?
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
marshalpear said:
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
Click to expand...
Click to collapse
I definitly want CyanogenMod 12.1 on my Z3C. Is it still possible?
I hope you can decypher the URL h t t p : / / t i n y u r l . c o m / j 6 4 u 8 u a
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
marshalpear said:
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
Click to expand...
Click to collapse
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
If you are on CM recovery, then there is the problem. AFAIK you can't flash anything through that, so you have to push TWRP on your device using fastboot and then flash AOSP/CM rom you want.
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
More info about my error:
h t t p : / / t i n y u r l . c o m / z b e v y u 2
Each version of step #3 doesn't work. Still trying to figure out how to get TWRP...
marshalpear said:
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
Click to expand...
Click to collapse
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
SYLVER SECOND said:
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
Click to expand...
Click to collapse
OK, your problem is that you messed up your system, so wiping it is not gonna solve this issue. You need to download a stock firmware file (an FTF file) and flash it through Flashtool, because your device name seems to be "." which is why you were getting "error 7". As for the recovery.img, you will use it to flash TWRP recovery on your phone. TWRP app doesn't work correctly if you don't flash it to your recovery partition so do as follows:
1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work. :good:
marshalpear said:
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
Click to expand...
Click to collapse
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Cirra92 said:
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
marshalpear said:
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
Click to expand...
Click to collapse
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Cirra92 said:
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Click to expand...
Click to collapse
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
marshalpear said:
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
Click to expand...
Click to collapse
Logical step, didn't think about it that way, I assumed OP knew how to enter recovery
"1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work."
K, so I guess I'm finished with #1 and #2. Sorry, had a ****-ton of chores to do. Before I progress, I wanted to send you guys
this pic:
https://img3.picload.org/image/rdricord/unbenannt.png
Is the root access necessary, or can I progress?
That's the sites I've used, if anybody wonders why something is the way it is right now:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
http://forum.xda-developers.com/showpost.php?p=66275965&postcount=2029
http://forum.xda-developers.com/showpost.php?p=60001557&postcount=829
Von "Sony Mobile Flasher by Androxyde":
"23/023/2016 22:23:52 - INFO - Root access denied
23/024/2016 22:24:07 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:12 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:13 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
23/024/2016 22:24:14 - INFO - Root access denied"
FlashTool says the firmware has been flashed so I don't understand what are you trying to do after that? After flashing the FTF file you should flash TWRP through "FASTBOOT". Then follow the instructions.
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
SYLVER SECOND said:
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
Click to expand...
Click to collapse
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
marshalpear said:
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
Click to expand...
Click to collapse
K, cool feature. Got it all set up now, but back to the main subject:
Is it even possible to install CyanogenMod 12.1 on Sony Z3C?
Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops:
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
Make sure to follow this guide precisely, as order matters. At the end, I will post an explanation of why we need to execute these steps. I spent an entire weekend of trial and error on my Huawei Honor Note 10, and now I have figured out the ins and outs so you don't have to. You're welcome
Prerequisites
Huawei Honor Note 10 device, either on stock ROM or rooted (doesn't matter)
MicroSD card (formatted exFAT or FAT, doesn't matter)
Bootloader unlock code for Huawei Honor Note 10 (follows a format like my own HBP38K14DBK2RNB4)
Computer with admin privileges
Before You Flash Anything
Back up, back up, back up! I am not responsible if you lose valuable or sensitive data. Your Huawei Honor Note 10 will factory reset a number of times (probably more) before you can get back up and running again. Either use TWRP to do this, or use HiSuite (not recommended but will work on a locked bootloader).
Remove your SIM card! Your carrier may get charged ridiculous amounts of fees if you have a limited data plan, such as 256MB (Canada has notoriously expensive phone plans, so Canadians beware). When you reboot, expect Huawei's stock ROM to use copious amounts of data on retrieving the latest version of bloatware and spyware.
Ensure you have stock recovery installed. If you don't, download the stock recovery image, place it in your Minimal ADB and Fastboot folder, then boot to download mode by holding the VOLUME DOWN button and simultaneously plug in in your Huawei Honor Note 10 device, then open Minimal ADB and Fastboot on your computer and run this command:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Steps to Install Custom ROM on Huawei Honor Note 10
Download the EMUI 9 stock ROM and place the dload folder on your MicroSD card
Boot to (stock) recovery by holding down the VOLUME UP, VOLUME DOWN, and POWER buttons at the same time. The update should begin immediately. Wait patiently for your phone to reboot
Fill out the bloatware questionnaire by Huawei and download any and all updates under Settings. This will ensure you have the latest boot image. You will reboot at least once.
Once you have completed all the updates, reboot to download mode; press and hold the VOLUME DOWN button while you plug in your Huawei Honor Note 10 device to your computer
On your computer, download and open Minimal ADB and Fastboot
Run the following command:
Code:
fastboot oem unlock <code>
(where code corresponds to a format that looks like this: HBP38K14DBK2RNB4)
Confirm unlocking your bootloader by using the VOLUME keys, selecting yes, and pressing the POWER button. The Huawei Honor Note 10 device will now perform a factory reset
IMPORTANT step. DO NOT let the Huawei Honor Note 10 reboot. DO NOT. Impatiently wait for the low-level factory reset to complete and as soon as it does, enter download mode again by pressing the VOLUME DOWN key and plugging in the device again
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
IMPORTANT: disable_Dm-Verity_ForceEncrypt by installing this zip. If you don't do this, you won't be able to enter TWRP again
Optionally install magisk, titanium backup, and other magisk mods
Reboot system and profit
Update: 2021-04-06
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. This should boot you to stock RECOVERY.
Wipe to factory reset. Confirm by typing "yes" (WARNING: this wipes your device)
Plug in your Huawei Honor Note 10 to your PC with ADB
Boot to DOWNLOAD mode by holding down the VOLUME DOWN button as soon as your Huawei Honor Note 10 reboots
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
Install any custom ROM you wish via selecting a system image (or zip file if you have EMUI 8)
Install magisk, titanium backup, and other magisk mods (note that you will NOT be able to boot to recovery after this; consider this you last chance to install any mods)
Reboot system and profit
Background and Explanation
When you first flash a ROM, even in EMUI 8, your Huawei Honor Note 10 encrypts /system to prevent third parties such as TWRP from mounting it. Hence, you may successfully boot to TWRP, but /system will be mounted as read-only. This is problematic, as it means you can't install any new ROMs (however, you can make a backup, which can be useful for backing up stock, encrypted /system partitions)
Because /system gets encrypted, it means you have to wipe /system completely. Doing a factory reset (low-level) does this, once you unlock your bootloader. However, if you were to let your Huawei Honor Note 10 boot, then the stock ROM would, by default, encrypt /system, forcing you to start this process all over again (as TWRP will, in most cases, not even boot with an encrypted /system). If your TWRP hangs on the TWRP logo, your /system partition is likely encrypted. You need to factory reset, install TWRP again, and then wipe /system, followed by installing the Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip script.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
I hope this guide helps other fellow Huawei Honor Note 10 owners. If you have any questions, please also make sure to include your EMUI version and steps taken so that I can best help you. I hope that I have saved some of you trouble when updating to EMUI 9 and also helped to explain why updating can become so tedious.
Thank you for the instructions! I've got some questions...
ForgottenSolstace said:
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
Click to expand...
Click to collapse
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
null00005 said:
Thank you for the instructions! I've got some questions...
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
Click to expand...
Click to collapse
Yep, so it sounds like you have an encrypted /data.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
(Note: this will erase everything on /data)
Then boot to TWRP again. Check the logs and try again.
ForgottenSolstace said:
Yep, so it sounds like you have an encrypted /system.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
Then boot to TWRP again. Check the logs and try again.
Click to expand...
Click to collapse
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
null00005 said:
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
Click to expand...
Click to collapse
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
ForgottenSolstace said:
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
Click to expand...
Click to collapse
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
null00005 said:
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
Click to expand...
Click to collapse
If you roll back to stock and unlock your bootloader again, then you don't need to do fastboot erase userdata because "factory reset low-level" will perform that once you unlock your bootloader again. So you should be able to flash TWRP, boot fine (only that one time), install whatever ROM you want, flash magisk, and boot (note: on EMUI9, you must reboot to recovery, as boot_ramdisk only exists in EMUI8).
In the past, I have ignored the message "failed to mount '/odm'" and still had success; just pay attention to the status code at the end when you install /system. Don't bother wiping odm, as we really care about mounting /system. Perform a factory reset just to be safe, and feel free to wipe /data, but it won't matter if you already performed a factory-reset (low-level) from unlocking your bootloader again.
Try installing your ROM of choice from TWRP despite this error, flashing magisk, and confirm if that works.
ForgottenSolstace said:
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
Click to expand...
Click to collapse
Hi, how about root with magisk in this rom?!
TheFastGT said:
Hi, how about root with magisk in this rom?!
Click to expand...
Click to collapse
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
jazzzy said:
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
Click to expand...
Click to collapse
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
TheFastGT said:
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
Click to expand...
Click to collapse
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
jazzzy said:
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
Click to expand...
Click to collapse
I've a Honor Note 10 and i haven't TWRP installed, i use stock recovery and Openkirin rom...
How can I unlock my bootloader?
Darj said:
How can I unlock my bootloader?
Click to expand...
Click to collapse
HCU client
TheFastGT said:
HCU client
Click to expand...
Click to collapse
Thanks.. this is the only device I have so I wanted to ask what would happen if I mess it up
TheFastGT said:
HCU client
Click to expand...
Click to collapse
And once I unlock the bootloader using HCU client, do I have to follow the steps above or can I just install a custom recover how you'd do on any phone?
@Darj , did you manage to sort out rooting your Huawei Honor Note 10? I've updated the installation steps to reflect the shortened steps I last took to get Magisk running (downgraded to EMUI8 on my Huawei Honor Note 10 to try to preserve TWRP).
Hopefully, we'll see more ROMS from the OpenKirin project, as the latest security patch is almost a year old on EMUI8.
@ForgottenSolstace not yet. I want to make sure I have all the informations I need before spending money to unlock the bootloader
@Darj , it only costs 15USD to unlock your Huawei Honor Note 10. Why not go ahead and try?
I assure you that the effort is much worth it; Stock ROM is bloated with all kinds of spyware from the Chinese government. When you install AOSP, you can actually secure your phone following the updated instructions which encrypts /data.
Let me know if you have any questions. Happy to help
Hi ...got problem using twrp?
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147
After installing Gsi
After installing Gsi, can I get the fast boot mode later
Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes
raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes
I unlocked bootloader, booted into TWRP, clean flashed Custom ROM and TWRP and rebooted. It doesn't boot into the system, only TWRP. When I try to install it again, it can't recognize system_ext, vendor and product partitions anymore, even after "Format Data".
When I try to run "fastboot format" on them, I receive:
Code:
fastboot: error: Formatting is not supported for file system with type 'raw'.
Also, should I install TWRP with "Flash Current TWRP" or "Install Recovery Ramdisk"? Or are they virtually the same, with the same drawbacks?
Trying to flash Project Elixir v3.3
I just had to boot into ROM before flashing TWRP. Everything works now, except TWRP, but I assume that's a problem with the ROM.