Database Develop

[Q] factory standard stuck at boot

someone on one of the pages on facebook asked if anyone could help, her phone was working fine then suddenly wasnt and stuck at this stage (see pic)
its a factory standard phone, not been rooted, not been bootloader unlocked and S-ON, how to get the phone working again

Well the first thing to try is a Factory Reset, if its been tried already the only other thing you can do is Unlock the bootloader. This will void the warranty if there is any and if the phone still doesn't boot after flashing a rom you won't be able to reyurn it under warranty so that should be considered before unlocking it.
In fact you could try flashing a firmware package before unlocking that may or may not fix it without unlocking the bootloader. Do you know how to use adb and fastboot?

i dont think unlocking the bootloader is an option, any simpler things to try first?

SnowManWales said:
i dont think unlocking the bootloader is an option, any simpler things to try first?
Click to expand...
Click to collapse
Flashing the firmware is about the only thing you can do. Not necessarily simpler than unlocking the boot loader and won't be a guaranteed solution depending what the actual problem is. But it won't effect the warranty in anyway.

SnowManWales said:
i dont think unlocking the bootloader is an option, any simpler things to try first?
Click to expand...
Click to collapse
Danny201281 said:
Flashing the firmware is about the only thing you can do. Not necessarily simpler than unlocking the boot loader and won't be a guaranteed solution depending what the actual problem is. But it won't effect the warranty in anyway.
Click to expand...
Click to collapse
Also Don't Forget unlocking the bootloader will completely erase the phone ...everything on it will be lost.
Boot to stock recovery from the bootloader
the screen will go black wait a few seconds and press volume up and tap power you should see the stock recovery menu
do a clear cache from their and see if it boots
if no go back to the same screen and choose factory reset ... this will erase the phone also but it might boot up afterwords

[Q] Cannot lock bootloader after flashing factory 5.1

Hi all,
Running into issues with the new 5.1 factory image. After flashing, booting up, setting up my google account, and enabling the new Allow OEM Unlock setting in dev options, I jump to the bootloader to relock. I've tried running the lock from both fastboot and mfastboot. In either case, it says locking was successful, sets the lock status to (2). I hit Start (or fastboot reboot, etc.) and it hits the Google splash (no unlock icon at the bottom), quickly reboots, goes to Google splash, and then sits at the system update screen... the one with the green android/open chest/blue spinning wireframe. It never passes this. If I erase the cache, it hangs at the spinning colored dots splash screen forever. If I unlock, erase userdata and cache, it'll boot fine, but I'm back to where I was in the first place... data reset, unable to lock the bootloader.
I *have to* lock the bootloader because of stupid Mobile Iron requirements from work. Any ideas? My goal is to have a full factory install, unrooted, locked, on 5.1 so I can install Mobile Iron.
Thanks!

Have you tried flashing the full factory image a second time? Maybe do each part separately

rootSU said:
Have you tried flashing the full factory image a second time? Maybe do each part separately
Click to expand...
Click to collapse
Yeah, I've tried multiple times with flash-all (both latest fastboot and modified to use mfastboot) and got the "error: update package missing system.img" error so I used mflashboot to flash the bootloader, radio, recovery, boot, system, cache, and userdata partitions.
I have not tried an OTA.
So full history: device was brand new about 2 weeks ago (t-mobile), came with 5.0.1. I never unlocked it or rooted or anything up until yesterday when I tried to flash the full factory 5.1 from google as described above. I downloaded the full 5.1 image, booted into fastboot, did "fastboot oem unlock", tried flash-all, hit that error, individually flashed everything. Unlocked dev options, enabled oem unlock setting, back into fastboot, 'mfastboot oem lock', this issue.
Trying to go back to 5.0.1 right now to see if I can at least get it back up and running with Mobile Iron.

negativefx said:
Trying to go back to 5.0.1 right now to see if I can at least get it back up and running with Mobile Iron.
Click to expand...
Click to collapse
Same problem on 5.0.1. Sigh.
Interesting though, if I try the lock, reboot, get the system update screen, and force it back into bootloader (vol down+power) and run oem unlock, I still get the system update screen. Have to blow away the cache to get it to boot.
Not sure if it matters but when unlocked, status code is 3, when locked, it goes to 2. I didn't pay attention to what the code value was prior to unlocking the first time.

