Develop Bugs

[Q] Son in trouble with pissed off dad about bricked KF!

OK, I have ready many posts and guides an am completely lost. This is my 12 year old sons Kindle Fire that he decided to "root". I am fairly computer savvy but this thing has got me baffled. He used "superoneclick" and now it tries to boot and stops at the kindle fire boot screen and goes no further. Any help on pointing me in the right direction would be appreciated. I do know this. The hard reset obviously does not work because I have tried that at least 100 times. My pc currently does not allow me to access it as a drive although it does show up. It sounds like a bootloader" problem? Again, please give me hand before I kill my son after telling him in advance not to do this.
Thanks
Forrest

Try and see if you can get KindleFireUtility to recognize your Kindle Fire
http://forum.xda-developers.com/showthread.php?t=1399889

Veeman, thanks I will try that and report back.

do you have fastboot?
type
fastboot devices in terminal and see if it returns your kindle number.
you are stuck in fastbootmode.
kfu will sort it out for you.
some more info would be of help.
what operating system on pc?
has your son got fastboot installed in sdk/tools or sdk/platform tools?
what stage was he at in the rooting process?
don't worry, has far as i know there is only one hardbrick issue at the moment, and that has to do with one type of recovery and doing a wipe/restore.
Sent from my Galaxy Nexus using xda premium

I understand your concern, and I don't mean to be out of line and tell you how to be a parent but...
If you're really computer savvy, you know that on the way there, you fudged some settings that made the computer unstable or unbootable. You installed programs, printers, a different way and had it not quite work out because you didn't follow directions.
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
What I would do? Work together with him to fix it. Show him what and how you're doing it, how you're asking for help (and that that's okay) and where to find what he needs to fix it.
You're not hard bricked, at least its unlikely, you're likely just stuck in fastboot which is not a big deal at all.
Just take it with a grain of salt. I know to when a kid breaks something it's "There goes X dollars" But sometimes, you have to break some eggs.
Good luck though.

Well, you came to the right place for guidance! I'm sure a forum search for "stuck in fastboot" would lead you and your son in the right direction. Unless there is a better way I'm not aware of, you will need to get adb up and running on a PC (which is most of the work). Then you will be able to get the kf out of fastboot by issuing commands from your computer's terminal/command prompt
But....
I think you should let your son do it... Especially if he plans on keeping his fire rooted. "Rooting" allows users to make changes to critical system files... On one hand this is really cool because it will allow your son to load custom ROMs (operating systems) and take full advantage of the kf's hardware....But, it will also make it very easy to royally screw things up.
So, if that's something he's interested in he needs to learn how to troubleshoot and fix things himself. You definitely came to the right place though... xda is a very sweet resource.
Goodluck!

http://forum.xda-developers.com/showthread.php?t=1668159

Update
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?

Firemancfd said:
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?
Click to expand...
Click to collapse
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip

Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.

Felnarion said:
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
Click to expand...
Click to collapse
True, but I think it's a tad different when you spend a couple of hundred dollars on something and specifically asked the lad not to do this one thing.

Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Try letting it sit while it "bootloops."
Might sound strange but I've had this exact same thing happen recently after a fresh install, and it loaded up back to normal after a handful of loops.

sbeddoesdesign, you are right i was upset not about the act but that he done it after i told him not to, then he lied to me about doing it. Either way, I have calmed down about it now and he is helping and participating. We are learning a lot together and its good dad/son time.
anomalya, i tried that and let it sit for an hour and no change.

FIXED
Thanks to all who helped. We finally got it to work correctly. Everyone was a big help and we appreciate everything.

I am glad that you got it working, but I am posting this for anyone else that can't seem to read or do a simple search. If you have the KFU all you need to do is have it running and restart your KF while connected the computer, and send the normal boot cmd when it first connects for those few seconds, and you are good to go, but seeing how too many people are to stupid to understand this, I believe that everyone should stop responding to them!!! We see this too often and everyone gives them this long work around...

kinfauns said:
3) Not all "stuck on bootlogo" problems are fixable with the KFU remedy you provided.
Click to expand...
Click to collapse
Are -any- such problems fixable with KFU? :silly:

Yeah, because 99% of the problems can be fixed by simply sending the command to start in normal boot you are offended and want to try and say I was saying something about you? If you are offended, then yu might be one of the people that can't seem to learn from the past!!!
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
BTW, seeing how most of the issues that fall under this, have been fixed in the exact way I described, it adds to my credit!

Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Blue Kindle Fire logo is FFF1.4a

Thread cleaned up and closed.

[Q] Kindle Fire is completely blank, except for TWRP

Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!

heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
Click to expand...
Click to collapse
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.

Sorry, but where do I enter these commands?

soupmagnet said:
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Click to expand...
Click to collapse
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?

heatherrc77 said:
Sorry, but where do I enter these commands?
Click to expand...
Click to collapse
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038

