Hi everyone, as the title already says, I am having issues booting a custom kernel on my SM-T500. I have been able to flash agreenbhm's TWRP and boot that just fine, but that is using the prebuilt kernel. When I try to boot a custom kernel, OEM locking gets enabled out of nowhere and I have to reflash the stock ROM in order to be able to use the tab. I initially tried booting a WIP close-to-mainline kernel, so I assumed it's just an issue of the bootloader not liking the mainline kernel, but then I tried to flash a custom compiled downstream kernel and I got the same issue. Has anyone else ever had such an issue, even if it's on another device? Were you able to work around it? If yes, how? Thanks in advance for any answers.
LegoLivesMatter said:
Hi everyone, as the title already says, I am having issues booting a custom kernel on my SM-T500. I have been able to flash agreenbhm's TWRP and boot that just fine, but that is using the prebuilt kernel. When I try to boot a custom kernel, OEM locking gets enabled out of nowhere and I have to reflash the stock ROM in order to be able to use the tab. I initially tried booting a WIP close-to-mainline kernel, so I assumed it's just an issue of the bootloader not liking the mainline kernel, but then I tried to flash a custom compiled downstream kernel and I got the same issue. Has anyone else ever had such an issue, even if it's on another device? Were you able to work around it? If yes, how? Thanks in advance for any answers.
Click to expand...
Click to collapse
What do you mean by "OEM locking"? Do you mean the FRP lock that you disable by enabling OEM mode in Developer options? That only requires you to enter the google account login and password to finish booting.
lewmur said:
What do you mean by "OEM locking"? Do you mean the FRP lock that you disable by enabling OEM mode in Developer options? That only requires you to enter the google account login and password to finish booting.
Click to expand...
Click to collapse
OEM locking is indeed what I mean. Google Account is not a problem because I never log into it in the first place, and when I open up developer options OEM unlocking is enabled and grayed out with a "Bootloader is already unlocked" message.
LegoLivesMatter said:
OEM locking is indeed what I mean. Google Account is not a problem because I never log into it in the first place, and when I open up developer options OEM unlocking is enabled and grayed out with a "Bootloader is already unlocked" message.
Click to expand...
Click to collapse
If you don't have a google account setup on the tablet, the FRP is irrelevant. So what's the problem? BTW, the FRP lock and the bootloader lock are two entirely different things. One has nothing to do with the other. The FRP lock has been around long before Samsung started locking the bootloader on non-carrier tablets.
The problem is that, even when the bootloader is unlocked, the tablet simply won't accept a custom kernel. If you want to know why I believe OEM lock is at fault here, first take a look at the download mode screen **before** flashing a custom kernel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, after flashing a custom kernel:
(sorry for the below average picture quality, especially on the last one)
After flashing the custom kernel, "Current Binary" goes from "Samsung Official" to "Custom", and **OEM lock** goes from Off to **On**, and every time I restart the tablet it will go straight to download mode until I reflash the stock firmware.
LegoLivesMatter said:
The problem is that, even when the bootloader is unlocked, the tablet simply won't accept a custom kernel. If you want to know why I believe OEM lock is at fault here, first take a look at the download mode screen **before** flashing a custom kernel:
View attachment 5371623
Then, after flashing a custom kernel:
View attachment 5371625
(sorry for the below average picture quality, especially on the last one)
After flashing the custom kernel, "Current Binary" goes from "Samsung Official" to "Custom", and **OEM lock** goes from Off to **On**, and every time I restart the tablet it will go straight to download mode until I reflash the stock firmware.
Click to expand...
Click to collapse
If you ever get the tablet to boot, and look in Develper options, you find the setting for OEM is enabled and greyed out so you can't change it. IOW, OEM lock is ON and your custom ROM has no Factory Reset Protection. If someone steels the tablet, they can get past the lock screen simply by doing a factory reset. There is some other reason you are boot looping.
The 'qualcomm_secureboot' enabled might be the actual problem.
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
lewmur said:
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
did u ever solve this
xAriana said:
did u ever solve this
Click to expand...
Click to collapse
I'm not the one who had the problem. I've had LOS 18.1 installed for a long time.
lewmur said:
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM. I copied the following from the thread on installing LOS 18.1.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
I don't know if that file is something you want to use... I recently flashed it and have been having a similar issue ever since... I can root the device and everything but after some time it will fail to boot out of nowhere and give me the "only official binaries may be flashed" error with the vbmeta file shown as the issue. And even after reflashing the stock firmware. It always shows that the device is custom in the settings/device status menu and won't do updates. No matter what I do I cannot get it to show device normal anymore... and once it shows that error the ONLY fix is to flash stock firmware. I can't reflash the disabled vbmeta or even a stock vbmeta on its own to the device. It has to be the full firmware. Period... I think that disabled vbmeta file has some sort of issue with it and it needs to be checked into. I know pretty much everything there is with samsung devices and I've never seen any device act this way until the day I flashed that vbmeta file...
I think that is controlled by the vbmeta.img. That's normally the first step in flashing a custom ROM.
Click to expand...
Click to collapse
Thanks for mentioning that, judging by what's going on this very well could be the cause.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Click to expand...
Click to collapse
Can this be created manually with
Code:
avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
or do I have to download it from the LineageOS post?
did u ever solve this
Click to expand...
Click to collapse
Not yet.
Related
I followed Heisenberg's How-To Guide For Beginners and unlocked the bootloader, then installed TWRP.
It was fine yesterday, rebooted it several different times and no issues. Had the normal warning about the bootloader being unlocked. Today, I powered the phone on, not to bootloader, just to android, and got the "Your device is corrupt. It can't be trusted and may not work properly." See image below.
What do I need to do? Do I just do a factory reset? Or should I try re-flashing TWRP?
Thanks for any help you guys can offer, I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just wait 10 seconds and your device will boot. This is normal warning after making changes to OS.
Try to use search. This issue has few threads going on.
http://forum.xda-developers.com/search.php?searchid=396007182
This message will appear until u will lock it bootloadet again
emiwonder said:
This message will appear until u will lock it bootloadet again
Click to expand...
Click to collapse
Message for unlocked bootlader is orange.
https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
Witek_M said:
Just wait 10 seconds and your device will boot. This is normal warning after making changes to OS.
Try to use search. This issue has few threads going on.
http://forum.xda-developers.com/search.php?searchid=396007182
Click to expand...
Click to collapse
I apologize, I should have mentioned that I have not rooted the phone. The farthest I went was to unlock the bootloader and then install TWRP.
I did search the XDA Nexus 6P Q&A, Help & Troubleshooting forum and found this thread. However, the OP already had his phone rooted, but my phone is not rooted, so I did not want to mess the phone up any further. I am very new at this. This is the first time I have unlocked a bootloader and installed a custom recovery.
Also, the OP's phone would not go past the google logo, however, my phone will boot all the way up and it operates normally. Another reason I didn't follow what he did (performing part 9 of Heisenberg's guide).
j.r.pitcher said:
I apologize, I should have mentioned that I have not rooted the phone. The farthest I went was to unlock the bootloader and then install TWRP.
I did search the XDA Nexus 6P Q&A, Help & Troubleshooting forum and found this thread. However, the OP already had his phone rooted, but my phone is not rooted, so I did not want to mess the phone up any further. I am very new at this. This is the first time I have unlocked a bootloader and installed a custom recovery.
Also, the OP's phone would not go past the google logo, however, my phone will boot all the way up and it operates normally. Another reason I didn't follow what he did (performing part 9 of Heisenberg's guide).
Click to expand...
Click to collapse
Does that warning impair in any form or fashion usability of your device? Unable to browse? Unable to text? Unable to call or receive calls?:cyclops:
Did you forget to flash the modded boot image or something? I would just flash everything back to stock and start over if I were you
Witek_M said:
Does that warning impair in any form or fashion usability of your device? Unable to browse? Unable to text? Unable to call or receive calls?:cyclops:
Click to expand...
Click to collapse
It does not impair anything so far as I've seen. I've used most of my apps with no problems. I can make and receive calls and texts just fine. I am also able to browse the web just fine as well. Everything seems to be working normally. I just get that red triangle (Your device is corrupt...) warning whenever I boot the phone.
Here is what happens in order of booting first into the bootloader:
I boot into the bootloader and it comes up normally.
I go down and select recovery mode, it comes up with the normal orangish-yellow triangle (bootloader unlocked) warning, then the Google logo with the unlocked padlock, then the TWRP splash screen, then into TWRP.
Within TWRP, if I select "Reboot", then "System" I get the screen asking if I want to install SuperSU now, I tap "Do not Install" (per Heisenberg's guide), the screen goes blank, the normal orangish-yellow triangle (bootloader unlocked) warning comes up, then the Google logo with the unlocked padlock, then blank again, then the red triangle (Your device is corrupt...) warning, then the Google logo with the unlocked padlock then the animated circles that finally morph into "android", then the phone is on and I can use it normally.
Does that help in diagnosing the problem at all?
In my limited experience the corrupt screen but able to boot means that something on the phone is the wrong version. Flash the vendor image, radio, and boot img that is made for your rom.
Systemless root is the likely the cause because the boot img is from an earlier build.
btort1 said:
Did you forget to flash the modded boot image or something? I would just flash everything back to stock and start over if I were you
Click to expand...
Click to collapse
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
siegesoldier said:
In my limited experience the corrupt screen but able to boot means that something on the phone is the wrong version. Flash the vendor image, radio, and boot img that is made for your rom.
Systemless root is the likely the cause because the boot img is from an earlier build.
Click to expand...
Click to collapse
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
j.r.pitcher said:
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
Click to expand...
Click to collapse
I did not realize you did not change the boot img. Without flashing a boot img with verity checks disabled, (basically everyone besides stock) you'll get the corrupt warning if ANYTHING in the system partition gets modified. which is likely what happened when you swiped.
The warning means nothing, nothing is effected and if you flash one without verity checks you just get the yellow warning instead.
siegesoldier said:
I did not realize you did not change the boot img. Without flashing a boot img with verity checks disabled, (basically everyone besides stock) you'll get the corrupt warning if ANYTHING in the system partition gets modified. which is likely what happened when you swiped.
The warning means nothing, nothing is effected and if you flash one without verity checks you just get the yellow warning instead.
Click to expand...
Click to collapse
I forgot to mention that after doing the "swipe to allow modifications" and TWRP installed, I rebooted the phone multiple times that day, Monday (11/30), and did not get the red triangle (Your device is corrupt...) warning at all. The following day, Tuesday (12/1), I rebooted the phone and got the red triangle (Your device is corrupt...) warning. Between installing TWRP (with swiping to allow modifications) and getting the red triangle (Your device is corrupt...) warning the following day, I did nothing else other than normal use of the phone. That is what is confusing to me.
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
dumberthandumb said:
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
Click to expand...
Click to collapse
go into fastboot mode and do.... fastboot -w
Tech_Savvy said:
go into fastboot mode and do.... fastboot -w
Click to expand...
Click to collapse
I did that and it didn’t work
dumberthandumb said:
I did that and it didn’t work
Click to expand...
Click to collapse
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Nick80835 said:
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Click to expand...
Click to collapse
How do I unlock critical partitions? Also I have already flashed TWRP. If I try to push the factory image without TWRP it tells me not enough space.
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
nstirton said:
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
Click to expand...
Click to collapse
My slot b has been fleshed with TWRP and a with the original os. I still can’t get it to boot. Is there anyways that I can just flash everything back to factory setting? I don’t care about personal data. I even tried flashing both slots with the os and still no luck
flash OTA via adb sideload , it will fix your issue
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
galakanokis said:
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
Click to expand...
Click to collapse
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
dumberthandumb said:
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
Click to expand...
Click to collapse
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
You NEED to unlock critical partitions to flash all of them.
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
Flash all? How do I do this?
dumberthandumb said:
Flash all? How do I do this?
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds
galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
Seems you don't know how to boot into recovery,when you see this Android guy you need to press volume up and power.
Hi, can someone help me with this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
galakanokis said:
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
Click to expand...
Click to collapse
Thank you I finally got it to work, Apparently only my boot loader was unlocked and I did not have critical partitions unlocked, ones I unlocked critical partitions the flash I was able to go through
Thank you everyone for your help
nibera said:
Hi, can someone help me with this problem?
View attachment 4612857
Click to expand...
Click to collapse
Do you have creitical partitions unlocked ?
so, my OP 6t is stuck at bootloop and I cvan not turn it off...
any sugestion and help?
Thanks
maraschino said:
so, my OP 6t is stuck at bootloop and I cvan not turn it off...
any sugestion and help?
Thanks
Click to expand...
Click to collapse
anyway, for others
finally I did manage to turn off the device by pressing volume up + power off button.
after that started phone regulary again and booted normally...
I don't know why this hapend, but made me nervous as hell
got the same problem, find the same solution to boot, however still blocked in a bootloop any advice someone ?
Soujyu51 said:
got the same problem, find the same solution to boot, however still blocked in a bootloop any advice someone ?
Click to expand...
Click to collapse
Some more information would help, bootloader locked or unlocked, in the process of root, flashing stock firmware or whatever you were doing when it bootlooped.
ggrant3876 said:
Some more information would help, bootloader locked or unlocked, in the process of root, flashing stock firmware or whatever you were doing when it bootlooped.
Click to expand...
Click to collapse
sorry, my bad
bootloader unlocked, OP6T root , magisk installed
bootloop appeared in the process of uninstalling 2 modules
Word is that it's a bug in Magisk, I believe I had it on version 17.1 and 17.3 both.
YrrchSebor said:
Word is that it's a bug in Magisk, I believe I had it on version 17.1 and 17.3 both.
Click to expand...
Click to collapse
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?
Soujyu51 said:
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?
Click to expand...
Click to collapse
You installed Magisk by fastboot flashing the modified boot.img? Couldn't you just flash the stock boot.img?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Soujyu51 said:
sorry, my bad
bootloader unlocked, OP6T root , magisk installed
bootloop appeared in the process of uninstalling 2 modules
Click to expand...
Click to collapse
There's literally another thread in this forum about another member who is stuck in bootloop after uninstalling a magisk module.
I suggested that he fastboot flash the stock boot.img
That's probably me. But that did not help.
Soujyu51 said:
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?
Click to expand...
Click to collapse
You should be able to use the button combo to power down and then get it to boot up normally, then just uninstall magisk through the app if you want to prevent it from happening again. Or just run it and deal with it, knowing that it doesn't seem to happen on every reboot or anything
YrrchSebor said:
You should be able to use the button combo to power down and then get it to boot up normally, then just uninstall magisk through the app if you want to prevent it from happening again. Or just run it and deal with it, knowing that it doesn't seem to happen on every reboot or anything
Click to expand...
Click to collapse
seems to be a 100% boot in bootloop Ahah (22/22 run)
well I tried a couple of thing
in the fastboot mode, I flashed the stock boot img ( no success)
in recovery mode I tried to flash the uninstaller no success (error 1)
Full disclosure, I don't have this phone (yet), but isn't it an A/B slot phone?
Are you sure you are flashing stuff to the right slot? Are you sure you are booting from the right slot?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
Full disclosure, I don't have this phone (yet), but isn't it an A/B slot phone?
Are you sure you are flashing stuff to the right slot? Are you sure you are booting from the right slot?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
How would we know if we are? Or which slot is booting? I'm coming from a non a b phone so it's all new to me
So I'm guessing this is the core of your problem. You need to read as much as possible about how A/B slot phones work.
In a nutshell, there are two complete sets partitions (things like system, boot, vendor...). One is the A set, the other B. This is done to ensure that a device continues to operate even if there is a failed OTA, and help speed up the upgrade process by doing it to the non-booted slot.
What can be very confusing is that after flashing something, the bootloader may choose to switch to the other slot.
You can find out what the active slot is in adb:
Code:
adb shell getprop ro.boot.slot_suffix
and in fastboot:
Code:
fastboot getvar current-slot
Switching to the other slot is done in fastboot:
Code:
fastboot set_active other
-or-
Code:
fastboot set_active [a,b]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
So I'm guessing this is the core of your problem. You need to read as much as possible about how A/B slot phones work.
In a nutshell, there are two complete sets partitions (things like system, boot, vendor...). One is the A set, the other B. This is done to ensure that a device continues to operate even if there is a failed OTA, and help speed up the upgrade process by doing it to the non-booted slot.
What can be very confusing is that after flashing something, the bootloader may choose to switch to the other slot.
You can find out what the active slot is in adb:
Code:
adb shell getprop ro.boot.slot_suffix
and in fastboot:
Code:
fastboot getvar current-slot
Switching to the other slot is done in fastboot:
Code:
fastboot set_active other
-or-
Code:
fastboot set_active [a,b]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
I am stuck with the phone ONLY booting into slot A bootloader.
I can't get into recovery mode at all, not with the commands, nor with buttons- always goes into the bootloader.
This happend after installing TWRP and Magisk.
The commands:
"fastboot getvar current-slot" tells me that I am on slot "A"
"fastboot set_active other" and "fastboot set_active " do not work, no error but the long help list of commands comes up.
Am I using the wrong ADB-Version where these commands are not included, because I can't find them in the "help" list?
Can anyone please help, I am stuck.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
stuck at boot loader is unlocked screen
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks
have you guys tried pressing and holding vol+, vol-, and power until it turns off or goes to Bootloader screen.? i had a hard time with that on my 6t.
acele7 said:
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks
Click to expand...
Click to collapse
First have you asked over in the 7pro side of the house as this is the 6t side... And a bit more info would help.. like what did you do prior to it getting stuck... Are you on a custom rom or stock.. ect...
acele7 said:
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks
Click to expand...
Click to collapse
I use a OnePlus6t and know absolutely nothing about the 7 pro but if you guys have msm tool that's where I'd be headed to if I were in your same situation. Any unbricking tools and or guides is where I would read everything.
If i was in exact same situation on my 6t I would try holding my +&- volume keys down and my power button until I see fastboot on screen them release and go from there but I would run the msm tool we have for my device model. If for some reason I couldn't get that going which I don't believe that sort of thing happens much but if it did I'd go over to the collection of unbricking tools thread and memorize the entire thread and see if something there may work. Possibly fastboot flash a fastboot rom..
Maybe If you have another device upload a pic of what screen you're stuck on to help us better understand..
EDIT: I don't think it's verity. I think something more is going on. I tried installing another rom with its own kernel, and the problem did not go away. So what's keeping me from getting rid of this nuissance and booting normally?
I've done some searching around to try to fix this problem, and frankly, I've got a headache now. Ok. I've got my bootloader unlocked, and I've installed TWRP and Magisk. Now I want to disable DM Verity so my device will boot normally. As it is, I have to go into the Bootloader in order to get the system to boot: no other option. Edit: Is it even verity doing this? Is it something else?
The guides for disabling dm verity have not worked. Iinstalled Magisk, and some people said that that would disable dm verity all on its own. It didn't. I installed the no-verity-opt-encrypt thing, hoping that would disable dm verity. I actually tried that option before installing Magisk. It didn't work.
Well, any ideas? Do I have the right dm verity thing? Is there more than one? Did I maybe use the one for the G5 by mistake? How do I get past this annoying thing? Please advise.
I'm not familiar with the layout of the Moto G5, so I can only relate what I've learned on Pixel devices.
I assume this is what you're seeing when you attempt to boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What this means is that a verification error was encountered during run time. This is a function of Android Verified Boot; more details here.
Disabling dm-verity is generally done by flashing the [icode[vbmeta[/icode] image with the --disable-verity --disable-verification arguments, as such:
Code:
fastboot flash vbmeta <vbmeta image> --disable-verity --disable-verification
However, this may not apply to the Moto G5, as I'm not sure its partition structure is similar to the Pixels. Additionally, this should generally be unnecessary if you're on a stock ROM with a stock kernel.
It seems others have encountered the same problem before. It's rather wise to search before posting. Check out this thread:
Stuck at 'Your device has been unlocked and can't be trusted'. Can't enter recovery
I was flashing a rom and followed all the steps correctly: unlocked bootloader, flashed twrp, rooted and then flashed. Everything worked fine on the first go but the phone app was foreclosing instantly so i rebooted into recovery to wipe data and...
forum.xda-developers.com
No, that's not it. What happens is that when I reboot it tells me:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
Click to expand...
Click to collapse
And then it boots into recovery.
My device is by no means "stuck". It boots into recovery. In order to actually boot the system, I have to choose the option Reboot > Bootloader. And then when the bootloader comes up, I choose Start, and then the system boots. But this is not what I want my phone to do! I want it to, you know, behave!
There doesn't appear to be a separate vbmeta thing. There's just boot.img. AND when I tried installing a custom rom that came with its own kernel, it did not solve the problem. So something else must be going on here.
And I did everything this guy said to do regarding flashing the stock rom: https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/
No good. Need more help.
For anyone who goes searching desperately for a solution to this same problem: There is a workaround, and that seems to be the best we can do.
Step 1: Get the raw boot.img from your firmware package.
Step 2: Patch boot.img with Magisk. Copy it to your PC.
Step 3: Get TWRP. But you've gotta get an older version, because it's smaller. Get 3.5.0. It's going to matter in a moment.
Step 4: Reboot to Bootloader (hold Vol- while phone is turning on or rebooting).
Step 5: Use fastboot to flash the modified Boot image to the Recovery partition (fastboot flash recovery <themodifiedbootimage>). It's not where a Boot image is supposed to go, but in this case, it's what needs to happen.
Step 6: Likewise, flash TWRP to the Boot partition (fastboot flash boot <twrp.img>).
So far, that seems to work. Now, when you reboot, your phone will boot into the system like it's supposed to. If you want to launch Recovery, what you now have to do is boot into the Bootloader (see Step 4 above) and choose Start. This would normally start the system, but because TWRP is sitting in the Boot partition, it will launch TWRP instead.
I don't have a guide yet for how to make the Boot partition bigger, so that the latest version of TWRP can comfortably fit into it. And I don't know where this whole problem came from in the first place, and how to fix it the right way. But this is what we've got for now, and as far as I can tell, it works pretty well.
But remember: Your Boot and Recovery images are switched now. So any time you want to make any modifications to either, you have to remember where they are.