Database Info

[Q] HTC One S(ville) black screen, thats it... just a black screen, what can i do???

I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?

Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry

Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!

You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.

I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.

Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best

Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]

yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol

good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed

Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:

you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe

rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:

see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands

rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up

I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track

rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot

good luck on it

[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

[Q] Moto G Stuck on Boot

Hi. I've got the Moto G and i decided to unlock the bootloader and then download CWM. That all worked fine but now when i switch my phone on, it gets stuck on the 'Motorola by Google' Logo. It seems like its frozen on there but the power button is able to function, not the volume buttons though. Ive tried RSD Lite but it's not finding my device. I'm 14 so im not very good using a terminal but any guidance would be fine. I've also tried flashing the Paranoid 4.4.4 zip, The Stock Firmware zips and even Gapps but they all come up with the same message,
finding update package
opening update package
verifying update package
Installation Aborted.
Please could any one help me out and explain what went wrong with the phone? THANKS!

How?
burrt said:
You could flash the factory image by Motorola through ADB so it resets everything, I'm sure you can find the link somewhere in the forums (I'm using the 4G version so my method may be different slightly). I found rooting my phone very intuitive from the guides, only problem I had was making sure I had administrative privileges and access in the command window directory.
If I remember correctly, this will probably remove CWM and if you insist on a third party recovery, give TWRP, the problem could be related to CWM.
Click to expand...
Click to collapse
Could you tell me exactly what to do? i dont have much experience but ive downloaded the 4.3 and 4.4.2 Retail zips, extracted them and then opened CMD and tried things such as 'fastboot flash .....zip or image'. Still doesnt work and sometimes i get 'hab' errors and 'image is too large'.

Thanks
burrt said:
I'm not too sure about your problems, were you on Stock 4.4.4 running fine? I'm going to assume you are using the Moto G 3G version.
Although I haven't personally tried this guide myself, from what I see, it is reliable:
[GUIDE] Moto G - Restore stock firmware
Just a helpful tip when you open a terminal (took me a while to figure out when I first rooted my phone), located to the folder where they wan't the terminal and hold Shift + Right Click. This will give you an option "Open command window here", look carefully. Once again, make sure you are downloading the correct files for your device and read the steps carefully, you can minimise a lot of headaches and realise some shortcuts. It is also an 'old' guide so be sure to verify links etc.
Click to expand...
Click to collapse
Thanks so much for helping but i've done that, probably over 5 times. I am on Moto G 4.4.4 and whenever i flash stuff it gives 'hab' warnings and 'invalid piv' and 'image size too big'

[Q] HTC ONE M7 on 5.0.2 lolli w/ HBOOT 1.6 Help with root

Hello, I'm a noob with mild skill with jailbreak and mods. (WII,Windows,etc..) I unlocked my boot loader the other day. Apparently did not get S off. My phone now has the tampered message in the boot loader. Not really important to me because I own my phone. However I still need to root it and am not sure this will prevent me from accomplishing this. Does anyone know? Also cannot seem to nail down how to get root done or by who's instructions? Google search pulls up confusing info and I need specifics for my model correct? 3rd. Issue the recovery I used was from twrp which I festooned by computer and all worked great. Now however when I hit recovery and TWRP loads it is frozen. No touch commands work. I was told to flash newer recovery the same way I did first but command says error cannot load. So now I'm stuck. Phone works but it's not completed. Not sure which to tackle first. Please helps

You should list this is in the HTC one M7 questions forum... Not this one in order to get some help

Thank for the advice. New to xda and was not sure exactly were to go. Just fyi, i did find a resolve to my problem. Apparently I was renamining the twrp image files as I was directed to by another blog but I was putting img as part of the file name. When you are in the command prompt I was typing the file name exactly as it read but i was not adding a second img to the end of the command example: file name twrp.img has to be commanded as twrp.img.img. So infact i should of never renamed putting img at the end of the file name. It was causing confusion. So I renamed it twrp and thats it. really a Noob mistake and I shouldve known better. Anyhow I did reflash a updated twrp file and all is good and rooted now. Thanks

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!