Database Info

[Q] flash system.img from recovery, please help me

When i put
flash_images system /sdcard/system.img
i have error 1 on TRWP recovery
sorry for my English :3

kingspeed said:
When i put
flash_images system /sdcard/system.img
i have error 1
sorry for my English :3
Click to expand...
Click to collapse
I tried several things and never succeded. Tried to make a flashable zip able to flash images, but wont work.

kingspeed said:
When i put
flash_images system /sdcard/system.img
i have error 1 on TRWP recovery
sorry for my English :3
Click to expand...
Click to collapse
You can't flash images from recovery, only zips. You need to use fastboot to flash a system image.

So there isn't any way

kingspeed said:
So there isn't any way
Click to expand...
Click to collapse
Actually, looking at your screenshots I might be wrong. I'm still on 2.8.0 and there is no option to flash images, only zips. But it looks like the version of TWRP you're running does have the option to flash images. I've never seen that before, you learn something new every day I guess. That being the case, I don't know why you would be getting that error. Are you sure you're trying to flash the correct image?
EDIT: I just checked out the TWRP thread, and according to the OP, you can only flash boot and recovery images, not system images. So I guess my original post still stands. If you want to flash a system image, you need to use fastboot. Otherwise, flash a ROM.
http://forum.xda-developers.com/showpost.php?p=47108907&postcount=1
What's the big deal? Why not just use fastboot?

Thank you sir
did you know if anyone modified system.img to .zip ?
just system file without data
for don't delete my app
and again sorry for my English

Fastboot flash system system.img is all you need

oh i didn't read the last one
unfortunately my computer breakdown last night and where i live in syria there isn't a lot of computers

kingspeed said:
oh i didn't read the last one
unfortunately my computer breakdown last night and where i live in syria there isn't a lot of computers
Click to expand...
Click to collapse
Are you unable to boot or something? Can you get a ROM onto your phone and flash that?

no i cann't flash any rom
and now i try to install Miui and flash it on MultiRom

kingspeed said:
no i cann't flash any rom
and now i try to install Miui and flash it on MultiRom
Click to expand...
Click to collapse
What do you mean you can't flash any ROM? Please try and be as clear as possible- if I don't understand what's going on, I can't be of much assistance.
What situation are you in? How did you get into your current situation?

So is your original system wiped? You can't boot into android anymore?

I'm so sorry sir
I have multirom manager , and by mistake I install Miui OS on the primary OS , after 10 seconds i stop it , so the primary KitKat system wiped.
Thanks to god I solved this problem by flash system.img from laptop and flash another recovery by (NRT toolkit ) than open multirom from the primary OS to reinstall last version of kernel and TWRP recovery

If you have the latest twrp you can flash img. If there is an error then the system.img must be corrupt (maybe bad download). Is your multirom up to date?
Sent from my Nexus 5 using XDA Premium App

wangdaning said:
If you have the latest twrp you can flash img. If there is an error then the system.img must be corrupt (maybe bad download). Is your multirom up to date?
Sent from my Nexus 5 using XDA Premium App
Click to expand...
Click to collapse
It was my understanding that you can flash any .img other than system.img. At least that's what it said in the OP of the TWRP thread when I read it the other day.
---------- Post added at 06:56 AM ---------- Previous post was at 06:54 AM ----------
kingspeed said:
I'm so sorry sir
I have multirom manager , and by mistake I install Miui OS on the primary OS , after 10 seconds i stop it , so the primary KitKat system wiped.
Thanks to god I solved this problem by flash system.img from laptop and flash another recovery by (NRT toolkit ) than open multirom from the primary OS to reinstall last version of kernel and TWRP recovery
Click to expand...
Click to collapse
So are you up and running then?
And FYI, stop using toolkits. You should have flashed recovery the same way you flashed system.img, from your laptop with fastboot. Toolkits can cause a lot of problems and if you rely solely on them, you'll never learn how to fix any problems that you may encounter.

Oh, never actually used it, just knew you could flash img files.
Sent from my Nexus 5 using XDA Premium App

Thank you all :* , now everything fine.
just how to install CM 12 on Multirom if was the primary kitkat
i try to install this ,than flash official CM12 but it stuck on logo :3

