Database Develop

Nexus 5 Error Updating

Received the phone. Insert SIM, unpackaged and booted up. Setup wifi and was told I *need* to install an update (you can't get around this).
Attempted to download the update. The progress bar filled up as you might expect, but when it got to the end it waited for a while, then restarted. This repeated 3 times.
Rebooted the phone manually and tried again. This time the system update download completed and the phone reboot automatically. Got part way through the update and encountered an error.
{
"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"
}
I've factory reset numerous times and repeated the process. It always ends in the same error.
My recovery console is as follows:
Can someone please upload a photo of their recovery mode details, I want to know if my version matches.

Benjamin Dobell said:
Received the phone. Insert SIM, unpackaged and booted up. Setup wifi and was told I *need* to install an update (you can't get around this).
Attempted to download the update. The progress bar filled up as you might expect, but when it got to the end it waited for a while, then restarted. This repeated 3 times.
Rebooted the phone manually and tried again. This time the system update download completed and the phone reboot automatically. Got part way through the update and encountered an error.
I've factory reset numerous times and repeated the process. It always ends in the same error.
My recovery console is as follows:
Can someone please upload a photo of their recovery mode details, I want to know if my version matches.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images#hammerhead
It looks like D820 and D821 use the same firmware? Needs verification, but you'll probably need to flash that.

Flash the factory image from google
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Flash the factory image from google
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I already have the firmware downloaded on my PC... just not sure if that will impede my ability to make a warranty claim when it doesn't work

Yeah flashing worked... well Wallet crashed when it first boot. But it no longer needed to download and update and hence I setup the phone.

Benjamin Dobell said:
Yeah flashing worked... well Wallet crashed when it first boot. But it no longer needed to download and update and hence I setup the phone.
Click to expand...
Click to collapse
Woo-hoo!
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Woo-hoo!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not so fast unfortunately.
Getting crashes all over the system, installing apps, opening settings etc.
Seems to be SecurityExceptions mostly

Benjamin Dobell said:
Not so fast unfortunately.
Getting crashes all over the system, installing apps, opening settings etc.
Seems to be SecurityExceptions mostly
Click to expand...
Click to collapse
Relock that Nexus and send it back. Hardware failure
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Relock that Nexus and send it back. Hardware failure
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Strangely enough, after relocking and rebooting I'm yet to see an exception. I'll stick with it for a little while longer and see how I go.

Damn, looks like I'm going to have to RMA.
Chrome crashes (in native code) and bluetooth tethering stops working after a while (whilst the phone itself can still access the Internet).
EDIT: Ugh, and just made my first phone call. I hope it's just this defective phone, but the call quality was disgusting.

Nexus 5 no command !!?
How do you solve the no command on update, I have just took it out of the box it completed the update did not restart and now says no command what do I do ?!!
---------- Post added at 11:53 AM ---------- Previous post was at 11:23 AM ----------
-Nexus5- said:
How do you solve the no command on update, I have just took it out of the box it completed the update did not restart and now says no command what do I do ?!!
Click to expand...
Click to collapse
ANYONE ?

xt1254 hangs on bootloader/recovery

Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
also every few days i have to go into apns and click one of the verizon ones again before my data will work, but that might just be a rom issue.

jombo2323 said:
xt1254 hangs on bootloader/recovery
Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
Click to expand...
Click to collapse
At first I thought you were saying your phone was booting to the bootloader screen or even booting to TWRP recovery, which would be very strange. That's happened to people before... which means the phone is really messed up.
But reading your actual write-up, (if you wrote it correctly) instead your phone is just NORMALLY booting. It's just taking a long time. Your phone is just staying stuck on the boot image, which is not the bootloader or recovery screens. It's just an image you see before the boot animation starts until finally you see your normal Android system GUI. In your case, it's the "bootloader warning screen" which is something you should replace.
THIS is the bootloader screen:
{
"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"
}
But instead you're seeing this, right?
It's the boot image Motorola has replaced to warn you your bootloader is unlocked. Yeah, I did it on purpose! As did you. No need to see it every day. You can flash a replacement boot image very easily in TWRP or ADB. <There's several to choose from.
WHY is it hanging on the boot image? You are right that something is wrong, but I don't think your phone is very messed up -- at least it's not booting to the bootloader screen!
You've tried clearing all the caches in TWRP? You've tried dirty flashing your ROM again? Sometimes something can get slightly corrupted and re-flashing your ROM over itself can fix the issue. Clearing all the caches in TWRP and letting all the apps re-optimize can also fix some issues.
Do you have any add-on xposed modules? I would temporarily disable all exposed modules, reboot a couple of times, see what happens? You can always re-enable them later. Xposed modules can conflict with your normal ROM functions and should be used very sparingly. Some modules like Gravity Box are really another ROM and settings in Gravity Box can conflict with settings in your ROM. But to a lesser degree so can almost any other xposed module.
Have you restored your TWRP backup which you made before all this happened? You do have a good TWRP backup, right?
Last, yeah, if none of that works, factory reset and reinstall the ROM.

Are you encrypted? I've noticed that once you encrypt the storage that the phone takes forever to boot. I haven't found any way around that and someone with more knowledge of the hardware than me mentioned that it's because the drivers for HW decrypt acceleration are missing.

I will add to this as I am having the same issue and have moved to another 32GB Turbo for the time being but now I'm having Radio issues with this one.
My 64 was encrypted, running CF's 1.0.8, xposed. Doing restoring the factory image did the same thing. Only thing is now that i think about it TWRP didn't ask for my pin for encryption though like it was before so it may not be encryped. I'm going to be doing some factory images this weekend and see if i can find out the issue and if I find anything I'll post back. Only thing that sucks is I only have one good screen between the two phones lol

Ugh, sorry for the lack of response. Ive been really busy.
To answer all questions. Ive done everything but wipe some crap with fastboot commands and performing a clean flash of the rom. Im on resurrection remix right now, i think i want to change though because my battery life is kinda ****.
Also no xposed, etc, just the basic rom.
Sorry for taking so long and thanks for the responses!

Le S3 x626 bricked issue

Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"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"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL

You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom

damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .

it was necessary to use a mirror. for example, in the bathroom

after brick and ressurect what write in (telephone settings) model?

Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop

Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?

take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.

Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.

Phone had issues with crashing, and now won't even launch

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?

ASUS ROG Phone 2 E:Failed...

Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
{
"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"
}
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?

did you backup your phone precautiously before
if you havent u lost all your important files
is your phone under warranty

Lavithiran -=-=-= said:
if you havent u lost all your important files
Click to expand...
Click to collapse
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.

mosa00 said:
Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
View attachment 5640881
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?
Click to expand...
Click to collapse
Do it this way:
1. Make a Wipe
2. Download this file https://androidfilehost.com/?fid=8889791610682901175
3. Run fastboot bootloader and connect to computer (side port)
4. Unpack and run "flashall_AFT.cmd" wait for the phone to reset and start up.
Should help.

mosa00 said:
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.
Click to expand...
Click to collapse
i dont think so you can retrive your old files