Related
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
kismetmookz said:
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks, I have been using this and used it as I was wring the article, I'm just trying to see how we flash the ROMs on this puppy.
i use to do these steps
wipe caches
install rom
install twrp.zip for taimen
reboot
setup phone
if you want root then reboot on recovery again then install magisk.
I do these steps and have no failure when flashing; after I wipe the Caches, I flash the ROM and then the TWRP partition flasher and reboot the system. I've waited 15 minutes to have the device boot with no luck and I don't want to risk any longer due to the Pixel 2/ XL having burn-in issues.
thowersome said:
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
Click to expand...
Click to collapse
Probably because there's not a full OS on the slot your flashing to. If you know your fastboot, it's relatively easy going forward. The Dueces scrip it's great tool for sure to help out. If you want to do it manually, fastboot the factory image to both slots with the -w removed from the flash-all.bat file.
Once that's done, go back to fastboot, and boot into twrp. Then do a twrp factory reset with the swipe bar. Flash the rom, then the twrp.zip and let it boot up. Once in the OS, keep lock screen set to swipe, and do a minimal setup. Then go back to twrp and flash your custom kernel(optional) then flash magisk. And that should do it :good:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
thowersome said:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
Click to expand...
Click to collapse
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Badger50 said:
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Click to expand...
Click to collapse
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
thowersome said:
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
Click to expand...
Click to collapse
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend! ??
Badger50 said:
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend!
Click to expand...
Click to collapse
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
thowersome said:
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
Click to expand...
Click to collapse
Outstanding! Well done :good::good:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.
Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.
Thanks all! I flashed the patched boot.img again and it seems to be working OK
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.
Is Xposed worth having these days? Are people still actively developing useful mods?
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.
Hello everyone,
after many hours of research I couldn't find anyone with the same problem or any solution for this.
Recently (yesterday) magisk brought out a new update 20.0 and I got a notification so I opened magisk manager and clicked on update magisk auto (recommended). After it updated successfuly, a reboot button appeared on right bottom corner and I clicked it. After it turned off and on it went directly to download mode and of top of the screen there was this error:
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Screenshots:
https://prnt.sc/pigzsh
https://prnt.sc/pih0ax
And after like 3-5 times I hardreset (VOL DOWN + POWER) then immediately press VOL UP + POWER to come into magisk root mode again, the device boot but I have no root anymore. And there is no auto update choice anymore at magisk. I tried also patching the official firmware again and flash it but didn't work, I'm still not rooted and I get always many times to download mode with this error if I reboot the device.
Did anything go wrong during magisk auto update?
If yes, why it said "update success"?
Do I have to update magisk? I used the auto update method the first time and I am deep in trouble.
What should I do to fix this and getting rooted again?
If possible without losing my files/wipe data.
My device: Galaxy A70 (SM-A705FN/DS)
Android 9
Thanks in advance
HH
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Vmbeta Image
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
xeedes said:
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
Click to expand...
Click to collapse
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Ial69 said:
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Click to expand...
Click to collapse
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
xeedes said:
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
Click to expand...
Click to collapse
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
ps : cant post link to samfirm because the forum lock me to post external link....(because im a new user)
and you need to have unlock your bootloader to flash, bad things can happens with a lock bootloader. like brick.
Ial69 said:
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
Click to expand...
Click to collapse
hey, thank you for the reply, i've tried flashing the stock rom but nothing happens. downloading it from samfirm though. im going to sleep. thank you for the help
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
emadhussein said:
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
Click to expand...
Click to collapse
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
Reboot phone and pc. Then retry to flash TWRP. The phone will boot fine.
this work for me.
I root this phone with magisk at first time. no problem...
follow tuto.
for magisk :
https://forum.xda-developers.com/galaxy-a70/how-to/to-root-magisk-odin-t3930099
for TWRP :
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
i have vbmeta error too, bypass with TWRP. cant help you more than that, sorry....
BK said:
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
Click to expand...
Click to collapse
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
emadhussein said:
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
Click to expand...
Click to collapse
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Ial69 said:
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Click to expand...
Click to collapse
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
sorry, do you have try to install twrp ? he cause the vbmeta error ?
what odin says ?
Do you have reboot phone and pc before each try ?
need to uncheck autoreboot in odin too, like even.
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
Better try flash twrp since it works for many.
Read all answers in this thread.
HornyHugo said:
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
Better try flash twrp since it works for many.
Read all answers in this thread.
Click to expand...
Click to collapse
this is what i say from the beginning.
Ial69 said:
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Click to expand...
Click to collapse
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
HornyHugo said:
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
Click to expand...
Click to collapse
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
4 - Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
You begin from step 4. step 4 no need to wipe.
wipe is for step 3.
you are already unlock and rooted your phone if you have tried to update magisk and get stuck on vbmeta error.
ps : just do step 4. flashing recovery. then step 5 for root access ^^
good luck !
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
just connect your device to computer with cable and boot it with volume buttons
booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Edit: fixed but its now stuck on boot logo
2nd Edit: fixed by installing miui 13.0.2 (IM EXCITED)
itayalush said:
booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Click to expand...
Click to collapse
What do you want to do?
SubwayChamp said:
What do you want to do?
Click to expand...
Click to collapse
to get miui work again
oh wait i fixed this but now its stuck on the logo and after a few hundred years it turns off + i really want someone to make a custom rom for this device
itayalush said:
to get miui work again
Click to expand...
Click to collapse
Flash the stock ROM
I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem
You have to copy orange fox and original boot.img to your phone. Flash the original boot.img and then flash orangefox recovery ramdisk however I don't know because I only know how to install TWRP this way
SubwayChamp said:
Flash the stock ROM
Click to expand...
Click to collapse
i did, like a million times
Stephanizgo said:
I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem
Click to expand...
Click to collapse
i also tried with stock boot... result: still stuck on boot logo
pls anyone help
i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting
itayalush said:
i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting
Click to expand...
Click to collapse
Format data
Stephanizgo said:
Format data
Click to expand...
Click to collapse
tried a million times before
itayalush said:
i did, like a million times
Click to expand...
Click to collapse
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?
I recommend replacing Orange Fox with TWRP.
I just had this issue on a different Xiaomi phone. I replaced Orange Fox with TWRP and was able to flash LOS and fix the problem.
SubwayChamp said:
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?
Click to expand...
Click to collapse
i flashed my stock rom after finally unlocking my phone after millions of tries with the "Unknown Error -1", i finally found a modified unlock tool that fixes it. still stuck on boot logo
if you want my unlock tool, this is the file (u can publish it wherever you want)
Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)
itayalush said:
Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)
Click to expand...
Click to collapse
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible
You can now install my TWRP lol
Stephanizgo said:
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible
Click to expand...
Click to collapse
No, they unlocked the bootloader, as it said in the first post.
SPFT and mtk-client tools can flash even to locked devices.