Develop Bugs

Zenfone 2 failed update, can't flash stock firmware

I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.

PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?

http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.

PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.

Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!

.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me

Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...

Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.

mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***

Cannot root marlin

I have a Pixel XL that was purchased from the google store and WAS running the latest image flawlessly (NDE63V).
i got a little frisky and decided to root, and see if some of my favorite root applications would work.
i checked "oem unlocking" in developer settings, then proceeded to boot into fastboot to unlock.
i ran the unlock command successfully, rebooted, and set my phone back up.
i then downloaded "root-marlin-pixelxl.zip" which had the latest su (SR3).
i booted into fastboot, and ran the command "fastboot boot boot-to-root.img", it completed successfully.
the device then rebooted, rebooted again, then got stuck in a bootloop. i let it sit for an hour hoping patience would fix my issue.
it never did. i held power, and force restarted the device and let it attempt to boot again (never did).
as a last resort, i booted into recovery, wiped data/reset, and attempted to boot one more time. again, it never did.
I downloaded the factory image from google (NDE63V), flashed it, and attempted root one more time.
i went through the whole process as before, even tried using the earlier boot-to-root, and still nothing. i am currently flashing my pixel xl back to stock ONE MORE TIME, and i doubt ill try to root again.
i did a search on the forums, as well as google, and couldnt find answers. i found people with similar problems, but they never received help.
Anyone have any suggestions? similar problems?

Was it with the latest fastboot tool? There are so many versions flying about, I wouldn't give up until you've made sure it's the latest from Google.
Sent from my Pixel XL using Tapatalk

DaveHTC200 said:
Was it with the latest fastboot tool? There are so many versions flying about, I wouldn't give up until you've made sure it's the latest from Google.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
My operating system is Linux Mint 18 "cinnamon" 64 bit.
i obtained the latest fastboot and adb drivers from the Google repository. i ran
>sudo apt-get update
>sudo apt-get install android-tools-fastboot android-tools-adb
when using adb and fastboot commands on my 5x and 6p, all commands are executed and work flawlessly.
i

noidea24 said:
My operating system is Linux Mint 18 "cinnamon" 64 bit.
i obtained the latest fastboot and adb drivers from the Google repository. i ran
>sudo apt-get update
>sudo apt-get install android-tools-fastboot android-tools-adb
when using adb and fastboot commands on my 5x and 6p, all commands are executed and work flawlessly.
i
Click to expand...
Click to collapse
Well if they're from Google then it's odd!!
Just because they work with the 5x and 6p doesn't mean too much because of the new boot slots with the pixel, so it's slightly different.
I'm at loss as much of you, as there isn't any reason you should have this issue
Sent from my Pixel XL using Tapatalk

ive watched a video or two and seen one difference between what i did and what others did.
after "fastboot oem unlock" i had let my phone boot back up.
i seen others run "fastboot oem unlock" and then without booting they run the "fastboot boot boot-to-root.img" before boot. then they let it boot, reboot and run the "fastboot boot boot-to-root.img" one more time.
i guess ill try it once more.

Update.
while waiting for the factory image to download (accidentally deleted it) i figured id keep ****ing with it.
quick explanations of whats happened.
unlocked bootloader
fastboot booted boot-to-root
go stuck in a bootloop
tried reset in recovery
kept bootlooping
while still bootlooping, i (just being curious) booted to bootloader, fastboot flashed elementalx, fastboot reboot'ed, got the device to power up fine.
now im tryin to boot-to-root one more time, if it doesnt work i guess ill be fine with no root with ex kernel.

noidea24 said:
Update.
while waiting for the factory image to download (accidentally deleted it) i figured id keep ****ing with it.
quick explanations of whats happened.
unlocked bootloader
fastboot booted boot-to-root
go stuck in a bootloop
tried reset in recovery
kept bootlooping
while still bootlooping, i (just being curious) booted to bootloader, fastboot flashed elementalx, fastboot reboot'ed, got the device to power up fine.
now im tryin to boot-to-root one more time, if it doesnt work i guess ill be fine with no root with ex kernel.
Click to expand...
Click to collapse
Let us / me know what happens. This is a problem a lot of peeps are having...
Thanks!
-Scott

Scott said:
Let us / me know what happens. This is a problem a lot of peeps are having...
Thanks!
-Scott
Click to expand...
Click to collapse
this has worked, refer to post #710 here
in case your lazy, ill qoute my post here...
------------------------------------------------------------------------------------
noidea24 said:
In the same boot. bootloop after fastboot booting the sr2 and sr3 boot-to-root.
i couldnt get it to stop bootlooping, so i started downloading the factory image.
while downloading i figured id mess around with it.
i took my bootlooping pixel xl, put it in bootloader mode, and fastboot flashed elementalX kernel, then fastboot reboot'ed.
oddly enough, flashing EX kernel fixed the bootloop, and it booted properly.
so now im flashing elemental, then doing the boot-to-root, to see if i cant get my pixel to boot with root.
------------------------------------------------------------------------------------------------------
this has worked!
ill tell you exactly what happened.
flashed stock, tried rooting via boot-to-root sr3, boot looped.
flashed to stock, tried rooting via boot-to-root sr2, bootlooped.
while bootlooping, i flashed the elementalX kernel, this stopped the bootloop.
i then booted back into bootloader and tried the boot-to-root while on EX kernel, and it worked flawlessly, no boot loops.
so just to be sure, i repeated my process. boot to root would always cause a bootloop on a stock device (my device)
but as long as elementalx was flashed first, boot-to-root would not cause a boot loop
tl:dr
Boot to root would not work (caused bootloop) on completley stock pixel xl
Boot to root does work as long as i flash elementalx first.
Click to expand...
Click to collapse

