I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
Related
So, I've used Revolutionary to S-off and root, but now there's a system update (I assume for the security vulnerability that was found a week or two ago). I'd like to install this update, but it just fails when I try... Does anyone know how to turn it into a flashable zip, or will I have to un-s-off/root, update, then re-s-off/root?
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Lucas0511 said:
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Click to expand...
Click to collapse
It appears there's a new update today, and it's only about 4.5 megs - I think HTC may actually be that fast
I really don't want to install a ROM, I just want stock with root (to help with development)... Any suggestions appreciated!
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Removing the recovery.img? I've rezipped everything and it's only 510kb now, surely that cant be it?
Recovery.img's are large files it was just a minor updat to probably fix a couple internal things nothing major. It was a small file at 4mb already.
Hy
Can you please upload the edit-update?
Thanks
ric242 said:
Hy
Can you please upload the edit-update?
Thanks
Click to expand...
Click to collapse
Will do once i'm home!
adaimespechip said:
Will do once i'm home!
Click to expand...
Click to collapse
Thanks! Might be able to make it into a flash able zip.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Thanks for the helpful guidelines...
Just a quick question and pardon me since I am a newcomer to Android universe. What do You mean when You say stock?
Thanks again...
BTY
HTC_Flyer / Revolutionary / CWM
Hi guys
The official OTA update (B380) with Andoid 6 and Emui 4.0.1 arrived on my PLK-AL10 around a week ago and I was very disappointed when I saw the "privacy protection" feature is not there anymore. This feature allowed me to create "visitor" account and the visitor could not see all the apps and albums.
Now I installed B395 hoping the feature included but it is still not.
I would like to revert to the previous system (as I remember it was B320) or any working version with Android 5 and EMUI 3.1.
I tried to install all the rollback files I found on the net but all stopped after a few percentages with the error message "software install failed".
Pls help me, what can I do?
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
DigiGoon said:
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
Really?
May I get a bit more detailed explanation what to modify?
tgergo said:
Really?
May I get a bit more detailed explanation what to modify?
Click to expand...
Click to collapse
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
You can set how many users you want by editing max user line.
lionboy33 said:
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
Click to expand...
Click to collapse
I can find in other topics how to root the phone, thank you. I think I can do it with these. Thanks a lot.
DigiGoon said:
You can set how many users you want by editing max user line.
Click to expand...
Click to collapse
Great.
I will come back if I get into trouble.
tgergo said:
Great.
I will come back if I get into trouble.
Click to expand...
Click to collapse
Always here to help buddy.
DigiGoon said:
Always here to help buddy.
Click to expand...
Click to collapse
Hi again,
Finally I managed to edit my build.prop and got "users" option. The problem is that is is not the same function as "Privacy protection" was in android 5. Privacy protection left the icon layout untouched, it was just possible to hide albums and applications.
Here when I create a guest and switch to it, it shows a completely empty system without any installed apps, pictures, etc..
Therefore I still want to go back to Android 5. How is it possible? I have TWRP installed. My current rom is B395 and phone is PLK-AL10.
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
zinko_pt said:
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
Click to expand...
Click to collapse
I don't think he was rooted, as the official update was missing a feature and he just wanted to get back to Lollipop.
Sent from my PLK-L01 using Tapatalk
pixelitect said:
You have to first flash the transition package to go back to Lollipop. For transition package to work you have to first flash STOCK recovery.img.
To do that execute the following command:
Code:
fastboot flash recovery recovery.img[/b]
Here [b]recovery.img[/b] is the name of your recovery file, and execute this command from the folder where you have saved the STOCK recovery.img. If you don't have STOCK recovery then you can extract it form the [b]UPDATE.APP[/b] using [URL="http://forum.xda-developers.com/showthread.php?t=2433454"]Huawei Update Extractor tool[/URL].[/QUOTE]
First I wanted to do so, but I could not find any transition package that worked with B380 stock rom (now I have 395). All I tried stopped with "software install failed" :(
Click to expand...
Click to collapse
pixelitect said:
Oh, then you can debrand your device using Multi-Tool to the one which has rollback package, and flash the Lollipop of that model.
Click to expand...
Click to collapse
Ok, I haven't heard about this yet but I'll try.
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
I managed to get back to Android 5 and EMUI 3.1 with a rollback file.
Here what I did:
1. Download Downgrade pack.
2. Download C185B130 ROM, which i want to install.
3. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
4. Copy update app from Downgrade pack to dload folder on mobile internal memory.
5. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
6. The system will be installed from mobile internal memory. I had no issues with the installation.
7. Copy update app from C185B130 ROM to dload folder on mobile internal memory.
8. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
9. The system will be installed from mobile internal memory. I had no issues with the installation.
10. Factory reset the mobile if the memory is showing 4gb.
11. The the native app icons look different than my previous lollipop system.
Thanks to tgergo and rest of everyone for the kind help.
Follow my guide at your own risk.
*WARNING* You are doing it at your own risk, I am not responsible for any damages due to bricked phones or broken ones
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
N7Gabe said:
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
Click to expand...
Click to collapse
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
MigoMujahid said:
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
Click to expand...
Click to collapse
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
N7Gabe said:
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
Click to expand...
Click to collapse
No, no need for that, just the ROM, and it won't delete anything.
MigoMujahid said:
No, no need for that, just the ROM, and it won't delete anything.
Click to expand...
Click to collapse
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
N7Gabe said:
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
Click to expand...
Click to collapse
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
MigoMujahid said:
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
Click to expand...
Click to collapse
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
Code:
D:\Android\sdk\platform-tools>adb devices
List of devices attached
0009bd0863c43f unauthorized
Code:
D:\Android\sdk\platform-tools>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
N7Gabe said:
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
Click to expand...
Click to collapse
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
MigoMujahid said:
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
Click to expand...
Click to collapse
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
N7Gabe said:
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
Click to expand...
Click to collapse
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
MigoMujahid said:
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
Click to expand...
Click to collapse
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Code:
D:\Android\sdk\platform-tools>adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
D:\Android\sdk\platform-tools>adb shell
~ # [6n
~ # [6nls
and-sec init.recovery.service.rc selinux_version
boot init.recovery.smdk4210.rc sepolicy
boot.txt init.recovery.usb.rc service_contexts
cache license sideload
charger mnt supersu
data proc sys
default.prop property_contexts system
dev recovery tmp
etc res twres
file_contexts sbin ueventd.rc
fstab.smdk4210 sdcard0 ueventd.smdk4210.rc
init sdcard1 usbotg
init.rc seapp_contexts
~ # [6ncd data
/data # [6nls
/data # [6n
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
N7Gabe said:
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
Click to expand...
Click to collapse
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
MigoMujahid said:
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
Click to expand...
Click to collapse
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
N7Gabe said:
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
Click to expand...
Click to collapse
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
MigoMujahid said:
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
Click to expand...
Click to collapse
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
N7Gabe said:
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
Click to expand...
Click to collapse
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
(not the same path for the contacts.db file)
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
MigoMujahid said:
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
Click to expand...
Click to collapse
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
N7Gabe said:
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
Click to expand...
Click to collapse
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
MigoMujahid said:
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
Click to expand...
Click to collapse
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
N7Gabe said:
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
Click to expand...
Click to collapse
Thanks for the tip, i have a marshmallow ROM right now, it seems that the location was changed in Nogut, I'll keep that in mind.
Have a good life too.
This will be basically the copy of this thread:
https://forum.xda-developers.com/p10-plus/development/downgrade-p10-plus-oreo-to-nougat-t3724382
But it seems to me that I am not the only one who didn't find it first, so I post it here
I am not responsible if you brick your device, or just damage it!
And all credit goes to @mankindtw and @NoMercyWWE
Always make a backup of your important data, and if you rollback, you need to make a factory reset!
I only tested it with L09, but should work with L29 as well
First of all, you need a P10
2. It only works with oreo firmwares
3. Download the three zip files that are required for update, these are:
update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
3/b. You can download them with Firmware Finder, or just search on xda. If you want to make a rollback to Nougat, you need rollback firmwares!
3/c. update_data_public and update_all_hw comes with a slightly different name, but rename both files to these names, otherwise the update will fail!
4. Download HWOTA8 from this topic
5. Put the three update files in HWOTA8 dir
5/b. If you want to rollback, but your files in the repack folder, and run repack.bat
6. Create a new folder on your EXTERNAL sd, named HWOTA8
7. Put your three files in it, plus copy MHA_RECOVERY8_NoCheck.img, and hwota8_update.zip
8. Now install P10 Plus twrp_oreo.img, if you havent't yet:
fastboot flash recovery_ramdisk twrp_oreo.img
Click to expand...
Click to collapse
credit to @OldDroid
9. Reboot into recovery, install hwota8_update.zip it replaces your recovery with the Mate 9 one, reboots and updates
10. Done! If you downgraded, or just encounter any problems, go back in recovery, and make a factory reset!
Can I do this without an sdcard?
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
I think it is possible, but you need to rewrite hwota8_update.zip, since the links there are pointing to the external sd. But I dont know what you need to write there instead
Not sure if I did this right but now my phone shows---> Build number System 8.0.0.046(02ZP)
I had showing before---> Build number System 8.0.0.046(01BN)
I don't seem to have it right still
I also have somethong like System 8.0.0.046(02BQ) but .321(C10) installed. And there were some visible updates from the C900log Oreo, eg auto shazam disappeared from the status bar.
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Droiduser67 said:
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Click to expand...
Click to collapse
Here he says that you need to install su, and rename three directories, but for me themes are working even without this. As soon as I try it, these steps will be added to the tutorial though.
EDIT: I followed the steps and renamed the directories, but there was no change anywhere.
Yes just tried it myself too and no change...still no themes...had an extra folder in there on mine named "optus"...not sure but the twrp and rooting work awesome but wasn't able to make a nandroid backup to my external storage...it failed
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
Without a SD card it is impossible, with firmware via TWRP, internal memory can be reset and then the firmware will not go to the end. Therefore, the programs are located on the SD.
urn said:
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
Click to expand...
Click to collapse
If this question is for me, I did not test the rollback (I am fine with Oreo), but I would use C432B180. You can check the description of an update in FF to see if it's a rollback one.
Here's the solution : https://youtu.be/WYSVq1TE2kI
OREO
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Nakedchef said:
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Click to expand...
Click to collapse
Hey, there are many ways of doing it i would recommend https://forum.xda-developers.com/showthread.php?t=3691013
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo it works great. Go for the hwota rebrand way, it work like charm for me.
Sent from my [device_name] using XDA-Developers Legacy app
Perfect! I applied the update as described in the OP, then did a factory reset and relocked the bootloader (which did another factory reset). Now, at least I can't tell anymore that the phone has been unlocked and rooted...
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
dukenuken said:
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Click to expand...
Click to collapse
Which TWRP are you using?
Hey everyone so I have a BLA-A09 c567 (US) I got this phone used and it came with the bootloader unlocked. I managed to get the code and relock the bootloader at a later time. After going through the settings I noticed that the system update feature is still gone? I thought after relocking the bootloader and factory resetting it would come back. Is there something I am missing or will I not be able to receive OTA updates now? Please give me some guidance and thank you!
What's the status of the phone when you got it aside from Unlocked BL? Is it rooted?
You should never loose system update regardless of the BL status. I suspect the previous owner debloated it.
side_flip15 said:
What's the status of the phone when you got it aside from Unlocked BL? Is it rooted?
You should never loose system update regardless of the BL status. I suspect the previous owner debloated it.
Click to expand...
Click to collapse
They didn't flash the hw/public zip when updating.
Or possibly just removed it, for some reason...
So is there something I can do to return the system update feature? Or should I enjoy the blessing of a free debloat? My only issue is how will I get OTA updates. Can I just use the hisuite app the update instead?
Currently my Bootloader is relocked and unrooted looks like they messed around with the device then just relocked it and unrooted. When I purchased the device it was "like new" used for a week only.
I am on the C567 .119 patch
A flashable zip with instructions or apk would be amazing please help, but if it isn't an issue and I can just use hisuite to update I won't lose sleep over it.
Also is there anything important in the bloat zip besides system update?
I had the same issue when I flashed my phone with 119. I extracted the update ap apk from the hw zip file of 119, attempted an install, but it will not work. The app is in the play store but won't install on the phone. I will try to pm you the apk
innocentone1 said:
So is there something I can do to return the system update feature? Or should I enjoy the blessing of a free debloat? My only issue is how will I get OTA updates. Can I just use the hisuite app the update instead?
Currently my Bootloader is relocked and unrooted looks like they messed around with the device then just relocked it and unrooted. When I purchased the device it was "like new" used for a week only.
I am on the C567 .119 patch
A flashable zip with instructions or apk would be amazing please help, but if it isn't an issue and I can just use hisuite to update I won't lose sleep over it.
Also is there anything important in the bloat zip besides system update?
Click to expand...
Click to collapse
nabril15 said:
I had the same issue when I flashed my phone with 119. I extracted the update ap apk from the hw zip file of 119, attempted an install, but it will not work. The app is in the play store but won't install on the phone. I will try to pm you the apk
Click to expand...
Click to collapse
It won't install by using the package manager.
You can however download the hw zip file and flash it through TWRP, this requires unlocked bootloader and TWRP.
It will show a bunch of errors when installing through TWRP but the hw_init folder is copied successfully to /data/hw_init/
You can find it here: https://forum.xda-developers.com/showpost.php?p=77248270&postcount=72
ante0 said:
It won't install by using the package manager.
You can however download the hw zip file and flash it through TWRP, this requires unlocked bootloader and TWRP.
It will show a bunch of errors when installing through TWRP but the hw_init folder is copied successfully to /data/hw_init/
You can find it here: https://forum.xda-developers.com/showpost.php?p=77248270&postcount=72
Click to expand...
Click to collapse
For some reason, in TWRP, I cannot see the contents of my sdcard. I wiped the data partition when I flashed the 119 zip files using huru, so I don't know why I cant see that directory.
nabril15 said:
For some reason, in TWRP, I cannot see the contents of my sdcard. I wiped the data partition when I flashed the 119 zip files using huru, so I don't know why I cant see that directory.
Click to expand...
Click to collapse
Try going to Mount and unmount then mount Data again.
Or just mount if it's not mounted
(If you are encrypted and not using Pretoriano80's TWRP you won't be able to anyway as it would require either TWRP with decryption support or decrypting by Format Data then edit fstab and remove encryption. Dont Format Data now as it will wipe your /data)
ante0 said:
Try going to Mount and unmount then mount Data again.
Or just mount if it's not mounted
(If you are encrypted and not using Pretoriano80's TWRP you won't be able to anyway as it would require either TWRP with decryption support or decrypting by Format Data then edit fstab and remove encryption. Dont Format Data now as it will wipe your /data)
Click to expand...
Click to collapse
thanks ante
I unmounted and mounted and I now see a bunch of folders whose name starts with a (.). I am using twrp version 3.2.1.0, which is the same version as BLANC, I believe, which is for unencrypted data.
nabril15 said:
thanks ante
I unmounted and mounted and I now see a bunch of folders whose name starts with a (.). I am using twrp version 3.2.1.0, which is the same version as BLANC, I believe, which is for unencrypted data.
Click to expand...
Click to collapse
If it's just a bunch of random lettera/numbers it means your are encrypted. You could switch to https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Just flash it and reboot recovery. You will get a Pin/password input prompt, input your pin/pw and it will decrypt.
You can use adb to push the image to /data:
adb push twrp.img /data/
Then select Install and tap the dots to go up a level, go into /data, tap the Install Image button, scroll down and select twrp.img.
Or flash using fastboot as thats easier xD
ante0 said:
If it's just a bunch of random lettera/numbers it means your are encrypted. You could switch to https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Just flash it and reboot recovery. You will get a Pin/password input prompt, input your pin/pw and it will decrypt.
Click to expand...
Click to collapse
Thanks again. I did not know that we can flash twrp using twrp itself. Weird.
What pin/password is to be used?
nabril15 said:
Thanks again. I did not know that we can flash twrp using twrp itself. Weird.
What pin/password is to be used?
Click to expand...
Click to collapse
The one you use on lockscreen
When it's done, transfer zip to sdcard and flash.
As I said, it will error and say it failed but it does copy hw_init.
ante0 said:
The one you use on lockscreen.
Click to expand...
Click to collapse
I have a pattern
nabril15 said:
I have a pattern
Click to expand...
Click to collapse
Try entering it as numbers. Pattern would look like this in number mode:
1 2 3
4 5 6
7 8 9
I guess you could just remove pattern temporarily if your only goal is to flash hw
@ante0/culi
I flashed the twrp blanc, and as able to see my downloads. Cool. I then flashed the update_all_hw.zip file and it errored out at the end of the script with a write data error update_huawei_pkg from the zip file.
E:unknown command
Error installing file
Nothing else gave an error
EDIT - disregard..I rebooted and I see that I have the system update app now AND, it found the long-seeked 119 patch, which I installed. Cool. After the patch was applied, the phone rebooted itself into recovery, I saw it run some script, and then it rebooted into system. Weird. The phone, however, still shows the version as 119, and not 119 patch 01 or something.
RE-EDIT - redisregard. THe version shows as 119 patch AND the themes got installed from the zip. Ok, so it looks like I now have a complete version 119 US variant of the stubborn and cumbersome Mate 10 Pro. Though I read that an update came out yesterday with the August security patches.
nabril15 said:
@ante0/culi
I flashed the twrp blanc, and as able to see my downloads. Cool. I then flashed the update_all_hw.zip file and it errored out at the end of the script with a write data error update_huawei_pkg from the zip file.
E:unknown command
Error installing file
Nothing else gave an error
EDIT - disregard..I rebooted and I see that I have the system update app now AND, it found the long-seeked 119 patch, which I installed. Cool. After the patch was applied, the phone rebooted itself into recovery, I saw it run some script, and then it rebooted into system. Weird. The phone, however, still shows the version as 119, and not 119 patch 01 or something.
Click to expand...
Click to collapse
Yeah, flashing hw/public zips will give errors. This is because its supposed to be installed using Huaweis update binary. So twrp can't process the commads.