Database Info

[SOLVED] (Soft?) Bricked nexus 5? Seeking expert input - please

EDIT:
SOLVED! Thanks for the support!
In the end I decided to flash back to stock factory image from Google downloaded at the following link (https://developers.google.com/android/nexus/images) and installed using the very easy method of inputting a single command. Exactly the kind of solution I needed after pulling hair out.
Hopefully this post is of assistance to others in need.
In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211
Original question:
Need help - I think I bricked my Nexus 5 (was running KOT49H stock ROM). And would really appreciate some sage advice now to get me out of trouble.
Not my first root, custom ROM experience - have done on 3 previous devices, but first Nexus 5 and first stuff up for me. Not a complete noob, but please be clear in your advice. Thanks.
I "followed" this guide (http://www.teamandroid.com/2013/12/10/root-nexus-5-android-442-kot49h-kitkat-install-cwm-recovery/2/)
However, at Step 13-15 I was unable to mount an SD card (Nexus 5 is all internal), and I then opted to sideload the UPDATE-SuperSU-v1.80.zip file using "adb sideload". It is now stuck in a boot animation loop (say 10mins of waiting?). So what has gone wrong here?
I also guides from the same site to unlock bootloader and install CWM - that all worked.
I am able to get back to the bootloader and can get into CWM still, just cannot boot.
Not sure if my phone is charging, but I believe I still have some juice so looking for a solution. Have I somehow replaced all of the ROM software with just the SuperSU file? Is that possible? This is my first outing with the Nexus 5 but I have rooted and custom ROMed many phones before, but this is my first with no external SD card.
I could not mount any / partition from what I could tell.... such as /data (not sure if this helps your advice?)
In another thread, someone mentioned a catch all solution might be this : http://forum.xda-developers.com/showthread.php?t=2513701
As I said, I can get into the bootloader and CWM and phone is still recognised by PC.
If I am not mistaken, this would basically sideload everything back to factory?
Would this matter if my phone was at KOT49H before everything went wrong, or will that just come down via OTA later anyway (I was getting OTA updates just fine).
I think I should still have about 50% battery charge, but I don't know if it is charging (nothing shows) and the battery is completely internal on these.
Your help = much appreciated! Please - its Christmas afterall...
Cheers Adriaan

Sorry to hear about your troubles! I know how frustrating it can be when you softbrick for no apparent reason. However, the fact the phone still boots into recovery and all that means that there shouldn't be anything we can't recover from. The link you provided would work. You might also check out one of the toolkits that helps automate most of the stuff you are looking for, like this: http://forum.xda-developers.com/showthread.php?t=2525026 .
That being said, me personally, I would attempt some fixes via CWM first (though I much prefer TWRP). It could be something as simple as wiping the caches and fixing permissions. Possibly a factory reset could help, though I suspect probably not at this stage. Are you comfortable with manual ADB and fastboot commands? I would download a rom zip and adb push it to /sdcard, perform resets and reboot. Should be fine at that point and rooted to boot. If you're all about the stock root experience (never really understood that, but to each their own ) then try this: http://forum.xda-developers.com/showthread.php?t=2557523
Once you would download that, and are able to get ADB access in recovery (should work if you have the right drivers and all - if not, would recommend switching to TWRP) then you would use this command:
adb push rom.zip /sdcard/ - where rom.zip is the name of whatever that one downloads as...
Then wipe factory reset and caches (system too if you want to be thorough) then install the rom and reboot. Should be back to where you want.
If you would like some more 1 on 1 type help, feel free to hit me up on Hangouts with this username. Good luck!

You can flash the factory images directly from Google which should get you back up and running again.
Download and extract them.
Boot your phone to the bootloader and plug into your PC.
Run the flashall.bat
Note that this will fully wipe your phone
Sent from my Nexus 4 using xda app-developers app

First reboot recovery and factory reset the phone. If it boots your good. If not install the google factory image.

Everyone, thank you for your input. My phone is back alive and well.
In the end, I decided to flash all back to a stock factory image from Google. Only had 1% battery left by the time it booted into the fresh flash. Figured this was the best place to recommence my efforts to gain root again, and hopefully this time with a better outcome.
I will probably give the chain fire auto method a shot this time, after a bit more research.
Thank you again for your help and for the very quick responses. Great community.

In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211

[Completed] HELP! LG_Home launcher deleted and phone bricked

I was trying to free up space and saw LG Home was taking up some space. Never knew it was a critical launcher. Ive tried millions of methods on various sites including xda, android forums, android central with no luck. Here is a rundown of the situation.
1. I had clockwork installed then it "disappeared" adb reboot recovery stopped letting me go to the clockwork bootloader
2. I have a custom ROM sitting on an sdcard called Cyanogen.zip Its never been messed with yet.
3. I do not have a "nandroid" backup or backup of the stock rom because clockworkmod never worked
4. Doing a factory reset did not fix the issue because apparently the OS runs live off the rom aka it never installs itself to the device like in WIndows . SO I get a total black screen setup screen with only a signal bar on top.
So the latest thing ive been trying is adb pushing a copy of LG_Home into the /system . This is not working because im getting a "permission denied" . Now before you get hasty please do not have me do these commands:
1. mount /system already did this back when doing clockwork
2. remount -o ,rw does not work, probably due to already having root
3. adb root tried it and it doesn't really do anything, I still get permission denied, and usage errors
This does not make sense because the phone is rooted (does factory reset take away root? ) , chmod 777 has been applied to /system . If I lost root doing a factory reset, is there a way to root the phone now that I don't have a functioning phone?
Here is what im aming to do with your help
1. Force the LG_Home.apk file into the /system
2. Force some way to get cyanogen mod installed as I now have a corrupt stock rom
Something has to work and im hoping someone will help me

Hi,
I would need to know your model of LG to point you in a direction to ask for help.
Thanks!

Darth said:
Hi,
I would need to know your model of LG to point you in a direction to ask for help.
Thanks!
Click to expand...
Click to collapse
sorry hah, its an LG Enlighten

OK, Unfortunately there's no section for your device on XDA. You will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

Thank you. Thread closed.

[Q] Stuck booting

Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag

You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!

Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)

shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.

berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington

When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.

shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.

Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag

Rooted and bricked without a custom recovery.

rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.

XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!

joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man

jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.

joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot

jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!

Google Pixel XL - cannot get past bootloader/Android Recovery

I'll start off with an apology, as well as a thank you to anyone willing to read this
Google Pixel XL: bootloader has been successfully unlocked and I had TWRP installed successfully at one point but I wiped data/factory reset from Android Recovery as an attempt to get any where beyond this only to make things worse. I've downloaded factory images, OTA, etc and tried a few different commands with ADB but only get the return error message "error: device '(null)' not found"; I think that started occurring after updating 'latest_usb_drivers_windows'. Even tried uninstalling those drivers and re-installing, no luck but it's possible I messed something else up at some point.
Sorry for the lack of information, I'll be happy to provide any pertinent information if anyone is free to assist. First rooted device was a Nexus 6P and that went well and instantly fell in love, probably shouldn't have attempted the systemless root method this early in my career lol.
P.s. I did look through some forums and there were some similar but I haven't been able to replicate any of those with success; there may not be hope for me after all.
Update: I was somehow able to get back into TWRP, but when I attempt to install a recovery image I get the following error message: "Failed to mount '/vendor' (Invalid argument). Maybe now that I'm back in TWRP someone has some ideas?
Update: I'm back in, this can be closed.