Develop Bugs

[Q] Gnex wont boot. Cant flash from fastboot (too many links error)

CDMA GALAXY NEXUS> Hey guys, I was running Romanbb's 4.0.4 build earlier today. I clicked on a video (which may or may not have been on a porn site) all of a sudden my screen went all wacky. Where it was kind of fuzzy and running diagnal across the screen. I could only see part of it. I thought I might have gotten a virus or something because i have never had one of my devices do this before. So I immideatly rebooted the phone into recovery and wiped eveything including formatting system. I went to flash a nandroid I had of black ice and in the middle of flashing that my phone rebooted itself and stayed there (bootlooping at the google logo) I can get into fastboot and I can get into recovery about one out of every ten times but I cant do anything in recovery because the phone turns itself off insted of booting recovery most of the time (I have clockwork touch) When I do get into recovery without it turning off it reboots if I try to flash anything. It seems to be stable in fastboot (thank god!) but When I get it connected in Wugs Root tool kit and try to flash the stock image it goes through the motions and says FAILED on every step exept the first (which I believe is checking radio). It says ( error too many links) on the first two) and I cant remember the error on the last four but I have tried it a couple times so I can replicate it if needed. Can anyone tell me what to do from here? I really appreciate in advance!!! If this is a hardware error then I would like to get it back to stock to get it replaced. It is weird that it happened while running a rom. Its not like I messed up while flashing or anything.
ADB will recognize it in Fastboot. I already set all of that up when I rooted. when I try to flash the stock+unroot option on wugfresh's toolbox it errors out on every step like there is something wrong with my internal sd on my phone? Im wondering if I should try odin. IDK? Im hoping somebody who has seen this or had this happen before will save the day and tell me what to do.

lol why did you rush into CWM and start wiping things? you should have let it reboot and it probably could have been a one off..
you can try this http://rootzwiki.com/topic/14145-od...actory-odin-restore-402-with-radios-unrooted/

It is stable in fastboot but in cwr it is still geeking out
It still is glitching in cwr. most of the time it either turns off or reboots when I try to go into cwr. i can wipe but if I flash anything it freezes at the point where it starts writing to storage. I have never seen anything like this before.

I have now tried oden as well
It looks like it is a problem with the hardware. The phone is only a couple months old if that. So I really wish I could flash the stock image or at least get rid of cwm. but that is not looking likely. Here are a couple pics of odin showing the problem. Any guidace would be much appreciated. This SUCKS

Why in the heck are you trying to use Odin?

I can only get into fastboot and odin.
CWM wont let me do anything. it crashes and reboots into a bootloop if I try to flash anything. The poster above suggested odin. I dont know what else to do. Please help if you can!

Can you get a screencap of when it fails fastbooting the stock images?

yes
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now

drumdestroyer said:
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
Click to expand...
Click to collapse
How are you attempting to access fastboot?

Vol + and Vol - and power all at the same time
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.

That screen says you (now) have a corrupt partition.
At this point, you must use Odin, which is unfortunate. What URL did you use to download the image? The current image in that thread was on multiupload.

drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.

I downloaded the one later in the thread
Here's the Modem: http://dl.dropbox.co...15.EK02_LTE.tar
Here's the System: http://dl.dropbox.co...L53F_signed.tar
from this thread on page 3 housry23 posted them from his dropbox:
http://rootzwiki.com/topic/14145-od...restore-402-with-radios-unrooted/page__st__30
there were a couple other posts right around the same time with it but they all were the same file name
I thought I saw the same files in the xda thread i found also
I used that thread because it is the one that the second post linked for me.

drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium

loveubuntu said:
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
Click to expand...
Click to collapse
no luck with that. it seems to only open to the "corupted partision" screen. Thanks for the suggestion.

ljwnow said:
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I pm'd you to ask how you could fix it. Just wondering if I could do it. I can follow instructions well. I have never had a problem and have been flashing stuff for a year or so. IDK what happened here.

I can't help but I wanted to share that I had a similar experience. I was bonne stock and clicked on a you tube video and my phone immediately shut down and tried to reboot itself, but only would boot loop. I had to manually reformat my partitions to recover. Sounds like your case might be even worse. Still don't know what my problem was.
Sent from my Galaxy Nexus using XDA

Thanks. Any feedback is appreciated.

so you can't get into bootloader or odin screen any more? if so try using a Jig it works to get the phone into odin mode for me. i used the same usb jig i made for the captivate.

I got the same suggestion from someone else. I have to wait until radio shack opens in the morning and I will give it a shot. Otherwise, I went by verizon and they are having samsung send me a replacment. I would much rather keep this one if I can though
I tried flashing the stock image from fastboot and it failed though when I could get there, and I also tried flashing the stock image through oden when I could get there and both failed multiple times so I don't have much hope. I think something broke.
I am headed to radio shack now. Be back soon with a answer as to wheather I can save my baby or not.

[Q] Another Bricked Kindle

To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?

Could you post what you did or tried to do that bricked it?

