[Q] Trouble Unbricking - Nexus 5 Q&A, Help & Troubleshooting

Hey all,
Recently took advantage of Google's 1 time replacement policy as my phone is completely shattered. Received the new one in the mail the next day, installed everything and transferred my data, then went to set the old one up to send it back. I decided to unroot and relock the bootloader, then I went to wipe data via TWRP (why I didn't flash stock recovery before wiping I don't know...) Unfortunately, I was rushing and managed to stupidly hit wipe everything, and I have no OS. The phone is soft bricked. Normally this wouldn't be too much of a challenge, but my phone also refuses to be recognized by my computer (Windows 7). The new one installs drivers and pops up perfectly, but the old one doesn't show up while in bootloader or recovery. When I try to run fastboot commands, any application I try says "Waiting for Device" (including the Kwongger toolkit unbricking setup).
Short explanation: I managed to idiotically wipe the OS, now my computer won't recognize it while it's in TWRP or bootloader.
Anybody have advice on how to fix this and flash a stock image? Should I risk sending it to Google like this?
Thanks for any help you can provide!

If you're worried about it, flash the factory image in fastboot. But I wouldn't worry too much. Google's pretty cool about flashing stuff to your phone.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you're worried about it, flash the factory image in fastboot. But I wouldn't worry too much. Google's pretty cool about flashing stuff to your phone.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How would I go about getting the file onto the phone (my stock backup disappeared from TWRP, forgot to mention that in the OP) if I can't connect to my computer?
Thanks for the reassurance - if I can't get it working by tomorrow I think I'll probably just send it in and see what happens.

All you can do is try lg flash tool. Link in my signature
Sent from my Nexus 5 using Tapatalk

rootSU said:
All you can do is try lg flash tool. Link in my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice - I tried it, but the phone doesn't enter download mode. It just enters the powered off but charging state (where the charging battery symbol flashes on the screen).
Additionally, when I launch the FlashTool, it says "LG USB/Parallel lock key is not detected" then sends me to a login screen (it appears this person had the same issue, but solved it without posting how to solve it). Any ideas?

miller150 said:
Thanks for the advice - I tried it, but the phone doesn't enter download mode. It just enters the powered off but charging state (where the charging battery symbol flashes on the screen).
Additionally, when I launch the FlashTool, it says "LG USB/Parallel lock key is not detected" then sends me to a login screen (it appears this person had the same issue, but solved it without posting how to solve it). Any ideas?
Click to expand...
Click to collapse
I haven't. You can try posting in the LG Flashtool thread... You may get better answers there

miller150 said:
Thanks for the advice - I tried it, but the phone doesn't enter download mode. It just enters the powered off but charging state (where the charging battery symbol flashes on the screen).
Additionally, when I launch the FlashTool, it says "LG USB/Parallel lock key is not detected" then sends me to a login screen (it appears this person had the same issue, but solved it without posting how to solve it). Any ideas?
Click to expand...
Click to collapse
There is a megalock dll in the crack folder. Replace the original dll with the one from the crack folder.

I wouldn't worry about flashing back to stock. Like said before, Google doesn't really care about what firmware you're running. You're not going to run into any problems if you send the phone back in its current state.
Sent from my iPhone 6 using Tapatalk

bitdomo said:
There is a megalock dll in the crack folder. Replace the original dll with the one from the crack folder.
Click to expand...
Click to collapse
That fixed the issue with flashtool, but unfortunately something on my phone must be busted; it won't go into download mode. I tried my new one just to ensure the cable and port were working, and it went right in. I think I'll just have to send it in and hope they don't mind. Thanks for the help guys!

Related

