just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked
What version g pro you have?
Sent from my LG-E980 using Tapatalk 2
att version
e980
Clutchz said:
att version
e980
Click to expand...
Click to collapse
Try posting your issue in the actual thread in original android development
Sent from my LG-E980 using Tapatalk 2
Only your recovery and possibly boot partitions are touched, so worst case you can always get to download mode. However if the phone won't turn on at all its something not directly related. What happened before you rebooted into this state?
Sent from my LG-LS970 using xda app-developers app
i was doing the freegee thing and it had finished i went to home and hit reboot and nothing it stayed there
FreeGee has been updated and I unlocked my phone without any issues.
Clutchz said:
just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked
Click to expand...
Click to collapse
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
wahida76 said:
FreeGee has been updated and I unlocked my phone without any issues.
Click to expand...
Click to collapse
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.
the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG
lessthanzach said:
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.
Click to expand...
Click to collapse
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Clutchz said:
the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG
Click to expand...
Click to collapse
Your phone hard bricked and flashing might work
wahida76 said:
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Your phone hard bricked and flashing might work
Click to expand...
Click to collapse
the flash tools dont detect the phone
Clutchz said:
the flash tools dont detect the phone
Click to expand...
Click to collapse
I am really sorry to say this but if that is the case then your hard brick can't be fixed your option is warranty.
oh well i'll go to att tomorrow thanks guys
Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
If you bought the phone within the last 14 days then you can return it if not you can call at&t and speak to warranty and they will send you a warranty replacement your other option is to ask if they have a local warranty center they can try to flash it or exchange it.
Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
Are you sure you were putting it into download mode? You take out the battery. Then put battery back in the phone. THen I believe you hold the volume down key and plug the phone into the computer. Then LGNPST should recognize the phone after you change the COM port to I believe 41 or 42
Edit: You hold BOTH volume keys while plugging the phone into the computer. It needs to be completely off when you do this.
Edit 2: Here's the guide : http://forum.xda-developers.com/showthread.php?t=2302660
Switch it under device manager to COM port 41. Now flash tools should recognize it.
I'm honestly bummed that I'm now going to have to re-setup everything again. I just had to flash my phone 2 weeks ago to get rid of 2nd Init recovery to install the value pack. Now I get to do it again, then run the update, then re-root, and put my 200+ apps back on, lol. FML. I guess this just isn't the phone the tinker with. Never had any of these issues on my S1, S2, S3, HTC One, One X, Note, etc. Oh well.
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2
turilo said:
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
no dice tried it on both even xp i'm gonna give up on it i'll return it its easier
Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
Hey do you remember what version of freegee you installed? I think somehow you might have gotten version 1.0.6 instead of 1.1.0. Ive been through everything and the only thing that could have bricked you was using and older version of freegee. I didn't post on xda till Google showed the updated 1.1.0 version was live but maybe somehow you got an older on?
Sent from my LG-LS970 using xda app-developers app
Bootloader NOT UNLOCKED
I was wrong the bootloader is still Locked the developer of the App corrected his app info and this shows that.
http://forum.xda-developers.com/showpost.php?p=43813711&postcount=14
Related
I bricked my phone, its the t-mobile version... Does anyone know what I can do to restore it back to stock?
Flash stock using Odin
what is odin??
Daviddc1144 said:
what is odin??
Click to expand...
Click to collapse
O.O say what? You need to do some reading bud.
Odin is a program from Samsung that allows the loading of img files to your phone.
Sent from my ADR6425LVW using xda app-developers app
Go to youtube search this "how to unroot samsung galaxy s3 (tmobile). just follow the video
---------- Post added at 05:00 AM ---------- Previous post was at 04:57 AM ----------
BTW can you get it onto download mode?
You shouldn't be flashing things if you don't even know the basics. You should do research before you get all over excited and brick.
Sent from my SPH-L710 using xda app-developers app
Brick? Siyah Kernel problem
So I just flashed the latest Siyah kernel to my sprint samsung galaxy SIII. After choosing it from the internal storage on CWM my phone turned off and will not turn back on. Even when I plug it in it just stays dark! Any suggestions of the $(#* is going on? Anyone else with this problem and if so how the hell do I fix it when I cannot even get it to boot into recovery?
Try to get it into download mode and flash stock rom using odin
mjhay19 said:
Try to get it into download mode and flash stock rom using odin
Click to expand...
Click to collapse
I wish I could the damn thing will not turn on at all. No recovery mode no nothing and it will not charge when I place it into a charger.
Nice thread jacking.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm sorry, but if you bricked your phone and are not familiar with Odin you really need to do some reading/research before playing with root or system files. There's plenty of information all around this site applicable to your device. And do everything manually, you'll learn much quicker.
Sent from my Galaxy Nexus using xda app-developers app
brettrermcfetter said:
I wish I could the damn thing will not turn on at all. No recovery mode no nothing and it will not charge when I place it into a charger.
Click to expand...
Click to collapse
Well thats good news then. Just go to the store tell them phone died. You have 1 year warranty. They will swap it
Willanhanyard said:
Nice thread jacking.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I thought the thread was about bricked SIII right? If there is somewhere else I need to go just let mem know. I just need some help.
brettrermcfetter said:
I thought the thread was about bricked SIII right? If there is somewhere else I need to go just let mem know. I just need some help.
Click to expand...
Click to collapse
Pull the battery from your phone and let it sit for a couple hours. Then put it back in and press volume down + home + power to get into download mode. From there you can use Odin to install the stock firmware. If after that you can't get into download mode, you have a hard brick. If you take it in make sure you pull you external SD before hand. Found out the hard way that tmo is not a fan of rooting.
Sent from my SPH-L710 using Tapatalk 2
damn mate I hope you can fix it, or get it replaced on warranty
holy **** im tired of seeing this ****...
And to think some ass challanged me when I said I saw where verizon was coming from in locking the bootloader. This is it right here. These phones brick easy as ****, read b4 u flash. Or go get a galaxy nexus. That being said, plug it in the computer. If device manager shows QHSUSB DLOAD there's your confirmation. U have a paperweight. Best of luck please read n b careful next time and spread the word
brettrermcfetter said:
So I just flashed the latest Siyah kernel to my sprint samsung galaxy SIII. After choosing it from the internal storage on CWM my phone turned off and will not turn back on. Even when I plug it in it just stays dark! Any suggestions of the $(#* is going on? Anyone else with this problem and if so how the hell do I fix it when I cannot even get it to boot into recovery?
Click to expand...
Click to collapse
You are hard bricked, unless you can get into download mode.
This company unbricked my phone and they did it quick. The usbjig will probably not work, I tried.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii/
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
billard412 said:
And to think some ass challanged me when I said I saw where verizon was coming from in locking the bootloader. This is it right here. These phones brick easy as ****, read b4 u flash. Or go get a galaxy nexus. That being said, plug it in the computer. If device manager shows QHSUSB DLOAD there's your confirmation. U have a paperweight. Best of luck please read n b careful next time and spread the word
Click to expand...
Click to collapse
This IS the correct answer...good luck
Daviddc1144 said:
what is odin??
Click to expand...
Click to collapse
The ruler of Asgard. Read up on your Norse mythology =)
---------- Post added at 05:33 PM ---------- Previous post was at 05:27 PM ----------
shane6374 said:
Pull the battery from your phone and let it sit for a couple hours. Then put it back in and press volume down + home + power to get into download mode. From there you can use Odin to install the stock firmware. If after that you can't get into download mode, you have a hard brick. If you take it in make sure you pull you external SD before hand. Found out the hard way that tmo is not a fan of rooting.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I don't mean to be an ass but you are "the problem". If you were willing to play with fire then you should get burned. I don't think warranty should cover your misfortunes. Why should X company pay for your gambling? You know I'm right about this...
If you (not specifically) really have a brick then you should just pay for a jtag servicer to get it back in line. On your own dime.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app[/QUOTE]
if you are hard bricked and can not access the download mode for Odin, I would recommend the jig for few bucks on Amazon.
brettrermcfetter said:
I wish I could the damn thing will not turn on at all. No recovery mode no nothing and it will not charge when I place it into a charger.
Click to expand...
Click to collapse
Hardbricked is what ya have...paper weight. No download mode...no worky.
Return it or use a Jtag sevice.
So basically I can boot up the phone but it only shows the LG Logo and its stuck there. It can turn on but it cant go to download mode. The phone is recognized as a device but its unspecified. Help me with this ASAP
xmagiicsx said:
So basically I can boot up the phone but it only shows the LG Logo and its stuck there. It can turn on but it cant go to download mode. The phone is recognized as a device but its unspecified. Help me with this ASAP
Click to expand...
Click to collapse
what happens when you try to enter download mode
nothing just stays at the lg logo
I mean the phone boots to LG splash screen and it stops. No download mode but there is hardware key settings. I tried adb but no luck. It says device is unauthorized. The usb is LG adb interface but mtp is not working(obviously). Can someone help me because I don't want to RMA'd my phone again -.-
What did you exactly do to get in this position?
Sent from my LG-D851 using Tapatalk
I installed PAC ROM for D851(Yes I'm using the correct model) and cleared system and cache. Something went wrong and now I cant boot up my phone.
I still have my nandroid backup on my sd but I dont know how am I going to restore into this phone.
I must been ridiculously stupid that I missed something. So I have root, no download mode, no factory reset, a nandroid backup, an usb that says its in ADB Interface, adb not working(Phone unrecognized or phone offline), and a damn stuck LG Splash Screen. My day is going to be in a nutshell........
I know I sound annoying right now but I tried everything but it seems not to be working. Can someone help me with adb because the phone is recognized but not authorized. I dont even know how to even flash or restore now through anything. Please I need your help. Its booting to LG Splash Screen only but no download mode. Calling all senpais and developers to help me! Please reply ASAP D:
Sent from my Nexus 4 using XDA Free mobile app
xmagiicsx said:
I know I sound annoying right now but I tried everything but it seems not to be working. Can someone help me with adb because the phone is recognized but not authorized. I dont even know how to even flash or restore now through anything. Please I need your help. Its booting to LG Splash Screen only but no download mode. Calling all senpais and developers to help me! Please reply ASAP D:
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Okay update your Android sdk you can Google that and find that and use the New adb in that package. That'll make your device come online. Then go to the Pac man forum and flash the boot.img through adb. Then it should turn on.
xmagiicsx said:
I know I sound annoying right now but I tried everything but it seems not to be working. Can someone help me with adb because the phone is recognized but not authorized. I dont even know how to even flash or restore now through anything. Please I need your help. Its booting to LG Splash Screen only but no download mode. Calling all senpais and developers to help me! Please reply ASAP D:
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
you have one opportunity only in recovery mode:
Remove your battery and just enter recovery mode with the power and volume buttons, then go recover your system with a another worked flash rom or your personal nand backup.
Tried that and it didn't work. I think LG G2 had the same problem and someone did it with universal adb driver and some adb. Going to try that when I get home. In the mean time, can someone confirm this?
Edit: Oh you mean to only take the battery out without putting it back in. Going to try that when I get home but I think it only shows the no battery inserted screen
Sent from my Nexus 4 using XDA Free mobile app
jm2k7 said:
you have one opportunity only in recovery mode:
Remove your battery and just enter recovery mode with the power and volume buttons, then go recover your system with a another worked flash rom or your personal nand backup.
Click to expand...
Click to collapse
It just sounds like he didn't flash the boot.img no biggie. If you have an outdated adb from the Android Sdk it'll say device online. So it is an easy fix. I've had this happen before when I had an HTC one x.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
xmagiicsx said:
Tried that and it didn't work. I think LG G2 had the same problem and someone did it with universal adb driver and some adb. Going to try that when I get home. In the mean time, can someone confirm this?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
You've already updated the sdk?
Downloaded but didn't install it due to school in the morning -.- and two hours of sleep. After I get out of school and work I'll head to my computer and install it ;D
Sent from my Nexus 4 using XDA Free mobile app
xmagiicsx said:
Downloaded but didn't install it due to school in the morning -.- and two hours of sleep. After I get out of school and work I'll head to my computer and install it ;D
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Ya it won't boot without the boot.img
kdouvia said:
It just sounds like he didn't flash the boot.img no biggie. If you have an outdated adb from the Android Sdk it'll say device online. So it is an easy fix. I've had this happen before when I had an HTC one x.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
You've already updated the sdk?
Click to expand...
Click to collapse
Can you PM me the step by step guide lol. I feel I'm derping right now with the lack of sleep
Sent from my Nexus 4 using XDA Free mobile app
xmagiicsx said:
Can you PM me the step by step guide lol. I feel I'm derping right now with the lack of sleep
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Yes at my lunch
Yes! Thank you so much. I hope Ill be put my phone online or authorized . Are you positive that this will work?
Sent from my Nexus 4 using XDA Free mobile app
I'm about to cry and whine D:
BUMP
Someone help me!!!! I can't even adb, no download mode, no hard reset!
EDIT 1: HOW DO YOU EVEN BOOT IT TO TWRP I NEED ANSWERS PLEASE!!!!
Sent from my Nexus 4 using XDA Free mobile app
Hey guys ,
I'm new to here. Searched everywhere for this issue but haven't seen any real solutions. Got an LG G3 here. Less than A month old. Owner left it on doing some app updates overnight and she woke up the next morning and it could not be turned on. She dropped it off at a fixit guy who said he tried several firmwares (even the official LG one that he said he had to pay close to 100us for :/ ) and still nothing. She was really pissed as she bought this brand new wth only 14days warranty which is up and it's basically bricked. I told her I'd have a go with it but I was unable o go into download or recovery mode. Windows detects it as a Qualcomm Usb loader of some sort.
I was wondering if there's any way to manually format or recover this using Linux or Mac OS. I have all three OS so any help I can get to get this booted up and running would be of great help. I'll donate to the one who led me to get this stupid thing working again. Thanks! ?
vivsterist said:
Hey guys ,
I'm new to here. Searched everywhere for this issue but haven't seen any real solutions. Got an LG G3 here. Less than A month old. Owner left it on doing some app updates overnight and she woke up the next morning and it could not be turned on. She dropped it off at a fixit guy who said he tried several firmwares (even the official LG one that he said he had to pay close to 100us for :/ ) and still nothing. She was really pissed as she bought this brand new wth only 14days warranty which is up and it's basically bricked. I told her I'd have a go with it but I was unable o go into download or recovery mode. Windows detects it as a Qualcomm Usb loader of some sort.
I was wondering if there's any way to manually format or recover this using Linux or Mac OS. I have all three OS so any help I can get to get this booted up and running would be of great help. I'll donate to the one who led me to get this stupid thing working again. Thanks! ?
Click to expand...
Click to collapse
1st thing pull the battery and put back in and hold power vol up for download mode
jaythenut said:
1st thing pull the battery and put back in and hold power vol up for download mode
Click to expand...
Click to collapse
Yup. Tried it before. Tried it again. Nothing. What's next ?
Update: somehow windows doesn't detect my phone as Qualcomm anymore. It's seen as 'unknown device'
Isn't the phone still under warranty? I had the same problem and used the manufacturer warranty (1 year) and you only to pay shipping
vivsterist said:
Yup. Tried it before. Tried it again. Nothing. What's next ?
Click to expand...
Click to collapse
G3 download mode instructions here www.ninjaromeo.com/download-mode-lg-g3/
verify g3 variant and do not flash firmware made for another variant, else brick.
hwong96 said:
G3 download mode instructions here www.ninjaromeo.com/download-mode-lg-g3/
Click to expand...
Click to collapse
Not going to work. Motherboard is corrupted or dead
xmagiicsx said:
Isn't the phone still under warranty? I had the same problem and used the manufacturer warranty (1 year) and you only to pay shipping
Click to expand...
Click to collapse
nope. no warranty as i'm no longer in the US.
xmagiicsx said:
Not going to work. Motherboard is corrupted or dead
Click to expand...
Click to collapse
ANy reasons for this? QPST sees my phone in Download Mode on COM19. But it lists it under Phone as "Q/QCP-XXX. ESN, Phone number and Banner all state *Download*
I've read that it's really hard to kill an LG phone. 99% of the times there is a solution.. just to find it.
vivsterist said:
ANy reasons for this? QPST sees my phone in Download Mode on COM19. But it lists it under Phone as "Q/QCP-XXX. ESN, Phone number and Banner all state *Download*
I've read that it's really hard to kill an LG phone. 99% of the times there is a solution.. just to find it.
Click to expand...
Click to collapse
Should be changed to COM41.
vivsterist said:
ANy reasons for this? QPST sees my phone in Download Mode on COM19. But it lists it under Phone as "Q/QCP-XXX. ESN, Phone number and Banner all state *Download*
Ive read that its really hard to kill an LG phone. 99% of the times there is a solution.. just to find it.
Click to expand...
Click to collapse
Well QPST still recognizes the phone as a device but there are no data that can fix the problem on the motherboard. Tried to used the kdz file and it recognized the phone but there was no data like the modem or the IMEI to recognize it. As a result the only way you can fix it if somehow you get all files from modem to boot imgs. Tried that for two weeks straight and no solution. So apparently gave up and gave it to LG. There are no solutions at this moment
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
hwong96 said:
Should be changed to COM41.
Click to expand...
Click to collapse
Tot and .dll wouldnt work because IMEI and s/w is lost which result in a fail download
hwong96 said:
Should be changed to COM41.
Click to expand...
Click to collapse
Changed to com 41. what's next?
vivsterist said:
Changed to com 41. whats next?
Click to expand...
Click to collapse
Telling you LG Flash Tools isn't going to work(both kdz and tot
xmagiicsx said:
Well QPST still recognizes the phone as a device but there are no data that can fix the problem on the motherboard. Tried to used the kdz file and it recognized the phone but there was no data like the modem or the IMEI to recognize it. As a result the only way you can fix it if somehow you get all files from modem to boot imgs. Tried that for two weeks straight and no solution. So apparently gave up and gave it to LG. There are no solutions at this moment
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Tot and .dll wouldnt work because IMEI and s/w is lost which result in a fail download
Click to expand...
Click to collapse
well that's depressing..
imgur.com/OnIukxU
Sorry but I tried all of the solutions
---------- Post added at 02:19 PM ---------- Previous post was at 02:16 PM ----------
http://forum.xda-developers.com/tmobile-lg-g3/help/pleae-helpany-to-boot-lg-g3-hardbrick-t2878203
My posts from 2 months ago. Sorry, its not going to work
I have been up and down all the sites and recovery methods.
ISSUE:
In an attempt to root my Zenfone 2 (2.19.40.22 Lollipop) the tool I was using seemed to get stuck looking for my device. This was after installing a fastboot, or an attempt I believe. After a minute or so I noticed the phone screen was constantly showing the USB Logo.
I can turn on my phone and use it no problem. HOWEVER, I cannot POWER + VOL UP, to enter the bootloader. It just goes back to that USB Logo with the White Bar under it. And I have to power off and ON my phone again to get back to normal operation.
As you can imagine this makes it rather difficult to flash anything or use the ADB Tools whatsoever. Is there anything I can do to get that back, or am I doomed with a phone that can never be rooted?
[The tool that started this whole issue was the TWRPRecovery-Install]
Twrp tool only installs twrp recovery which you need an unlocked boot loader to install, so it should have never been used, can you use adb from the phone in normal operation? Can you get into recovery at all? Sometimes you can boot to recovery from adb shell when phone is in normal boot. Most of the solutions I can think of requires root but if you figure out how to get to recovery you can sideload a full update file to restore everything
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
And I am not sure if it will work now, but there is a one click root tool for this phone you could try it, but if you have an unusable bootloader it may not work, let me do some research for other options, may not find anything but we'll see
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:40 PM ----------
Start here
https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2
Sent from my ASUS_Z00AD using Tapatalk
Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.
JetPKFR said:
Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.
Click to expand...
Click to collapse
That is generally considered bricked... Only ASUS can fix for now....
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
Go into the bootloader and on a PC with adb run "fastboot flashing unlock" and see what happens. I don't think you need adb enabled to do it but I could be wrong so just try
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
@piotrus22 another option would be to go into recovery and adb sideload the latest ota package from google.
Can you side load with debugging off?
Also have you factory reset from recovery?
DR3W5K1 said:
Can you side load with debugging off?
Also have you factory reset from recovery?
Click to expand...
Click to collapse
Not sure if you can but it wouldn't hurt to try. That night work too
Try to sideload the latest ota image.
Sent from my Pixel C using Tapatalk
piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
im having a similar issue. my phone just started to bootloop randomly yesterday, i tried to flash stock and once i get to the setup screen it shuts down and reboots...
thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found
piotrus22 said:
thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found
Click to expand...
Click to collapse
What were you trying to do to get it like that?
Veid71 said:
What were you trying to do to get it like that?
Click to expand...
Click to collapse
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....
piotrus22 said:
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....
Click to expand...
Click to collapse
Have you tried a factory reset?
DR3W5K1 said:
Have you tried a factory reset?
Click to expand...
Click to collapse
yes of course -
piotrus22 said:
yes of course -
Click to expand...
Click to collapse
Well unfortunately you're out of things to try.
If your phone happens to be a 128gb model this is actually quite common.
---------- Post added at 12:25 PM ---------- Previous post was at 12:11 PM ----------
Further confirmation of problems with some 128 units.
https://support.google.com/pixelphone/forum/AAAAb4-OgUsZ1zs71de3Io/?hl=by
I hope your phone is under warranty because Google won't do crap if it isn't. I'm a proud owner of a POS 128GB brick thanks to their junk they sell.
Sent from my [device_name] using XDA-Developers Legacy app