The codes are accurate

rootSU said:
The codes are accurate
Click to expand...
Click to collapse
Any idea beyond this? Could it have something to do with the encrypted storage?

I might try flashing another rom and recovery and working from there.

Strange... the OEM unlocking setting in dev options doesn't seem to stick between restarts. I have to set it each time. Is that expected behavior?

negativefx said:
Strange... the OEM unlocking setting in dev options doesn't seem to stick between restarts. I have to set it each time. Is that expected behavior?
Click to expand...
Click to collapse
On 5.1 it is.
No idea though ultimately

I managed to get it to lock finally. I don't remember the exact combination but it eventually prompted me during reboot to provide my pass for the encrypted storage and I tried my PIN, that didn't work. Went in to fastboot, reflashed userdata and cache, went to android device manager on my PC and did a remote wipe. After that, it let me lock.

negativefx said:
Hi all,
Running into issues with the new 5.1 factory image. After flashing, booting up, setting up my google account, and enabling the new Allow OEM Unlock setting in dev options, I jump to the bootloader to relock. I've tried running the lock from both fastboot and mfastboot. In either case, it says locking was successful, sets the lock status to (2). I hit Start (or fastboot reboot, etc.) and it hits the Google splash (no unlock icon at the bottom), quickly reboots, goes to Google splash, and then sits at the system update screen... the one with the green android/open chest/blue spinning wireframe. It never passes this. If I erase the cache, it hangs at the spinning colored dots splash screen forever. If I unlock, erase userdata and cache, it'll boot fine, but I'm back to where I was in the first place... data reset, unable to lock the bootloader.
I *have to* lock the bootloader because of stupid Mobile Iron requirements from work. Any ideas? My goal is to have a full factory install, unrooted, locked, on 5.1 so I can install Mobile Iron.
Thanks!
Click to expand...
Click to collapse
I see you got it to work :good:, but just a little explanation:
The N6 forces a wipe when you lock the bootloader. And sometimes it hangs. What you need to do is boot into the stock recovery after you have locked your bootloader and do a factory reset. Then you should be able to boot normally with a locked bootloader.

[Q] Can't update to 5.1 (Previously unlocked & rooted, but re-locked)

I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?

if any files have changed in the system, any, and just one, then you can not update via ota.

simms22 said:
if any files have changed in the system, any, and just one, then you can not update via ota.
Click to expand...
Click to collapse
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...

RichCowell said:
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
Click to expand...
Click to collapse
Click the OTA link in my signature for some more information.

RichCowell said:
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
Click to expand...
Click to collapse
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).

simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Agreed, factory image should get you back to Ota ready.

simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
for the future, if you are flashing a factory img, then yes.

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Same thing. Everything has to be 100% stock.
No need to wipe if you don't relock your bootloader.

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?

RichCowell said:
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
Click to expand...
Click to collapse
if it booted fine, and your about phone says 5.1, then youre fine.

simms22 said:
if it booted fine, and your about phone says 5.1, then youre fine.
Click to expand...
Click to collapse
Awesome, thanks
Need to decide now whether to bother rooting to make future updates easier...

I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?

sarshadd said:
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
Click to expand...
Click to collapse
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.

rootSU said:
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
Click to expand...
Click to collapse
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.

sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
What does it say when you sideload?

sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
After you put the boot loader in sideload mode, unplug and replug the USB cable, then run adb sideload.

Bricked Nexus6 stucked in bootloader with locked and stock recovery

Really trouble because of locked boot loader and stuck in boot loader with stock recovery. Try and with no luck cannot fast boot flash anything because it always ask for unlock boot loader allowed in developer mode. Don't understand google on this features at all. All is stock if anyone have anyway to tick the box without boot or force flash with locked boot loader.

your only option is to rma it. theres no way to fix your error.

@tanipat
Sorry, but there's nothing you can do under the situation you describe. You will have to return it for repair/replacement.