99 times out of 100 rebooting will fix the "waiting for device" problem, especially if the PC drivers are installed appropriately, but I'm guessing you already tried that. I'd do it a few times, why not?

Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.

soupmagnet said:
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
Click to expand...
Click to collapse
Win7 64bit Ultimate
Stock
It's a clean kindle with nothing on it that got bricked while I was rooting it, some how.
My experience is really only a 1 time root when i first bought it back in January.
Very familiar with my OS.
Average with command line interface

Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?

nchevaux said:
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
Click to expand...
Click to collapse
it stays on the kindle fire logo until i hard reset it.
I was using KFU when this happened.

Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"

soupmagnet said:
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
Click to expand...
Click to collapse
how am I supposed to put it on the kindle... Did you not read my other posts?
It won't let me do ANYTHING to it.

Did you install the drivers from kfu with your kindle plugged in?

needhelpplease3 said:
how am I supposed to put it on the kindle... Did you not read my other posts?
Click to expand...
Click to collapse
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
needhelpplease3 said:
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
Click to expand...
Click to collapse
Don't make a long story short. The more information you can provide, the better.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Click to expand...
Click to collapse
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.

soupmagnet said:
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
Don't make a long story short. The more information you can provide, the better.
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
Click to expand...
Click to collapse
Sorry, I've just been really agitated by this whole situation. I've asked another forum and got back with horrible answers.
To start all over again, this is what happened.
I had my kindle fire at 6.3, unrooted (only unrooted because of the update), and decided to why not root it again, just so it's updated.
I got all the necessities to root the kindle, the same things I used when I first got it, and started up the process.
At first, the drivers were giving me issues, but that got settled quite quickly.
Then when I started up KFU, I did the perm root, but it somehow got canceled in the middle of it, so I'm guessing that's what has screwed it up.
Now when I plug it into either my Wall or USB adapters, it doesn't work.
I've tried that hard reset way, where you hold down the power button for 30 seconds, and that didn't work either.
So I got fed up, and came here for answers.
Right now, it's basically a dead Kindle Fire.

Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152

soupmagnet said:
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
Click to expand...
Click to collapse
Great... I'll try it. I'll tell ya what happens. Thanks

just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.

needhelpplease3 said:
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
Click to expand...
Click to collapse
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?

soupmagnet said:
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
Click to expand...
Click to collapse
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?

needhelpplease3 said:
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
Click to expand...
Click to collapse
Stop! before you screw something up.
More to follow....

soupmagnet said:
Stop! before you screw something up.
More to follow....
Click to expand...
Click to collapse
You're confusing me.
More to follow?

When I asked you "What happens when you try to power the device on?", I'm looking for specifics, i.e. "When I press the power button, nothing happens and the screen doesn't come on at all", or "The screen comes on, but the boot logo flashes on and off", or "The screen comes on, but hangs steady at the boot logo".
It is very important that you make this clear from the very beginning because it will help us in not telling you do do the wrong thing and potentially causing serious harm to your device.
I'm getting conflicting symptoms from you and it is making helping you rather difficult. If your screen doesn't come on at all the only fix for that starts with the "shorting trick". When you say that your screen was turning on and off it makes me think that it was doing that all along, which would require a completely fix.
If I'm going to help you I need to know exactly what is going on with your device along with any changes it has made and when they happened.

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

[Q] Trouble with LG G2 (Sprint)

Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care

well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands

Trippinshrumes said:
Hello Im Terry
Well this is far from my first root and flashing roms to phones....
i recently got a lg g2 sprint device 4.2.2, and of course i came here to root it, now the root was simple went through fine using a method i found here on the site... after this i wanted to put a different rom on it... well i installed twrp recovery, then i was trying to boot up into recovery, it wouldnt work at all whatsoever, wether i tried turning the phone off and holding the power and volume down button, releasing when screen turns on for a second then pushing them both again... this would just load the normal sprint screen, so i would try through the twrp program to reboot into recovery and the exact same thing happened.....so i googled it and i found this method to "supposably" fix it...
teamw.in /project/twrp2/197 <----- sorry about the space there but the forum wouldnt let me post the link and i cant describe what i did to cause my problem if i cant post this link.
i used the method here with the file for sprint phones.
now after doing this i tried to reboot into recovery mode using the power and volume down method, still nothing, so then i tried through the twrp program, well what happens is a screen comes up, which when ive searched this its only people that cant get past this screen and there phone is soft bricked.... [470] fastboot mode started and on the line under that it says [520] udc_start()
this is a black screen and it stays there.... now i found a file here that a guy put on the phone to help get wifi working, which i can be happy with the phone if i cant figure out how to put a rom on the phone if i can atleast be able to tether my phone since that is one of the main reasons i root, well when i tried to flash this file using the twrp program with the phone on it rebooted to the black screen with fastboot and udc_start
so basically i cant get into recovery mode at all, and i havent been able to this entire time, i could never even get to the initial sprint option to erase all settings holding those 2 buttons down.
now obviously i want to fix this, i want to figure out how to get into recovery mode. and i just got this phone from sprint 2 days ago so it already has the sprint spark update, im not sure if that what might be causing all of this if its incompatible with sprint spark or not... i know the 1 rom i looked into said it was incompatible with it, but i didnt see anything with the others....
so after figuring out how to get into recovery mode and fix my recovery mode can someone please tell me which of the roms that are currently out for my phone are compatible with sprint spark if any. thanks so much and i hope somebody can help me. have a great day and take care
Click to expand...
Click to collapse
Since your phone is only new, have you tried calling the tech support of Sprint? Or have you tried going to Sprint store to help you out with that?

