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.
Related
Hi guys.
I unlocked my bootloader, and installed the Global Beta Rom via TWRP.
Now, that I am finishing that, TWRP is not installed anymore. And I can't install it.
When I boot into fastboot, and install TWRP like usual, everything is ok. No error appears. But when I want to boot into TWRP via key-combination, nothing happens. When I boot MiUi again, then reboot and try to boot into TWRP again, the Mi-Recoverymenue appears. But not TWRP. Can anyone help here?
After ROM package installed, boot and setup everythings you need, reboot to fastboot mode.
You must install TWRP again, then boot to TWRP by using command, same as the first time you install TWRP. Full commands:
1. fastboot devices.
2. fastboot flash recovery twrp.img
3. fastboot boot twrp.img
DungHD said:
After ROM package installed, boot and setup everythings you need, reboot to fastboot mode.
You must install TWRP again, then boot to TWRP by using command, same as the first time you install TWRP. Full commands:
1. fastboot devices.
2. fastboot flash recovery twrp.img
3. fastboot boot twrp.img
Click to expand...
Click to collapse
Done that.
Device reboot, screen turns black. Then device reboot again, and MIUI will start.
After you install TWRP via fastboot command boot into TWRP via fastboot using the TWRP image on your computer. After TWRP comes up disconnect your phone from your computer, go into the TWRP reboot menu and select reboot into recovery. After you boot back into TWRP it should stick until you flash another ROM zip.
Same issue here.....please have a look at attached picture to see what I have done.
Even after a couple of minutes the screen remains black after trying to boot into TWRP.img with "fastboot boot twrp.img"
Is this a wrong command?
OK with rebooting the system is replacing TWRP, mens I need to go directly into TWRP without rebooting OS., but neither the command above nor ´"fastboot reboot" and simultaniously holding Vol+ and Power ware entering TWRP .....even more
Entering "fastboot reboot" afterwards, device is rebooting normally.
Would be great to explain how I can successfully get TWRP run.
Thx a lot!!
MIUI overwrites the recovery with each boot.
You'll have to get root access and adjust s few files (there is a guide somewhere here on xda) to get it to stay
flyingjack said:
Same issue here.....please have a look at attached picture to see what I have done.
Even after a couple of minutes the screen remains black after trying to boot into TWRP.img with "fastboot boot twrp.img"
Is this a wrong command?
OK with rebooting the system is replacing TWRP, mens I need to go directly into TWRP without rebooting OS., but neither the command above nor ´"fastboot reboot" and simultaniously holding Vol+ and Power ware entering TWRP .....even more
Entering "fastboot reboot" afterwards, device is rebooting normally.
Would be great to explain how I can successfully get TWRP run.
Thx a lot!!
Click to expand...
Click to collapse
Did you download wrong .img file for polaris?
All versions has capacity more than 46 MB. Latest version is 46788 KB.
DungHD said:
Did you download wrong .img file for polaris?
All versions has capacity more than 46 MB. Latest version is 46788 KB.
Click to expand...
Click to collapse
THx mate! actually I downloaded the wrong file. With the correct one evreythink is working fine!!!
Alright so I screwed Up. I got in a rush and followed some guys advice in a thread for a different phone and not sure how to get back on track. Can someone help?
Heres what I did.....
G:\Downloads\oneplus 6 root\android p>fastboot flash recovery twrp-3.2.3-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26744 KB)...
OKAY [ 0.569s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.577s
Click to expand...
Click to collapse
Nothing..... SO I googled and then typed this:
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
Phone rebooted and showed twrp, cool. I restarted from there then, sh1t! Now I can't get back to twrp nor the os to follow the correct guide.
I tried holding power for 7 seconds - reboots and shows the red dot with white dots circling eternally
I tried holding volume down + power for 7 seconds - reboots and does the same thing
I tried holding volume up + power for 7 seconds - it goes into this all black recovery mode or something
no recovery mode is seen again yet since my mistake
As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44
dgunn said:
As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44
Click to expand...
Click to collapse
Hey thanks for trying to help me. I somehow just got it into fastboot mode....... Not really sure how, but I tried to follow the guide here to get in to it.
Anyway. I was running android oreo not android p before I tried to flash twrp.. does that make a difference?
So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post
dgunn said:
So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post
Click to expand...
Click to collapse
Hey! sorry, I made the folder called "Android P" because i will be upgrading to android p lineage os 16. Before I made this mistake, I was running the latest version of android oreo.
GOOD NEWS THOUGH. I somehow got into twrp through fastboot (using bootloader? option). now it keeps booting into twrp. How can I restore stock recovery from here and have a do-over? Thank you!
If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere
dgunn said:
If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere
Click to expand...
Click to collapse
Ok this is weird..........
I boot into twrp, then I choose; reboot, slot a (instead of default slot b), then the phone boots and it's running android P. what the heck!?
Not sure what happened....... here's the history
1- Android 8
2- Installed Android P dev preview
3- Rolled back to Android 8
4- Installed TWRP, screwed it up
5- Got back to TWRP, chose slot B, now it's booted
6- How is it running Android P
I really just want to get it back to full stock and start over since i screwed up. or even better... just want to fix my screw up the way it's meant to be done right......
Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo
dgunn said:
Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo
Click to expand...
Click to collapse
So is slot A and B only for ROMS and not for recovery?
When I downgraded to 8 from 9, technically 9 was still installed:silly:?
R0ttenB4ndit said:
hey @ajsmsg78. when i do adb devices through usb, it doesn't find it. it will keep booting to the red dot and spinning white dots around it. no recovery option appears on the phone. what mode do I have to be in for the pc to see it at this point?
Click to expand...
Click to collapse
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat
I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
UPDATE: OK I see your previous response, I'll try and report back.
R0ttenB4ndit said:
I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
Click to expand...
Click to collapse
Well, easiest way is the last mentioned one, its a real simple procedure. Hook up to fastboot, then click the corresponding bat and wait, heres the thread. Then to get twrp running follow my previous posted steps
forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page57
After installing the zip... should I wipe the cache/dalvik?
Update: the answer is yes, I'm reading. will update soon.
efinityy said:
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat
Click to expand...
Click to collapse
Alright, thought I had it............ but no, now it just keeps rebooting into fast mode. Maybe I'm getting ahead of myself here. Sorry....
Here's what I did:
cmd
>>fastboot flash boot_a twrp-3.2.3-0-enchilada.img
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
all ok
>>fastboot boot twrp-3.2.3-0-enchilada.img
the phone boots into twrp, cool
cmd again
>>adb push twrp-installer-enchilada-3.2.3-0.zip /sdcard/
then installed twrp-installer-enchilada-3.2.3-0.zip to make it stay
wiped dalvik/cache and it rebooted to twrp again
think I am now in the clear yay (not).
>>adb push lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip /sdcard/
then installed lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip
success
I reboot but it still goes to twrp
i change slot to b (it was set to A) hoping maybe it'd boot to lineage
phone reboots and now I can't make it go back to twrp. It keep rebooting into fastboot no matter what I do (hard keys reset/options to choose)
stuck again.
When try to mount the twrp image just to boot into it, I get this now:
>>fastboot boot twrp-3.2.3-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.568s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.584s
so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?
R0ttenB4ndit said:
so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?
Click to expand...
Click to collapse
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for Oreo.. Scratch that, v2 works for all.
Dont flash the twrp img in boot partition yo ? you want the stock boot image/ kernel there... Twrp will later be merged with your current boot, flashing twrp to boot a or b will make you have no kernel, having no kernel equals having no instructions to get android running, and instead of calling the kernel to boot android it will just call twrp over and over
Why we are installing the zip is because previously we had recovery partition, a dedicated partition made for the recovery, now we don't, the recovery is part of the kernel, and we don't ever wanna lose our kernel because that means the phone doesn't know how to boot itself to a usable state, so that's why we only fastboot BOOT twrpimghere... Then install the twrp zip to to patch out the old recovery, like removing a tumor from a body, then patch that empty place with a bandaid that is twrp, so you have your old kernel, the one that can boot the system, and a fresh bandaid on top of it that is twrp... Sorry for the weird metaphoring, I trying to put a/b partitions and it's functions in condensed text is a challenge, but as soon as you grasp the concept you will understand how to do it flawlessly every time
efinityy said:
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for oreo
Click to expand...
Click to collapse
In the OP it says:
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
Click to expand...
Click to collapse
When you say I want the twrp..... is this something else I need before I run the Stock Fastboot ROM bat file?
which step did I go wrong?
I did Replace _x with _a then _b, to flash it to both slots
I thought it was meaning to flash it to both A and B? What did that mean? Thank you!
#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
Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom
Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.
worked for me while anything else didnt
LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?
Didn't work for me. My boot image was patched already this is probably why.
ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)
Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!
can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s
@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
kraken-gz said:
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
Click to expand...
Click to collapse
Connect to adb while booted into TWRP and type the command:
adb reboot bootloader
That "should" boot into fastboot
For future reference, when flashing TWRP via fastboot, immediately after you flash the TWRP.img, enter the command:
adb reboot recovery
That should boot straight into TWRP and keep TWRP. If you let the device boot into any other mode than recovery, it will revert back to stock recovery, you have to boot directly into TWRP immediately after flashing it in order to keep TWRP.