heatherrc77 said:
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
Click to expand...
Click to collapse
You need to download the Android sdk, then you can run adb from the command line.
Sent from my Amazon Kindle Fire using Tapatalk HD

heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory,
Click to expand...
Click to collapse
I know this isn't helpful now. But the original problem (I am pretty sure) had to do with the drivers with the audio. You probably had the volume all the way down, which causes the error you were receiving. If you mute it, that is fine, just don't have the volume down all the way.
----------------------------------------------
Sorry. I know this probably doesn't do you any good, but I thought I would let you know what I thought.

soupmagnet said:
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".

heatherrc77 said:
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
Click to expand...
Click to collapse
I put a lot of thought into how I should respond to this post, so bear with what I'm about to tell you.
My previous post was not intended to "belittle" you, rather, wake you up to the reality that you might not be ready to take on such an endeavor. This is not an iPhone and it isn't as simple as plugging it in and pressing a few buttons. For new users, there is a high degree of risk involved in certain aspects of modifying the Kindle Fire, especially when it comes to repartitioning...which is what you'll need to do to get your Kindle working again.
My harshness is NOT out of ego or feeling "holier than thou". It is not to make myself feel better or to make up for some low self esteem. Treating people with kid gloves around here tends to give them a false sense of security that quite often leads to them getting into very stressful situations. Besides, a little "tough love" is better than indifference any day.
I created a thread in the General forum a while back, titled "**WARNING** You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!!". The purpose of that thread is to warn owners of newer 2nd generation Kindle Fires of the DISASTROUS consequences of trying to modify those devices in the same way the 1st generation devices are. One would think, with a title like that, there would be very few people to make that mistake. Of course one would be wrong, as there are at least two individuals a week that were not prepared to deal with the situation at hand and did not give it the appropriate amount of respect, therefore their Kindles are completely worthless. Needless to say, if something I say is construed as rude yet prevents mishaps like that...so be it...and I'll consider it worth the hurt feelings.
And I agree, in order to learn, sometimes you have to get your hands dirty. But there is a big difference between tweaking some system files contained within a single partition and actually modifying partitions. And yes, you do have to start somewhere, but if you don't know that commands go in the command prompt (and I'm saying this respectfully), this is not the place for you to start. Go back, read through the links I gave you, and get a better foundation to work from before trying to fix your Kindle Fire. Not doing so, would do you a great deal of injustice.
No hard feelings,
And I wish you the best of luck.

[Q] Dead kindle after installing TWRP

hello everyone..i just rooted my kindle fire (non HD) everything went smooth and i was having trouble installing TWRP. i search and found a way of installing it manually since kindle fire utility wasn't letting me install it there. well i followed the steps and after i finished the device rebooted and never turn on again. i have pressed the power button down for minutes and minutes and there is no sign of life on that kindle.
is it bricked? can someone point me towards the right direction if they been through this. apologies if someone else have asked the same question but i have done my research and didn't find that same problem i have.

Having the same problem here. Exactly the same. Got a fastboot cable but that's not really helping.

1. What version was your kindle fire? KF1 or KF2? (easy way to tell i'm told is that the kf1 came in a brown box and the kf2 came in a black one.)
2. How did you root?
3. How did you install TWRP?
4. What OS are you running on your computer?
5. ???

Quoting from a thread I made about the issue
Right, I've received a Kindle Fire 2 for Christmas as a gift from the US (I live in The Netherlands), and by accident I managed to wreck it.
It worked perfectly for a while, but I hate the Amazon fork of Android, so I looked into getting Jelly Bean on it. I successfully rooted my device on 10.2.4, installed the Play Store, and then I decided I wanted more. I found a guide to flashing FFF + TWRP for Kindle Fire, unknowingly I didn't realize that that guide was for the original Kindle Fire, and _not_ for the Kindle Fire 2. This resulted in me messing up the partition layout of my KF2.
It doesn't turn on anymore, no matter how long I keep the power button pressed, the screen won't turn on and the power button doesn't light up either. Hooking it up to my computer running Windows 7 doesn't help either, adb can't find it, neither can fastboot. I bought a factory cable from SkOrPn to try to fix it, hooked it up to my computer again, still no response. Might be a driver issue on Windows though. I tried an Ubuntu live-cd with FireKit, and tried to boot my Kindle into fastboot, with the cable, no result.
I tried contacting Amazon myself, but they don't have a call centre over here, so I can't call for a replacement. I had a conversation with an Amazon employee in the US who told me I have to give the address of the person who gifted it to me, so they can ship a free replacement there. That would mean that person would have to ship it themselves my way, and that's not something I'd like to happen.
Basically, I'd like to solve it myself, but I'm unsure how to do that. Help?
Click to expand...
Click to collapse

plinders said:
Quoting from a thread I made about the issue
Click to expand...
Click to collapse
That sounds like company policy... and I think that means that you're sol... I'm sorry.

fmkilo said:
That sounds like company policy... and I think that means that you're sol... I'm sorry.
Click to expand...
Click to collapse
Nah, I thought I was a more elegant solution than just copy pasting the thread URL here, haha.
Figured as much, oh well. **** happens I guess.

plinders said:
Nah, I thought I was a more elegant solution than just copy pasting the thread URL here, haha.
Figured as much, oh well. **** happens I guess.
Click to expand...
Click to collapse
With the number of times I've bricked mine, I'm glad they offer free replacements...

fmkilo said:
With the number of times I've bricked mine, I'm glad they offer free replacements...
Click to expand...
Click to collapse
Yeah I know. As I've said earlier (in that quoted piece of text), I contacted Amazon, but they said I can get a replacement shipped to the person who gifted it to me in the US (over here in The Netherlands we don't have Amazon, and therefore no helpdesk lines), meaning the device would have to be shipped from there to here. And I don't want to put that person in that situation to be honest.

plinders said:
Yeah I know. As I've said earlier (in that quoted piece of text), I contacted Amazon, but they said I can get a replacement shipped to the person who gifted it to me in the US (over here in The Netherlands we don't have Amazon, and therefore no helpdesk lines), meaning the device would have to be shipped from there to here. And I don't want to put that person in that situation to be honest.
Click to expand...
Click to collapse
yeah...

fmkilo said:
1. What version was your kindle fire? KF1 or KF2? (easy way to tell i'm told is that the kf1 came in a brown box and the kf2 came in a black one.)
2. How did you root?
3. How did you install TWRP?
4. What OS are you running on your computer?
5. ???
Click to expand...
Click to collapse
Hello there..
1. i have KF2
2.i rooted with this guide..http://forum.xda-developers.com/showthread.php?t=2075959
3.installed TWRP with this guide...http://liliputing.com/2011/12/how-t...ire-backup-restore-flash-custom-firmware.html
4.Win 7

keepitlow13 said:
Hello there..
1. i have KF2
2.i rooted with this guide..http://forum.xda-developers.com/showthread.php?t=2075959
3.installed TWRP with this guide...http://liliputing.com/2011/12/how-t...ire-backup-restore-flash-custom-firmware.html
4.Win 7
Click to expand...
Click to collapse
you're in the same boat. installing the wrong device's stuff! I wish people would read. there is an easier way to install twrp...

fmkilo said:
you're in the same boat. installing the wrong device's stuff! I wish people would read. there is an easier way to install twrp...
Click to expand...
Click to collapse
i tried to install twrp with kindle fire utility but it was getting stuck and pretty much nothing was working for me. so does this mean the kindle is done?

Similar problem but mine worked for two days.
Twrp and running CM10. Everything running sweet for two days, the wife says she went to use it and it just wouldn't turn on. Power button is green and it does nothing.

recover
maybe you need to recover using a "factory" cable and "fastboot" search for it. grtz..
---------- Post added at 12:06 PM ---------- Previous post was at 12:01 PM ----------
hmm.. there's lots of stuff to read, one only has to find the right noob manual, so where to find the right working one?

wannalude said:
Similar problem but mine worked for two days.
Twrp and running CM10. Everything running sweet for two days, the wife says she went to use it and it just wouldn't turn on. Power button is green and it does nothing.
Click to expand...
Click to collapse
I also had this problem today, I performed a hard reset. holding powerbutton for 20 sec, It rebooted fine, it has since been working.

ROOT FAIL HELP PLEASE probably wrong spot but i'm new to android and i am panicking

i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.

UTubeMeBeach said:
i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2381582

http://goo.gl/lF0HEC
This is the driver you need to install to use ADB while in recovery which is different to the one for Fastboot and ADB while booted.

Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!

thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
OMG if this works ill pm you and tell you

thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped

UTubeMeBeach said:
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
Click to expand...
Click to collapse
If you insist, there should be a "Donate to Me" box next to my information on the left.

I had the same problem. Got stuck with no OS installed, USB debugging disabled, and no ROM I could flash. I was scared ****less but I ended up fixing it with a restore program.
Glad you got it fixed.

I learned how to unlock, root, flash custom kernels with my old nexus 7 before I attempted on my new nexus 7. Didn't want to make an expensive mistake. I looked at things here last year when I got my first n7, got confused and didn't attempt it. Now, I definitely won't go back to just stock. Hope you get it all sorted out! It was definitely scary for me the first time.
Sent from my Nexus 7 using Tapatalk 4

I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.

Geodude074 said:
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Click to expand...
Click to collapse
It's mainly the word "brick" that gets on my nerves.
Most of these are really just bootloops or boot hangs. My last one was the latter (and a little unsettling, I'll admit). Turns out that trying to flash a root zip before you've signed into the tablet at least somewhere to create the sdcard directories just leads to a headache for me.

I Have bricked my htc one m8

Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol

mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.

Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol

Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol

unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner

nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help

mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.

Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,

adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.

redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.

redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!

sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.

redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.