Database Info

[Q] Soft bricked Half rooted nexus s! need help

Bootloader version I9020xxka3
Baseband version I9020xxkd1
Lock State - Unlocked
I followed the steps given on XDA forum to root my phone I was able to unlock the boot loader. But that's it. It doesn't go beyond it.
After selecting recovery, it did reboot but got the google screen with unlock icon.
Then splashed a installer screen, as if phone wants to install something and couldn't find it. Screen splashes an Exclamatory mark with in a triangle.
Now when I boot my phone it doesnot go beyond the google screen.
We all know, a lot of people have been facing this issue but how do we resolve it?
Is my phone useless or is there a way out? If we have genius devs who can rewrite the android platform I'm sure some dev can find a fix to this also.

I couldn't find a solution anywhere. But I brought my phone back to life.
Before you think of a root or ROM mod make a Nandroid back up.
SO here's the deal.
Why would it not work for me or you when root works for entire world?
It's sweet and simple, files we used were corrupted or USB drivers we are using, just don't fit.
So I looked around for best version of files we need like recovery.img or boot.img and repeated the process. If files are in good shape, it will work second time.
It's important you use same USD drivers which you used to find your way to get bricked else you'll keep getting "<Waiting for device>"
If nothing works (which I doubt) adb programming can push back the soul into the phone.
Heck, it ain't I-Phone ---- It's Opensource. Android doesn't die.
Hope it makes sense to a lot of people who be in a similar situation.

[Completed] Phone inoperable did nothing but followed steps.

Ok so I am unsure if someone is filtering out OLD topics but i keep coming across FORUM posts from people and it seems like they are getting no help or being referred to NON existent topics.
I just recently bought a HTC ONE M8 H/K from sprint. I have had android for a decade and am seriously tired of the ROOT it people. so I figured why not no down falls and everyone says it is easy. Well I am Murphy last name law and you people have not seen or know the things I am about to post
I recently spent over 32 hours watching video and preparing for ROOTING. I unlocked phone got Pilz touch recovery and everything worked fine. I even got CWM and SUPERSU and Busy box. all of which needed OTHER files to work properly. Again a few forced quits everything was fine.
I wanted to Switch to TWRP and the install didnt go through. however now I have BOOTloop. trust me this is the tip of the berg at this point.
Just short of finding NO help after another 24hrs binge session on the CPU and just shy of RUNNING MY PHONE OVER WITH A DAMN CAR>
I get oh so simple easy fix and the only posts I see are FIXED IT!!! so that helps me approximately as much as my phone helps me make phone calls currently.
After the boot loop SEVERAL friends versed in this so called ROOTING (which I still find to be a hoax and not actually possible by any means at this point and time.) and no one has any clue. Tried flashing ROMS RUU's everything comes back to NO will not work.
Then it brings me to the STOCK RUU config for the HK M8 which seemed like it was going to work through ADB flash but guess what. 2 hrs idle NOTHING. after that The recovery program dropped out and boot loader only stated RUU in the menu. (something never before logged in a forum or post as I can tell) after many attempts to do GOD KNOWS WHAT WITHOUT ANSWERS as i was about to smash my beautiful gold phone into a dozen tiny peices and claim accident the Recovery came back to...... You guessed it NOTHING. All directories are UNMOUNTED and cannot be mounted.
I am stuck. Seriously you all fix my phone or help i am willing to send gifts because I am out 700$ now on this nice paperweight but everything and everyone tells me. OH SO SIMPLE you have recovery it aint no thang.
Well guess what it is and I am tired of being so PISSED OFF for something that was so automated.
Again I am Murphy and what you attempt to get me to follow will come up with some REALLY weird repercussions I will post back.
Please oh mighty gods of ruining my life. Spare me this one thing I will never ask for another again.
How do I get my phone to just WORK, Simple. Right?

Hi there! I think I found a thread that can get you back on track. Please read every word carefully and follow every step. If you have further trouble or want to clarify anything, please ask in the thread. They know the device best and can help you I'm sure.
http://forum.xda-developers.com/showthread.php?t=2503646
I'm afraid that is the extent of what we do in the XDA Assist Section. We are guides...pointing people in the right direction when they can't find what they are looking for. Unfortunately we don't do hands on support in this section, so as I said....if you need a further hand, I am sure someone in the thread I linked can help.
And make sure anything you download and flash is for your model. And as always, do a Nandroid backup in recovery... before flashing anything new....it can be a lifesaver to help restore you when you hit trouble.
Good luck!

