Your device software cannot be checked for corruption......

cirenj

Member
Mar 20, 2011
41
5
0
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
 

TonikJDK

Senior Member
Dec 9, 2012
2,620
1,301
183
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
I am assuming your boot loader is unlocked.

Power it down. Then hold power and volume down to boot into recovery mode. Download the latest factory image. Then use the flashall bat file to flash it back.

Edit the flashall bat file to remove the -w so you save your data and apps and flash it.
 

cirenj

Member
Mar 20, 2011
41
5
0
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
 

3aucla1r3

Senior Member
Dec 11, 2013
137
62
0
South Carolina
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
With the bootloader unlocked you can always get out of these bootloops but it a lot of times requires flashing a new factory image. I have gotten out of bootloops by going back into twrp and doing the factory reset but of course you lose all your data with that. It just depends on what sent you into the bootloop but they can all be fixed by flashing a new factory image. So far, I've never hard bricked a device but I've been in many bootloops!

PS: if you're on the May edition of the OS, then you need the verified boot signer to install twrp or root.
 
Last edited:

3aucla1r3

Senior Member
Dec 11, 2013
137
62
0
South Carolina
It went into the bootloop trying to flash TWRP...lol
If you're on May, download the verified boot signer, go into bootloader mode, flash the twrp.img so you get to twrp again and reflash the twrp.zip along with the verified boot signer. If you're on June, then that's not the problem but if you have mismatched slots (a/b not the same) you can get into these problems as well.
 

cirenj

Member
Mar 20, 2011
41
5
0
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
 

3aucla1r3

Senior Member
Dec 11, 2013
137
62
0
South Carolina
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
This one is definitely different than my nexus 6 was, the 2 slots, etc. But after you flash it with June, you don't need the boot signer. You've seen some guides about the temp twrp.img first from adb/fastboot, then the permanent twrp.zip next flashed from within the temporary twrp, SU 2.82 is what I install next from twrp. You can find the guides. Having the June factory image on both slots can avoid a lot of problems (at least it did for me).
 

jhs39

Senior Member
Oct 8, 2015
2,486
717
0
Chicago
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
 

Master Cylinder

Senior Member
Oct 31, 2013
1,253
531
143
Albuquerque
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
Does anyone know a trick to disable that notification?
 

fiverings

Senior Member
Oct 2, 2014
240
34
48
It went into the bootloop trying to flash TWRP...lol
I've found that if you fastboot reboot bootloader, then fastboot boot twrp.img.
Then flash twrp installer zip in twrp and then boot into system, I should work. Then you can download Magisk zip into phone and flash it in twrp. You will have root as super su doesn't work anymore. I'm on a Pixel XL with January 8.1 update. Good luck
 

toti23

Member
Oct 24, 2015
9
0
0
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?

Mod edit Google Translate :
Hi, I happen to the same thing but I want to root it, someone has a tutorial to continue with the procedure, because the sign says that it is only unlocked and not rooted, no?
 
Last edited by a moderator:

Nevermindthelabel

Senior Member
Aug 19, 2014
558
372
93
Phoenix
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?
inglés solo en el foro
English only on the forum.

The message is because the bootloader is unlocked, not because it is rooted. Fastboot boot or flash twrp and flash magisk if you want it rooted