sorry, more information.
everything ive said before is still correct, but......
the boot-to-root is not working.
with elementalx, it does prevent the bootloop after flashing boot-to-root, but it does not root.
no superuser app is installed, and after installing the superuser app it says the su binary is not installed.
ive tried going back and flashing boot-to-root, it reboots twice, boots properly, but no su binary still.

I am in the same boat...
i used the method of flashing the elemental kernel to fix the bootloop, however, i now have the app but no binaries.

Deus_eps_machina said:
I am in the same boat...
i used the method of flashing the elemental kernel to fix the bootloop, however, i now have the app but no binaries.
Click to expand...
Click to collapse
would you do me a favor, and boot into your bootloader, and tell me the manufacturer of your "UFS" and your "DRAM"?

noidea24 said:
would you do me a favor, and boot into your bootloader, and tell me the manufacturer of your "UFS" and your "DRAM"?
Click to expand...
Click to collapse
Samsung

Deus_eps_machina said:
Samsung
Click to expand...
Click to collapse
i think that variance is part of the problem.
from the people ive asked, the only people with problems all have samsung...

noidea24 said:
i think that variance is part of the problem.
from the people ive asked, the only people with problems all have samsung...
Click to expand...
Click to collapse
i do not think thats the problem...
I just downgraded to the October build 63P and i have working root...

I think most or all the people with issues were on V and some, I think went to X and it worked.

jjayzx said:
I think most or all the people with issues were on V and some, I think went to X and it worked.
Click to expand...
Click to collapse
yep, i was on V

noidea24 said:
this has worked, refer to post #710 here
in case your lazy, ill qoute my post here...
------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Good stuff!
I am totally trolling the Xl forums to see what issues peeps have (yep, I got one).
Thanks for the feedback. Made a note in my notebook :good:
-Scott

Can you keep root and move to the latest build?

noidea24 said:
Can you keep root and move to the latest build?
Click to expand...
Click to collapse
You will need to re-root

Scott said:
You will need to re-root
Click to expand...
Click to collapse
But then that's a problem, Since we are having problems rooting on the nde63v build.
I think I can sacrifice root to stay on the latest build for now.

Help, might have killed my device

Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?

ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.

like Fury said, your platform tools need to be updated, same thing happened to me.

What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app

fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.

Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.

Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.

Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.

Question [Solved] root problems

So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?

can you get into bootloader and does it detect?

passion8059 said:
can you get into bootloader and does it detect?
Click to expand...
Click to collapse
Okay, so how do I even get it into bootloader?

TheShinyEnd said:
Okay, so how do I even get it into bootloader?
Click to expand...
Click to collapse
Power + Vol - (down)

passion8059 said:
Power + Vol - (down)
Click to expand...
Click to collapse
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?

TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck

Okay I manage to get it into Fastboot, thank you very much both! much appreciate the help and your time!

TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
remove any cables wait till nothing on screen & try again

jcp2 said:
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck
Click to expand...
Click to collapse
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file

I always download the full zip in order to get the boot.img for the zip, then I use Android Flash Tool to download and flash the full zip update. Let the phone reboot unrooted. If you have the magisk patched boot.img from your phone, copy it to your PC and use Platform tools to flash it to both slots using the CMD prompt.
Open a Command Prompt in the folder you copied the patched boot.img to.
Flash the boot.img (Magisk Patched) to both slots: fastboot flash boot <drag and drop boot.img> --slot all

TheShinyEnd said:
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file
Click to expand...
Click to collapse
Before you do any more modding, have you flashed the A13 bootloader to both slots so you don't get in trouble with the new ARB? If not, I suggest you do so before you do anything.
If you have, never mind, lol...

I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover

TheShinyEnd said:
I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover
Click to expand...
Click to collapse
Fixed it.
so a little back story, at a random point in my day the phone(p6p) said restart to apply update, and I was rooted at the time and thought it would failed, and I went for it. it did manage to install(2nd "July" august update). then I saw a vid about A13 and thought I might aswell try to install A13 on my phone, I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
I think this was the problem. I don't know as to how, but maybe magisk or some module manage to make the device itself think it's not rooted.. albeit it shows that the bootloader is indeed unlocked.
Needless to say, I managed to fix the problem, gained root perms again. thanks for the help and your time! much appreciated

TheShinyEnd said:
I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
Click to expand...
Click to collapse
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.

roirraW edor ehT said:
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.
Click to expand...
Click to collapse
I meant the System update downloading phase

TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
same issue here, did you find any solution buddy??
snaptube
vidmate​

paulanswer240 said:
same issue here, did you find any solution buddy??
Click to expand...
Click to collapse
explain? can you not boot or you don't have root? or both

S10e - impossibility to install Lineage OS

I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?

Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)

Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC

frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself

Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable

frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.

anyway glad for support sigmund
you re my friend now