PS : I AM LEARNING ENGLISH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link From Bug Report :
Code:
https://android.googleapis.com/packages/ota-api/xiaomi_tissotsprout_tissot/ee592cfc37713ab6404363513c1d7a51c1551d83.zip
Google Drive Link (If Above Link Doesn't Works For You) :
Code:
https://drive.google.com/file/d/1kdXbdP-Cus6vKE4VXLZFj98P7HD8EHXA/view?usp=sharing
Code:
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:1222:1166394845,payload_properties.txt:1166396125:155,care_map.txt:458:717,metadata:69:341
ota-type=AB
post-build=xiaomi/tissot/tissot_sprout:8.0.0/OPR1.170623.026/8.1.10:user/release-keys
post-build-incremental=8.1.10
post-timestamp=1515569993
pre-device=tissot_sprout
Can i clean flash it with mi flash ??
If not then how can I install it ?
Can it be flashed with TWRP?
rex28818 said:
Can i clean flash it with mi flash ??
If not then how can I install it ?
Click to expand...
Click to collapse
Its not fastboot image , so it can't be flashed using Mi flash tool.
rex28818 said:
Can i clean flash it with mi flash ??
If not then how can I install it ?
Click to expand...
Click to collapse
You can sideload it using the stock recovery.
xb360 said:
Can it be flashed with TWRP?
Click to expand...
Click to collapse
Nope. Official OTA updates need to be sideloaded via stock recovery.
DJBhardwaj said:
You can sideload it using the stock recovery.
Nope. Official OTA updates need to be sideloaded via stock recovery.
Click to expand...
Click to collapse
Any guide to sideload ota via stock recovery would be greatly appreciated.
Thanks
rex28818 said:
Any guide to sideload ota via stock recovery would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I made this if you want, you can flash it using TWRP
rex28818 said:
Any guide to sideload ota via stock recovery would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
As a matter of fact, I am covering a guide to sideload OTA zips as I am writing this.
But I also have a previous tutorial that includes the instructions on how to install this zip. Kindly send me a PM, and I shall share the link with you.
DJBhardwaj said:
You can sideload it using the stock recovery.
Nope. Official OTA updates need to be sideloaded via stock recovery.
Click to expand...
Click to collapse
Thanks for the reply.
Do you know where I can get the stock recover?
Or if I flash the patched_boot.zip, will it restore the stock recovery?
xb360 said:
Thanks for the reply.
Do you know where I can get the stock recover?
Or if I flash the patched_boot.zip, will it restore the stock recovery?
Click to expand...
Click to collapse
1) Download the fastboot image from here: http://en.miui.com/download-333.html
2) Extract the *.tgz file and find the recovery.img in "Images" folder.
---------- Post added at 02:57 PM ---------- Previous post was at 02:37 PM ----------
@salkollizz I have tried sideloading the OTA via ADB and the installation was aborted. Any heads up?
The process started fine and the file transfer was initiated, but after about 66 seconds, it showed me an unusual error.
https://imgur.com/a/Bb81l
DJBhardwaj said:
1) Download the fastboot image from here: http://en.miui.com/download-333.html
2) Extract the *.tgz file and find the recovery.img in "Images" folder.
---------- Post added at 02:57 PM ---------- Previous post was at 02:37 PM ----------
@salkollizz I have tried sideloading the OTA via ADB and the installation was aborted. Any heads up?
The process started fine and the file transfer was initiated, but after about 66 seconds, it showed me an unusual error.
https://imgur.com/a/Bb81l
Click to expand...
Click to collapse
Ua downloaded OTA From GoogleCDN / Google Drive?
Edit : try installing OTA Zip from root of sdcard/internal memory .
salkollizz said:
Ua downloaded OTA From GoogleCDN / Google Drive?
Edit : try installing OTA Zip from root of sdcard/internal memory .
Click to expand...
Click to collapse
Google servers.
Okay, I will give it a go.
---------- Post added at 03:42 PM ---------- Previous post was at 03:31 PM ----------
salkollizz said:
Ua downloaded OTA From GoogleCDN / Google Drive?
Edit : try installing OTA Zip from root of sdcard/internal memory .
Click to expand...
Click to collapse
Upon applying update from SD card, it couldn't mount the SD card and shows an error.
DJBhardwaj said:
1) Download the fastboot image from here: http://en.miui.com/download-333.html
2) Extract the *.tgz file and find the recovery.img in "Images" folder.
---------- Post added at 02:57 PM ---------- Previous post was at 02:37 PM ----------
@salkollizz I have tried sideloading the OTA via ADB and the installation was aborted. Any heads up?
The process started fine and the file transfer was initiated, but after about 66 seconds, it showed me an unusual error.
https://imgur.com/a/Bb81l
Click to expand...
Click to collapse
Thanks.
Ota from OREO december to January was about 90mb. This one is more than 1gb. is it intended to be applied in nougat?
I still didn't get an update via Ota, is this update for global or just for some region?
Sorry for my bad English
mhdsanto85 said:
Ota from OREO december to January was about 90mb. This one is more than 1gb. is it intended to be applied in nougat?
Click to expand...
Click to collapse
Yes.
kdrinvsn said:
I still didn't get an update via Ota, is this update for global or just for some region?
Sorry for my bad English
Click to expand...
Click to collapse
Donno
mhdsanto85 said:
Ota from OREO december to January was about 90mb. This one is more than 1gb. is it intended to be applied in nougat?
Click to expand...
Click to collapse
Can someone upload this incremental OTA?
I have not found it, actual Oreo December ROM Is very buggy.
this doesnt work, device shuts down after selecting the package from stock recovery
how can I install it ? Any guide?
Related
Dear XDA User
This is XQ55 Files fo help you with OnePlus2
OnePlus2 Drivers
OnePlus2 Roms
OnePlus2 Recovery
OnePlus2 ToolBox
OnePlus2 System Files
OnePlus2 Wallpapers
OnePlus2 Teardown Images
For more Files
If this Files help you you can say Thank you
Thanks for sharing
Does this work properly? the TWRP is not officially there on TWRP page what does this use?
---------- Post added at 05:28 PM ---------- Previous post was at 05:18 PM ----------
how to relock the bootloader if we want?
matrix.bharath said:
Does this work properly? the TWRP is not officially there on TWRP page what does this use?
---------- Post added at 05:28 PM ---------- Previous post was at 05:18 PM ----------
how to relock the bootloader if we want?
Click to expand...
Click to collapse
This One from OnePlus2 Forum and it's worked with me
XQ55 said:
This One from OnePlus2 Forum and it's worked with me
Click to expand...
Click to collapse
how to re lock the boot loader? there is npot option in tool kit.
Anyone please post the instructions how to install these files in any way.
Can we install the system apps like the launcher on OPO?
Please confirm is there a way to relook the bootloader and get back to stock. And once we root will get ota on oxygen or not?
It works fine! Great work! Thanks!
matrix.bharath said:
Please confirm is there a way to relook the bootloader and get back to stock. And once we root will get ota on oxygen or not?
Click to expand...
Click to collapse
yes from toolbox
XQ55 said:
yes from toolbox
Click to expand...
Click to collapse
There is no option in tool box to relook bootloader can you please check.
matrix.bharath said:
There is no option in tool box to relook bootloader can you please check.
Click to expand...
Click to collapse
Bring device in fastboot mode, then enter
fastboot oem lock
on your PC.
This will lock your bootloader again. Afterwards, do a full wipe of the system and you should be pretty much back to start again.
Andi
May i know how to flash the 1.1gb update from oneplus for oneplus 2 manually?i m using stock recovery on oxygenOS
Lord Boeffla said:
Bring device in fastboot mode, then enter
fastboot oem lock
on your PC.
This will lock your bootloader again. Afterwards, do a full wipe of the system and you should be pretty much back to start again.
Andi
Click to expand...
Click to collapse
Thanks sir, but there is no such option in the tool box to lock bootloader again.
XQ55 said:
Dear XDA User
This is XQ55 Files fo help you with OnePlus2
OnePlus2 Drivers
OnePlus2 Roms
OnePlus2 Recovery
OnePlus2 ToolBox
OnePlus2 System Files
OnePlus2 Wallpapers
OnePlus2 Teardown Images
For more Files
If this Files help you you can say Thank you
Click to expand...
Click to collapse
Made an usefull video guide. thot it might be usefull you can add in OP
Oneplus 2 - How to Root, Unlock, TWRP
In this video lets unlock the Bootloader, install Custom recovery (TWRP) & flash Super SU to root your oneplus 2 all in simple steps
Download Links
Tool Kit - https://goo.gl/XshfG9
Super SU - https://goo.gl/o73tkf
XDA Link -
1. http://goo.gl/0B8WMb
2. http://goo.gl/oqFFuZ
Oneplus Forum Link - https://goo.gl/6NAmk3
file have been removed...please upload again..
Which one of the supplied files is the stock recovery?
fusion_master said:
Which one of the supplied files is the stock recovery?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347818542 for OxygenOS 2.0.2.
Waterdroid said:
https://www.androidfilehost.com/?fid=24052804347818542 for OxygenOS 2.0.2.
Click to expand...
Click to collapse
Can I just flash the boot.img through ADB sideload? The reason I ask is that I have TWRP on an encrypted phone (before checking that encryption wasn't supported oops!); so currently only able to ADB sideload as sdcard is not mountable to flash full zip.
Waterdroid said:
https://www.androidfilehost.com/?fid=24052804347818542 for OxygenOS 2.0.2.
Click to expand...
Click to collapse
can this .zip be flashed with flashify or do we need to extract the boot.img and just fastboot flash that...?
also in the recoveries download link we have the files in the pic below...3 actual recovery.img's and 2 boot.img's
will these boot.img's replace my current TWRP.img i have in the device ATM and there also seem to be two to choose from...can i use either one..confused.com...?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
https://drive.google.com/file/d/0B_Hol5T47S-bZHRYNW5naHVYUUk/view?usp=sharing
: LGUP
1. Download this.
2. Install the LG Drivers.
3. Extract the RAR File to get the .TOT file.
4. Unzip "lgupnew.zip"
5. Run LGUP_Store_Frame_Ver_1_14_3.msi
6. LGUP_8994_DLL_Ver_0_0_1_18.msi
7. Copy the "common" folder to "C:\Program Files (x86)\LG Electronics\LGUP\model"
8. Plug phone into Downloadmod.
9. Run "LGUP" from your start menu.
10. Select your Phone if see option.
11. For the "BIN File" select the file you extracted in step 3.
12. You'll have root in about 3 minutes!
Donate : [email protected]
frp or root
@tungkick is this for root or frp bypass
This bypass
Error: TOT file invalid
---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------
I got to 9% by using the FOTA Upgrade option; however, I receive Error: Error Code = 0x2000, Invalid command response
xyros7 said:
Error: TOT file invalid
---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------
I got to 9% by using the FOTA Upgrade option; however, I receive Error: Error Code = 0x2000, Invalid command response
Click to expand...
Click to collapse
phone version android 6.0 or 5.1.1
If 6.0 i need make again fw 6.0
tungkick said:
phone version android 6.0 or 5.1.1
If 6.0 i need make again fw 6.0
Click to expand...
Click to collapse
I'm on the latest 5.1.1. 10f. I used the TOT file for root access. I have access to the launcher and settings, but unable to figure out what to do next. I just kept getting multiple errors trying to flash your TOT file. I tried every setting to no avail.
xyros7 said:
i'm on the latest 5.1.1. 10f. I used the tot file for root access. I have access to the launcher and settings, but unable to figure out what to do next. I just kept getting multiple errors trying to flash your tot file. I tried every setting to no avail.
Click to expand...
Click to collapse
open teamveiwer send id pass form i check file
tungkick said:
phone version android 6.0 or 5.1.1
If 6.0 i need make again fw 6.0
Click to expand...
Click to collapse
sorry for highjacking thread, but this is the second time ive seen someone talk bout Marshmallow as if its out already... can anybody confirm if I can update?
File worked excellent! Thanks tungkick! I am uploading the new one tungkick modified. Will post link in a few.
https://drive.google.com/file/d/0Bwg7QqL2W-xeX1dWY1dNMVNuOGc/view?usp=sharing
m_reyna_16 said:
sorry for highjacking thread, but this is the second time ive seen someone talk bout Marshmallow as if its out already... can anybody confirm if I can update?
Click to expand...
Click to collapse
For some international variants, for Verizon and for T-Mobile (as of Monday)
Haven't seen it mentioned for AT&T model yet...
Sent from my pretty nifty brand new LG V10
tungkick said:
This bypass
Click to expand...
Click to collapse
Many thanks @tungkick
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
xyros7 said:
https://drive.google.com/file/d/0Bwg7QqL2W-xeX1dWY1dNMVNuOGc/view?usp=sharing
Click to expand...
Click to collapse
Thanks for the new upload!
What is frp again?
I'm confused, how is this different from the other rooted tot file that tungkick created?
Yeah im successfully rooted but should I change to this new method for some reason? Also would root have anything to do with decreased battery life?
This is simply a custom tot to bypass google account activation lock. There is no reason to use this tot unless you are locked out of your phone because you forgot the Google account originally used and were locked out.
tungkick said:
phone version android 6.0 or 5.1.1
If 6.0 i need make again fw 6.0
Click to expand...
Click to collapse
I have successfully used the bypass tot. Factory Reset the phone. It is rooted. Is it possible to flash the stock 5.1 tot so I can upgrade to Marshmallow 6.0?
reycingef9 said:
I have successfully used the bypass tot. Factory Reset the phone. It is rooted. Is it possible to flash the stock 5.1 tot so I can upgrade to Marshmallow 6.0?
Click to expand...
Click to collapse
You could, but I believe the FRP lock would be back.
xyros7 said:
You could, but I believe the FRP lock would be back.
Click to expand...
Click to collapse
You are correct. FRP came back. Thanks.
eror
It gives this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Overview
This is a patched recovery image which bypasses the usual checks performed during a firmware flash, allowing you to flash unapproved OTA firmwares. For example, the latest FullOTA-MF b394:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can also downgrade without using the b300 rollback package (untested)
Prerequisites
Unlocked bootloader
Rooted
Backup your data (flashing may cause bootloader to re-lock or restore factory default etc. - don't blame me if it goes wrong!)
Instructions
Download firmware:
Use Huawei Firmware Finder (Play Store link) to download the latest firmware files - you will need all 3 zip files:
- update.zip
- update_data_full_public.zip
- update_full_EVA-L09_hw_eu.zip
Tips: check for the latest number (102064 for b394) and ensure you have the larger filesize (around 2GB). For example, these are the latest at time of writing b394:
Flash nocheck recovery:
Reboot device to fastboot mode (power off fully, hold down volume button and connect USB cable)
Run the following to flash recovery:
Code:
fastboot flash recovery eva_l09b391_nocheckrecovery.img
fastboot reboot
Send commands via ADB
Phone should be booted back to system - connect phone via adb and allow root prompt:
Code:
adb shell
su
Create HWOTA folder:
Code:
mkdir /data/update/HWOTA
Copy firmware to HWOTA folder (replace 102064 below with correct value - this is for b394):
Code:
cp /sdcard/HWFF/102064/update* /data/update/HWOTA/
Paste recovery command:
Code:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_full_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_full_EVA-L09_hw_eu.zip" >> /cache/recovery/command
exit
Finally reboot to recovery to start firmware upgrade:
Code:
adb reboot recovery
Firmware should install and reboot automatically
Extras
You can probably Re-Brand to alternative customers too i.e. c636 (Asian region) to c432 (European region). Follow the tutorial here: https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886 - you'll need the correct OEMINFO files, this is untested.
Thanks
- Olddroid
- Mankindtw
- Hackslash
- DkiOnline (L09 tester)
- jimz6 (L19 tester)
- LastStandingDroid
XDA:DevDB Information
EVA NoCheck Recovery, Tool/Utility for the Huawei P9
Contributors
Atarii
Version Information
Status: Stable
Created 2017-11-14
Last Updated 2017-11-17
Changelog
31-01-2018
Added L29 recovery image
17-11-2017
Added L19 recovery image
14-11-2017
Initial release
THX, i try and successfully, i am on latest firmware now
rafitcu said:
THX, i try and successfully, i am on latest firmware now
Click to expand...
Click to collapse
Great - thanks for the feedback
Update: I've added the L19 recovery image after successful feedback
updated succesfully.
only two points, on prerequisites I think you should add that the phone should be rooted cause after I flashed the nochechrecovery I needed to reflash twrp and root.
and the second point is that there is missing a / before de * in the step when you copy the 3 zips to data.
nice to know there is a method to bypass the verification on firmwares :good::good:
Can any one try downgrade after update to b394 using b300???
Can one modify the recovery.img file for a certain firmware version other than B391?
kukubau said:
Can one modify the recovery.img file for a certain firmware version other than B391?
Click to expand...
Click to collapse
You haven't read OP #1?
Tecalote said:
You haven't read OP #1?
Click to expand...
Click to collapse
You didn't understand my question.
Can one modify the recovery.img from another firmware package, other than B391?
Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.
Is this possible? What should I look for?
For learning purposes.
kukubau said:
You didn't understand my question.
Can one modify the recovery.img from another firmware package, other than B391.
Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.
Is this possible? What should I look for?
For learning purposes.
Click to expand...
Click to collapse
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.
You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
@Atarii
Do you try downgrade using b300 update.app and then to b136 or b182???
Your method it's safe?? What when we brick device
Atarii said:
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.
You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
Click to expand...
Click to collapse
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
kukubau said:
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
Click to expand...
Click to collapse
if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
kukubau said:
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
Click to expand...
Click to collapse
Did you use the 2GB file?
Atarii said:
Did you use the 2GB file?
Click to expand...
Click to collapse
Yes.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
dkionline said:
if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
Click to expand...
Click to collapse
I've flashed my phone and unbricked it hundreds of times.
I've even posted an unbrick guide here on XDA forums.
I guess I know how to force flash it using the three key combo.
chudy_85 said:
@Atarii
Do you try downgrade using b300 update.app and then to b136 or b182???
Your method it's safe?? What when we brick device
Click to expand...
Click to collapse
I haven't personally tested this but I know others have for other device - so use at your own risk
kukubau said:
Yes.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
I've flashed my phone and unbricked it hundreds of times.
I've even posted an unbrick guide here on XDA forums.
I guess I know how to force flash it using the three key combo.
Click to expand...
Click to collapse
Im not using 3 key, only 1.
If not boot, you have manually boot with key i posted before.
This is so nice. Is it possible to make one for PO Plus, VIE-L09 and VIE-L29? Thanks
dkionline said:
Im not using 3 key, only 1.
If not boot, you have manually boot with key i posted before.
Click to expand...
Click to collapse
Doesn't boot into android os, no matter what.
I'll post a follow up after I try the B390 fw, maybe incremental updates are required.
So when it comes to the newly released EMUI8 for Honor 9 things get a little bit tricky, as we don't have any official update for our region yet (only for C900 and AL variants - chinese).
Every file i provided have been built during the way finding how stuff works on oreo - and alot of stuff changed EDIT: Official update is out for C432 - i recommend to not use the provided TWRP for daily, reliable usage.
PART 1
0. download the B360a zip from my mega folder
1. read README.txt from fw zip and follow the steps carefully (easy install)
2. have fun with official oreo
Rollback instructions
1. copy the rollback zip and nocheck recovery (!!oreo version!!) to the root of your MicroSD card
2. enable usb debugging in developer options
3. connect your phone to your computer, start an adb shell and issue the following commands:
Code:
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk
echo --update_package=/sdcard/update_rollback_al10c00b190.zip > /cache/recovery/command
4. last but not least reboot recovery, again in adb shell:
Code:
reboot recovery
5. your device should start to flash a chinese version of nougat (EMUI 5.1)
hint: if you get an error during the installation, just press the reboot button, it still boots.
device crashes during boot? do a low-level data partition format, boot into erecovery when you get asked to.
6. prepare the MicroSD (8gb atleast, exFAT formatted)
download the C432 firmware and extract it
copy the dload folder you extracted to the root of your MicroSD
7. if required unlock your bootloader
8. flash the nocheck recovery (nougat version) to recovery and recovery2 partition using fastboot
Code:
fastboot flash recovery STF_RECOVERY_NoCheck.img
fastboot flash recovery2 STF_RECOVERY_NoCheck.img
9. boot your device into force dload mode (keep vol+, vol- and power pressed until the installation starts)
10. you should boot into a fresh L09C432B100 installation
I've uploaded every file you need for the process to mega.nz - please do not mirror any of the stuff provided!
[url]https://mega.nz/#F!W1QUAIbZ!7Gbf79dC6NwD1e_zdY_O3Q[/URL]
Huge thanks to @LastStandingDroid for providing the modified SuperSU installation package.
Best Regards,
OldDroid
To fix the file manager, open your root file explorer and follow the steps carefully:
1. create a folder called "normal" in /cust/hw
2. create a second folder in the previously created one, name it "app"
3. now move HwCloudDrive_Local folder from /cust/hw/eu/app to /cust/hw/normal/app
4. reboot
Thank you!
I'll try it!
Does bootloader uncloked ?
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
BobekMark said:
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
Click to expand...
Click to collapse
don't relock the bootloader after the whole process
OldDroid said:
don't relock the bootloader after the whole process
Click to expand...
Click to collapse
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my result. :\
It's okay, or there should be some other apps? Or should it be C432 instead of C900 ? :S
(There is no Huawei Account option :S )
BobekMark said:
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
This is my result. :\
It's okay, or there should be some other apps?
(There is no Huawei Account option :S )
Click to expand...
Click to collapse
which h9 version do you have, C432?
OldDroid said:
which h9 version do you have, C432?
Click to expand...
Click to collapse
Yes (I updated the pictures)
BobekMark said:
Yes (I updated the pictures)
Click to expand...
Click to collapse
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
OldDroid said:
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
Click to expand...
Click to collapse
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
BobekMark said:
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
Click to expand...
Click to collapse
where did you find them?
I have problem with installation.
I have NTFS system files on my SD card and i can't mount this card in TWRP.
What i have to do?
Format to FAT32 or what?
So awesome, thank you for that.
Is there a version of this that will work the same or similar on the P10 (standard P10). Thanks
OldDroid said:
where did you find them?
Click to expand...
Click to collapse
There
BobekMark said:
There
Click to expand...
Click to collapse
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]View attachment 4337715View attachment 4337718View attachment 4337719
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Hi! And first of all, thanks a lot for this guide as you just gave hopeless H9 owners a bit of light...
Now I haven't gone through the process yet but I got a bit confused as of part.3 (that is recommended but not needed), should we unroot BEFORE flashing Ramdisk and Recovery Ramdisk? I then have an old UnSu script by Osmosis, would it work or the "Full Unroot" option from the SuperSu app is okay?
Thanks in advance for your reply and Thanks again for this guide!! Cheers
BobekMark said:
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Click to expand...
Click to collapse
Install huawei services from play store but it won't help ;P
Because online themes is disabled by default
Sent from my DUK-L09 using Tapatalk
Firmware Downloads
Changelogs:
2021
January Update / Pixel / Device Released: 04.01.2021
2020
December Update / Pixel / Device / Features Released: 07.12.2020
November Update / Pixel / Device Released: 02.11.2020
You flashed it or it was an OTA?
Changelog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link: https://support.google.com/pixelphone/thread/80591482
TokedUp said:
You flashed it or it was an OTA?
Click to expand...
Click to collapse
It was OTA
cheptii said:
Changelog:
Link: https://support.google.com/pixelphone/thread/80591482
Click to expand...
Click to collapse
Thanks, i add it to the OP
Bummer, I don't see anything about the battery bug.
Yeah i thought/hoped they would fix more with the first update
Does anyone know if magisk root works with this update correctly? I'd assume yes since it's not a large change.
ManicMondays said:
Does anyone know if magisk root works with this update correctly? I'd assume yes since it's not a large change.
Click to expand...
Click to collapse
Absolutely. Everytime. I don't know what you guys are doing wrong. But it works everytime.
Golf c said:
Absolutely. Everytime. I don't know what you guys are doing wrong. But it works everytime.
Click to expand...
Click to collapse
Can you please tell us how you updated your device? What are the steps to follow to keep magisk without having to patch the boot.img again ?
cheptii said:
Can you please tell us how you updated your device? What are the steps to follow to keep magisk without having to patch the boot.img again ?
Click to expand...
Click to collapse
I don't do that.I have my thing for years. I patch the boot image with the latest Canary. Transfer that image to my pc.
Flash the factory image after erasing -w in the flash all bat.file. So it doesn't erase your internal storage or data. Boot.
Boot back to bootloader.
Fastboot flash boot magisk-patched.img.
Done. Everything is as it was.
Simple.
Never took an OTA in my life. Against my Religion. Lol
---------- Post added at 01:52 AM ---------- Previous post was at 01:38 AM ----------
Give me a week to evaluate this update. I love the way everyone use to say it's faster. Hahahaha. It's not. It will settle down and be the same. Yummy!
Golf c said:
Flash the factory image after erasing -w in the flash all bat.file. So it doesn't erase your internal storage or data.
---------- Post added at 01:52 AM ---------- Previous post was at 01:38 AM ----------
Give me a week to evaluate this update. I love the way everyone use to say it's faster. Hahahaha. It's not. It will settle down and be the same. Yummy!
Click to expand...
Click to collapse
Could you please explain this in another way?
When are you executing? -w
Are you typing.- w in the flashall.bat?
What does - w do? If you don't do it then you will lose user data?
Why wouldn't this work instead?
adb sideload ota_file.zip
fastboot flash boot magisk_patched_boot.img
xT29c said:
Could you please explain this in another way?
When are you executing? -w
Are you typing.- w in the flashall.bat?
What does - w do? If you don't do it then you will lose user data?
Click to expand...
Click to collapse
Ugh. I'm removing -W in the Flash all bat. File. Otherwise it will wipe your data . -W In the factory image flash all. Bat for Windows wipes your data. Known as a clean flash.
Removing the -W from the flash- all bat. Provides a dirty flash. Data and Internal storage intact. And everything is the same as it was before
I have alot of respect for clean flashing if you have the proper back up
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
It's definitely faster. Like everyone else 10 years before me. Hahahaha. We shall see later
Golf c said:
Ugh. I'm removing -W in the Flash all bat. File. Otherwise it will wipe your data . -W In the factory image flash all. Bat for Windows wipes your data. Known as a clean flash.
Removing the -W from the flash- all bat. Provides a dirty flash. Data and Internal storage intact. And everything is the same as it was before
I have alot of respect for clean flashing if you have the proper back up
Click to expand...
Click to collapse
Gotcha! Thanks for the quick reply. But your method is for Full Android Images.
OTA, doesn't include the flash all.bat file you are referencing.
Would this work for an OTA file?
"adb sideload ota_file.zip"
"fastboot flash boot magisk_patched_boot.img"
After that, all user data remains intact?
xT29c said:
Gotcha! Thanks for the quick reply. But your method is for Full Android Images.
OTA, doesn't include the flash all.bat file you are referencing.
Would this work for an OTA file?
"adb sideload ota_file.zip"
"fastboot flash boot magisk_patched_boot.img"
Click to expand...
Click to collapse
Of course not. I don't do that. Don't be lazy. Let's celebrate the first of the Monday of the month. Like I do. There is supposed to be a way to do it. I can't help you with that
Golf c said:
Of course not. I don't do that. Don't be lazy. Let's celebrate the first of the Monday of the month. Like I do. There is supposed to be a way to do it. I can't help you with that
Click to expand...
Click to collapse
You are ****ing weird. But thank you for your reply.
Golf c said:
Of course not. I don't do that. Don't be lazy. Let's celebrate the first of the Monday of the month. Like I do. There is supposed to be a way to do it. I can't help you with that
Click to expand...
Click to collapse
I get this error when i try your method on Windows PC:
error: failed to load 'image-redfin-rd1a.200810.022.a4.zip': Not enough space
cubandanger05 said:
I get this error when i try your method on Windows PC:
error: failed to load 'image-redfin-rd1a.200810.022.a4.zip': Not enough space
Click to expand...
Click to collapse
Your a Momo. What can I say.
Golf c said:
Your a Momo. What can I say.
Click to expand...
Click to collapse
You will promptly be reported. You can kindly piss off.
cubandanger05 said:
I get this error when i try your method on Windows PC:
error: failed to load 'image-redfin-rd1a.200810.022.a4.zip': Not enough space
Click to expand...
Click to collapse
You need to extract the zip until you see all the files like boot.img and system.img
xT29c said:
You will promptly be reported. You are kindly piss off.
Click to expand...
Click to collapse
Are you using power shell or CMD?
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
xT29c said:
You need to extract the zip until you see all the files like boot.img and system.img
Click to expand...
Click to collapse
It's way beyond that