Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.
Hi,
Earlier Xposed was working good i download apk & updated & tired to install the frame work it failed. I was having problem with installing the Xposed Frame work from TWRP it was getting a boot loop i tried 86, 87, 88 version none of them was working it removed /data/data/conf/.de/disable file it did not worked on the xposed it was giving unable to open error.log then i created error.log file with RW,RW,RW permission then check on Xposed it showed error.php permission error then I changed to RWX,RWX,RWX still it was giving the error. I thought to flash my Phone again & reinstall twrp, I downloaded the J500FXXU1BPH1_J500FODD1BPH1_J500FDDU1BPH1_HOME.tar when i try to flash it gives error it show "An error occurred while updating the device software. user Emergency recovery function in the smart switch PC software" i tried with samsing smarch switch says "Connected device is not Supported"
My device is Samsung J500F
J500FXXU1BPH1
J500FODD1BPH1
I need to get back my phone back please help me.
Geekahmed said:
Hi,... I need to get back my phone back please help me.
Click to expand...
Click to collapse
I don't have this device but, the following threads should be of assistance regarding XPosed for your device.
https://forum.xda-developers.com/showthread.php?t=3701895
https://forum.xda-developers.com/showthread.php?t=3666155
You had posted this issue within the XPosed area of the forum that, initially, tells me that your seeking assistance with XPosed.
Your statement began with an XPosed issue and then you ended up with asking for assistance with recovering your device itself.
I'm not turning you away or lecturing you. I'm only pointing out something.
Your ultimately asking for assistance with recovering your device and really should be posted within the dedicated area of the forum that's specific to your device.
https://forum.xda-developers.com/galaxy-j5
Here's a variety/various list of helpful threads that, i believe, one or more will be helpful with recovering your device. Don't be afraid to ask for member guidance on those threads either.
https://forum.xda-developers.com/showthread.php?t=3219901
https://forum.xda-developers.com/showthread.php?t=3416960
https://forum.xda-developers.com/showthread.php?t=3588533
https://forum.xda-developers.com/showthread.php?t=3305976
https://forum.xda-developers.com/showthread.php?t=3588627
https://forum.xda-developers.com/showthread.php?t=3527700
https://forum.xda-developers.com/showthread.php?t=3209783
https://forum.xda-developers.com/showthread.php?t=3443904
I do wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi all.. I have rog phone 3 snapdragon 865plus I'm root and install twrp on the device after I opened the bootloader.. Problem is i lock oem bootloader from adb asus oem-lock
When restart phone not work i can go to recovery mod and i can go bootloader.. Always back on CSC fastboot
Any help? Or i kill the devices?
Please i speed all my money on this phone
mustafa.devel said:
Hi all.. I have rog phone 3 snapdragon 865plus I'm root and install twrp on the device after I opened the bootloader.. Problem is i lock oem bootloader from adb asus oem-lock
When restart phone not work i can go to recovery mod and i can go bootloader.. Always back on CSC fastboot
Any help? Or i kill the devices?
Please i speed all my money on this phone
Click to expand...
Click to collapse
THREAD CLOSED as duplicate of https://forum.xda-developers.com/t/csc-fastbood-mod-any-help.4202807/.
Both threads had been moved to Q&A section. Please read the sticked guide to the device fora.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Hi all, i really need help with the problem I have.
I've just replaced my broken screen (with frame).
However, the phone keep restarting itself once I've unlocked it using the pattern.
I heard wiping/factory reset will fix this, before I wipe the data, I really need to save all the data inside....I can't use USB debugger since I can't even unlock the screen to choose the usb debugging option.
What if I install TWRP via fastboot then flash other ROM, will this save my data?
Really appreciate the helps, thank you very much.
wilkho said:
Hi all, i really need help with the problem I have.
I've just replaced my broken screen (with frame).
However, the phone keep restarting itself once I've unlocked it using the pattern.
I heard wiping/factory reset will fix this, before I wipe the data, I really need to save all the data inside....I can't use USB debugger since I can't even unlock the screen to choose the usb debugging option.
What if I install TWRP via fastboot then flash other ROM, will this save my data?
Really appreciate the helps, thank you very much.
Click to expand...
Click to collapse
Hi, were you able to solve this problem?
THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/...hange-restart-after-entering-the-pin.4187603/
Regards,
shadowstep
Forum Moderator
I'm attempting to root my Pixel 4 XL with magisk, but am getting hung up on one part. So far I have:
downloaded and patched the system's boot image
installed adb and fastboot on my pc
turned on OEM unlock and USB debugging
gotten into fastboot mode both by using ADB on my computer, as well as using the device buttons (power + vol down)
when I'm in fastboot, though, the device's state is "locked" regardless of OEM unlock is on or not, so I am unable to flash the magisk image. I've read around that it might be a drivers issue on my Windows 11 PC, but I am unable to find a reliable way to get the correct drivers for this task. Is there a good way for me to fix this?
The phone is an unlocked google pixel 4 XL that I bought refurbished after my initial one died. I've read that some random unlocked pixels have permanently locked bootloaders (to pixel users' chagrin), and I'm a little worried that that's the case. I tried looking up my devices IEMI to double check that it's an unlocked phone, and I didn't see anything out of the ordinary there.
the exact issue I'm facing is: When I type ".\fastboot flashing unlock" into command prompt, I get < waiting for any device > as a response which softlocks the powershell as far as I can tell.
As stated above, I have tried searching around for this issue and have come to the conclusion that it's likely a driver issue, but I am unable to figure out how to get the necessary drivers.
thank you for any help in advance!
coltonious said:
I'm attempting to root my Pixel 4 XL with magisk, but am getting hung up on one part. So far I have:
downloaded and patched the system's boot image
installed adb and fastboot on my pc
turned on OEM unlock and USB debugging
gotten into fastboot mode both by using ADB on my computer, as well as using the device buttons (power + vol down)
when I'm in fastboot, though, the device's state is "locked" regardless of OEM unlock is on or not, so I am unable to flash the magisk image. I've read around that it might be a drivers issue on my Windows 11 PC, but I am unable to find a reliable way to get the correct drivers for this task. Is there a good way for me to fix this?
The phone is an unlocked google pixel 4 XL that I bought refurbished after my initial one died. I've read that some random unlocked pixels have permanently locked bootloaders (to pixel users' chagrin), and I'm a little worried that that's the case. I tried looking up my devices IEMI to double check that it's an unlocked phone, and I didn't see anything out of the ordinary there.
the exact issue I'm facing is: When I type ".\fastboot flashing unlock" into command prompt, I get < waiting for any device > as a response which softlocks the powershell as far as I can tell.
As stated above, I have tried searching around for this issue and have come to the conclusion that it's likely a driver issue, but I am unable to figure out how to get the necessary drivers.
thank you for any help in advance!
Click to expand...
Click to collapse
Hello and good morning, @coltonious
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to
Google Pixel 4 XL Questions & Answers
Ask your questions about the Google Pixel 4 XL and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator