Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.
You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.
So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.
sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.
Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com
#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .
Related
Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
s_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=192 vcore=11 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Aug 5 2013 10:54:27] ver:f07e92b-dirty
OTP s0x000000FF lkg curr=192 mAnd_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v94 loaded from 0x00174000
[SHOWLOGO] stopped
Boot normal GTV image
fts: record v95 commited @ 0x00178000
Uncompressing Linux... done, booting the kernel.
Click to expand...
Click to collapse
bse10093 said:
Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
Click to expand...
Click to collapse
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official signed USB image.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Here is the link for the Official 13300 update. http://dl.google.com/googletv-eurek....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
tried recovery, but no luck
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
ddggttff3 said:
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official update.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Click to expand...
Click to collapse
Have you tried doing a factory reset on the chromecast? by button, or the setup application?
bse10093 said:
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
Click to expand...
Click to collapse
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
factory default
ddggttff3 said:
Have you tried doing a factory reset on the chromecast? by button, or the setup application?
Click to expand...
Click to collapse
Yes I've tried it and it runs without errors, reboots however when back in normal boot mode it still shows the black screen instead of chromecast desktop.
P.S. maybe I should mention that the chromecast ad-hoc network also comes up, unfortunately though that doesn't seem to help.
doesn't seem to activate usb key
tvall said:
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
Click to expand...
Click to collapse
I tried renaming, however when starting recovery with the usb key containing the official 13300 renamed as ota.zip, it never has any disk activity on the usb key, however I can verify that it can read the key from the bootloader as it detect the key, but fails the signing step
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
plotgee said:
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
Click to expand...
Click to collapse
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
projectisaac said:
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
Click to expand...
Click to collapse
I have the vivid , and yes it says *** locked ***
I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..
Thanks, I hope this works.
Fingers crossed here. Let me know what happens.
Sent from my Vivid 4G using xda app-developers app
Alright! So apparently this solution worked (got a PM from OP)!
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
pleckers87 said:
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
Click to expand...
Click to collapse
Tell details. What's your phone model?
Do you have download mode?
What's the error you getting?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Model is D950. Originally had 4.4.x. I can enter download mode no problem. I don't have adb commands. When I type adb devices, it shows a blank space.
LG flash tools gives me a "device model different. Check device model". Mind you, tried flashing the stock TOT with the d950dll and also tried the generic dll that G2 users were using. I'll post a pic in a little bit of the error I get....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
[/URL][/IMG]
pleckers87 said:
[/URL][/IMG]
Click to expand...
Click to collapse
Lols..
How did you bricked your set? I am just curious to find out..
What on screen If You normal start?
Try to connect your Phone with PC in normal mode.
Whats the Windows version?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Alright, here goes...
Started when the volume buttons stopped registering pushes. I replaced the clickers (for lack of better term) but problem did not go away. I then attempted a backup restore via TWRP but Flex powered down (battery level was above 90% prior to restore). I then connected to computer (then running W8) and it showed up as qual_blahblah. I d/l factory partitions and followed a guide to fix partitions...well the guide did not work out in my favor because after reboot, device would show LG splash, go black and show LG splash again, followed by an android guy on his back with the yellow triangle above him. I will note that that is the only thing (android guy on back) I see when I try a normal boot up/power on.
I am running W10 on my PC currently.
First of all why did you try to restore your partitions if you had twrp and a saved backup. That should have solved any issue there. The volume buttons going bad wouldn't have been a software thing unless you used some mod that could have disabled them. Then that can be fixed via factory reset. Or restore backup.
OK so to fix your FLEX just plug it up in download mode and to your PC with lg's PC suite software installed on your PC. Not sure if windows 10 is supported for PC suite or not or if this works on win 10. May have to try someone else's pc. And make sure you have internet service on that PC.
At the top of the PC suite program window there are several options to choose from. Not sure off the top of my head what they're called but there is an option some where up there to restore from bad update or recover from bad update. Something like that. I wrote a tutorial about a year ago on how to do this. It should be in the general section. Try that out.
Back to the volume buttons or clickers as you call them. The ones that you replaced them with may be defective. If you bought some cheap Chinese BS then it could possibly be for be made as more of a universal off brand made to work in a lot of lg's but for some reason not compatible with the FLEX. I've bought a new sim card /sd card ribbon for an asus zenfone 2 before that was that very issue. Speaking from experience.....spend the extra dough and get the quality parts not Chinese sweat shop BS.
And good luck
Maybe you guys could help me. I'm at a loss and customer support told me to turn it off and turn it back on. I bought the Razer Phone 2 on December 27th. Around mid to late February, I had an instance where the phone crashed and was black screen, but the vibration reacted to me touching/pressing the power button. Hard resetting the phone allowed it to go back to normal. It got more frequently and more annoying, and it got to the point where multiple resets wouldn't fix it. Several times I got a screen telling me it couldn't load the android system(First image). After several instances of that screen, I tried to wipe the phone and reset it to factory, and now it's just an expensive paperweight. I can press Power+Volume Up to get to android recovery, but choosing to start up does nothing, reboot to bootloader does nothing, and pretty much everything else is useless.
Like I said, I contacted customer support, and their response was to tell me to wipe the phone and try again, which does nothing. After I said it didn't work, they said that was the best they could come up with, and that I would have to send it in and pay the costs as it was out of warranty, even though it's not even 6 months old. I tried finding a fix for it on google, and saw someone posted a similar issue, but it was fixed by power+vol up and that was the end of it, so not as far as my issue is currently. I've come to you guys as a last ditch effort to see if I could fix it before having to spend even more money to this company. This is the second phone I've got from them and both have had issues. Hoping someone saves me...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you unlocked your bootloader? Rooted? I'm having similar issues and I'm completely stock, I have not unlocked my bootloader or rooted or anything. If my screen goes off it won't come back but I get vibration when I press power button and I have to reset with volume up and power.
Bloodeagle said:
Maybe you guys could help me. I'm at a loss and customer support told me to turn it off and turn it back on. I bought the Razer Phone 2 on December 27th. Around mid to late February, I had an instance where the phone crashed and was black screen, but the vibration reacted to me touching/pressing the power button. Hard resetting the phone allowed it to go back to normal. It got more frequently and more annoying, and it got to the point where multiple resets wouldn't fix it. Several times I got a screen telling me it couldn't load the android system(First image). After several instances of that screen, I tried to wipe the phone and reset it to factory, and now it's just an expensive paperweight. I can press Power+Volume Up to get to android recovery, but choosing to start up does nothing, reboot to bootloader does nothing, and pretty much everything else is useless. ...Hoping someone saves me...
Click to expand...
Click to collapse
My phone does this every once in a while. I believe it's something wrong with the second pie update and without having an unlocked bootloader this isn't something that a lot can be done about.
You have access to the recovery at least, and that's good if you can find someone willing to share the update payload zip then you might be able to apply the update again over ADB. Doing so might restore your phone to working-enough condition to fully flash a factory image just be sure there's nothing corrupt in the bootstack or system image. My suggestion would be to ask around and see if anyone is willing to revert to an older version of the firmware to grab the update payload(or has one archived) so that you can try this method. It might be your best shot.
If all of that doesn't pan out, then you might be SOL unless you can wipe it over ADB/Fastboot while in the recovery or bootloader. There's a slight possibility that the phone isn't properly resetting when you do it through the recovery menu but is just deleting personal data without defaulting the configs or checking for errors. There might even be a chance that you can configure it to boot from slot B through fastboot. I'm not sure how to do that one but as far as I'm aware, when you apply updates it moves the old data to slot B so it can put fresh images in slot A(someone correct me if I'm wrong).
natefck420 said:
Have you unlocked your bootloader? Rooted? I'm having similar issues and I'm completely stock, I have not unlocked my bootloader or rooted or anything. If my screen goes off it won't come back but I get vibration when I press power button and I have to reset with volume up and power.
Click to expand...
Click to collapse
Before your issue gets to the point where your phone doesn't boot correctly like OPs, you should follow the tutorial on Razer's Dev site to unlock your bootloader so if something does happen or the issue persists, you can flash the stock firmware onto your phone with minimal issue. If you end up unlocking, DO NOT relock the bootloader. Nothing bad actually happens if you do unless you've got a custom ROM or kernel installed, then you will probably brick. I wouldn't know since I'm not willing to try relocking with non-factory images...
It's just that having the bootloader unlocked is required to flash the images from Razer so if you're having the black screen bug then you really should unlock for safety. Naturally, if you're still in warranty then try to get it fixed through Razer. This is a more "If all else fails" or " Just in case" kind of a solution for people who like fixing their own stuff or are out of warranty. Also, unlocking your bootloader gives you the ability to install Arter97's kernel and TWRP which can improve your phones stability and reduce the need to restart from the screen off bug. TWRP backups are a huge bonus, too.
Razer is not suitable for mobile phones, this phone is all bug?
Wrote this message to Google support. I don't suspect I'll hear anything from anybody but I'll post here for my fellow Pixel brothers and sisters that perhaps may experience something similar. I'm disappointed. I know the phone is relatively inexpensive (cheap) and you get what you pay for (?) but this points to bad hardware, simple and plain. How does my 2019 LG G7 on android 9 (!!??) outlast a 4a5g?? I expected more but, alas it is what it is. Peace out, Pixel 4a5g.
"Over my time since I've been on Google Fi I've used and bought a few devices. I started out with a Pixel 4a, then upgraded to the 4a5g and now I'm on the 6 Pro. I love Google phones and have always been a fan since days of the Nexus devices. I was disappointed when my 4a5g started bootlooping 2 months ago. It has never been unlocked or have I attempted to flash ROMs on it. It would eventually stop and boot back up, last for a week or so then bootloop again. This time around it continued for a longer period of time. When I went to try to do a factory reset it is stuck in Fastboot saying "no valid slot to boot." Based on the research on this issue I realize the phone is pretty much dead, even though I can use Google's own Flash tool to flash factory images for it. The phone is no longer under warranty and your support doesn't give any other options than paying for repair upt to $350, which is beyond the worth of the device. I am disappointed that the phone bootlooped to the point of death after only owning the device for LESS THAN 2 YEARS. (Nov 2020). My previous device, a LG G7 that I previously had on Verizon lasted longer, and my dad still uses that phone to this day. I purchased that phone in March of 2019. I know this post will only fall on deaf ears and no one can do anything about it but for the first time in a long time I'm disappointed by a Google phone."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why not reflash since those ROMs are easily available? You have access fastboot, no?
Kaynejulian said:
Why not reflash since those ROMs are easily available? You have access fastboot, no?
Click to expand...
Click to collapse
I've been flashing and re-flashing this phone for 2 days.
What's the output? What is error code? What commands are you using? What does fastboot getvar all show?
I'm using the android flash site to flash the phone with a stock image from Google. It goes through the process with no errors, then it acts like it's going to boot, bootloops twice then goes to the pictured fastboot mode showing "no valid slot to boot." Fastboot shows the build number (android 11 or 12 depending on which I've flashed) but when i try to wipe data i get /system/bin/tune2fs is missing.
I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org
Thordim said:
I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org
Click to expand...
Click to collapse
Thanks for trying, I get file format is not recognized error message. I tried manually installing the Pixel Experience ROM and even got that ROM's recovery to flash, and flashed the ROM, all went well exactly as the website said but then it said that the phone is corrupted and bootlooped. Flashed the stock 12.1 image using the Android Flash Tool, back to above error message after 2 bootloops.
Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.
smokejumper76 said:
Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.
Click to expand...
Click to collapse
What confuses me is that even when I manually flash a custom ROM or stock image it goes through the process just fine, no error messages. It boots up, does the little G circle animation and right as it's about to go to the next screen.. bam, it reboots. Does it a second time, then immediately goes to the above-mentioned screen shot. So I think somewhere the hardware or storage drive or whatever you want to call it is broken. I wonder if I triggered it when I tried to enter fastboot during one of the times I tried to factory reset it. I dunno... I'm attempted to let the battery die then recharge and try again or something.
It's ok, I'm sort of over it.. my feelings are hurt at this point. I've been Rooting and Romming since the days of Moto Droid X2, Galaxy Note 2 (before vzw locked their bootloader) and the Nexus 6, so when I got into the Pixel phones I was relieved when I didn't feel like I didn't have to do all of that just to get the phone to feeling like it's working smoothly. I have a 4a that has a broken screen, this one and a 6 Pro (factory), so I've really liked the Google Pixel devices and the software experience. So for this to start bootlooping even without me tinkering with it for over a year is just a disappointment.
If anyone can understand it, here are screenshots of the recover.log file from the recovery screen.
Tried flashing the first Android 11 OTA image from the Google Images site, A4 October 2020 as it's a unlocked Google purchased phone. I noticed it goes through the motions but says status 0 then further that system/bin/tune2fs is missing so nothing is being written. This must be happening every time I try to flash but I'm not actually seeing that nothing's happening on the Google flash website.
Have you already tried the Android Flash Tool? Given the circumstances I would recommend checking the Force flash all partitions box.
yeah, that was the first thing i did, tried 11, 12, 13 beta, 13 official... nothing. Lineage too.