Database Users

TWRP blowing away OS - user error?

Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found

Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.

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.

[Solved] P8 Lite ALE-L21 HI6210SFT bootloop

Hi all,
Interesting problem. I've been updating some P8 Lite units that were shipped to us with a single SIM ROM with dual SIM ROM. I've already done two phones without issues (both ALE-L21). Onto the third phone (also ALE-L21), and this time there's a problem.
I'm not quite clear if the HiSilicon Kirin 620 and HI6210SFT are the same chipset or not. An answer to this would be helpful!
Steps taken:
Unlocked bootloader via Huawei website. Fastboot says PHONE Unlocked and fastboot oem get-bootinfo replies: (bootloader) unlocked
Flashed boot, recovery, cust, and system.img via fastboot following the guide (using dual SIM unbrick files)
Phone does not boot past Huawei logo, I get a black screen and then after a minute or so it reboots
Pretty odd, since I've done this on two other phones of the same model and the process worked without any issues.
TWRP 2.8.7 does not boot on the phone (black screen and reboot to Huawei logo)
TWRP 3.0.2 does boot.
Unfortunately I didn't think to take a backup of the system before I started this since I'd done it twice before without problems.
Here's what I've tried to do to get this phone to boot again:
Took TWRP backup of another ALE-L21 running B584 and restore it. Result: bootloop/not booting past Huawei logo
Flashed B052 via fastboot from here. Result: bootloop/not booting past Huawei logo
Flash recovery.img from the guide (not sure which OS version this is based on) and put UPDATE.APP for B052 on sdcard\dload\UPDATE.app. Result: black screen after Huawei logo, no activity
Tried the above with UPDATE.APP from B584. Result: black screen after Huawei logo, no activity
Using Huawei eRecovery from fastboot. Result: "getting package info failed"
I know the phone isn't bricked, because TWRP 3.0.2 still boots.
However, I cannot for the life of me get any Huawei OS to boot on this phone anymore. I'm using fastboot for everything (Linux) and I don't have any problems to flash:
$ fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.887s]
writing 'boot'...
OKAY [ 1.692s]
finished. total time: 2.580s
$ fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 1.420s]
writing 'recovery'...
OKAY [ 2.615s]
finished. total time: 4.036s
$ fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 8.815s]
writing 'cust'...
OKAY [ 5.691s]
finished. total time: 14.507s
$ fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 24.211s]
writing 'system'...
OKAY [ 10.338s]
sending sparse 'system' (460385 KB)...
OKAY [ 23.630s]
writing 'system'...
OKAY [ 10.617s]
sending sparse 'system' (460747 KB)...
OKAY [ 23.682s]
writing 'system'...
OKAY [ 11.319s]
sending sparse 'system' (457010 KB)...
OKAY [ 23.684s]
writing 'system'...
OKAY [ 10.537s]
sending sparse 'system' (443304 KB)...
OKAY [ 23.432s]
writing 'system'...
OKAY [ 10.011s]
finished. total time: 171.461s
My next step would be to try a custom ROM, but there isn't much choice here of flashable zips, and all the custom ROMs seem to be broken or missing features. what I really want is to get this phone back to booting the Huawei OS, but this is seeming impossible.
I'm using Ubuntu 16.04 amd64 and have no issues with adb/fastboot or drivers.
Does anyone have any ideas why this phone refuses to boot after the attempted dual SIM conversion?

I don't really know about this stuff but
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.

keikari said:
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.
Click to expand...
Click to collapse
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?

icewewe said:
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?
Click to expand...
Click to collapse
Power + Vol UP
---------- Post added at 07:41 PM ---------- Previous post was at 07:34 PM ----------
Also you can test updateflaher.zip from this thread to use TWRP to install stock rom https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702. I'm not sure will it work for p8lite, but it can install p8lite firmware to honor4x so maybe it can also install p8lite firmware to p8lite. No idea will it help though.

I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.

keikari said:
Power + Vol UP
Click to expand...
Click to collapse
Does nothing. I get the Huawei logo and then a black screen.
bumjrah said:
I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.
Click to expand...
Click to collapse
What guide are you referring to? The one I linked to doesn't use TWRP and flashes the system via fastboot, which doesn't require a wipe.

Okay, I fixed the issue. I'm really not sure why it didn't work before.
Here are the steps I took:
Restored a TWRP backup I took of another ALE-L21 running B584
Wipe Data/Cache
Flash RECOVERY.img from B584 UPDATE.APP
But then I had the Balong bug. I figured out this is because the oeminfo partition contained data from somewhere. Lollipop or the single SIM build, I don't know.
The UPDATE.APP containing the fix for Balong wouldn't flash in the Huawei recovery. Probably because it's intended for Lollipop and B584 is MM. Or something. Whatever.
So I flashed TWRP and using adb created /data/custom.bin with
Code:
hw/eu
and permissions 0666. This got rid of Balong build, but neither SIM card was recognized by Android.
Then what I did was take a copy of oeminfo from another hw/eu phone, one I had successfully converted earlier, and flashed that. For others reading, oeminfo partition is /dev/block/mtdblk0p8. It's 32MB but almost entirely 0's, so the zip compressed version is really small (80KB).
So here are the steps again:
Restore TWRP backup of another phone running B584
Wipe Data/Cache
Flashed oeminfo for hw/eu from another phone running B584
Flashed Huawei stock recovery from B584
Performed a system update using Huawei recovery with B584 UPDATE.APP
Now the phone recognizes both SIM cards correctly, and has the correct region/oeminfo.
If anyone else has problems with Balong build and you're running MM, here is the oeminfo I used to fix the phone. You will need to unzip and flash in TWRP (or Android if you have root) using the dd command listed above.
Example:
Code:
unzip oeminfo-eu.zip
adb push oeminfo-eu.bin /tmp/
adb shell
dd if=/tmp/oeminfo-eu.bin of=/dev/block/mmcblk0p8

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.

Need low level format by second hand Mi 9T ... to fastboot loop!

Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Never format persist partition u will be stuck in a fastboot loop, flash this twrp with the pc it has its own script and boot into twrp i guess u just have a missing vbmeta that can cause twrp to disappear in some cases
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Also you can use MiFlash and fastboot rom file to flash stock rom from scratch from fastboot.

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Flash stock rom using miflash,
Uncheck clean and lock

finally I used mi flash ... I modified the "format all and lock" file, to circumvent anti-rollback.
I installed miui 11. Now everything is fine ... thanks