thank you both pf you guys my problem is that Motorolla is no support here in Thailand anymore. the device is import from US. So i ho anyone able to find the solution on this, still dont understand Google to enable this issue without proper flash firmware in spite of all in my device is no root and all stock, really dont understand at all why we cant fix it in spite of it is all stock like this hurrr

tanipat said:
thank you both pf you guys my problem is that Motorolla is no support here in Thailand anymore. the device is import from US. So i ho anyone able to find the solution on this, still dont understand Google to enable this issue without proper flash firmware in spite of all in my device is no root and all stock, really dont understand at all why we cant fix it in spite of it is all stock like this hurrr
Click to expand...
Click to collapse
well, its a security feature. to prevent people stealing your device, then factory reseting it to set up their own account. if there was a way around it, it would make terrible security.

So if you hit start it just goes straight back into the bootloader?

tanipat said:
thank you both pf you guys my problem is that Motorolla is no support here in Thailand anymore. the device is import from US. So i ho anyone able to find the solution on this, still dont understand Google to enable this issue without proper flash firmware in spite of all in my device is no root and all stock, really dont understand at all why we cant fix it in spite of it is all stock like this hurrr
Click to expand...
Click to collapse
How did it get this way? Just out off the blue? What happens is you press Start?, What happens when you do Factory Reset?

i'm unlock bootloader when i get this phone. and using it without root or flash anything. the problem comes when i factory reset it and i go to sleep in the morning i found it in bootloader screen with this situation. i try start and it go back to bootloader again always. thing i can do is format or erase cache and data and can enter stock recovery.
can i adb sideload anything? i have no clue also why my phone seems lose everything except stock recovery any thoughs my friends?

tanipat said:
i'm unlock bootloader when i get this phone. and using it without root or flash anything. the problem comes when i factory reset it and i go to sleep in the morning i found it in bootloader screen with this situation. i try start and it go back to bootloader again always. thing i can do is format or erase cache and data and can enter stock recovery.
can i adb sideload anything? i have no clue also why my phone seems lose everything except stock recovery any thoughs my friends?
Click to expand...
Click to collapse
Try factory reset again?

tanipat said:
i'm unlock bootloader when i get this phone. and using it without root or flash anything. the problem comes when i factory reset it and i go to sleep in the morning i found it in bootloader screen with this situation. i try start and it go back to bootloader again always. thing i can do is format or erase cache and data and can enter stock recovery.
can i adb sideload anything? i have no clue also why my phone seems lose everything except stock recovery any thoughs my friends?
Click to expand...
Click to collapse
so, your bootloader is unlocked? if its unlocked, it can be fixed.

tanipat said:
i'm unlock bootloader when i get this phone. and using it without root or flash anything. the problem comes when i factory reset it and i go to sleep in the morning i found it in bootloader screen with this situation. i try start and it go back to bootloader again always. thing i can do is format or erase cache and data and can enter stock recovery.
can i adb sideload anything? i have no clue also why my phone seems lose everything except stock recovery any thoughs my friends?
Click to expand...
Click to collapse
Nope. If you format userdata and cache already, nothing else you can do.

yes it unlock before i do factory reset and now it is no longer unlock i dont know why. and yes i do factory reset and it still boot in to bootloader. and yes i did format cache anf dat via fastboot. i dont know how to do now

tanipat said:
yes it unlock before i do factory reset and now it is no longer unlock i dont know why. and yes i do factory reset and it still boot in to bootloader. and yes i did format cache anf dat via fastboot. i dont know how to do now
Click to expand...
Click to collapse
Nothing to do. Screwed.
Hope you have american friend to mail device to or $$$ for new motherboard.

tanipat said:
yes it unlock before i do factory reset and now it is no longer unlock i dont know why. and yes i do factory reset and it still boot in to bootloader. and yes i did format cache anf dat via fastboot. i dont know how to do now
Click to expand...
Click to collapse
Was this phone ever working? Why did you do Factory Reset?

bootloader log says
invalid boot image size!
fails to validate boot image
fastboot reason: Fall-through from normal boot mode
USB connected

