Hello all, I entered into recovery mode and got this warning today. http://i.imgur.com/CHya85E.jpg
For more info, I updated the other day to 4.1.2 and it removed my root access. Now, I was simply trying to remove the SuperSU app by going into recovery mode (don't know if it can be done there or not). Any help is extremely appreciated.
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
bobAbooE said:
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
Click to expand...
Click to collapse
Okay, thanks. Whenever I reboot my phone, there is text that comes up and says "custom" with an unlocked lock symbol. Could you point me in the right direction with this? Am I not able to go into recovery mode without the bootloader being unlocked?
I have the exact same issue. It came right after I upgraded Recovery to the latest Touch version. I am also on 4.1.2, but have been there a couple of weeks and have had no other problems. I don't believe I lost root with the upgrade.
If the boot loader has been relocked somehow, how can we fix it without being able to boot the phone? All attempts to boot including volume up/home/power, volume down/home/power, and home power just end up with the Verison message. It appears impossible to boot to recovery or even start the phone. I am lost.
See my thread called: “System software not authorized by Verizon Wireless has been found on your phone.” I also could not reboot the phone to fix it.
Some great info was posted there that enabled me to escape from the Verizon prison
Related
Yesterday I got the update on my S3. I am rooted and bootloader unlocked with EZ apps. when I got the update it went into EZ recovery and thinking maybe I could get the update I tried to install it. It looked like alot of it installed but it did kick me out in the end, or gave me an error or something. Anyway when I went to see if the update had gone through under info I saw I was on G1 still not G7 and it said I had an error 401. So I didn't think it had gone through. I tried to change my phone to CM-10 nightlies by invisiblek just now and followed all the steps in the tutorial and when I did my final reboot I get a exclamation point in a sign and a quote, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. I know there is a way to load to easy recovery and I will find that and go back to where I was but I thought I should post this as I have been researching quite a bit and hadn't seen this happen to anyone else. Maybe I missed it but just in case maybe this will help someone else. If someone could respond on how to boot into ez recovery I will do that or if someone has a different idea on what I should do I'm open to suggestions. Thanks in advance...
OK, read something about download mode so tried that. Power-Volume down-Home at same time. Screen came up asking if I wanted to install a custom OS and warning that a custom OS could be dangerous. Same exclamation point thing as not authorized so maybe another Verizon message? Anyway I said yes and it went to Downloading... screen and says do not turn off target. In the upper left hand corner it says Odin mode, product name: SCH-I535, Custom binaryDownload: no, Current Binary: Samsung official, System status: Official, Qualcomm secureboot: enable...
I'm guessing this is how you get into ODIN but as I have never done that and don't have the phone connected to my computer now I'm guessing it's safe to shut off my phone even though it says Do not turn off target!!!
Anyone know how I get to the bootloader? I'm guessing I can load my saved boot from there...UGH!
Tried shutting down phone but it won't. Do I have to remove battery?
Got Odin open but since my backup is a nandroid backup don't see how I can get to it through ODIN. I'm really stuck. Haven't pulled the battery yet as I was hoping someone would chime in here but guess I will have to soon. THere must be a way to get to the bootloader screen as why else would you do a nandroid backup? I also did a full backup on Titanium Backup bt again how do I get there?
OK loaded root66 through odin...phone restored...now what do i need to do to get cm10 on here....
Went and looked at phone under settings and that build was different now and the 401 error was gone so I installed CM10 and it's loading now! Yeah for me
Odin would be your best bet, if you can do that you should be golden, as to recovery ,I believe it's hold volume down, home then power button hold till you feel the vibration then release that should take you to either recovery or download mode.to Odin you need download mode.hope this helps a little
Sent from my SCH-I535 using xda premium
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.
I was attempting a network unlock on this device (not frp) as i actually own this phone. i managed to get the combination file flashed through odin and i obtained a network unlock code that worked just fine. i cannot get the device to boot into download mode for the life of me. i can get the device into recovery but not sure where to go from there. i've tried everything. i have the proper firmware downloaded but i can't flash it. odin picks up the device after it has booted into the combination binary. and upon selecting download mode or upload mode from within the UI it asks for a pin then does nothing. i tried straight talk and samsung technical support and they were absolutely no help. please help.
me too
oi0i0io said:
I was attempting a network unlock on this device (not frp) as i actually own this phone. i managed to get the combination file flashed through odin and i obtained a network unlock code that worked just fine. i cannot get the device to boot into download mode for the life of me. i can get the device into recovery but not sure where to go from there. i've tried everything. i have the proper firmware downloaded but i can't flash it. odin picks up the device after it has booted into the combination binary. and upon selecting download mode or upload mode from within the UI it asks for a pin then does nothing. i tried straight talk and samsung technical support and they were absolutely no help. please help.
Click to expand...
Click to collapse
I have been round and round with this device... I found that from recovery boot to bootloader takes it straight to download but not odin mode, phrase saying do not turn off target...wtf.. also at times, not always for some reason, holding ALL buttons to power up takes me in to dwnld mode... Im at the point I am willing to brick this unit just trying to get past frp.
this is running pie, im next goiung to attempt dwngrdng to 8.0 to try and bypass frp... It is my only available device and I am cvurrently without phone as apparently my moto e5 can not take stairs one at atime.. good luck.
remove sim...reboot to bootloader from recovery
sory, you prolly alreadt did this , im new here, just totally liking seeing someone elese hating the device atm... lol
I've had some troubles trying to root my new phone, as above mentioned in the title. First off, when I try to boot into recovery mode via "adb reboot recovery" command, the phone restarts into a black screen with a dead android with a red triangle and 'no command' below. I haven't yet attempted to actually root my brand new phone yet because I wanted to backup my entire phone (stock ROM/Firmware, etc,.). I am afraid I will end up bricking it and have no ways to back it up. I had the same issue with my older LG G5 with the dead android. Why is there no recovery? And why have I been able to easily backup and root older phones from 2012 from LG but not my newer models?
It's really frustrating.
BTW, I posted this thread in the wrong area and I cannot find an option to delete it or move it to the Developers Section, my bad.
big bad brad 31 said:
I've had some troubles trying to root my new phone, as above mentioned in the title. First off, when I try to boot into recovery mode via "adb reboot recovery" command, the phone restarts into a black screen with a dead android with a red triangle and 'no command' below. I haven't yet attempted to actually root my brand new phone yet because I wanted to backup my entire phone (stock ROM/Firmware, etc,.). I am afraid I will end up bricking it and have no ways to back it up. I had the same issue with my older LG G5 with the dead android. Why is there no recovery? And why have I been able to easily backup and root older phones from 2012 from LG but not my newer models?
It's really frustrating.
BTW, I posted this thread in the wrong area and I cannot find an option to delete it or move it to the Developers Section, my bad.
Click to expand...
Click to collapse
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.
edwaine said:
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.
Click to expand...
Click to collapse
HI any recent discoveries???
helppppp
saad6 said:
HI any recent discoveries???
Click to expand...
Click to collapse
hello. can you backup g7 one phone system for me？my phone doesn't work. case I flash wrong firmware. so i need system backup to write in my phone. help me please .please save my phone s life.
edwaine said:
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.
Click to expand...
Click to collapse
Have you tried the simplest 'fastboot oem unlock' command (having checked the Allow OEM Unlock option in Developer's option; most Android One devices' bootloader can be unlocked this way)?
If it doesn't work, how about the below method, which I believe is the 'official' LG bootloader unlock:
https://www.getdroidtips.com/unlock-bootloader-lg-g7-thinq/
I don't own the LG G7 One, am hoping to, if the bootloader can be unlocked and Magisk be installed.
All the best
potatohead said:
Have you tried the simplest 'fastboot oem unlock' command (having checked the Allow OEM Unlock option in Developer's option; most Android One devices' bootloader can be unlocked this way)?
If it doesn't work, how about the below method, which I believe is the 'official' LG bootloader unlock:
https://www.getdroidtips.com/unlock-bootloader-lg-g7-thinq/
I don't own the LG G7 One, am hoping to, if the bootloader can be unlocked and Magisk be installed.
All the best
Click to expand...
Click to collapse
Done all of that. Unfortunately, the "adb reboot bootloader" command does not take it to the bootloader screen. It just simply restarted the device.