ROOT-TWRP-UNLOCK BOOTLOADER FOR LENOVO K6 NOTE (K53a48)

I am not responsible if you don't know
what you are getting into and end up messing up your phone
In order to root K6 Note you need to do the following,
1. Unlock boot loader. how to do that follow here >>
http://lenovo-forums.ru/topic/21685-lenovo-vibe-k6-note-разблокировка-bootloader
( It will Wipe all Data)
2. Install Twrp from here>>
http://lenovo-forums.ru/topic/21687-lenovo-vibe-k6-note-rasshirennoe-rekaveri-twrp-by-sevenmaxs/
3. Modify boot image and flash modified boot image with Carliv Image Kitchen from here >>
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
4. Changing Values in boot.img
Unpack the boot image using the above tool, once unpacked go the unpack folder then into ramdisk folder and edit the default.prop using notepad++ or wordpad
Change the value of the following lines
1. ro.secure=1 to ro.secure=0
2. security.pref_harden= 1 to security.pref_harden= 0
(Change only 1 to 0 nothing else & do not forget to save the file )
3.Once done repack the boot image using the above tool.
5 .Flash the modified boot.image through fastboot, how to flash through fastboot refer here>>
https://forum.xda-developers.com/showthread.php?t=1752270
6. Reboot into recovery and flash supersu from here>>
https://download.chainfire.eu/1001/S…perSU-v2.78-20
The supersu installation should be successful now. reboot and you will see supersu app in the app drawer. Cheers :good::good::good::good:
(P.S I have attached the modified boot image for firmware k53_s123_170216_ROW, so no need to modify the boot image if you are on this firmware.)

Where is the attached k53_s123_170216_ROW boot image ?

mehmet6ok said:
Where is the attached k53_s123_170216_ROW boot image ?
Click to expand...
Click to collapse
Boot.img updated. Cheers

Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
tools>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (24894 KB)...
OKAY [ 0.816s]
writing 'boot'...
OKAY [ 0.331s]
finished. total time: 1.151s
Click to expand...
Click to collapse
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?

If will not modify the boot.img what will gonna happen?
Thanks to this furom....Really help for me

webvan said:
Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?
Click to expand...
Click to collapse
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?

Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?

firemax13 said:
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?
Click to expand...
Click to collapse
webvan said:
Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?
Click to expand...
Click to collapse
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?

firemax13 said:
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?
Click to expand...
Click to collapse
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.

adilrenzu said:
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.
Click to expand...
Click to collapse
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english

firemax13 said:
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english
Click to expand...
Click to collapse
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.

Can the stock recovery be downloaded anywhere ? Thanks !

adilrenzu said:
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.
Click to expand...
Click to collapse
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....

firemax13 said:
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....
Click to expand...
Click to collapse
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.

Hi there, mate. If I do this process, will I be able to remove TWRP if needed (for updating reasons), if so, what would the process be?

adilrenzu said:
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.
Click to expand...
Click to collapse
So you can't reflash the original recovery ? So that means no more OTA updates, but would it still work with an official update that was downloaded, assuming one becomes available ? Thanks !

adilrenzu
I was able to unlock bootloader, installed twrp and root according to your guide
and
also successfully returned to original stock 6.0 rom, stock recovery according to androidmtk's Lenovo_K53_USR_S107_1609131839_Q00380_ROW firmware.
This is a new toy for me now. Many thanks...:laugh:

Can you explain how you went back to stock?

webvan said:
Can you explain how you went back to stock?
Click to expand...
Click to collapse
Hi
Device cant update via ota. I dont really know K53_USR_S107_1609131839_Q00380_ROW firmware is last for some region or not. So Im trying to update to stock K53_S123_170216_ROW firmware. After testing and solving ota I will write all steps.

ok, thanks, I suppose it need to be downloaded first somewhere ?

(UNOFFICIAL)(BETA) TWRP 3.2.1-3 For OnePlus 6

