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
Related
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.
mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%
iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.
mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.
mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions
mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.
Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!
This is the new update 10.3.0, for indian 7Ts HD1901, i got this zip from device update itself
OTA rom - https://drive.google.com/open?id=14eM8AzKKeht6i_zHw8lvSaRoknN90PPk
you need payload dumper to open and extract payload.bin to get .imgs of roms
patched boot image - https://www.androidfilehost.com/?fid=4349826312261679634
use this guide to root your 7T using above img - https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
this is same as the new 10.0.7 for the global/eu versions
Can you please share original boot image from 10.0.7??? payload dumper gives me error.
sagardakua said:
Can you please share original boot image from 10.0.7??? payload dumper gives me error.
Click to expand...
Click to collapse
here it is https://drive.google.com/open?id=1eagdkkAMeaav2AtBI9b7b3m6_LQ-vLH6
this is for indian hd1901, so dont complain to me if you flash this on some another model and get error
I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?
sathya said:
I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?
Click to expand...
Click to collapse
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)
levai_spencer said:
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)
Click to expand...
Click to collapse
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk. Here is what i did.
Entered Fastboot mode
Through ADB, i used "fastboot boot magisk_patched.img
The phone booted fine
Opened Magisk as i was already rooted before
Clicked on Install
Selected "Direct Install"
Rebooted my phone
Stuck at the bootloader warning screen
Unless i load the image again via fastboot, it wont let me in. Hence i am not able to root
sathya said:
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk
Click to expand...
Click to collapse
are you booting or flashing? its a 2 different things...
levai_spencer said:
are you booting or flashing? its a 2 different things...
Click to expand...
Click to collapse
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.
sathya said:
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.
Click to expand...
Click to collapse
its a well known magisk bug, i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
I'll update the patched boot img just in case
levai_spencer said:
i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
Click to expand...
Click to collapse
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
yes, booting stock boot img will remove root, once you fix the problem, you can follow same root guide and patched img to root the phone again
sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
also, make sure to use same 10.3.0 files to restore your phone using the restore guide i gave (assuming you updated to 10.3.0)
Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.
sathya said:
Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.
Click to expand...
Click to collapse
did you try restore using the guide i gave? i used this guide to fix bootloader stuck
you'll need to download the ota file linked, extract zip, use payload dumper to get imgs, and flash all imgs according to the guide
you can also create your own magisk patched image, thats how i got mine and my 7T is rooted on 10.3.0
okay you can do this if flashing my patched img is causing issues
if you have an old 10.0.6 patched img, use that to get root
i got this one from xda, i was able to also root using that
Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot
sathya said:
Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot
Click to expand...
Click to collapse
did u try to wipe data/internal in recovery?