Develop Bugs

Nextbit Robin 00WW_1_19F Factory Image now available

Link: http://bit.ly/00WW_1_19F
//READ THIS//
Your phone must have an unlocked bootloader for this to flash properly
This link contains the files necessary to get your Robin back to the following:
Android Version: 6.0
Android Security Patch Level: January 1, 2016
Baseband Version: M8992FAAAANAAM
Build number: 00WW_1_19F
//INSTRUCTIONS for Windows//
1. Plug your Robin into your PC
2. Boot your Robin into Fastboot mode (Power + Volume Down)
3. Open a command window in the 119F folder (With the folder open, press Shift + Right click)
4. Type flash-all.bat and press Enter
5. Your phone will flash all the necessary files and reboot
//INSTRUCTIONS for Mac//
1. Plug your Robin into your Mac
2. Boot your Robin into Fastboot mode (Power + Volume Down)
3. Open Terminal and navigate into the directory containing the image files
4. Type ./flash-all.sh and press Return
5. Your phone will flash all the necessary files and reboot

Mine. Just in case.

Dammit @Nextbit_Khang - you beat me to the punch - I only just finished uploading my 119F images before noticing your post.
Thanks heaps for uploading this though! A fastboot-compatible system.img makes modding the Robin so much more easier.

[deXter said:
;1165754]Dammit @Nextbit_Khang - you beat me to the punch - I only just finished uploading my 119F images before noticing your post.
Thanks heaps for uploading this though! A fastboot-compatible system.img makes modding the Robin so much more easier.
Click to expand...
Click to collapse
Yeah no worries! The team knows how important the dev community is.. That's one reason Robin was built! Keep rocking and let me know if you have any questions.

Still Stuck
Nextbit_Khang said:
Yeah no worries! The team knows how important the dev community is.. That's one reason Robin was built! Keep rocking and let me know if you have any questions.
Click to expand...
Click to collapse
Just tried this a few times and my phone will not boot. It gets though the process fine (screenshot) but it goes straight back to the stock recovery screen when I'm done. I hit Reboot system now and it just takes me right back to recovery. I'm really stumped as to what is going on and I have an unusable Robin at the moment.

lordlittlebrooks said:
Just tried this a few times and my phone will not boot. It gets though the process fine (screenshot) but it goes straight back to the stock recovery screen when I'm done. I hit Reboot system now and it just takes me right back to recovery. I'm really stumped as to what is going on and I have an unusable Robin at the moment.
Click to expand...
Click to collapse
I think I figured it out. I must have relocked the bootloader at some point while trying to restore back to stock. So even though the command prompt results were telling me that it had completed successfully using the .bat file, it really hadn't. I tried doing the commands one at a time manually, line by line, and that is where I saw the "error" messages. So, if you're bootloader is not unlocked (fastboot oem device-info), type fastboot oem unlock in fastboot and then run the .bat file. Worked like a charm after that.

Thank you for the images

Worticus Rex said:
Thank you for the images
Click to expand...
Click to collapse
You're very welcome!

How soon can we get the updated system images for the new update @Nextbit_Khang ?

It is rolling out today!

I was running cm13 for a couple of weeks, decided to revert back to stock. Tried this method with success, but whenever i try to update the rom ota, it fail and boot to stock recovery with the error '' system partition has unexpected contents"
Tried to lock the bootloader and no luck. Plz help.

Rolex954 said:
I was running cm13 for a couple of weeks, decided to revert back to stock. Tried this method with success, but whenever i try to update the rom ota, it fail and boot to stock recovery with the error '' system partition has unexpected contents"
Tried to lock the bootloader and no luck. Plz help.
Click to expand...
Click to collapse
I would try Reflashinf the stock images, then immediately after it boots up for the first time and you go through setup, try locking the bootloader. If that doesn't work, you could try just flashing the latest image

I seem to be facing a rather odd problem. Everything EXCEPT Key_info succeeds.. This is the only one that fails stating partitions is missing/invalid on the target... Any luck? I can't boot into stock ROM.

Moto G7 Play XT1952-4 Recovery

Hello, does anybody know when a recovery for the moto G7 play XT1952-4 might be released? I am eager to root my new phone.