Stock Rom 5.1.5 (Fastboot Method)(6-8-2018):
https://drive.google.com/open?id=1Tq7aYB0TdsC5FcGxNT-UYdt8ON2Dtntj
Unzip, copy and paste commands. Works 10000% of the time. If it doesn't you skipped a step
********************************************
Temporary TWRP: (6-5-2018) This is if you want mods (kernels+other zips) but want to keep stock recovery @joemossjr
https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ
Run command inside fastboot folder: fastboot boot twrpbootable.img
********************************************
TWRP 3.2.1-x Themes: (6-4-2018) @lollyjay
https://androidfilehost.com/?w=files&flid=233367
********************************************
Updated TWRP 3.2.1-3 (fixed): (6-2-2018) @joemossjr
Flash twrp.img via TWRP<------------If you have TWRP installed already
fastboot flash boot twrp.img <------------If you don't have TWRP at all
https://drive.google.com/open?id=1PhPpzH1o9kqVgDmkkV0tfAIG1lXkJTD5
Flash root via TWRP:
https://drive.google.com/open?id=13Iu3iOXeSJIBMXzzX5X9Og55exmJ8BJd
********************************************
Modded (Beta)TWRP 3.2.1-0 (Until We Get Official From TWRP.ME)
Disclaimer: @charlieb620 or @joemossjr is not responsible for you not following directions [emoji14]
***FEEL FREE TO SKIP A STEP......IT WON'T WORK; START OVER***
Prerequisites: (thing or things that are required as a prior condition for something else to happen or exist)
-Unlocked Bootloader
-Running 5.1.5 OS
***FOLLOW THIS STEP BY STEP. IF YOU EXPERIENCE ERRORS, BROKEN WIFI, BOOTLOOPING, SOFTBRICK, HARDBRICK YOU DID SOMETHING WRONG; START OVER***
Download these files:
https://drive.google.com/open?id=1MJCcJAUgRAudolr3dmXgvk9rmWVlpgAi
-Put boot.img , root.zip, TWRP-BLUE-FIX.zip, and TWRPWorkingInstaller.zip on phone memory
-Put twrp.img in your fastboot/adb folder
Boot into bootloader mode
Flash using these commands (Recovery must be flashed to both partitions in order to boot):
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
Boot into TWRP from bootloader (vol up or vol down until you see recovery)
Decrypt using your lockscreen passcode
TWRP will boot in Chinese (change to English): Boot into recovery through bootloader, 3rd row to the right is Settings, pick the globe and switch to English
Flash boot.img via TWRP
Flash TWRPWorkingInstaller.zip
Flash TWRP-BLUE-FIX.zip
Flash Root.zip or you will bootloop
DONE

I just flashed Frankenkernel using this and it works perfectly :good: Thanks

The blue fix is The same as the installer bro?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Btw I made one you can just flash now wifi works

joemossjr said:
The blue fix is The same as the installer bro[emoji106]
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Btw I made one you can just flash now wifi works
Click to expand...
Click to collapse
Unless you updated it sir. You need to flash the blue fix or TWRP will be orange.

charlieb620 said:
Unless you updated it sir. You need to flash the blue fix or TWRP will be orange.
Click to expand...
Click to collapse
Yes I like the orange and I kept it lol

Hey,
Is this the same TWRP as post 70 from the other thread?
Sent from my OnePlus6 using XDA Labs

charlieb620 said:
Unless you updated it sir. You need to flash the blue fix or TWRP will be orange.
Click to expand...
Click to collapse
Eh orange is cool lol

lollyjay said:
I just flashed Frankenkernel using this and it works perfectly :good: Thanks
Click to expand...
Click to collapse
Did you install Frakenkernel for Oneplus 6 ? for stock rom ? May I get the link ?

rav101 said:
Hey,
Is this the same TWRP as post 70 from the other thread?
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
It is post 70 from the other thread, just moved out of the thread so people don't have to dig for it since it's extremely popular and the OP for some reason didn't put it on the OP

anupsnair said:
Did you install Frakenkernel for Oneplus 6 ? for stock rom ? May I get the link ?
Click to expand...
Click to collapse
It's in test phase rn
Go to the Telegram chat
Sent from my OnePlus6 using XDA Labs

Bradl79 said:
It is post 70 from the other thread, just moved out of the thread so people don't have to dig for it since it's extremely popular and the OP for some reason didn't put it on the OP
Click to expand...
Click to collapse
Awesome, thanks for confirming buddy
lollyjay said:
It's in test phase rn
Go to the Telegram chat
Click to expand...
Click to collapse
Do you have a link to the telegram group?
Sent from my OnePlus6 using XDA Labs

rav101 said:
Awesome, thanks for confirming buddy
Do you have a link to the telegram group?
Click to expand...
Click to collapse
Look in here:
https://forum.xda-developers.com/on...om-franken-official-8-1-t3775733/post76182154
Sent from my OnePlus6 using XDA Labs

charlieb620 said:
Modded (Beta)TWRP 3.2.1-0 (Until We Get Official From TWRP.ME)
Disclaimer: @charlieb620 or @joemossjr is not responsible for you not following directions [emoji14]
***FEEL FREE TO SKIP A STEP......IT WON'T WORK; START OVER***
***FOLLOW THIS STEP BY STEP. IF YOU EXPERIENCE ERRORS, BOOTLOOPING, SOFTBRICK, HARDBRICK YOU DID SOMETHING WRONG; START OVER***
Click to expand...
Click to collapse
Okay but what do we do if we flashed a and b partitions as you directed and we get stuck on TWRP bootup forever, and can't even boot into OOS?
I keep running into this problem
lollyjay said:
I just flashed Frankenkernel using this and it works perfectly :good: Thanks
Click to expand...
Click to collapse
Where is frankenkernel?!

masri1987 said:
Okay but what do we do if we flashed a and b partitions as you directed and we get stuck on TWRP bootup forever, and can't even boot into OOS?
I keep running into this problem
Where is frankenkernel?!
Click to expand...
Click to collapse
See post above
Sent from my OnePlus6 using XDA Labs

lollyjay said:
Yes I like the orange and I kept it lol
Click to expand...
Click to collapse
Franken kernel Op6?
Enviado desde mi ONEPLUS A6003 mediante Tapatalk

Do not quote the OP.

charlieb620 said:
Modded (Beta)TWRP 3.2.1-0 (Until We Get Official From TWRP.ME)
Click to expand...
Click to collapse
did you check this variant: try this post : https://forum.xda-developers.com/showpost.php?p=76681988&postcount=203
this twrp is blue without extra step and snappy without fix
further with this variant you can flash magisk 16.4 as it always have been from recovery, no need to flash an entire kernel, just flash the zip like for any other device and you'll be rooted.
i found out that wifi only breaks if for whatever reason (user error) someone is booting from the wrong slot.

magnamentis said:
did you check this variant: try this post : https://forum.xda-developers.com/sho...&postcount=203
this twrp is blue without extra step and snappy without fix
further with this variant you can flash magisk 16.4 as it always have been from recovery, no need to flash an entire kernel, just flash the zip like for any other device and you'll be rooted.
i found out that wifi only breaks if for whatever reason (user error) someone is booting from the wrong slot.
Click to expand...
Click to collapse
Link not working for me and OP method allows me to flash Magisk
Sent from my OnePlus6 using XDA Labs

magnamentis said:
did you check this variant: try this post : https://forum.xda-developers.com/sho...&postcount=203
this twrp is blue without extra step and snappy without fix
further with this variant you can flash magisk 16.4 as it always have been from recovery, no need to flash an entire kernel, just flash the zip like for any other device and you'll be rooted.
i found out that wifi only breaks if for whatever reason (user error) someone is booting from the wrong slot.
Click to expand...
Click to collapse
You can flash 16.4 with this variant as well (updated in OP). No different.

lollyjay said:
Link not working for me and OP method allows me to flash Magisk
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
thanks for letting me know: https://forum.xda-developers.com/showpost.php?p=76681988&postcount=203
link corrected in original post
good to know that things develop fast all around, the post is two days old, a lot of time at this stage after device release
if you still read the post in the link you'll see that there's more to it than magisk flashing, it's blue without blue fix and extremely snappy for one
but then again, it's just shared info so everyone has the chance to find max input

TWRP removed every time i reboot

every time i install TWRP recovery and reboot its roll back to stock recovery.
Root and Magiks work perfectly. how to solve this problem ?
bootloader unlocked
OOS: 5.1.11