Oh my friend seem i screwed it up like you said. it is expensive paper weight now.
i just wanna reset it because i will give this phone to my friend who have lost the phone, now i dont think he needs expensive paper weight!

tanipat said:
Oh my friend seem i screwed it up like you said. it is expensive paper weight now.
i just wanna reset it because i will give this phone to my friend who have lost the phone, now i dont think he needs expensive paper weight!
Click to expand...
Click to collapse
You have to know exactly what you have before you tinker, but your going to have to get a new phone. Gotta slow down and take your time

No way to get out of this friends?

tanipat said:
No way to get out of this friends?
Click to expand...
Click to collapse
If your device is bricked, and your bootloader is locked and you do not have TWRP recovery installed, then the only thing one can do is return the device for repair or replacement.
On the other hand, if bootloader is unlocked and/or one has TWRP recovery installed, then it is relatively easy to fix.

still no findaway method so far? of it is possible for me to adb push from stock recovery? Do we have that kind of firmware.zip other than factory image flashing?

bootloop, adb disabled, fastboot enabled; launch recovery?

tl;dr:
Version: D5803 with SliMM ROM, latest + Xposed +TWRP (maybe not TWRP anymore?)
Problem: bootloop at 2nd boot logo (1st Sony, 2nd Android)
Cause: Xposed Modul installed causig bootloop
Try: Get into recovery to deactivate Xposed via "touch /data/data/de.robv.android.xposed.installer/conf/disabled"
State: recovery not accessible, ADB probably disabled (crashed last time I clicked on developer options), fastboot accessible, locked bootloader
Hi, I have a problem I'm not able to solve by myself. After I installed an Xposed Module, my phone is at boot loop. So I wanted to go to the recovery and deactivate Xposed. But the recovery seems not to be accessible: The LED doesnt go green, so that I can push volume up/down. ADB seems to be disabled in developer options, because it crashed last time I clicked on developer options before the whole error occured. My bootloader is locked, so I'm not quite sure what to do, when accessing fastboot.
I tried fastboot boot twrp.img and to intall it, but - probably of the locked bootloader - an error appears.
So, what can I do to resolve my problem? Any ideas? Unlocking the bootloader without starting the phone?
thanks!
Tray

traydare said:
tl;dr:
Version: D5803 with SliMM ROM, latest + Xposed +TWRP (maybe not TWRP anymore?)
Problem: bootloop at 2nd boot logo (1st Sony, 2nd Android)
Cause: Xposed Modul installed causig bootloop
Try: Get into recovery to deactivate Xposed via "touch /data/data/de.robv.android.xposed.installer/conf/disabled"
State: recovery not accessible, ADB probably disabled (crashed last time I clicked on developer options), fastboot accessible, locked bootloader
Hi, I have a problem I'm not able to solve by myself. After I installed an Xposed Module, my phone is at boot loop. So I wanted to go to the recovery and deactivate Xposed. But the recovery seems not to be accessible: The LED doesnt go green, so that I can push volume up/down. ADB seems to be disabled in developer options, because it crashed last time I clicked on developer options before the whole error occured. My bootloader is locked, so I'm not quite sure what to do, when accessing fastboot.
I tried fastboot boot twrp.img and to intall it, but - probably of the locked bootloader - an error appears.
So, what can I do to resolve my problem? Any ideas? Unlocking the bootloader without starting the phone?
thanks!
Tray
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock ROM but you can also try this:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336

Dinkec27 said:
The only thing I can think of is to reflash the stock ROM but you can also try this:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
Thanks, didn't think of that. When I press a hardware button 5 times the vibration feedback is there, but the phone still gets stuck at the Android boot logo.
Which way do you mean to reflash the stock ROM?

traydare said:
Thanks, didn't think of that. When I press a hardware button 5 times the vibration feedback is there, but the phone still gets stuck at the Android boot logo.
Which way do you mean to reflash the stock ROM?
Click to expand...
Click to collapse
I mean through Flashtool,there are many guides on XDA,but it does wipe all of the data

Dinkec27 said:
I mean through Flashtool,there are many guides on XDA,but it does wipe all of the data
Click to expand...
Click to collapse
Thanks so far - I decided to reflash Stock. Worked.