Related
This is my fourth failed attempt to do anything custom with an android phone (yes, 4 different phones). Why is it so hard?
I'm following some nice instructions from teamandroid.com, but I can't get into recovery. Either I get "no command", or if I flash and go into recovery right away while connected, I get "Error: failed to load kernel!"
I wasn't able to flash TWRP ("Image size exeeded partition limits") but clockwork-6.0.4.7-falcon seemed to work. Just can't boot into it. I don't know what else to try, I don't know why it doesn't work.
Can anyone help me? Just trying to root my Moto G 2015 for development purposes. thanks so much.
rmp251 said:
This is my fourth failed attempt to do anything custom with an android phone (yes, 4 different phones). Why is it so hard?
I'm following some nice instructions from teamandroid.com, but I can't get into recovery. Either I get "no command", or if I flash and go into recovery right away while connected, I get "Error: failed to load kernel!"
I wasn't able to flash TWRP ("Image size exeeded partition limits") but clockwork-6.0.4.7-falcon seemed to work. Just can't boot into it. I don't know what else to try, I don't know why it doesn't work.
Can anyone help me? Just trying to root my Moto G 2015 for development purposes. thanks so much.
Click to expand...
Click to collapse
I assume your talking about this guide: http://www.teamandroid.com/2015/10/02/root-moto-g-2015-on-android-5-1-lollipop-with-supersu/
It is an OK guide, but you really have to read the details... did you unlock via the Motorola Bootloader Unlock page? Nothing will work properly until you do.
Yes that's the guide (xda didn't let me post the link). Yes I did unlock that way. I'm trying to follow all of the details and I don't think I've missed anything (hence my frustration).
http://forum.xda-developers.com/showthread.php?t=3188850
Thank you hp420! This is what worked for me:
fastboot boot twrp-osprey-2.8.7-test1.img
What helps you ... Can u please explain that... I have a same issue with moto g4 plus... Failed to load kernel....
Vishaly634 said:
What helps you ... Can u please explain that... I have a same issue with moto g4 plus... Failed to load kernel....
Click to expand...
Click to collapse
Kind of digging up an old thread here, what is the problem you are having and what process are you using? TBH, this is pretty simple but you need the TWRP specific to your device and just flash Magisk.
Moto g4 plus root problem..,
After installing twrp.img with mfastboot while I enter in recovery mode after few seconds it shows u need software repair assistant and final shows failed to load kernel.... Can u help me with this....I m totally confused: I Hove no idea what to do now...
..In red ....It shows..
Start up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
IN RED - AP Fastboot flash mode (secure)
In green - Fastboot reason: volume down key pressed
USB connected
.....
......
In red - failed to load kernel !
Boot up failed
This is what shows up after I enter into recovery mode
...Please help me to root my devices...And reply fast
Vishaly634 said:
After installing twrp.img with mfastboot while I enter in recovery mode after few seconds it shows u need software repair assistant and final shows failed to load kernel.... Can u help me with this....I m totally confused: I Hove no idea what to do now...
..In red ....It shows..
Start up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
IN RED - AP Fastboot flash mode (secure)
In green - Fastboot reason: volume down key pressed
USB connected
.....
......
In red - failed to load kernel !
Boot up failed
This is what shows up after I enter into recovery mode
...Please help me to root my devices...And reply fast
Click to expand...
Click to collapse
Flash the factory image... There are threads for the software and how to do it.
How to flash the factory image.... Can you please tell me in detail...Which thread ??? How to do it..
Vishaly634 said:
How to flash the factory image.... Can you please tell me in detail...Which thread ??? How to do it..
Click to expand...
Click to collapse
There is literally two threads in general... One is for factory firmware images, and one is how to flash factory firmware images. I am not going to spoon-feed you the answer just because you won't look. Find the threads, read a bit, and try it, if you have issues post in the appropriate thread.
So I've had quite of a rough evening today, first of all: I'm not a rooting newbie, so I really thought I could work out all errors on my own.
Haven't rootet my GM1910 yet, so I wanted to do that. Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
After some trying around and not getting it to work, I tried using this to get the device working again:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
tried both flashall.zip and flash-all-partitions.zip.
Now I'm in the QUALCOM CRASHDUMP again with the message
"dm-verity device corrupted Force Dump
kernel_restart"
I've been looking through forms for hours but nothing seems to work for me (mainly the things I wrote above)
I'd really appreciate any help, kind of getting sweaty palms now
Maybe this? It's what I used to unbrick mine but I'm tmobile GM1915....
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Yup, thanks for the reply, that worked! I'm not trying to root my device anymore though :laugh:
Thanks for making my night sleepable today
If you're trying to root your device.. and you have a pc.. just patch the boot.img of your latest rom using magisk.. then flash it via adb.. ???
thaiten said:
Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
What are the exact commands/steps did you us to flash TWRP? And why is "flashing" in quotes? You either boot TWRP.img and can just flash Magisk for root without flashing TWRP; or you boot TWRP.img, flash the TWRP installer zip, flash Magisk.
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
I suspect the condition may be due to wrong fastboot command or flashing the wrong file. But we'd need to know the details requested above to figure out what went wrong. What root guide were you following?
In any case, going to fastboot mode, the phone is most likely not bricked. Just stuck in a state that it can't boot into OOS. Probably can recovery using a fastboot ROM, or flash back to stock boot.img.
failed to load authenticate boot image load error twrp
Hi there,
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
solid.snake said:
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
Click to expand...
Click to collapse
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
redpoint73 said:
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
Click to expand...
Click to collapse
Already done, please look at my 1rst screenshot : twrp74.img
solid.snake said:
Already done, please look at my 1rst screenshot : twrp74.img
Click to expand...
Click to collapse
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Okay, i'll give a try and tell you.
redpoint73 said:
"flashing" in quotes?
Click to expand...
Click to collapse
Because I'm just booting into TWRP first and then install it I thought. And because it didnt work lol
redpoint73 said:
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
Click to expand...
Click to collapse
I am, not sure why it says boot.img
redpoint73 said:
I suspect the condition may be due to wrong fastboot command or flashing the wrong file.
Click to expand...
Click to collapse
I used
Code:
fastboot boot twrp.img
and
Code:
fastboot flash recovery twrp.img
If I'm not mistaken. Was a few days ago now
solid.snake said:
Please people, tell us your Oxyygen OS version before the incident.
Click to expand...
Click to collapse
Was on the latest OOS Beta. But since using the freshly installed ROM with the MSM Tool, my device feels way smoother and the FPS works way faster. I don't know if thats because I bought the Chinese Version of the phone and there where a lot of trojans running in the background /s
But seriously though, way smoother. Probably partly caused by the longer animation duration set by default, but no idea about the FPS
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Same result here
After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.
karlnorth said:
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.
Click to expand...
Click to collapse
Is your bootloader unlocked?
jc717 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?
karlnorth said:
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?
Click to expand...
Click to collapse
I've achieved an unlocked bootloader! Now I'm trying to figure out how to revert to a US build of Android 9.0
Could you please possibly elaborate on what you mean by the edl master library? Sorry, I have never had to work with edl type stuff before. I successfully extracted the payload I'm just not sure where to go from there. Thank you.
jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
how did you flash it back to the devices
and do you have the file for edl now
i am stuck in to edl and alot of trial for flashing the rom get error
jc717 said:
After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?
Click to expand...
Click to collapse
Hi jc717,
I am same situation you described, i was tried restore from my EDL backup but didn't work. How can fix this, could you explain simple as step by step for beginners, thanks.
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.
BillGoss said:
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.
Click to expand...
Click to collapse
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM
samjoandco said:
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM
Click to expand...
Click to collapse
Glad to hear that.
You can't afford to wait for TWRP 12 - it could be a very long wait.
So you can actually boot OOS 12 beta? What do you mean by "it is not completely up"?
You could try to install the apk mentioned in the https://forums.oneplus.com/threads/oxygenos-12-open-beta-1-for-the-oneplus-8t.1548475/ and use it to try to flash the beta zip again.
Also, if you can get into bootloader, you can always try to flash the files you get from payload dumper using the process described in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/ - just make sure you include all the my_* partitions (they are all logical partitions) as well.
Note also the process hidden in the "Spoiler" button which is where the my_* partitions need to be included.
Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.
samjoandco said:
Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.
Click to expand...
Click to collapse
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?
BillGoss said:
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?
Click to expand...
Click to collapse
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
one more thing i noticied after upgrade is that executing the following command to find the memory type does not return anything. its blank , neither 0 nor 1 . i am not sure what is wrong.
adb shell getprop ro.boot.ddr_type
Click to expand...
Click to collapse
i still dont have 5G or mobile data with OO12. i want to flash the OOS12 again but dont see an option
----
samjoandco said:
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
Click to expand...
Click to collapse
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.
BillGoss said:
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.
Click to expand...
Click to collapse
that entry is missing in getprop. there is no entry for ddr is what i am saying.
===edit====
I rolled back to OOS 11 using the APK you shared earlier from oneplus and have everything working back now.
apparently getprop | grep ddr =0 so i have LPDDR4X ( this is a more common chip for OP8T anyway)
all good. it was a good roller coaster ride for a day
Bill Thanks again
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
I am not sure but I read in a few places that flashing the wrong version will damage the phone.
What did you flash 4 or 5?
Which rom did you extract to imgs?
Was it the the same rom / version that you originally had?
Did you try reaching out to OnePlus support? You can try for repair.
coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
You're probably in CrashDump mode but with no error displayed (I've been there also)
You should be able to get back to bootloader by:
- hold down Pwr+Vol Up until the phone buzzes
- immediately hold Pwr+Vol Down (or Pwr+Vol Up+Vol Down) and you should boot into bootloader
You can then flash the correct xbl* image files
samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
same problem ....tried solution mentioned earlier but after first 3 commands same problem is there.... please help... tried erasing cache ...and recovery and tried flashing recovery again...but nothing is working
{Mod edit: Quotation fixed}
i am having the same problem "
the current image(boot/recovery) have been destroyed"
no solution has worked.
erase cache (Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
same problem presists with other erase commands
booting into recovery says
Sending 'boot.img' (102400 KB) OKAY [ 2.343s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
please help ....... i have no idea what to try ..
magbrave said:
please help ....... i have no idea what to try ..
Click to expand...
Click to collapse
Did you try MSM tool?
Rootk1t said:
Did you try MSM tool?
Click to expand...
Click to collapse
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
same issue here fastboot not not detecting my device after crashing recovery. i even downloaded and installed driver from android studio which worked earlier now its not. it keep shows waiting for device
magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
Boot to EDL using hard keys!
i have same issue. corruption of boot img recovery happens when i boot into recovery on latest c20 update on kb2005. does anyone elses phone get destroyed on c20 when booting into recovery?
Which recovery did you use when you tried to boot into recovery when on OOS 12?
BillGoss said:
Which recovery did you use when you tried to boot into recovery when on OOS 12?
Click to expand...
Click to collapse
was on normal recovery that flashes when upgrading to oos12, stock recovery worked on c16 but when on c21 when boot into stock recovery my phone gets boot img destroyed
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
What guide did you follow? Those steps seems very strange to me. Didn't you unlock your bootloader first? If it is the case, I think just flashing stock firmware with Odin should fix it.
SirFurion said:
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
Click to expand...
Click to collapse
Since none of what you tried to flash was a success, and your phone isn't dead, you can breathe easy. Only a little more research is required on your part to make it reboot successfully.
Hope this is of some reassurance to you, if not technical support.
blackhawk_LA said:
What guide did you follow? Those steps seems very strange to me. Didn't you unlock your bootloader first? If it is the case, I think just flashing stock firmware with Odin should fix it.
Click to expand...
Click to collapse
Hi,
I follow those steps:
How to Root any Samsung device via Magisk and Odin
In thios guide, we will show you the steps to root any Samsung device via Magisk and Odin by flashing the magisk_patched.tar file.
droidwin.com
But it failed at step 5, when I flashing with Odin.
It stay lock during "Prism" step on Odin.
I cancelled the download and ended up with the phone in Brick mode.
I used Hijacker to unbrick it and try to reset factory but unsuccessfully.
Someone advice me to follow this:
Download TWRP Recovery for Samsung Galaxy S22 Ultra | Root Using It
In this tutorial, we will guide you on how to install the TWRP Recovery on Samsung Galaxy S22 Ultra. TWRP recovery is probably the most
www.getdroidtips.com
And it seems work!
I've the welcome screen and I followed step to lauch my phone but recovery system from Google or Samsung doesn't work. So I restart my phone a first time and doesn't success.
I can do things but not finish the set-up of my phone.
I restart another time and I would like to lock bootloader because each time I restart my phone a too quickly red message appears on the screen.
But at the moment when I press up volume button for lock bootloader, my phone switch on download mode with message that I wrote in my first message.
SirFurion said:
Hi,
I must admit that I clearly underestimated the level required to root my phone.
Today, I have the feeling that my phone is dead and this is a bottle in the sea that I'm dropping here to try to resurrect it.
I am currently stuck on a green screen with "Downloading" written in the middle of the screen and this in the upper left corner:
ODIN MODE (SVB Fail)!
prism: No footer detected (0)
prism: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM prism
VBMETA S908BXXU4CWCG, 63617910R
Custom Binary(VBMETA) Blocked By OEM Lock
I put the phone in Download mode thanks to FRP Hijacker by Hagard, then I launch Odin and I tried to flash the file "vbmeta_disabled_R.tar" in USERDATA without success.
I can't flash "AURORA_TWRP_S908X_2200_3.6.2.12_OneUI4.X.tar" in AP either.
I also tried to flash the 4 files from "Samfw.com" about my phone "Samfw.com_SM-S908B_SFR_S908BXXU4CWCG_fac" without success.
I only dream of restarting my phone as on its first day.
This is how I ask you: please help me
Click to expand...
Click to collapse
I've bricked my previous Galaxy phone and successfully revived it. Just Google 'reinstall stock firmware Samsung Galaxy S22 Ultra Odin' and you'll see sites that can help you.