to the post above me... yea that sounds like a great idea, hey sprint can you help me root my phone so i can tether without you charging me? thanks guys!... can you please not troll? if you're not going to help you dont have to respond. Thanks!
so i followed this post now, what i didnt do was patch loki on the newer vza firmware.... so i followed this thread here which is supposed to fix that... and yet im still having the same thing, btw as i posted the change in commands before its because i had my phone plugged into my computer that it showed me that.
forum.xda-developers.com/showthread.php?t=2522965
im not sure what im doing wrong here, but as i go through this i will surely document it incase someone else runs into the same problem in the future.
thanks for any help in advance

i made a mistake when i was doing this.... after everything when it says to use flashify to find the file... it wants you to find what is now the updated twrp 2.6.3.3 version and flash that as the last step... this is now complete. if anyone else runs into this in the future hopefully you dont do something slightly stupid like i did. thanks again xda developers cuz your all some genius ass people with all this info here

Trippinshrumes said:
well just a quick update, i uninstalled and reinstalled twrp now this is what i get when trying to boot into recovery from the app
[470] fast mode started
520 udc_start()
690 - reset -
700 -port change-
890 STALL GET_DESCRIPTOR 128 6 1006 0 18
60710 fastboot: processing commands
Click to expand...
Click to collapse
Turns out you have to downgrade your ABOOT, I had the same problem .. ...
http://forum.xda-developers.com/showthread.php?t=2627765
Follow those instructions to downgrade to zv7-aboot.img, then use FLASHIFY to flash the TWRP recovery image .. ...

also, the problem i was having with booting into recovery is i just have to hold the power and volume down buttons till i get the recovery menu.... not let go when the light comes on like a bunch of things say....

also if anyone knows, it says the d3rp g2 rom doesnt work on spark that it will guaranteed brick my device, now i have it fully backed up and i could just do a test run and see... although i dont feel like having to mess with that....
has anyone successfully flashed d3rp to the spark version? and if that is incompatible none of the other roms mention anything about it.... so if someone could tell me which roms do work on the spark version i would appreciate that...
also +1 to the guy that offered help after i figured it out. i appreciate it!

HTC One M8 - help needed

hi its been a week now that i have not had a phone i have tried every thing i just cant get to grips with all the file changing and one thing and another so if theres any one out there that can take over my phone and get back running again i am willing to donate, thanks for now john

borstalsmurf said:
hi its been a week now that i have not had a phone i have tried every thing i just cant get to grips with all the file changing and one thing and another so if theres any one out there that can take over my phone and get back running again i am willing to donate, thanks for now john
Click to expand...
Click to collapse
Someone responded to you in the other thread and you never said anything back.
You need to outline exactly what you did, and exactly what is happening on your phone. Speak in complete sentences. People can only help you if you explain your situation clearly, because we're not in the room with you.

you are asking for help ? do it in the Q&A section, its made for a reason
and as been said above, you got responded there so keep it there. not reading those helpful hints there yet making a new thread in the wrong section is not correct !

soft brick htc m8
thebobmannh said:
Someone responded to you in the other thread and you never said anything back.
You need to outline exactly what you did, and exactly what is happening on your phone. Speak in complete sentences. People can only help you if you explain your situation clearly, because we're not in the room with you.
Click to expand...
Click to collapse
hi sorry for not explaining myself, i down loaded the htc m8 tool box i was not sure what i was doing i was trying too root the phone i managed to unlock the phone , i still have s-on i can get into fastboot usb, and thats it, i cant get into twrp.if press to go into recovery it goes as far as the white screen htc in green and thats it, it dont do nothing else unless i do start button and up volume if i go volume down it don't do nothing, that's about all i can tell u john

borstalsmurf said:
i down loaded the htc m8 tool box i was not sure what i was doing i was trying too root the phone i managed to unlock the phone , i still have s-on i can get into fastboot usb, and thats it, i cant get into twrp.
Click to expand...
Click to collapse
You need to install TWRP, before you can boot into TWRP.
borstalsmurf said:
it goes as far as the white screen htc in green and thats it, it dont do nothing else unless i do start button and up volume if i go volume down it don't do nothingn
Click to expand...
Click to collapse
If pressing vol down during a reboot doesn't get you to bootloader, you did it wrong. You either started pressing vol down to late, or let go too early (don't let go until the bootloader screen appears). Just try again, until it works.