Related
My TF300T will only boot into TWRP. I also can't access any storage (failed to mount error) and adb sideloading fails everytime so I can't flash the stock rom. I tried using these commands:
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Which let me reach the .zip file it still failed to flash.
The tablet had Jellybean 4.2.2 installed. The TWRP version is 2.6.3.0.
How do I fix this?
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Graiden05 said:
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Click to expand...
Click to collapse
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
dewdrop623 said:
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
Click to expand...
Click to collapse
Did You flash rom or recovery? And does blue progressbar appears?
Graiden05 said:
Did You flash rom or recovery? And does blue progressbar appears?
Click to expand...
Click to collapse
I was able to flash cwm recovery. So now instead of booting into twrm everytime I get stuck on the splash screen. That didn't really change anything
I tried fastboot -i 0x0b05 flash system boot.blob (the .blob file from the stock rom), and I got the blue progress bar then rebooted but I'm still stuck on the first splash screen.
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Graiden05 said:
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Click to expand...
Click to collapse
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
dewdrop623 said:
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
Click to expand...
Click to collapse
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Graiden05 said:
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Click to expand...
Click to collapse
Success. Thanks for the help.
Hey there guys. I have recently flashed CWM-touch-6.0.4.7-falcon.img im able to go into recovery when i flash it, on reboot i selected yes for the fix install stock recovery, when back to recovery and it has an android with an exclamation mark coming out of it with it saying 'no command' at the bottom. How do i fix this? Moto G 3G 1st gen
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
.:Dark:. said:
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
Click to expand...
Click to collapse
I did that and it was all success but same thing happened
Also i tried flashing stock recovery but still no luck
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
legolas06 said:
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
Click to expand...
Click to collapse
Oh right ok. No i haven't used TWRP, i don't really like it. I tried CWM touch but i haven't tried normal CWM yet
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
.:Dark:. said:
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
Click to expand...
Click to collapse
I always go straight into recovery after i flash it but when i reboot it goes back to stock recovery :/
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
legolas06 said:
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
Click to expand...
Click to collapse
I forget, ill check it tomorrow as today i am a bit busy
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
bublz654 said:
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
Click to expand...
Click to collapse
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
legolas06 said:
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
Click to expand...
Click to collapse
I have flashed CWM-touch and normal CWM before until flashify came along and made my recovery screwed up
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
lost101 said:
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
I just tried that and still the same issue occurs
bublz654 said:
I just tried that and still the same issue occurs
Click to expand...
Click to collapse
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I'll try the philz recovery first as Im not a real big fan of twrp lol
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I flashed philz recovery. Rebooted again and went into recovery and it worked, the recovery was still there
But one more thing on reboot of recovery it didn't ask if i wanted to fix root. Am i rooted already or not? :/
Are you on stock or a custom rom? Certain custom roms may have built in root access for everything else you will have to flash SuperSU.
Glad to see you got the recovery issue sorted. I'm with you I don't particularly like TWRP so I pretty much use Philz exclusively.
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Azyreal said:
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Click to expand...
Click to collapse
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
acejavelin said:
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Click to expand...
Click to collapse
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
Click to expand...
Click to collapse
Hey! Thank you! I've been able to flash the TWRP recovery and now I can do a factory reset (and also send sms, which I couldn't do anymore for some reason).
I still have the issue where the bootloader screen appears everytime I turn my phone on, and I still can't re lock my device because I can't flash anything either. I've recovered all of my data, so I think I'm going to stick with that for a moment but maybe I'll try what you said some day.
Again, really thank you for helping me!
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system, reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Click to expand...
Click to collapse
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
MrTooPhone said:
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
Click to expand...
Click to collapse
Don't power down, already you are in fastboot mode, you can just enter recovery from that. I forget the reference, but i will search and post.
---------- Post added at 04:41 PM ---------- Previous post was at 04:18 PM ----------
I get this from twrp official page
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
In our phone press simultaneously volume down + power button to enter recovery.
Hello,
I had Resurrection Remix Android 7.1.2 installed in my Mi4i. The apps were suddendly crashing (was getting app crashed alert) and thought to reboot the phone once.
Once I tried to reboot abnormality started showing up.
Tried flashing the Resurrection Remix again but it stuck at the boot animation screen.
Then tried flashing the official MIUI developer rom and it worked.
Again tried with RR but it did not boot up.
After trying a couple of times, none of the roms did boot up.
After some research found in TWRP logs that it is unable to mount system, cache, dalvik cache etc.
Also I could see that the space/memory is displayed as 0MB.
Some forums said to format the file system as ext4 and even the format failed saying it is unable to mount.
Now whenever I start the phone to goes to the fastboot screen.
The interesting point is that I tried flashing manually the developer rom and it said it falshed successfully.
But i still see the twrp as my recovery and not the stock recovery after flasing.
Also tried manually flashing the recovery like "fastboot flash recovery recovery.img" and did not find any errors still the stock recovery was not flashed instead the twrp remained as the recovery even after successful flash.
I am stuck with my phone now and not sure how to proceed.
Any help regarding this would really be helpful.
Help me to recover my phone please. :crying:
Thanks.
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Mukulkathuria008 said:
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Click to expand...
Click to collapse
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Probal Basak said:
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Click to expand...
Click to collapse
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Mukulkathuria008 said:
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Click to expand...
Click to collapse
Tried formating to ext4.. But nothing happened.. Still getting mount error.
Attaching pics below.
Attachment 1 : Advanced Wipe -> Wipe
Attachment 2 : Advanced Wipe -> Change File System -> /system -> ext4
I have also tried this
Code:
fastboot getvar all
Output:
Code:
all:
finished. total time: 0.001s
Any comments what may have gone wrong?
fix file system. or maybe emmc died
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.