[Q] Device completely unusable :( PLZ HELP

I tried following cyanogen wiki on an Inspire 4G. It didn't work and gave "Incorrect Model ID" error.
So I switched to use Hack-Ace tool. Everything worked as expected and I guess I was going good. When Hack-Ace completed, the phone went into an infinite look showing HTC logo then blind to a black screen with background light ON.
I could ADB and reboot in bootloader where I clashed the CM7 ROM. Every step went through fine and it restarted. Now all I get is nothing.
The device shows the HTC Logo on white screen after leaving a while and the vibrator is ON constantly. It doesn't help really but keeps doing that. It will only stop if I remove battery.
Plugging the device into USB doesn't detect on PC.
When tried charging, it shows the error messages and nothing happens, no buttons interact.
I guess I have a full brickd phone now
Have you tried flashing stock ruu thru bootloader
Sent from my Inspire 4G using XDA App
Download and flash this thru bootloader.
http://www.megaupload.com/?d=Q6YYQFIM
Sent from my Inspire 4G using XDA App
Yah, try the ruu. Seeing how it at least turns on means it might be fixable. Can you get into recovery?
Sent from my MB860 using XDA App
I'm trying the link given by creglem
stumpyz9, no man i've not been able to boot into recovery.. the device is doing nothing
kishu_27 said:
I'm trying the link given by creglem
stumpyz9, no man i've not been able to boot into recovery.. the device is doing nothing
Click to expand...
Click to collapse
The ruu will probably be your best bet then
Sent from my MB860 using XDA App
only if i could get it to install... i dunno what'll happen cuz i cannot go to recovery mode. i'm just going to try once
worst part is that this is a friend's phone
not able to open recovery
any other idea guys?
kishu_27 said:
only if i could get it to install... i dunno what'll happen cuz i cannot go to recovery mode. i'm just going to try once
worst part is that this is a friend's phone
Click to expand...
Click to collapse
http://webchat.freenode.net/?channels=#aahkSupport <--- go there to save said friends phone.
kishu_27 said:
not able to open recovery
any other idea guys?
Click to expand...
Click to collapse
You font nerd recovery with that file. Just out it on the root if your sdcard. Meaning not in any folder and boot into bootloader...not recovery then it will recognize the file then just follow onscreen instructions
Sent from my Inspire 4G using XDA App
kishu_27 said:
I tried following cyanogen wiki on an Inspire 4G. It didn't work and gave "Incorrect Model ID" error.
So I switched to use Hack-Ace tool. Everything worked as expected and I guess I was going good. When Hack-Ace completed, the phone went into an infinite look showing HTC logo then blind to a black screen with background light ON.
I could ADB and reboot in bootloader where I clashed the CM7 ROM. Every step went through fine and it restarted. Now all I get is nothing.
The device shows the HTC Logo on white screen after leaving a while and the vibrator is ON constantly. It doesn't help really but keeps doing that. It will only stop if I remove battery.
Plugging the device into USB doesn't detect on PC.
When tried charging, it shows the error messages and nothing happens, no buttons interact.
I guess I have a full brickd phone now
Click to expand...
Click to collapse
Dude download the PD98 file above it is the rooted updated gingerbread ROM. Place it in the root of your SD card (you will have to remove SD card and use adapter to move zip file to root of SD card if PC does not recognize phone with USB cable) and power phone off then power back up holding down power button and volume down button at same time. Phone should go to bootloader then it will recognize the PD98 zip file and ask if you want to istall. Volume up for yes and it will do its thing. No need to try to get into recover phone will do it itself with the PD98 zip file. Zip is (ATT ROM 2.47.502.7 w/Radio - 26.10.04.03_M)
Credit to Football

I think my lg g2x is bricked (im kind of a noob)

What i did before this problem
1.used the lg support tool to go from froyo to gingerbead (worked great)
2. attempted to use clockwork rom to install icecream sandwhich based rom (it failed)
What i get now
1.If i turn my phone on like i always would i would get the lg logo, and it would stay like that forever
2. if i try to boot into recovery i get "s/w upgrading"
I contacted lg and they said to send it in and wait 2 WEEKS to get it back and there may be an additional charge
Can someone please help me fix this without going to lg. I just want to be able to use my phone again :'(
run this:
http://forum.xda-developers.com/showthread.php?t=1590523
I did the exact same thing to my phone the other day. Then install the new rom via clockworld after its done.
But if you installed the 2.3.4 then don't update to any rom besides the kwes 2.3.4 because anything else you won't have audio or anything while in call there is no fix for it yet besides using kdz to downgrade.
Sent from my LG-P999 using xda premium
bj83gc said:
run this:
http://forum.xda-developers.com/showthread.php?t=1590523
I did the exact same thing to my phone the other day. Then install the new rom via clockworld after its done.
Click to expand...
Click to collapse
I tried it and it didnt help.
if i do a normal boot i get the lg logo wiht a loading bar that eventual stops and does nothing
if i boot into recovery i get "s/w upgrading" again
you have to use nvflash to snap it out of that... I remember i had it stuck on that for awhile until i flashed the stock recovery/bootloader stuff and then reflashed cwm and then it finally came to
NVflash CWM from http://forum.xda-developers.com/showthread.php?t=1566681
if you're unsure of the APX drivers set-up you have a more basic guide here:
http://forum.xda-developers.com/showthread.php?t=1056847
Remove the battery.
Plug in your USB cable to your PC.
Hold Volume Up and Volume Down at the same time keeping them held down.
Plug in the USB cable to your phone. (Keep the buttons held until Windows detects a new APX device.)
Open Device Manager in Windows and you should see "APX Device" listed with an error icon.
Right click on the APX device.
Select 'Update driver software'.
Select 'Browse my computer...'.
Select 'Let me pick...'.
Select 'Have disk'.
Browse to directory you extracted the *driver* software to: One-Click-G2x-recovery-flasher-09-23\APX.
Accept any warnings, including the big red alert (you may need to disable UAC).
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'.
If not, uninstall the driver, reboot, rinse and repeat.
Click to expand...
Click to collapse
Волк said:
NVflash CWM from http://forum.xda-developers.com/showthread.php?t=1566681
if you're unsure of the APX drivers set-up you have a more basic guide here:
http://forum.xda-developers.com/showthread.php?t=1056847
Click to expand...
Click to collapse
No change, thanks for trying :'(
just keep dicking around with NVflash... its the only way you can wake it up from a soft brick of that form
JHaste said:
just keep dicking around with NVflash... its the only way you can wake it up from a soft brick of that form
Click to expand...
Click to collapse
like what, what do i do. i am a total noob.
johnlicoski1204 said:
like what, what do i do. i am a total noob.
Click to expand...
Click to collapse
I don't think you're booting the phone up into cwm the right way.
Lol do this:
Make sure phone is off. While the phone is off hold down the volume down button.
While still holding volume down, hold the power button.
Continue to hold BOTH the volume down and power buttons. When the SECOND LG logo appears, let go of both of the buttons.
And no offense, but if you're not comfortable with modding your phone... you really shouldn't do it or ask someone else who knows what they're doing to do it.
buru898 said:
I don't think you're booting the phone up into cwm the right way.
Lol do this:
Make sure phone is off. While the phone is off hold down the volume down button.
While still holding volume down, hold the power button.
Continue to hold BOTH the volume down and power buttons. When the SECOND LG logo appears, let go of both of the buttons.
And no offense, but if you're not comfortable with modding your phone... you really shouldn't do it or ask someone else who knows what they're doing to do it.
Click to expand...
Click to collapse
Agree modification to a cellphone can be risky.
Sent from my LG-P999 using xda premium
From my personal experiance with the G2x (i thought i had bricked my phone), i have discovered that it is nearly impossible to brick this phone. I had ran the g2x nullifier and fully wiped my phone clean. When I power up the phone, all i get is the initial white LG logo. Luckely, i discovered the following thread that got my phone functional again:
http://forum.xda-developers.com/showthread.php?t=1248644
Try the above thread and see if your phone gets recovered to a functional state.
dot64 said:
From my personal experiance with the G2x (i thought i had bricked my phone), i have discovered that it is nearly impossible to brick this phone. I had ran the g2x nullifier and fully wiped my phone clean. When I power up the phone, all i get is the initial white LG logo. Luckely, i discovered the following thread that got my phone functional again:
http://forum.xda-developers.com/showthread.php?t=1248644
Try the above thread and see if your phone gets recovered to a functional state.
Click to expand...
Click to collapse
That script is perfectly fine and didn't hurt your phone at all. It states that it will wipe everything out even the rom you were previously on. So when the phone rebooted it stayed on that LG logo because it didn't have a rom to bootup.
At that point a quick battery pull and reboot into recovery was all you needed to do.
Sent from my LG-P999 using xda premium
Try flashing the stock recovery thru the one click nvflash utility and leave it off for a few min. Then run the g2x batch cleanup tool and see if it then let's u boot into the recovery. (By holding down volume - when hitting power on)
Sent from my LG-P999 using XDA
johnlicoski1204 said:
What i did before this problem
1.used the lg support tool to go from froyo to gingerbead (worked great)
2. attempted to use clockwork rom to install icecream sandwhich based rom (it failed)
What i get now
1.If i turn my phone on like i always would i would get the lg logo, and it would stay like that forever
2. if i try to boot into recovery i get "s/w upgrading"
I contacted lg and they said to send it in and wait 2 WEEKS to get it back and there may be an additional charge
Can someone please help me fix this without going to lg. I just want to be able to use my phone again :'(
Click to expand...
Click to collapse
Ok, so then its safe to assume that you rooted your phone first? Then you set up your phone by using nvflash so you can use ClockWorkMod (CWM)? Then booted your phone into recovery and tried to install ICS? If not done in this order then thats your fault. If you did it in this order then you missed something.
A common mistake is trying to install a ROM via CWM while the phone is running. When you do this the phone restarts and gives you the error triangle with android underneath it.
http://forum.xda-developers.com/showthread.php?t=1039985 Tells you how to do as well as provides links to everything it doesn't.
As for recovery they provisded the right link. Follow it to the "T" and you'll be ok.
Try the link below
johnlicoski1204 said:
What i did before this problem
1.used the lg support tool to go from froyo to gingerbead (worked great)
2. attempted to use clockwork rom to install icecream sandwhich based rom (it failed)
What i get now
1.If i turn my phone on like i always would i would get the lg logo, and it would stay like that forever
2. if i try to boot into recovery i get "s/w upgrading"
I contacted lg and they said to send it in and wait 2 WEEKS to get it back and there may be an additional charge
Can someone please help me fix this without going to lg. I just want to be able to use my phone again :'(
Click to expand...
Click to collapse
Hope fully this fix your issue: http://www.youtube.com/watch?feature=player_embedded&v=TozZKt7_JD8
d12unk13astard said:
That script is perfectly fine and didn't hurt your phone at all. It states that it will wipe everything out even the rom you were previously on. So when the phone rebooted it stayed on that LG logo because it didn't have a rom to bootup.
At that point a quick battery pull and reboot into recovery was all you needed to do.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
But the key issue was that CWM recovery was destroyed as well after nullifing thus leaving me in a stand still to do something. nvflash was the only thing left to recover the phone at that point which worked very well.
There is pretty much no way that after running either the One-Click or Cleanup Batch that he can't get the phone into CWM unless there is a hardware problem. This most likely means that the problem isn't with the scripts or phone, but with the procedure he is attempting.
Even if nullifier (which I don't think is of much use here) had wiped all partitions, the NVFlash will still pop you out of it and leave you with a working CWM.
So keep reading and keep watching videos of how to do it and make sure your drivers are correct. READ a bunch first.
And remember that he got here due to an LG software problem or issue with operation, not from trying to flash as a noob, so he knows he's in over his head right now.
Remember, we all had to start swimming somewhere and it usually wasn't pretty at first. Mine was a corrupted Motorola RAZR.
It appears that this is an older post, but if you are still having this issue, then maybe I can help. If anyone else finds this later, hopefully it helps them as well. I just did something similar and I thought I was screwed. I rooted my phone, installed a ROM (Hellfire... nice ROM BTW), then I got the nullifier. I installed the ROM before I ran the nullifier because I wanted to make sure the ROM worked. However, after running the nullifier, the ROM didn't work.
The only thing that I could get to show was the LG logo at the startup... no second logo (Blue LG), no SW upgrade... NOTHING. The phone wouldn't do anything else. Luckily, I wasn't the first to have this issue and they found the solution...
forum.xda-developers.com/showthread.php?t=1566681
Since you have already done other steps, I am assuming that you already have the drivers installed. So, the only thing you should need to do is download the ROM then install it by clicking flash.bat. The instructions on the page are pretty easy to follow.
No need to deal with the NvFlash until AFTER you do the above procedure. You will need to run it again after the above procedure because it puts it back in the original state (pretty much). The NvFlash will give you the superuser and Clockmod back. You should be good to go after that.
There is no way u can brick the g2x......even if u wanted to.........keep messing around
Sent from my cm_tenderloin using xda app-developers app

Accidentally deleted boot partition

Hi guys, I really hope someone can help me.
I accidentally deleted the boot partition on my vodafone smart 2.
I was trying to install the original recovery that came with the phone before the OTA update2 using a tool from roeddie BUT, I forgot to put all the images in the same folder as the tool and the tool ended up deleting the boot partition without having a boot image to flash, and now I have a phone that is stuck in the white screen with the green android in the middle =(
btw, if I "reboot" if and quickly plug the usb cable in I get and unkown device in the device manager with this ID VID_0A5C&PID_2132&REV_0204
:crying::crying::crying:
With the program that you flashed it with can't you just download all the required sectors (boot, recovery, Rom) and just reflash?
Sent from my SGH-T999
No, the computer does not recognize the phone anymore =(
To my knowledge every Android phone has like a "apx or apb mode" or something of that nature(don't quote me on that lol) didn't you have to go on some sort of mode to use the application?
Sent from my SGH-T999
Yes, I had to power the phone holding volume down + power, but that won't work anymore =/
Ok now i had this happen to me with the Asus transformer tf 101 i flashed only the Rom and the tablet wouldn't even return on but it did go to apx mode, where the screen would show nothing, basically off, but with the right drivers my computer was able to recognize it and I flashed the boot.img, recovery.img, and Rom hopefully you should be able to do the same thing.
Sent from my SGH-T999
But the computer does not recognize the phone when I plug it, usually it shows something in the device manager, but now it shows nothing at all, except for when I quickly plug the usb cable right after it powers up, but apparently that hardware id is from some broadcom wireless something.
I don't know i never has experience with that phone , did you try to boot into recovery?
Sent from my SGH-T999
It was the first thing I tried, but I guess before it goes into recovery it needs the boot partition, which is gone.
I found this thread
http://forum.xda-developers.com/showthread.php?t=1144773
ALCATEL OT-980 /OT-981 recovery
On how to recover a bricked phone with "fast boot" hope that helps you good luck mate
Sent from my SGH-T999
Already tried this, does not work with this phone =(
But thanks for the effort.
I guess I'll have to go to the vodafone store in which I bought the phone and try to send it to repair.
Sorry man good luck
Sent from my SGH-T999
Just got home with my phone =)
Took the phone to a vodafone store at lunch, around 4pm got a text saying I could go and get my phone, I guess they have some mojo, voodoo or black magic to bring the dead back to life.
I think you probably messed up a step with the tutorial but at least you got the phone fixed how much did it cost you?
Sent from my SGH-T999
Nothing, it's still under warranty
Nice man congrats and if you try again make sure you have a recovery img available lol
Sent from my SGH-T999
having The same problem!
i'm also having the same problem with my xperia c3
it is bricked due to custom recoery and my boot partition has somehow deleted now i'm unable to boot up my phone any possible waysssssssss?:good:

[q] nexus 5 bricked in first 4 days sos

Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.

Android phone stuck on installation / Android guy mode after factory reset.

My Micromax Canvas Spark q380 was stuck on logo screen after something bad happened during charging. So I did a factory reset from recovery screen but now it keeps showing some installation mode with that android guy. After 10 mins or so phone switches off automatically and on restarting that installation screen keeps coming up. I tried vol +/- but unable to go into even recovery.
Battery is nonremovable. Phone is not rooted.
I am not geek so plz explain in detailed.
no one?!
Biker Biker said:
My Micromax Canvas Spark q380 was stuck on logo screen after something bad happened during charging. So I did a factory reset from recovery screen but now it keeps showing some installation mode with that android guy. After 10 mins or so phone switches off automatically and on restarting that installation screen keeps coming up. I tried vol +/- but unable to go into even recovery.
Battery is nonremovable. Phone is not rooted.
I am not geek so plz explain in detailed.
Click to expand...
Click to collapse
Do a Google search for:
"Unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
I found a couple links showing to flash stock rom on Micromax Canvas Spark but they looked fake so I went to service center and the guy there flashed the rom (not sure what he did) and reported that it did not worked and will have to change the hardware
Any suggestions?
Biker Biker said:
I found a couple links showing to flash stock rom on Micromax Canvas Spark but they looked fake so I went to service center and the guy there flashed the rom (not sure what he did) and reported that it did not worked and will have to change the hardware
Any suggestions?
Click to expand...
Click to collapse
Who knows, you didn't state the condition of the device after the service center flashed it.
Does the device have any signs of life, does it do anything, does it respond any kind of way, does it connect to PC, does it charge when connected, does the LED come on when connected? Anything at all?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Who knows, you didn't state the condition of the device after the service center flashed it.
Does the device have any signs of life, does it do anything, does it respond any kind of way, does it connect to PC, does it charge when connected, does the LED come on when connected? Anything at all?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Oh sorry to forgot mention about it.
The mobile is still in same condition (see pic in 1st post) wherein that green android guy keeps moving its antenna relentlessly.
So after I came home from service centre I tried to flash is myself (I choose Download only mode in sp flash tool). After flash the mobile tried to start up and showed that mobile is encrypting but it got switched off soon after. So I charged it for some time and switched on. Than it showed that since the encrypting process was interrupted, the mobile needs to reset so I clicked on reset.
Next I got same screen (with that android guy running) but with "Erasing" written at bottom. And after some time stock recovery screen appeared. Then I selected Reboot from there and on start up the mobile again went into that screen with android guy.
Now I think I will flash again in "firmware upgrade" (will it make any difference?) mode. But waiting for battery to drain out. Another problem is my battery is non-removable. So maybe it switches on while flashing?
Any thoughts?
Biker Biker said:
Oh sorry to forgot mention about it.
The mobile is still in same condition (see pic in 1st post) wherein that green android guy keeps moving its antenna relentlessly.
So after I came home from service centre I tried to flash is myself (I choose Download only mode in sp flash tool). After flash the mobile tried to start up and showed that mobile is encrypting but it got switched off soon after. So I charged it for some time and switched on. Than it showed that since the encrypting process was interrupted, the mobile needs to reset so I clicked on reset.
Next I got same screen (with that android guy running) but with "Erasing" written at bottom. And after some time stock recovery screen appeared. Then I selected Reboot from there and on start up the mobile again went into that screen with android guy.
Now I think I will flash again in "firmware upgrade" (will it make any difference?) mode. But waiting for battery to drain out. Another problem is my battery is non-removable. So maybe it switches on while flashing?
Any thoughts?
Click to expand...
Click to collapse
Yikes, it's never good when a device powers down during flashing or during first boot after flashing.
Seems to me that you might have hardware issues now since the service center couldn't revive it. You might need to replace the motherboard. Trying to recover it with software tools is probably just gonna be a wild goose chase and will probably end with things being worse which will lead to replacing the motherboard anyway so just save yourself the headache and go straight for replacing it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Yikes, it's never good when a device powers down during flashing or during first boot after flashing.
Seems to me that you might have hardware issues now since the service center couldn't revive it. You might need to replace the motherboard. Trying to recover it with software tools is probably just gonna be a wild goose chase and will probably end with things being worse which will lead to replacing the motherboard anyway so just save yourself the headache and go straight for replacing it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I think the service center guy was lazy. He did not even bother to remove my battery or let it die (since its unremovable). He flashed with mobile on.
I again tried flashing with sp flash with "download only" option and it showed download successful at the end of flash. Before starting the mobile, I charged the battery fully and then the mobile started with "Encyrpting mobile...." and it got stuck at 229% (how can something be more than 100%? .. anyways) for some time and then it company logo screen appeared. I let be like that for few hrs but then nothing happened.
Do you think I should flash again? Does appearance of company logo screen indicate any hope?
I am sorry if it's too much of trouble... but replacing hardware will cost too much to me and am trying my best if I could make my mobile work..
Biker Biker said:
I think the service center guy was lazy. He did not even bother to remove my battery or let it die (since its unremovable). He flashed with mobile on.
I again tried flashing with sp flash with "download only" option and it showed download successful at the end of flash. Before starting the mobile, I charged the battery fully and then the mobile started with "Encyrpting mobile...." and it got stuck at 229% (how can something be more than 100%? .. anyways) for some time and then it company logo screen appeared. I let be like that for few hrs but then nothing happened.
Do you think I should flash again? Does appearance of company logo screen indicate any hope?
I am sorry if it's too much of trouble... but replacing hardware will cost too much to me and am trying my best if I could make my mobile work..
Click to expand...
Click to collapse
If it powers on and tries to boot and can get to flash mode then yeah, you can probably fix it. But without knowing what got corrupted, it won't be easy. It's gonna take trial and error between adb/fastboot, flash mode and flash tool, etc.. you can try flashing or pushing the individual .imgs form your stock firmware one at a time until whatever is corrupted gets replaced.
Droidriven said:
If it powers on and tries to boot and can get to flash mode then yeah, you can probably fix it. But without knowing what got corrupted, it won't be easy. It's gonna take trial and error between adb/fastboot, flash mode and flash tool, etc.. you can try flashing or pushing the individual .imgs form your stock firmware one at a time until whatever is corrupted gets replaced.
Click to expand...
Click to collapse
Thanks @Droidriven for your leads.. I will check out what is adb, fastboot and .imgs

Categories

Resources