Hello,
I have an "ex-rooted" nexus 5 that I just yesterday tried factory resetting, however, it won't do that and just stays stuck at erasing for 15-30 minutes before the broken android shows up. Now, when I say ex-rooted I mean that I have either uninstalled supersu with the supersu app, or I've tried just flashed over the old rom. Alas, I have no recovery at all, when I choose recovery from the bootloader the screen goes black and it goes back to try erasing the phone.
I would have just flashed it, but this is where my problem comes in. My phone doesn't show up on my computer at all. I have the right drivers and such, even tried different ports and cables.
Anyone have any ideas? Sorry if I'm ****ty at explaining my problem
I'll be eternally grateful for any help whatsoever
Recovery it what it goes to in order to FDR so you must have a recovery apparently. You can't boot up at ALL I am guessing?
Sent from my Nexus 5
Related
Dear guys and girls,
I have a problem. Since 2 days my tf300t is for some reason not starting up anymore. The start screen does not go away. Before it worked like a charm. I have tried almost everything, I can think of. As far as I know the latest firmware is installed. The problem is also that the tablet isn't in developer mode. So my options are limited afaik to fastboot. I have installed the naked drivers version 0.73. But windows is saying that the device is not started. Only fastboot is started as device. I have tried to reinstall the firmware by usb, but to no avail. It sends but doesn't write... I have drained the battery to zero level. Can anyone help me with this? What am I missing?
<>< A Dieu
Jaco Oversluizen
I'm also having this same issue. Tablet was working fine and then froze up. After rebooting we are now stuck on the Asus screen with the circular logo going. Waited over an hour with no change. Tried to boot into recovery and recovery crashes and gives me Error! This is a stock tablet that hasn't been unlocked or anything.
Update: Did a Data Wipe and the device rebooted and came up. Doing all the updates again. Hopefully it wont mess up again.
So you have an unlocked bootloader ?
Sorry if this info is posted somewhere already, I searched and could not find my exact issue.
So, woke up this morning noticed Nexus 5 was off. So i turned it on and it will not load past the Google logo. It doesn't keep rebooting to it like others have said but just stays on the Google logo.
I can do the Volume down + power to get into what it says is the FASTBOOT MODE with the green robot on its back. However, selecting Recovery mode just takes me to a blank screen.
I have tried installing TWRP but it did not appear to work. The install said it failed the first time after a while, tried again and it said it worked. However still nothing when selecting Recovery.
Phone is Rooted with stock Android 4.4.4 no custom ROMs.
I appreciate any help.
If this doesn't work, any reviews on the new Moto X? Does it get the new updates right away also? Really do not want to get away from Stock Android.
Fastboot a system and see if that works
Sent from my Android L Nexus 5 via Tapatalk
Ben36 said:
Fastboot a system and see if that works
Sent from my Android L Nexus 5 via Tapatalk
Click to expand...
Click to collapse
Can you give me more detail than that please.
OK, i believe I fastbooted a system.img like suggested. However still nothing.
When trying to do a factory reset "erase userdata" on the phone it hangs up on "erasing..." So it wont even factory reset lol. sigh....
Apparently Google cant fix it either. Getting a new phone
Lol. Might as well unlock the bootloader straight away then before any data is put on
Sent from my Android L Nexus 5 via Tapatalk
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.