Related
Has anybody tried this... If so does it work? https://www.xda-developers.com/lineageos-15-1-resurrection-remix-available-project-treble/
Feel free to give it a try!
Flash the system image from TWRP, reboot to recovery, then flash Gapps (if desired). Keep a backup factory system image handy if needed.
@Telperion I wish I could... Unfortunately I don't have the pixel 2. I am very much thinking about buying one though.
I'm sure it works, there's just not been much need to run a custom ROM. I'm on P DP1 and there's not yet a P GSI so I'd have to downgrade to 8.1 before flashing.
Telperion said:
Flash the system image from TWRP, reboot to recovery, then flash Gapps (if desired). Keep a backup factory system image handy if needed.
Click to expand...
Click to collapse
When I tried installing TWRP on my Pixel 2 a few days ago, I found the ui does not respond to screen touches.
It might be simpler to just use fastboot flash a GSI.
Note that to get a GSI to work on the Pixel 2, you also need to adjust the contents of the "vbmeta" partition, which can be done using "fastboot".
There are details about it here https://github.com/phhusson/treble_experimentations/wiki
Can confirm lineage, resurrectionremix and aosp gsi by phh all work, although the twrp bug jamuir mentions did occur for me. I got around this by just flashing the gsi through the bootloader and not twrp. If you want to flash some gapps after flashing system and vbmeta (needed for pixel2), just fastboot boot twrp.img instead of rebooting to recovery. Here are basic steps I followed:
clean flash phone or do a factory reset from twrp, then boot to bootloader
fastboot flash system system-arm64-ab.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img #from factory image
#and if you want gapps
fastboot boot twrp.img
adb push opengapps.zip
flash your gapps
You'll get the "vendor mismatch" warning we've all come to know and love, as well as a "Hardware Overlay Picker stopped working" message on startup. Other than that, they all work.
I understand the premise of project treble, but I wonder what's the implication for custom rom developers. I'm probably mistaken, but it seems like they could just do a one-size-fits-all build for all devices now?
The twrp "not responding to touch" bug happens when you reboot into recovery straight from system using the advanced reboot menu. To prevent this, simply power off the device, and use the button combination to boot into twrp, voila, touch is now working.
#Prerequisites:
Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img
Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for custom roms, when you need to install GApps.
Magisk: https://github.com/topjohnwu/Magisk/releases/download/v19.0/Magisk-v19.0.zip
Magisk Manager: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.1/MagiskManager-v7.1.1.apk
DM Verity Disabler: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
Unlocked Bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal ADB/Fastboot (Windows only): https://androidfilehost.com/?fid=962187416754459552
Moto USB Drivers (drivers only, no manager): https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
Windows hint:
For all what you want to do with your Motorola phone, you need the above provided Minimal ADB/Fastboot environment.
Download and extract it,
Move the files you want to flash into the folder
Open CMD (Windows Key and R - then type cmd) and navigate into the extracted folder.
//It's easier when you type cd into the cmd and drag the folder from your adb/fastboot environment into the cmd window and hit enter.
And that's it. The patched boot image is no longer needed.
Rooting the Moto G6
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
5. Repeat the wiping and reboot another time into recovery.
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
7. Go to Install and flash dm-verity disabler first, then magisk.
Thats it. You're rooted.
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Wait until it finished, disconnect your phone, wait and set it up.
That's it.
Simple and easy.
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
madbat99 said:
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
Click to expand...
Click to collapse
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
And for root not need boot.img file?
cecogor said:
And for root not need boot.img file?
Click to expand...
Click to collapse
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
ThisIsRussia said:
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
Click to expand...
Click to collapse
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
cecogor said:
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
Click to expand...
Click to collapse
Due to OS changes and it's a feature bundle.
It edits DM-Verity, ForceEncrypt and Disk Quota.
Can't get root
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
mward7221 said:
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
Click to expand...
Click to collapse
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
ThisIsRussia said:
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
Click to expand...
Click to collapse
I tried all that and couldn't get it to work, I downloaded everything from your links above but no go. Someone posted a no-verity boot image in another thread. post 598 I believe and I flashed that file, flashed Magisk 18.1 in twrp and now I have root so I'm set, Thanks for your reply
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
Of course on Linux no drivers are needed. But most running Linux don't need instructions. It's usually windows users needing such instructions.
That's the only reason I chimed in.
Carry on.
Nice guide.
ThisIsRussia said:
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Click to expand...
Click to collapse
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
kmssd said:
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Click to expand...
Click to collapse
If you Change major OS Version, you always need a clean Flash and rerooting.
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
I would change official TWRP to Dejello's unofficial TWRP as official one won't install Gapps
https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
Click to expand...
Click to collapse
>> Here is ok,
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
Click to expand...
Click to collapse
>> Here is ok too
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
Click to expand...
Click to collapse
>> Here is ok too, similar to flash my Sony
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
Click to expand...
Click to collapse
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
5. Repeat the wiping and reboot another time into recovery.
Click to expand...
Click to collapse
>> The phone will be need a wipe two wipes? or only one?
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
Click to expand...
Click to collapse
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
7. Go to Install and flash dm-verity disabler first, then magisk.
Click to expand...
Click to collapse
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
brunogroa said:
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
>> Here is ok,
>> Here is ok too
>> Here is ok too, similar to flash my Sony
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
>> The phone will be need a wipe two wipes? or only one?
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
Click to expand...
Click to collapse
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Stuck on Booting screen
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
theseeker2654 said:
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Click to expand...
Click to collapse
Ohh sure... So need twrp to do, I Will trie this, thx a lots, here is the same with pie
Tom Swift said:
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
Click to expand...
Click to collapse
On top of using the disabler download and flash the no verity boot.img from the link below. Works great on my xt1925-6 with pie.
Also, use Magisk 19.0
https://drive.google.com/file/d/1JLMVRBCsMnr7RYxdRFjFLOwVSy8r8hSQ/view
The DM Verity Disabler link not working:
https://zackptg5.com/downloads/Disab...02.04.2019.zip
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.
Code:
* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* before flashing GSI! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
you cant have magisk patched boot image installed unless you have also flashed a different product img
- under developer options enable oem unlocking
- adb reboot bootloader
- fastboot flashing unlock
- fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product (DONT DO THIS IF YOU WANT TO FLASH MAGISK. IF YOU DO THEN FOLLOW THIS GUIDE REGARDING MAGISK AND PRODUCT PARTITION https://forum.xda-developers.com/t/tutorial-magisk-on-gsi-on-devices-with-dynamic-partition.4311045/)
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot recovery
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Sarticle said:
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Click to expand...
Click to collapse
thats complete bs
your device must be launched with android 10 or newer to be able to have dynamic partitions.
google play certification has nothing to do with it.
and if you flash product partition you might get away without reinstalling magisk or xposed
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
thirtythr33 said:
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
Click to expand...
Click to collapse
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
ok the reason I ask is I am given the option to flash my backup boot image to super in twrp flash image screen, that's why I asked, and since twrp is reporting that I'm missing system_ext, product, and odm, that flashing to super would fix that, a long shot but I'm desperate.
so to be clear is it shared between slots or does each slot have it's own super? (or the partitions found in it)
kusti420 said:
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
also stock recovery must be installed
and you cant have magisk patched boot image installed
- under developer options enable oem unlocking
- fastboot flashing unlock and then fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
or if you dont have a custom recovery then you can just factory reset in stock recovery
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Click to expand...
Click to collapse
this is all done on pc right? is everything in order?
JordanPahlevi said:
this is all done on pc right? is everything in order?
Click to expand...
Click to collapse
yes its done on pc and everything is indeed in order
Flash gsi with twrp can't ?
Blacxx said:
Flash gsi with twrp can't ?
Click to expand...
Click to collapse
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Android prevents apps or pretty much anything from mounting the system.
Stephanie_Sy said:
Android prevents apps or pretty much anything from mounting the system.
Click to expand...
Click to collapse
mounting isnt the problem, it mounts just fine, but its read only, thats the problem
How did you port twrp for infinix zero 8? I need one for infinix note 10
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Parvej789 said:
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Click to expand...
Click to collapse
follow the tutorial and flash product partition
this may be of interest or help to Samsung users in particular.
getting fastboot via TWRP to work on windows 7 to 10. it worked for me on windows 10 pro and enabled me to flash GSIs successfully.
Latest ADB Fastboot and USB Drivers installer tool for windows
All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and above Steps: 1. Connect the phone in USB Debugging mode...
eu.community.samsung.com
it's not just for Samsung users though, it'll install the latest ADB and Fastboot drivers and download Microsoft dependencies. but now us Samsung users can have Fastboot and do
Code:
fastboot flash system system.img
... so yay !!
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
i flashed using these commands on my v60 tmobile
--AB devices--
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_insertslothere
Example
fastboot delete-logical-partition product_a
fastboot delete-logical-partition productb
fastboot flash system system.img
fastboot reboot recovery
i flashed 3 gsi A10s, los 17.1 didnt boot, pixel experiance and RR Remix booted but never entered android. and when i tried to flash my kdz it flashes all parititons except for super.img it fails everytime on different modes of LG up. I flashed super.img via Qfil but phon wont boot.
i even tried using ChonDoe_Flasher via twrp in a folder it flashes but it still wont boot at all. at this point i cant use LGup because i get stuck in download mode. any help would be greatly appreciated
blaze2051 said:
Try :
Click to expand...
Click to collapse
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Parvej789 said:
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Click to expand...
Click to collapse
i finally got a working rom install since i cant go back to oem stock, it wasnt the commands it was the roms, they just dont boot at all. except one 1 rom did boot. all others LOS 16-18 RR Remix and Pixel experiamce all failed to boot except for E foundation rom
/http://doc.e.foundation/how-tos/understand-and-use-gsi 7
/http://doc.e.foundation/how-tos/install-GSI 7
New linksto download the latest official
dev /e/ G.S.I. android.10 Q
Once you know which system image you need
Arm A 2 (system-arm-a.img.xz)
Arm A/B 3 (system-arm-ab.img.xz)
Arm64 A 11 (system-arm64-a.img.xz)
Arm64 A/B 31 (system-arm64-ab.img.xz)
Binder 64 A 1 (system-a64-a.img.xz)
Binder 64 A/B 4 (system-a64-ab.img.xz)
I no know.
Dynamic
gsi ROM
GsI Rom Link : Tested rom
Tecno kd7 work
*Official Android 11 :
1. AOSP 11.0 v313_system-roar-arusson
Download link AOSP 11.0 v313
*Unofficial QAndroid 11 :
1. Pixel Experience Plus 11.0 v313
Thanks for ponces
Download link PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz
*Unofficial Android 12 :
1.Pixel Experience 12.0 v400.e
Thanks for ponces
Full googel rom. my used 5 day . 1 bug : bootanimation not vew full size
Download link :PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img.xz
Hi All.
I have stuck in weird issue in my pixel 3. Can't able to install any custom rom
Process I hav gone through..
Flash the stock rom Android 10/11 using flash all.bat (downloaded from Google website)
Then install the custom ROM'S boot image and install rom using adb sideload.
There is no error after adb sideload. Showing success.
After reboot, it normally boot into stock os.
Please help me to fix the same. Thanks in advance.
logeshwywan said:
Hi All.
I have stuck in weird issue in my pixel 3. Can't able to install any custom rom
Process I hav gone through..
Flash the stock rom Android 10/11 using flash all.bat (downloaded from Google website)
Then install the custom ROM'S boot image and install rom using adb sideload.
There is no error after adb sideload. Showing success.
After reboot, it normally boot into stock os.
Please help me to fix the same. Thanks in advance.
Click to expand...
Click to collapse
I recently had similar issues (maybe same) doing Lineage. For me the key was to switch to using a usb 2.0 port. Lineage mentions doing this in their directions. I'm familiar with apps like qfil needing it also. Sure enough, all worked as expected with a 2.0 usb port.
cheers
Did you flash stock to both slots? Here's how I flash a custom ROM, starting with a clean flash of stock image:
Once in fastboot:
fastboot --slot=all flash bootloader stock-bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio stock-radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after.
From here, you enable USB debugging and reboot back into fastboot and follow the flashing instructions for your preferred ROM.
AlexKarimov said:
Did you flash stock to both slots? Here's how I flash a custom ROM, starting with a clean flash of stock image:
Once in fastboot:
fastboot --slot=all flash bootloader stock-bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio stock-radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after.
From here, you enable USB debugging and reboot back into fastboot and follow the flashing instructions for your preferred ROM.
Click to expand...
Click to collapse
Thanks for your inputs, will try with your steps.. I have one doubt on this..As per Google's statement "Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system." - Flash-all script won't flash on both slots? please clarify! Because I did stock rom flash in that way only..
AsItLies said:
I recently had similar issues (maybe same) doing Lineage. For me the key was to switch to using a usb 2.0 port. Lineage mentions doing this in their directions. I'm familiar with apps like qfil needing it also. Sure enough, all worked as expected with a 2.0 usb port.
cheers
Click to expand...
Click to collapse
Wholla! It's working fine with 2.0 USB Ports. Many thanks for your suggestions.
Tried with 2 custom roms, perfectly great with first attempts..!
logeshwywan said:
Thanks for your inputs, will try with your steps.. I have one doubt on this..As per Google's statement "Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system." - Flash-all script won't flash on both slots? please clarify! Because I did stock rom flash in that way only..
Click to expand...
Click to collapse
I don't use the flash-all script, I use ADB and fastboot. Someone in the Dirty Unicorns thread had the same issue and edited the flash-all.bat and left instructions but he still had to use ADB and fastboot in the end to set the active slot and run flash-all again.
From the DU thread:
And could you please explain how we flash it to both slots?
Edit; got it working now
- Removed the -w in flash-all (not sure if it was necesarry)
- Runned flash-all while on b
- Then fastboot --set-active a
- Runned flash-all while on a
Then followed the instructions, and it worked.
So, for those that may not realize, we should clarify why we may want to flash to both slots;
A custom rom isn't 'complete' by itself. It uses the 'blobs' that are a part of the original firmware. By flashing 'both' slots with the same firmware, that means when the custom rom does an 'update', both slots will have the same version of the 'blobs', and the update will work as expected.
So, if you never plan to update the custom rom, and only want to 'test' it, there's no reason to flash both slots. But, this does necessitate you know which slot you're on, and which slot things are being flashed to, of course.
Yeah, the A/B slot thing, it's confusing.
cheers