Try installing TWRP reboot back to Recovery ( don't reboot phone) then reboot phone.

ariyan rana said:
every time i install TWRP recovery and reboot its roll back to stock recovery.
Click to expand...
Click to collapse
Could you tell us exactly what the steps are that you're using to install TWRP when it fails? Are you doing this from a command line with:
Code:
fastboot boot twrp.img
If you are, that boots you into TWRP temporarily, but it doesn't install it on the device.
To do that, you need to install twrp.zip from within TWRP after booting into it per the command line step above?
Or are you trying something else?

maigre said:
Could you tell us exactly what the steps are that you're using to install TWRP when it fails? Are you doing this from a command line with:
Code:
fastboot boot twrp.img
If you are, that boots you into TWRP temporarily, but it doesn't install it on the device.
To do that, you need to install twrp.zip from within TWRP after booting into it per the command line step above?
Or are you trying something else?
Click to expand...
Click to collapse
i didnt install twrp.zip, maybe thats why my custom recovery get lost every time i reboot.

ariyan rana said:
i didnt install twrp.zip, maybe thats why my custom recovery get lost every time i reboot.
Click to expand...
Click to collapse
Not maybe.. That is why! Lol =p when following a guide, make sure to actually not skip any steps
Happy flashing!

ariyan rana said:
i didnt install twrp.zip, maybe thats why my custom recovery get lost every time i reboot.
Click to expand...
Click to collapse
Install the .zip file, and then also make sure to flash Magisk v16.7 after before rebooting to system.

Also Flash the zip file everytime you are updating your rom...or flashing another os...

-Deco- said:
Install the .zip file, and then also make sure to flash Magisk v16.7 after before rebooting to system.
Click to expand...
Click to collapse
That's incorrect. You need to install Magisk 16.4! THEN after boot let it update to Magisk 16.7 through the Magisk Manager.

ariyan rana said:
every time i install TWRP recovery and reboot its roll back to stock recovery.
Root and Magiks work perfectly. how to solve this problem ?
bootloader unlocked
OOS: 5.1.11
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5

Eric214 said:
That's incorrect. You need to install Magisk 16.4! THEN after boot let it update to Magisk 16.7 through the Magisk Manager.
Click to expand...
Click to collapse
That isn't incorrect, flashing Magisk 16.7/17.0 works perfectly fine.
Sent from my Nexus 6P using XDA Labs

-Deco- said:
That isn't incorrect, flashing Magisk 16.7/17.0 works perfectly fine.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
16.7 flashed from TWPR results in the error you see once you boot into the OS.

Eric214 said:
16.7 flashed from TWPR results in the error you see once you boot into the OS.
Click to expand...
Click to collapse
There's no error - I flashed 17.1 from the recovery perfectly fine.

-Deco- said:
There's no error - I flashed 17.1 from the recovery perfectly fine.
Click to expand...
Click to collapse
17.1 is the latest update and fixed the the Preserve AVB 2.0/dm-verity being uncheck by default which is why I said you can't flash 16.7, that you need to flash 16.4 in TWRP and then let Magisk Manager update to 16.7... Never said anything about 17.1
-Deco- said:
That isn't incorrect, flashing Magisk 16.7/17.0 works perfectly fine.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Eric214 said:
16.7 flashed from TWPR results in the error you see once you boot into the OS.
Click to expand...
Click to collapse

hey guys i have s7edge sm-935f i flash twrp through odin but i end up loosing it to stock recovery after i reboot thanks inadvance

1337-oxide said:
hey guys i have s7edge sm-935f i flash twrp through odin but i end up loosing it to stock recovery after i reboot thanks inadvance
Click to expand...
Click to collapse
You have to flash twrp.zip through reboot in twrp. You booted It with Image and now It needs the zip file to keep itself mounted.

1337-oxide said:
hey guys i have s7edge sm-935f i flash twrp through odin but i end up loosing it to stock recovery after i reboot thanks inadvance
Click to expand...
Click to collapse
So you decide to come to OP6 forum and necro bump a 1 year old post?
Please explain your process....

°Washy said:
You have to flash twrp.zip through reboot in twrp. You booted It with Image and now It needs the zip file to keep itself mounted.
Click to expand...
Click to collapse
What do u mean coyld u make a step tutorial with pjcs or vid so all us noobs can learn what u mean cause years ago it was root pho e then flash twrp through odin then bang u have it so i dont understand why i cant get it to work i so badly wanted Resurrection remix and only reason i rooted the phone know s health and samsung pay dont work i can work around not having it on custom rom but im on stock so want it to work plzzzz help i have discord or skype so we can talk share my screen show u whats going in
---------- Post added at 03:42 PM ---------- Previous post was at 03:39 PM ----------
only4dank said:
So you decide to come to OP6 forum and necro bump a 1 year old post?
Please explain your process....
Click to expand...
Click to collapse
Well aint my fault if u guys dont have active crap on this stuff u say u are 1 stop place so start acting like that i bumb thread cause it was issue i having or reason i replyied to it i dont just reply random i reply in things that im having issues and think that it can help me so stop winging and relax have a bong and just stfu

1337-oxide said:
What do u mean coyld u make a step tutorial with pjcs or vid so all us noobs can learn what u mean cause years ago it was root pho e then flash twrp through odin then bang u have it so i dont understand why i cant get it to work i so badly wanted Resurrection remix and only reason i rooted the phone know s health and samsung pay dont work i can work around not having it on custom rom but im on stock so want it to work plzzzz help i have discord or skype so we can talk share my screen show u whats going in
---------- Post added at 03:42 PM ---------- Previous post was at 03:39 PM ----------
Well aint my fault if u guys dont have active crap on this stuff u say u are 1 stop place so start acting like that i bumb thread cause it was issue i having or reason i replyied to it i dont just reply random i reply in things that im having issues and think that it can help me so stop winging and relax have a bong and just stfu
Click to expand...
Click to collapse
I.. I like this guy.... Bro, this is a OnePlus6 forum.
Do you want me to explain the difference between a OnePlus and Samsung device?

only4dank said:
I.. I like this guy.... Bro, this is a OnePlus6 forum.
Do you want me to explain the difference between a OnePlus and Samsung device?
Click to expand...
Click to collapse
if u like what is the diff
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
the reason i did is cause his issue is exact the same issue but on s7edge thast why i bumb stupoid old post cause buy the looks no retard answer my post i made so mabe u need to cheack ya emails a bit more

(Guide) How to install a GSI ROM on the Pixel 3 XL

First Step
Boot to Twrp and you need to flash the avbctdisable.zip
Link- https://drive.google.com/file/d/1GhZK04FDx7WlyKb32qq0gR-SO0t51CVE/view
2nd Step
flash the factory boot image in fastboot
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
ON A/B Partition
fastboot flash system_a gsi.img
fastboot flash system_b gsi.img
STEPS After GSI flashed
1.Boot TWRP thru Fastboot
2.Wipe Data and Dalvic / Art Cache
3.Flash the TWRP installer
4.Reboot to System
5. Reboot To Twrp Flash Gapps
6. Reboot To Twrp Flash Magisk And Optional Custom Kernel
7.Reboot
List of GSI roms I have found
Resurrection Remix
https://get.resurrectionremix.com/?dir=gsi
Havoc OS:
https://sourceforge.net/projects/havoc-os/files/arm64ab/
Arrow OS:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/
Octopus OS:
https://drive.google.com/file/d/1caTZ1rMxOuikF1Va5N3cJTFQLmLf7LUZ/view

Also FOR ERROR 70 WITH GAPPS
Steps
Boot Twrp
Click on wipe
Advance wipe
Click on system
Then Repair or Change File System
Then Resize File System
Flash Gapps Profit.
ALSO!
IF YOU HAVE BOOTING ISSUES WHEN YOU HAVE COMPLETED THESE STEPS, FLASH THE STOCK BOOT IMAGE, TWRP OR MAGISK IS CAUSING ISSUES

Cozzeck said:
Also FOR ERROR 70 WITH GAPPS
Steps
Boot Twrp
Click on wipe
Advance wipe
Click on system
Then Repair or Change File System
Then Resize File System
Flash Gapps Profit.
Click to expand...
Click to collapse
What GApps did you use ?, can you provide the link for that .

jawonder said:
What GApps did you use ?, can you provide the link for that .
Click to expand...
Click to collapse
Fixed the link and I used opengapps https://opengapps.org

Cozzeck said:
Fixed the link and I used opengapps https://opengapps.org
Click to expand...
Click to collapse
Thanks gonna try this, bored and need to flash something LOL .

What is the avbctdisable.zip for ? . Sorry first time doing GSI . Also i downloaded open GApps 9.0, is the the right one ?.

jawonder said:
What is the avbctdisable.zip fo ? . Sorry first time doing GSI . Also i downloaded open GApps 9.0, is the the right one ?.
Click to expand...
Click to collapse
not completely sure but believe that it disables encryption...

jawonder said:
What is the avbctdisable.zip fo ? . Sorry first time doing GSI . Also i downloaded open GApps 9.0, is the the right one ?.
Click to expand...
Click to collapse
Google implemented AVB verity to check and make sure that all the images in the partitions match each other before the device will boot. The device will not boot with a mismatched GSI image in the system partition. The zip disables the verity checks of the different partions allowing the device to boot with a GSI image.
https://android.googlesource.com/platform/external/avb/+/master/README.md
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
cmh714 said:
not completely sure but believe that it disables encryption...
Click to expand...
Click to collapse
Nothing to do with encryption. You will still be encrypted

Golf c said:
Google implemented AVB verity to check and make sure that all the images in the partitions match each other before the device will boot. The device will not boot with a mismatched GSI image in the system partition. The zip disables the verity checks of the different partions allowing the device to boot with a GSI image.
https://android.googlesource.com/platform/external/avb/+/master/README.md
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Nothing to do with encryption. You will still be encrypted
Click to expand...
Click to collapse
Thanks, there’s lots of interesting stuff to with the Pixel .

So it booted but when i went back and flash GApps i got error 70 and i didn’t do the fix while in twrp i wanted to reboot system first then go back to twrp and do the fix . Seems that wasn’t a good idea it booted to the google screen then back to bootloader with and error saying “error booting boot.img . Gonna try doing the process all over again and do the GApps fix after flashing GApps before rebooting.

Not working for me, boots fine until i flash GApps and reboot system it just goes to bootloader and says "no valid slot to boot" .

I dont really care but dont think this is really the correct place for much of this stuff....maybe poke around here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development

cmh714 said:
I dont really care but dont think this is really the correct place for much of this stuff....maybe poke around here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Click to expand...
Click to collapse
Those roms seem to be for older devices

jawonder said:
Not working for me, boots fine until i flash GApps and reboot system it just goes to bootloader and says "no valid slot to boot" .
Click to expand...
Click to collapse
I didn't have some booting issues at first with RR but I just flashed the stock boot image after it was all said and done and it boot fine. Not sure if it's twrp or magisk causing the issues
Edit guess I should add this in to the op

Cozzeck said:
I didn't have some booting issues at first with RR but I just flashed the stock boot image after it was all said and done and it boot fine. Not sure if it's twrp or magisk causing the issues
Edit guess I should add this in to the op
Click to expand...
Click to collapse
Funny i was thinking of doing that. Ok will try that . Doing a clean install of January patch and will have a go again .

Boots ok when i flashed boot.img after GApps but after a restart it just boots to fastboot and i if click on start or do a fastboot reboot it just goes back to bootloader . I think this needs some work .

jawonder said:
Those roms seem to be for older devices
Click to expand...
Click to collapse
no that is incorrect....but whatever.

Cozzeck said:
Fixed the link and I used opengapps https://opengapps.org
Click to expand...
Click to collapse
Which GApps to use ARM64 9,0 or ARM 9.0 ? . Was reading that ARM64 doesn't work on pixel
Edit: No worries, i see it’s ARM64 .

I did a factory reset then install just the system.img in TWRP then flash GApps and Magisk before reboot as per instructions in RR thread . I boots fine but give the Android system error before you unlock . I report this in the RR psi thread and they said it's a known issue should just ignore it for now . Everything works . I'm using Google Fi which works fine .

This looked like a chance but disabling AVB, FBE and making the Kernel SElinux permissive has not helped to boot this here: https://forum.xda-developers.com/pr...vice-development/pie-erfan-gsi-ports-t3906486
Anyone more lucky as i am or any ideas? Would really really like to get Miui or Xperia as System since it includes fancy stuff to play with...