I am also looking for the recovery of Moto G7 Play, I unlocked my BootlLoader to make Root and I do not think any Recovery

You don't need TWRP to root the phone. As long as the bootloader is unlocked, you can root with Magisk. Select the Link To Installation Instructions and follow the Boot Image Patching section. It requires using ABD commands, and although it looks/seems complicated, it is actually very easy. Plus, you will have learned something as well as root your phone.
If the G7 Play is actually code-named "Channel", then this link will give you stock firmware for you to download and extract the stock boot image.

Magisk boot.img
Ok I got the retail Canada ROM. Now I am going to extract boot img and patch it with Magisk manager. Once patched I am going to flash it to my phone using abd fastboot? At this point it will be rooted or do I use SuperSU to root? Under software channel on my phone it says "Bell" but the build number and model number matched up. XT1952-4 PPY29. 105-57 so it should be good hopefully.
Thanks

Error: cannot open 'magisk_patched.img'
Must be wrong Rom. Everything worked fine until I had to flash it. I put patched IMG right in adb directory and opened a command window from there but when I tried to flash it I got the error cannot open file. Oh well I think I will wait for a recovery it's the easy way for me.
Thanks

Code named 'channel'
There are 2 more versions of it in the list you provided. Not sure what the abbreviations are before CA for Canada but I will try them too. If I get the same error when flashing these patched boot.imgs I will have to wait for a recovery. Hopefully it won't by be too much longer. I just hope there will be a recovery.
Thanks

Continued error when flashing patched files.
I have tried 3 boot images from 3 different retail Canada firmwares. All 3 patched alright by magisk manager but when I try to fastboot flash boot magisk_patched.img I get the same error cannot open file. I must be doing something wrong. My phone's bootloader is unlocked so unless someone has a solution. I will definitely have to wait for a recovery. Hopefully soon!.
Thanks

Dumb question...when you are attempting to flash your patched boot image, is your phone in fastboot mode? Also, you may be able to extract your boot image via ADB. It's been a while since I've done it and am having trouble finding the proper commands, but you can try this:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Click to expand...
Click to collapse
It may or may not work. I hope it does but apologize if it does not.
Furthermore, you will likely have to wait quite a while for a custom recovery (TWRP). The G7 play has A/B partitions, which makes ROM building and recoveries very difficult. There is no separate "recovery" partition with A/B...the recovery is combined within the boot image. FYI - I have a Xiaomi A2 Lite that has A/B partitions. We still don't have a 100% working TWRP after 9 months. Custom ROMs have just been coming out slowly. I was able to root with Magisk using ABD commands though.
This link might provide clearer steps for installing Magisk.
Best of luck!

Yes, it was in fastboot mode. I will keep trying with your new intructions. Thanks for your help.

My mistake
I did not even have adb fastboot installed I was opening a command window out of the folder that was left over from uninstallation. I am about to try it again. It should work now. Stay tuned.

So far
Okay, so I installed adb fastboot and flashed the patched boot file from the RETCA firmware. I got this message " failed (boot a)" . So I tried the flashing the 2nd patched boot file that was from I think BWACA firmware. With this flash I got " not signed or corrupt" then the phone failed to start with bootloader log to confirm.
So I took the original unpatched boot.img from RETCA and flashed it. This fixed the phone so it would start fine making me believe that it's the right boot image but maybe the other firmware boot.img would have fixed the failing to start issue as well. So I think I need to pull the boot.img from the phone itself like you suggested. I am going to read some more and continue. I will figure it out. Any suggestions would be of great value.
Thanks.

Getting Closer
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks

jwreidmoto said:
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
Click to expand...
Click to collapse
A few posts back you said you flashed the stock RETCA boot image. If that's the case, then if you successfully pull the boot image from the phone, you are simply pulling the RETCA boot image you already flashed. It seems that the RETCA boot image is the correct one for you phone. I would start completely from scratch with that. To verify which build number you have, go to Settings>About Phone or ( Settings > About Phone > Software channel) and scroll down to Build Number. Match it up to one from link with all the firmware images.
The only other thing I can say is that you should read and completely understand what to do prior to doing it. I am sorry you are having difficulties with this. It really should not be so hard. As I don't have the phone I cannot be of much more assistance. However, once you figure it out, perhaps you can write a quick guide to help others.
EDIT: You should be rooted. SEE POSTS 10-13. Did you check for root?
EDIT 2: I'm assuming that since you unlocked the bootloader, when you reboot the phone the screen goes black and says "Bad Key", correct? That is normal for Moto phones.
2nd, after you root, when you reboot the phone, the screen should go black and say "N/A". Again that is normal for Moto phones.

