Database Users

Problem to install TWRP to the Huawei P8 with Mac OS X.

I am quite new to the android rooting & custom recovery and having a problem with my Huawei P8 GRA-UL00 flashing (purchased from China), when I try the procedure with MAC OS X. My step by step actions and result was as follows:
1. I installed "SDK Tools Only" for Mac. Connected the device via USB, launched terminal and successfully see the device with the "adb devices" command.
2. Vol +, Vol- and Power didn't work to enter to the fastboot&rescure mode. However, Vol- and Power worked. (Also, Vol+ and Power enters to the Huawei eRecovery mode, which shows EMUI logo, Reboot, Download new version and recovery and Shutdown buttons. I guess this is stock recovery???)
3. In the fastboot mode, I have successfully seen the device with "fastboot devices". Then I unlocked the bootloader with the code. The first problem was here, there were no auto-reboots and I entered "fastboot reboot" command, and stuck in seeing "reboooting..." in terminal. Nothing happened after this command. After 10 minutes I manually rebooted the phone by pressing power and entered into the fastboot mode. I was written as "Phone Unlocked". (Do u think it was really successful?)
4. I tried to flash the TWRP file which was uploaded by @jniklast (openrecovery-twrp-2.8.7.0-p8-ul10-r4.img). The result was like that:
MacBook-Airlatform-tools go$ ./fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img
target reported max download size of 471859200 bytes
sending 'recovery' (25566 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 1.056s
MacBook-Airlatform-tools go$
5. Tried fastboot reboot, but I wasn't successful:
MacBook-Airlatform-tools go$ ./fastboot reboot-bootloader
rebooting into bootloader...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.121s
MacBook-Airlatform-tools go$
I am not sure if I have correctly defined my problem. I guess I wasn't successful to install TWRP even it says so. What should I do after finishing the flash recovery command?
Can anyone help me with this error?

@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.

I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.

samusalo said:
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
Click to expand...
Click to collapse
Thank you samusalo.. Then I understand that TWRP for GRA-L09 can work on a GRA-UL00. I will try.
jniklast said:
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
Click to expand...
Click to collapse
I don't use adb reboot, I manually press Vol - and Power. Then, the Fastboot & Rescue mode opens, and I enter to the terminal "fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img". It quickly shows that the installation is successful. Then I enter fastboot reboot-bootloader (I guess this is required to launch TWRP) but it shows that usb read error.

@jniklast and @samusalo thank you for your explanations. They both worked.
I flashed the GRA-L09 version of the TWRP to my GRA-UL00 and it worked! Now I have a backup...
I also realized that I am doing something wrong.. After installing TWRP, I was trying to fastbot reboot-boatloader in order to get TWRP launched automatically. However, the only thing I need to do is to follow jniklast's instructions and after the phone shut down, press Vol+ Vol- and Power together to get the TWRP launch.
Now I will try to flash an official International ROM, instead of my Chinese ROM.
Is the following command correct for this?
fastboot flash system "HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version).zip"

No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor

jniklast said:
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
Click to expand...
Click to collapse
Many .img files exists in the update.app file. I guess I need to flash only the system.img?
If I flash the recovery.img or boot.img inside the update.app, will I lose the custom recovery and my backup?

I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky

Partially Successful
jniklast said:
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
Flashing boot and system was successful! Then, again, my "fastboot reboot-bootloader" didn't work and retured me my initial error. But I rebooted manually and successfully launched my phone OS.
I now have a slow-operating new Android firmware, which is a little weird )) I think it is now a international&chinese hybrid version. Some apps disappeared and I have a complete new page for google services and apps. However, my chinese stuff (baidu spotlight search, notifications, etc.) remains The EMUI Build is: GRA-UL00V100R001C00B120, which should be V100R001C900B141 as I have flashed the img files of this update.
I tried "fastboot erase userdata", "fastboot erase cache" and "fastboot erase system" but they both returned with "FAILED (remote: Command not allowed)".
The following were my successful fastboot flash commands:
MacBook-Airlatform-tools go$ ./fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23256 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.569s]
finished. total time: 1.222s
MacBook-Airlatform-tools go$ sudo ./fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459646 KB)...
OKAY [ 20.184s]
writing 'system'...
OKAY [ 6.149s]
sending sparse 'system' (450260 KB)...
OKAY [ 22.868s]
writing 'system'...
OKAY [ 6.051s]
sending sparse 'system' (437337 KB)...
OKAY [ 18.146s]
writing 'system'...
OKAY [ 5.952s]
sending sparse 'system' (460637 KB)...
OKAY [ 19.570s]
writing 'system'...
OKAY [ 6.267s]
sending sparse 'system' (448019 KB)...
OKAY [ 18.582s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (165186 KB)...
OKAY [ 6.853s]
writing 'system'...
OKAY [ 2.206s]
finished. total time: 138.824s
MacBook-Airlatform-tools go$

jniklast said:
it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
I was finally successful to flash cust.img with fastboot and now I have B141 and all Chinese apps are removed. All Chinese ROM specific apps are disappeared and the only remaining Chinese stuff is the text in the Magazine Unlock, accessible when swiped up from the bottom of the screen at the lock screen.
The remaining problem for now is; when I press the Dialer, Contacts and Messages apps at the bottom, they crash.
Do I need to flash any other from the following extracted img files?
3RDMODEM.img
CACHE.img
CRC.img
CURVER.img
DTIMAGE.img
EFI.img
FASTBOOT.img
HIFI.img
MCUIMAGE.img
MODEM.img
MODEM_DSP.img
MODEMNVM_UPDATE.img
RECOVERY.img
RECOVERY2.img
SENSORHUB.img
SHA256RSA.img
TEEOS.img
TRUSTFIRMWARE.img
USERDATA.img
VERLIST.img
XLOADER.img

This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8

jniklast said:
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
Click to expand...
Click to collapse
Hello again,
Actually the hardware is the same, it is GRA-UL00. The device originally had: GRA-UL00-UL10_EMUI3.1_Android5.0_C00B173
I tried to fastboot the following ROM:
HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version)
I was successful to flash Root, CUST and System but when I try to flash any Modem-related img files (Modem.img, 3RDMODEM.img, MODEM_DSP.img, MODEMNVM_UPDATE.img), I get the following error:
sending 'modem' (38865 KB)...
OKAY [ 1.038s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 1.039s
I didn't try to install APKs.
I am still having crash problems with the dialer, contacts, messages, google play, and some other google services.

Network Mode FREEZE AUTO
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.

Finally Done!
meetkhems said:
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Click to expand...
Click to collapse
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.

landros57 said:
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
Click to expand...
Click to collapse
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.[/QUOTE]

meetkhems said:
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.
Click to expand...
Click to collapse
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.

Any Update on this anyone? I am unable to use the phone as it drains a lot of battery on 3G and i cant change it to 2G as due to Blank Mobile Network Settings.

Guys I have one problem I want to flash stock recovery for P8 L09 but in cmd it fails like not allowed command anybody knows why ?

landros57 said:
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Click to expand...
Click to collapse
Hi landro57 have you tried to flash the update.app file of 18 Kb from local update? Some owners of the P8 gra ul09 variant are using that file to debrand their P8s. The mobile networks problem you ae experiencing is the same some other people have turnaround with that trick. You should check with it and report back to us, because if that goes ok, it means no more china firmware on our P8 gra ul00, we can simply flash the international general P8 firmware V100R001C900B141.
Inviato dal mio SGP311 utilizzando Tapatalk

GryphonA said:
flash the update.app file of 18 Kb from local update
Click to expand...
Click to collapse
Hi GryphonA, I don't get it, which 18kb update.app file do you mean?
I got the same problem (no access to mobile networks settings) and I can't remember if I never had that access or it happened due to my rooting/cusomizing activities.
I have GRA-UL00C433B180. I flashed also C470B180 but that didn't solve the problem.
BTW: There are a lot of mobile network setting apps and widgets in the Play Store but all apps I tested show the same failure as the mobile network settings: There seems to be a network reset and nothing more.

Marshmallow factory images are available.

Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.

https://developers.google.com/android/nexus/images

Flash-all script worked like a charm, setting everything up right now

But it's not February yet.

maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer

Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.

Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!

I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.

PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk

Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc

I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here

I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???

Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk

Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img

gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.

Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL

Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s

NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?

Deleted

No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.

Need help trying to unbrick phone

Hello,
I was trying to bring phone back to factory state and I messed things up. My options are very limited and I'd like to ask for help.
I have Revolution Recovery installed on my phone. I made backups of data, system, boot, oeminfo, cust. I flashed custom oeminfo from this thread. I hoped to download a rescue package via Huawei eRecovery. But it said that my data partition is corrupted and asked me to format it. So I did. My data is wiped and formatted. But it shows cannot download package after trying.
Right now, I can access fastboot, but I cannot flash anything:
Code:
$ fastboot flash recovery ~/Desktop/RevolutionRecovery_Nougat_P9Lite/TWRP.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.691s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.697s
When I try to start the phone (normal start, or volume up + power key) it goes straight to Huawei eRecovery. I cannot open recovery.
My phone is VNS-L31, before any changes I wrote down build number from system settings: VNS-L31C432B371. I bought it through an online store in Switzerland last summer, so I probably have some Europe edition. I don't have any backups from the initial state before I even had my custom rom installed.
Is there any chance to install recovery or whatever straight from SD card?
I'm happy to provide any additional data if I know what else is needed.
Thanks for help!

There is. That "FAILED (remote: Command not allowed)" just means you somehow locked your booloader again.
Mou must revert back to MM, which uses dload method.
It is quite easy, just follow https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955

Oneplus 6T 8/256GB LineageOS problem

Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Code:
[email protected]:~/Downloads/ota/output$ ./fastboot update images.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e5a9f9c
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (64 MB) to disk... took 0.187s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.032s]
Writing 'boot_a' OKAY [ 0.333s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.052s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2860 MB) to disk... took 12.379s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/6 (513608 KB) OKAY [ 16.216s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/6 (514145 KB) OKAY [ 18.289s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 3/6 (515013 KB) OKAY [ 18.389s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/6 (515534 KB) OKAY [ 18.281s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 5/6 (510919 KB) OKAY [ 18.317s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 6/6 (184768 KB) OKAY [ 8.139s]
Writing 'system_a' OKAY [ 0.001s]
archive does not contain 'system_ext.img'
archive does not contain 'system_other.img'
extracting vendor.img (1024 MB) to disk... took 4.095s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Sending sparse 'vendor' 1/2 (511135 KB) OKAY [ 16.211s]
Writing 'vendor' OKAY [ 0.001s]
Sending sparse 'vendor' 2/2 (389097 KB) OKAY [ 15.169s]
Writing 'vendor' OKAY [ 0.001s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 10.729s]
Finished. Total time: 165.761s

mudlee said:
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Click to expand...
Click to collapse
Can you Reboot to Fastboot? If so then load up TWRP via Fastboot Boot. Once in TWRP, flash OOS ZIP and TWRP Installer. Once that's done, Reboot to Recovery and Again flash OOS ZIP and TWRP Installer. Then Format Data by going to Wipe -> Format Data. Once that's done, Reboot to OOS and skip the Initial Setup. Transfer the LOS ROM and TWRP Installer as well as Gapps to Phone Storage and Reboot your phone to Recovery. Once there, go to Install and Flash LOS and TWRP Installer. Once that finishes, Reboot to TWRP and flash Gapps. After flashing Gapps, Format Data again and Reboot. Hopefully you boot into LOS. Also, if you are trying to install LOS 16, Use OOS 9.0.17 ZIP and if you're trying to Install LOS 17, Use OOS 10.3.0

thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.

mudlee said:
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
Click to expand...
Click to collapse
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.

DarthVader said:
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
Click to expand...
Click to collapse
:-O I have to grab a windows pc then.

mudlee said:
:-O I have to grab a windows pc then.
Click to expand...
Click to collapse
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.

DarthVader said:
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
Click to expand...
Click to collapse
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS

mudlee said:
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
Click to expand...
Click to collapse
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran
Code:
fastboot flash boot twrp.img
then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg

mudlee said:
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
Click to expand...
Click to collapse
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?

DarthVader said:
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
Click to expand...
Click to collapse
- As I said, I tried multiple twrp versions. Currently I'm trying out this one: https://eu.dl.twrp.me/fajita/twrp-3.3.1-1-fajita.img.html
- OOS: 10.3.0
- Android: 10
Maybe the problem is that I flashed last time too new OOS and that's why twrp does not work?

The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.

mudlee said:
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
Click to expand...
Click to collapse
Are you trying to install LOS 17 or 16?

DarthVader said:
Are you trying to install LOS 17 or 16?
Click to expand...
Click to collapse
I installed LOS 16 in the end, I might try the unofficial 17 as well, will see if I have time. I'm getting used to this flashing this and that here and there stuff
Thank you for your really valuable help!

eellogofusciouhipoppokunurious
Quote:
Originally Posted by OhioYJ
Appreciate it. This step maybe the key. I was using the TWRP installer, that maybe where I was going wrong. I'll have to give it another try.
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
(CUSTOM ROM)
lineage-17.1-20200115_153235-UNOFFICIAL-fajita
(TWRP WITH SUCESSFULL DECRYPTION OF BASE STOCK ROM / CUSTOM ROM STORAGE)
twrp 3.3.1-30 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - arm64-10.0-pico-20200116-BETA
(Latest)
RadioactiveKernel _ V10.2.0_CUSTOM_OnePlus6-6T
(Latest)
NanoDroid - 22.5.1.20200102
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE/WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MY)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
Last edited by Johndoesmoked; 18th January 2020 at 07:13 AM. Reason: i dont know
Michelsup
19th January 2020, 08:55 AM |#743
Member91 posts Thanks: 133
Quote:
Originally Posted by OhioYJ
You were able to install TWRP? A lot of us cant install TWRP anymore, only boot it. If this has changed it would be nice to have a recovery
There was a bug on the first 17.1. With the last builds you can update like you always did; lineage.zip, twrp.zip, reboot to twrp, gapps.zip, magisk.zip, reboot and profit.
Of course you obviously had to update /vendor, as stated on Luk's post.

Install Android 12 Beta

Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!

Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson

Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson

speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.

A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...