Details
Let me re iterate.
All guides are demanding S-Off (cannot as I cannot acess phone apps to do so)
All guides need HOME access for apps to modify certain things
I cannot:
Push packet through adb as they are unreadable
Get past boot screen
Recovery is only 40% operational with visibilty of phone only working sometime.
Cannot flash
Cannot push
Cannot fastboot
Cannot see device on CPU as it is stuck in recovery
ALL DIRECTORIES in /SDCARD have been removed
No Firmware
No RUU
No img
As far as I can tell.....Phone is empty and cannot be populated with anythin. I did manage to get SuperSu pushed through and installed. But how do I open it?
No ROOT access as well in the recovery.
I followed ALL STEPS of EASY guides even downloaded one button app that runs it all for me. Can't talk to phone does not see it in ADB.
The other guide I went to was helpful but I have already attempted all of those things.
With an empty phone NO DATA and no ability to get ADB to even run data over cable I am baffled.
I did exactly like the 500 guides i read said.
1) bootlock unlock
2)instal recovery (Philzmod)
3) get CWM (retrieved from playstore) Need a .zip to run in ADB
Phone worked fine until I changed from Philz mod to TWRP which never took place. Philz mod still runs but TWRP said it installed.
Now I have a completely worthless empty phone and I have cried about a tub worth of tears over the 700 i will be dropping over the next year for a piece of metal.
Oh and 99.9% of time if ADB DOES do something either no directory once pushed, cannot read or cannot FIND/Open directory stating BAD installation aborted I NEED a better recovery

I understand your frustration. Not a fun situation at all.
As I said, XDA Assist is here to help navigate the website. Not to troubleshoot I'm afraid.
The purpose of XDA Assist... http://forum.xda-developers.com/showthread.php?t=2764768
The very best place to ask for help in your situation is right here, in the Q&A section for your device... http://forum.xda-developers.com/showthread.php?t=2764768
The people there know your device best. Start a thread that's to the point, polite and accurate....what is exactly wrong, and the exact steps you took to get there. And hopefully help will follow.
Hope it can be solved for you!

How to find stock ROM files for my BL unlocked XT925 with no backups?

First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )

only one stock kitkat rom for XT925 ! i'll upload this for you !

You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

Installing TWRP per instructions and now phone DOA...

Hi all,
I've been ROM'ing since 2013 on multiple devices so I am somewhat familiar with adb/fastboot flashing and commands, what to do, what not to do, etc.... I just picked up a used pixel and first thing I did was unlock the bootloader - no problem. Next I go to root, so I began following this tutorial https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/ , as instructed I DL the required drivers, image files, patch file etc...and follow this tutorial for installing TWRP https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ , I get to step 8 and instruct via the command window to fastboot boot twrp.img, just as instructed. Everything appeared to be going the way it should as it started to boot to TWRP but almost as quickly the phone just died. I mean dead as a door nail. It won't do a thing. It won't even charge now. I have never had a phone just die like this. I fear I have met my first true full on brick.
I mean, yeah, I have soft bricked phones many a times but always had a backup to restore or was able to dig my way out one way or another but that was explainable by messing with questionable ROM's or something similar. Here I was just booting to the phone specific most recent version of TWRP by a solid well known tutorial with solid links, no indication that these could be the wrong images or zip's at all....but I'll be damned if this phone is dead as hell. I'm hoping someone can shed some light as to what happened or even miraculously tell me that it can be fixed.
Guys, is this a worst case scenario full on brick with no hope or getting it back to life? If so, why? Where did I go wrong? If this is going to be what I fear it is I hope to at least understand how it happened so I can avoid it in the future. This was a very expensive F-up on my part. I am beside myself with grief and disbelief that I could have done this with as many times as I have unlocked bootloaders, rooted, installed TWRP, flashed ROM's, etc.. I mean I 'm not the best but I am not a noob by any means. I feel like such a dumb ass right now!
Appreciate any help or explanation anyone can offer. Thanks.

We don't flash avb or any other patches anymore and haven't for like an android version and a half. For future reference look for more current information when modding a phone and for simple things like root guides go to xda don't just ask Google.

@kerryh420,
Those are some pretty old tutorials!
After plugging in the charger and wait for say 10seconds, can you boot into bootloader with button combo?
(Power + volume down or power + volume up for recovery as alternative)
Cheers
Sent from my Galaxy Tab S2 8.0 using XDA Labs

No offense, if you've been ROM'ing since 2013 you'd know not to go to other websites for tutorials! XDA is your best friend to follow instructions on Rooting, Flashing a recovery, and etc! Sorry that happened to ya. If it's literally dead you're probably out of luck and I know that's not what you want to hear. My best advice is to not follow tutorials on other websites. Good luck on your next device!