I understand what you are saying I would also expect the N/A on the black screen that's when I knew I successfully rooted my old phone. I must have the right boot image if flashing it fixed the startup failure. I am going to start all over again and see.

Have to give up.
Tried and tried it's just not going to work. I think it's the patching because the boot file starts out as 32mb and only 18mb after being patched. Flashing has no effect on my phone even though it says 'okay' when I flash. I never get the N/A on boot unless there is a startup failure. Oh well have to live with ads among other anoyyances. My Moto g4 play is rooted I can use than in case a solution comes up. Thanks for all your help.

jwreidmoto said:
Oh well have to live with ads among other anoyyances.
Click to expand...
Click to collapse
DNS66 is your friend! I have used it on other unrooted phones. It was decent from what I remember. Good luck!
Sorry that root wasn't working.
EDIT - If you are up for a little more testing...I just found this. I don't remember if it's what I had to do for my Xiaomi or not, but it makes sense. (Further research - No I did not have to do this). Scroll down to method #2 and look for the part about A/B partitions:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
Edit #2 - I don't give up easily LOL
After any of your attempts to flash the patched_boot image, did you ever boot the phone and open the Magisk Manager app? Doing so should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.

Neither do I
I have been trying everything since we last talked. Just so you know the link labelled as "this" in your last response is not working. I always opened the magisk app after flashing to see if it was either installed or gave me the option to do a direct install unfortunately, it did not. I have magisk manager installed on my rooted Moto G4 plus and it gives me that option to do a direct install. Will definitely try your new info. Thanks so much for more help. I will let you know.

Still no luck
Without the link I got the jist of what you were saying by the quote boot_a boot_b I tried both consequtively and then tried it for ever possible retail Canada image still no luck. Thanks for your help. I don't know why it's so hard for this phone. I will keep researching.

I'm at about the same place where jwreidmoto is. I purchased my unlocked g7play from Best Buy. First I tried the files in the channel/RETUS folder, these all caused a bootloop. I then tried in the RETAIL folder... still no joy. None of the version numbers quite matched up, and none worked to restore the phone. I finally found a matching file in the AMZ folder, which I was able to use to get the phone to boot up again. So I used that boot.img file with magisk and when I flashed, it gave no errors, no indication anything failed. Unfortunately though, I do not have root access. I started over from scratch and did the process over with the AMZ boot img again, and again no errors, but no root. I've never rooted before, so I don't know if there's another part somewhere I missed, but I do feel like I was able to follow the directions on the g7 thread by mingkee, and performed the steps accurately. I supposed it's just the wrong boot img. The about phone says the software channel is US Retail, and the build number is PPY29.105-36. The RETUS folder only has PPY29.105-43 and RETAIL folder has five different zip files, but none were PPY29.105-36.

You are doing it right
You have not missed any steps. If the boot.img fixed the boot loop then it should be the right one. I had the same issue with a startup failure and fixed it with the RETCA boot.img so I am also using the right one also. I think it's an issue with the model of phone, this method just does not work. We might have to wait a while until someone comes up with a solutuon. I know it sucks.

Flashing back to stock Recovery. Help!

I'm having trouble getting stock recovery to flash using Fastboot. I've followed the correct method but continue getting an error. Bootloader is unlocked and I am rooted. OEM unlocking is checked in Dev options and so is USB debugging. What is the deal?

Not sure but try typing recovery ramdisk without caps.

christo31 said:
Not sure but try typing recovery ramdisk without caps.
Click to expand...
Click to collapse
That's how the file is named in the folder. I've tried renaming it and no matter how I do it, same results.

That's okay that's the files name but why are you typing the word "recovery_ramdisk" as RECOVERY_RAMDISK

