Related
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
You'll have to fastboot twrp, then install twrp... with twrp... yea.
I've been running into the same issue, and I'm on developer preview 3
Sent from my Pixel XL using XDA-Developers Legacy app
I ran into the exact same problem but it might not be for the same reason as you. I was on Android O and downgraded to Nougat. Someone suggested that I run the flash-all.bat command and flash the stock image separately to both partitions A & B. Not really understanding the partitions I don't know why that worked but right after I did it I was able to boot into fastboot TWRP immediately --and this was after hours of trying anything and everything I could think of with nothing working.
---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------
madnik said:
I've been running into the same issue, and I'm on developer preview 3
Click to expand...
Click to collapse
Are you talking about Android O? I don't think TWRP works on Android O yet.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
Which TWRP image are you trying to boot. I use aphla2 and it always boots right in. Maybe try a diff version to see if it works for you.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
Same thing here, but i solved with update adb/fastboot at last version.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
I have 7.1.2 nkg47b flashed to both slots, newest platform tools from google, issue command: fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img and it goes right in to twrp. then from temporary twrp image, I install the twrp RC1 zip for the permanent recovery. works great for me. So, maybe make sure both slots are the same, new updated adb/fastboot tools, RC1 works better that RC2 for me, do temporary by flashing the img file, then permanent install with the zip file.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
I had a similar issue the other day for no apparent reason - was getting stuck on TWRP splash screen. I switched from boot slot B to slot A and it worked after that.
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
docluv01 said:
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
Click to expand...
Click to collapse
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Ok, SO teh message is normal?
I flashed factory 8.0.0, and I get the same message,
TheSt33v said:
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Click to expand...
Click to collapse
docluv01 said:
Ok, SO teh message is normal?
After I did a factory reset, I got the message, clicked power when it asked to, then phone just sits at the google screen.
Click to expand...
Click to collapse
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Oh wait, you get the same message if you flash the stock image? Well in that case, I'm not sure what's wrong. You may need to re-lock the bootloader before that message goes away, but make sure you're on 100% stock software before that happens. It might have something to do with the fact that Pixel devices have A and B firmware slots, so if you bring A back to stock, B might still have the Magisk patched image on it. Someone more familiar with Pixel devices should chime in.
TheSt33v said:
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Click to expand...
Click to collapse
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
docluv01 said:
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
Click to expand...
Click to collapse
I'm thinking so. I'm not sure what the proper procedure is for designating which slot you're flashing to on the Pixel 2's, but it's possible that you now have 1 slot with stock firmware and 1 slot with the Magisk patched image. For the original Pixel devices, the partition names were boot_a and boot_b. So I think, and someone please correct me if I'm wrong, fastboot flash boot <file> will flash the file to whichever slot is active, but using boot_a and boot_b will flash to those designated slots. So to fix your issue, you need to make sure that both boot_a and boot_b contain stock images.
Keep in mind that I've never owned a Pixel before now (although I'm pretty comfortable with flashing other android devices), and I'm not 100% sure about this, so you might not want to take my advice.
relock the bootloader.
Here is what I did:
Fastboot flashing lock
fastboot flashing lock_critical
then tried running the flash-all.bat, got FAILED being it was locked
SO then I ran
Fastboot flashing unlock
fastboot flashing unlock_critical
ran flash-all.bat, seemed to have gone fine. Phone reboots, then after you get the circle, where it says "erasing", after about 10 seconds it reboots and says "your device is corrupt..."
Ughhh, I hope I didn't brick this thing???
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
docluv01 said:
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
Click to expand...
Click to collapse
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
relock your bootloader
canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
Make sure you have the latest version of adb and fastboot from the developer site.
https://developer.android.com/studio/releases/platform-tools.html
I got the message as soon as I unlocked the bootloader. It's normal
I had this issue with old platform tools and could not get my device to boot no matter how many times I flash-all'ed or changed the current boot slot. Upgrade to the latest platform tools and run the flash-all from that directory. If it's still not working, I also unlocked critical: fastboot flashing unlock_critical , so that the flash-all could flash my bootloader as well.
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
charesa39 said:
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
Click to expand...
Click to collapse
This is somewhat true. There are 2 different messages. One that says you are running unsupported software and the color is orange. This message pops up on every boot while the bootloader is unlocked. The other message says your device is corrupt, in red. The phone will not boot. I just ran into this issue while trying to flash the november update
EDIT:
I was able to resolve this by updating adb/fastboot. I updated adb/fastboot before but i guess i did it on my other computer.
So was there any way to fix this without having to relook the bootloader? I've already had to set this phone up a second time after the longest marathon session of trying to get both TWRP and magisk to live happily together on this device, so I'd rather not do it again if it's avoidable.
Literally all I did to cause this is press the button in TWRP to switch to slot A, and after rebooting I immediately got the new scarier message that requires a power button press to boot, after which you get the regular nag about the unlocked BL. The device then hung at the Google padlock screen, so I used the buttons to reboot into BL then tried TWRP. TWRP then hung at the splash screen, so I hooked up to the PC and fastboot booted TWRP. When I tried to switch back to B, strangely, it said I already was. I pressed the button to switch to B anyway, then rebooted. The error happened again, but at least the device boots. I tried rebooting again to see if it had cleared up, but unfortunately not.
I would really like to be rid of this without having to start over. I do have a nandroid but I don't even know if I trust a restore to be successful and potentially make **** worse. Thanks in advance!
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
matt1313 said:
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
IrocD said:
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
Click to expand...
Click to collapse
Flash boot.img first. Don't select which slot
Then reboot bootloader and fastboot active slot b
Sent from my Pixel 2 XL using Tapatalk
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.
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