christo31 said:
That's okay that's the files name but why are you typing the word "recovery_ramdisk" as RECOVERY_RAMDISK
Click to expand...
Click to collapse
Typing it that way because that's how the file is named. All caps. Even if I change it to no capital letters it still does it.

Are you in nougat or oreo?

christo31 said:
Are you in nougat or oreo?
Click to expand...
Click to collapse
I was on O but I resolved it. It was as the all caps causing the issue. I was typing exactly as the file was named but I guess it didn't like the all caps

MikeyLee said:
I was on O but I resolved it. It was as the all caps causing the issue. I was typing exactly as the file was named but I guess it didn't like the all caps
Click to expand...
Click to collapse
I got this second hand phone which is honor 7x
And I want to update it to the latest sowtfare but twrp was installed on this phone..
How to get over it??
I'm not familiar on how to and that...
All I want is to have a good performance on my phone
(It's a CHINA ROM) VERSION
I'm currently on android version 7.0 nougat
Emui 5.1
And my question is would it lock my network carrier from where I'm from currently in???

I was fiddling around now for two full days with my 7X. Trying to root the phone which has been upgraded to 9.1.0.162 is a mess. Finally back to stock but still unsatisfied.
There are several lessons learned and findings from those two days:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
Be aware! To go back to stock, do NOT use methods that flash kernel.img from older versions. Since boot.img and kernel.img are related, there might be a great chance to brick the phone.
Lessons learned: Huawei tries to avoid rooting the phone. Since I bought the phone (it is mine!) I am the one who decides what to do with it. Even thought the hardware is still good, I'm done with this messy firmware handling. So now it is time for new hardware from a different company. For the time being I will use it unrooted and accept ads in my news readers, but it will only be a matter of time.

Question [Solved] Stuck at bootloop after animation, unlocked bootloader...

So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?

banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).

Lughnasadh said:
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).
Click to expand...
Click to collapse
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.

banshee28 said:
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.
Click to expand...
Click to collapse
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.

banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).

Alekos said:
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).
Click to expand...
Click to collapse
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?

Tulsadiver said:
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.
Click to expand...
Click to collapse
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.

banshee28 said:
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?
Click to expand...
Click to collapse
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
banshee28 said:
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.
Click to expand...
Click to collapse
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.

roirraW edor ehT said:
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.
Click to expand...
Click to collapse
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.

banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!

roirraW edor ehT said:
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!
Click to expand...
Click to collapse
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?

banshee28 said:
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?
Click to expand...
Click to collapse
I wish I knew what else to suggest. About the only option left seems to be to use the Android Flash Tool including a full wipe. I would allow it to force flash all partitions and just untick the option to re-lock the bootloader so it stays unlocked.

banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.

Lughnasadh said:
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.
Click to expand...
Click to collapse
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.

banshee28 said:
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.
Click to expand...
Click to collapse
If you're bootloader is unlocked, just downloaded the full factory image (non ota), remove the " -w " command (which wipes data) in the flash-all.bat file and flash away. This will keep your data intact.
The flash tool should do the same thing but doing it manually, you can keep an eye on the progress in the command terminal window to make sure there are no errors.
The data and system partitions are different. Filling up your data partition won't cause corruption like this. They are completely separated partition tables.
Also you tried the flash tool and unchecked wipe and re-lock options?

I used the PixelFlahser app as well as the online official Android Flash Tool, with all those options unchecked, yes.
Both flashed with no errors although the phone never booted. I will try using ADB directly now and see if that helps!

So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
I have flashed just using the zip files before with no special unzipping and they have always worked fine.

banshee28 said:
So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
Click to expand...
Click to collapse
That is normal. That happens with every month's update.

Would installing a CUSTOM ROM or 13 Beta make any difference???

banshee28 said:
Would installing a CUSTOM ROM or 13 Beta make any difference???
Click to expand...
Click to collapse
No. Don't go down that road. If you can't get Stable working, then there's something deeper wrong. So you've tried the Android Flash Tool with all default options checked (to wipe, flash all partitions) except not to lock the bootloader? i.e. letting it wipe all your data?

Question Google pixel 6 pro bootloops after root

I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?

webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.

Stupid question also could be the wire your using and usb port

If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .

It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.

fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....

simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards

fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!