Okay, so I was on Sense 3, unrooted. I tried to root, but it had to downgrade me to GB. That went okay. Here's the issue.
After going through the whole root process with Gingerbread, Command Prompt said that root was successful(Not those exact words, but I remember myself thinking, "YES!"). Then, when it booted into the HTC screen, it faded away slowly and now it's a dim black screen. Nothing but that. Can I get some help from anyone?
Boot into hboot, volume down plus power button.
What does it say there?
More info....
http://forum.xda-developers.com/showthread.php?p=30020025
Sent from a dream.
Teichopsia said:
Boot into hboot, volume down plus power button.
What does it say there?
More info....
http://forum.xda-developers.com/showthread.php?p=30020025
Sent from a dream.
Click to expand...
Click to collapse
Sorry, I don't know much of the vocabulary, how do I boot into HBOOT?
Teichopsia said:
Boot into hboot, volume down plus power button.
What does it say there?
More info....
http://forum.xda-developers.com/showthread.php?p=30020025
Sent from a dream.
Click to expand...
Click to collapse
I can't do it. I press the V- and Power and hold and nothing ever comes up. All that's on the phone is the Orange charging LED. I'm pretty sure it's off now.
AndresGalvan98 said:
Sorry, I don't know much of the vocabulary, how do I boot into HBOOT?
Click to expand...
Click to collapse
When your phone's off hold volume down and power
Sent from my Inspire 4G using xda app-developers app
boss man Kole said:
When your phone's off hold volume down and power
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Yeah, I didn't put that together, sorry. It's off, but nothing happens when I do that.
AndresGalvan98 said:
Yeah, I didn't put that together, sorry. It's off, but nothing happens when I do that.
Click to expand...
Click to collapse
Sorry, forgot to mention the phone had to be off.
Pull the battery, wait five minutes, press and hold the volume down button, then press the power button. Hold both for a few seconds, should turn on in hboot.
Sent from a dream.
---------- Post added at 07:05 AM ---------- Previous post was at 07:02 AM ----------
Does the phone boot into the rom as usual? If it does, search for fastbook and uncheck it. It's either under development settings or battery or one of those.
Edit: I just went through your posts. Buddy, just read the whole guide I sent you. Try to familiarize yourself with it and you will be fine.
Sent from a dream.
Teichopsia said:
Sorry, forgot to mention the phone had to be off.
Pull the battery, wait five minutes, press and hold the volume down button, then press the power button. Hold both for a few seconds, should turn on in hboot.
Sent from a dream.
---------- Post added at 07:05 AM ---------- Previous post was at 07:02 AM ----------
Does the phone boot into the rom as usual? If it does, search for fastbook and uncheck it. It's either under development settings or battery or one of those.
Edit: I just went through your posts. Buddy, just read the whole guide I sent you. Try to familiarize yourself with it and you will be fine.
Sent from a dream.
Click to expand...
Click to collapse
Well it goes to the screen that says HBOOT in blue. On top it says "ACE PUT SHIP S-OFF RL" then some other stuff. If I do Reboot or Recovery, it goes to the same dim lighted screen. Should I do a Factory Reset then just try to root again?
AndresGalvan98 said:
Well it goes to the screen that says HBOOT in blue. On top it says "ACE PUT SHIP S-OFF RL" then some other stuff. If I do Reboot or Recovery, it goes to the same dim lighted screen. Should I do a Factory Reset then just try to root again?
Click to expand...
Click to collapse
Nope, cause you are already rooted. If you run the hack kit again, chances are you will mess something up. That is what the s-off means.
Why it goes to the dim screen, no idea. Read the effen manual, find out what is going on. This part is serious, read the effen manual. If you don't find the solution there, then go to the irc channel and ask for help. Be patient. If you requesting for help for something that is covered in the manual, you will be ignored and kicked from the channel. So read the effen manual.
That is, if the problem started after running the hack kit. If not, well, take a different route.
Sent from a dream.
You get this resolved?
Sent from my Inspire 4G using xda premium
No, not yet. I can't find anything in the manual
Sent from my Nexus 7 using xda app-developers app
AndresGalvan98 said:
No, not yet. I can't find anything in the manual
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can 100% confirm that the HK said "Attained root, s-off, and installed Clockworkmod" It's just after that that things got messed up. When I tried to turn it on normally this morning, the orange LED started flashing and it viberated 3 times. Nothing else except the flashing LED. I understand that if I had bricked it, the ugly Red ! triangle would come up, right?
Come on, I know SOMEONE can help! Please, people? I want to try to have it running AS SOON AS POSSIBLE, rooted or not. Is it harmful that I've rooted it before, then unrooted it? I unrooted less than a month ago, in case it matters. I wanted to use Blackout ICS, so I wanted to root it again.
AndresGalvan98 said:
Come on, I know SOMEONE can help! Please, people? I want to try to have it running AS SOON AS POSSIBLE, rooted or not. Is it harmful that I've rooted it before, then unrooted it? I unrooted less than a month ago, in case it matters. I wanted to use Blackout ICS, so I wanted to root it again.
Click to expand...
Click to collapse
Can you use adb from the blacked out screen. What happens when you plug it in to your computer after turning it on, does the pc at least recognize it. If so you can use adb to reboot it into recovery. Once there install a Rom. Seems you have no boot IMG at the moment which would be causing your problem.
Sent from my Inspire 4G using xda premium
---------- Post added at 07:26 PM ---------- Previous post was at 07:08 PM ----------
Have you tried pulling the battery for a few seconds too and then booting into hboot. It's probably a good idea to get into hboot first to confirm you have s off. Adb can be used to boot into bootloader as well.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Can you use adb from the blacked out screen. What happens when you plug it in to your computer after turning it on, does the pc at least recognize it. If so you can use adb to reboot it into recovery. Once there install a Rom. Seems you have no boot IMG at the moment which would be causing your problem.
Sent from my Inspire 4G using xda premium
---------- Post added at 07:26 PM ---------- Previous post was at 07:08 PM ----------
Have you tried pulling the battery for a few seconds too and then booting into hboot. It's probably a good idea to get into hboot first to confirm you have s off. Adb can be used to boot into bootloader as well.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Yes, I do have S-Off, the HBOOT screen says so, and so did Command Prompt. How do I get into ADB? I already have my preferred ROM on my memory card.
We need to see if adb can even recognize your phone. Use this guide to get adb running on pc. Boot phone as normal and let it go to black screen then plug into pc. From there type "adb devices" and it should list a device. From there type "adb reboot recovery". If you still can't get to recovery but device is recognized flash recovery again from aahk options menu from same black screen. And try the adb recovery command again. If you get to recovery report back as there is a trick to flashing blackout that I'll fill you in on so you dont end up back where you are. Aroma installer in blackout can cause issues if not done properly.
Sent from my Inspire 4G using xda premium
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Only follow adb guide to step 9
Sent from my Inspire 4G using xda premium
Gizmoe said:
We need to see if adb can even recognize your phone. Use this guide to get adb running on pc. Boot phone as normal and let it go to black screen then plug into pc. From there type "adb devices" and it should list a device. From there type "adb reboot recovery". If you still can't get to recovery but device is recognized flash recovery again from aahk options menu from same black screen. And try the adb recovery command again. If you get to recovery report back as there is a trick to flashing blackout that I'll fill you in on so you dont end up back where you are. Aroma installer in blackout can cause issues if not done properly.
Sent from my Inspire 4G using xda premium
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Only follow adb guide to step 9
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
It went into the HTC screen (not Quietly Brilliant), then did the same thing The touch buttons are lit now, what does that mean? Should I wait a bit? And I just checked, Blackout isn't on my SD card!! I SWEAR I put it in. It's not too late, is it?
Gizmoe said:
We need to see if adb can even recognize your phone. Use this guide to get adb running on pc. Boot phone as normal and let it go to black screen then plug into pc. From there type "adb devices" and it should list a device. From there type "adb reboot recovery". If you still can't get to recovery but device is recognized flash recovery again from aahk options menu from same black screen. And try the adb recovery command again. If you get to recovery report back as there is a trick to flashing blackout that I'll fill you in on so you dont end up back where you are. Aroma installer in blackout can cause issues if not done properly.
Sent from my Inspire 4G using xda premium
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Only follow adb guide to step 9
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Okay, I'm trying to reflash recovery, but where do I go to after Options?
Never mind, I was so nervous I didn't read it its currently flashing.
Update: It STARTED, but then it said Device not found, waiting for device. What now?? The ADB recognized it, and so did the hack kit at first.
You could try flashing recovery by this alternate method in this thread. You could also try and installing a rom via PD98IMG which is also covered is this thread.
http://forum.xda-developers.com/showthread.php?p=20382502
Once back to stock by Rom method you could just reflash recovery and then a Rom.
Sent from my Inspire 4G using xda premium
Gizmoe said:
You could try flashing recovery by this alternate method in this thread. You could also try and installing a rom via PD98IMG which is also covered is this thread.
http://forum.xda-developers.com/showthread.php?p=20382502
Once back to stock by Rom method you could just reflash recovery and then a Rom.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Before I read this, I tried flashing it again through AAHK again. It SEEMED like it finished. It said a bunch of things on cmd, then returned to the Main Menu without telling me it flashed. Then I pressed SOME kind of combo with the V & Power, and it came up to a screen that I didn't have much time to look at. It looked KIND OF the same as CWM, but I'm pretty sure I read the words Ace Hack Kit. What is that?
Another update: It was CWM, but the screen was flashing so I didn't know what to do. I know how to navigate around it(I was rooted a few months back), but I didn't have time do much before it completely exited and went to the usual.
Related
Hi, I tried flashing a new radio to my phone because the current one I had was draining battery really fast and I wasn't getting a good mobile connection. Well when I flashed it rebooted and it now it just stays stuck on the HTC screen. When I try to boot into recovery it just goes straight back to the HTC screen and stays stuck there.
Is there anything I can do about this?
Thank you.
What radio did you try flashing and by what method. Also have you tried a battery pull?
Sent from my Inspire 4G using xda premium
Gizmoe said:
What radio did you try flashing and by what method. Also have you tried a battery pull?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I tried flashing this radio 20.71.30.0833U_3831.17.00.16_M and I did it by using adb. I also have tried a battery pull but every time I start it, it just stays stuck at the HTC screen
toodazed said:
I tried flashing this radio 20.71.30.0833U_3831.17.00.16_M and I did it by using adb. I also have tried a battery pull but every time I start it, it just stays stuck at the HTC screen
Click to expand...
Click to collapse
That is definitely not an inspire radio. It's really a bad idea to flash anything but inspire compatible radios. It's the one sure way to brick a device. Is the phone recognized by your pc when you plug it in while its on the HTC screen?
Sent from my Inspire 4G using xda premium
Gizmoe said:
That is definitely not an inspire radio. It's really a bad idea to flash anything but inspire compatible radios. It's the one sure way to brick a device. Is the phone recognized by your pc when you plug it in while its on the HTC screen?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
When I plug it into the computer it makes the sound that it's connected and then I think it disconnects really quick, but the device doesn't even show up at all on my computer
When I plug it into the computer on bootloader mode it says something like USB bootloader. So I'm guessing my PC is recognizing it.
toodazed said:
When I plug it into the computer it makes the sound that it's connected and then I think it disconnects really quick, but the device doesn't even show up at all on my computer
Click to expand...
Click to collapse
Are you able to enter hboot at all or is that what you mean when you say you can't enter recovery? If you can still get into hboot load a PD98IMG of a compatible radio from radio thread onto sdcard and enter hboot and it will prompt you. If you can't get to hboot by volume down and power then see if adb will recognize the device by typing "adb devices". If it sees your phone type "adb reboot downloader" and select bootloader.
Sent from my Inspire 4G using xda premium
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
toodazed said:
When I plug it into the computer it makes the sound that it's connected and then I think it disconnects really quick, but the device doesn't even show up at all on my computer
Click to expand...
Click to collapse
Are you able to enter hboot at all or is that what you mean when you say you can't enter recovery? If you can still get into hboot load a PD98IMG of a compatible radio from radio thread onto sdcard and enter hboot and it will prompt you. If you can't get to hboot by volume down and power then see if adb will recognize the device by typing "adb devices". If it sees your phone type "adb reboot bootloader" and select bootloader.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Are you able to enter hboot at all or is that what you mean when you say you can't enter recovery? If you can still get into hboot load a PD98IMG of a compatible radio from radio thread onto sdcard and enter hboot and it will prompt you. If you can't get to hboot by volume down and power then see if adb will recognize the device by typing "adb devices". If it sees your phone type "adb reboot downloader" and select bootloader.
Sent from my Inspire 4G using xda premium
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Are you able to enter hboot at all or is that what you mean when you say you can't enter recovery? If you can still get into hboot load a PD98IMG of a compatible radio from radio thread onto sdcard and enter hboot and it will prompt you. If you can't get to hboot by volume down and power then see if adb will recognize the device by typing "adb devices". If it sees your phone type "adb reboot bootloader" and select bootloader.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Yes I can go to hboot. I will try that and post back.
Thank you for your help so far!
Nope still nothing. I tried putting 12.56.60.25x_26.10.04.03_M on there but it doesn't prompt me when I enter hboot
toodazed said:
Nope still nothing. I tried putting 12.56.60.25x_26.10.04.03_M on there but it doesn't prompt me when I enter hboot
Click to expand...
Click to collapse
Are you putting it directly onto root of sdcard and making sure its named just PD98IMG.zip. here try this one and just place onto sd card in no folder http://db.tt/pIbQBQgF
Sent from my Inspire 4G using xda premium
Gizmoe said:
Are you putting it directly onto root of sdcard and making sure its named just PD98IMG.zip. here try this one and just place onto sd card in no folder http://db.tt/pIbQBQgF
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I tried that and still no luck
toodazed said:
I tried that and still no luck
Click to expand...
Click to collapse
Well I would try and pushing the radio IMG contained in the PD98IMG via adb the same way you got the current one on there. But if your phone can't be accessed with adb then it may be bricked. Try adb from both the HTC screen and from bootloader to see if it will recognize it with the "adb devices" command. If it lists your device then you may be able to push the radio IMG.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Well I would try and pushing the radio IMG contained in the PD98IMG via adb the same way you got the current one on there. But if your phone can't be accessed with adb then it may be bricked. Try adb from both the HTC screen and from bootloader to see if it will recognize it with the "adb devices" command. If it lists your device then you may be able to push the radio IMG.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Well it may be bricked Earlier when I would plug the cable into the phone it would say like HBOOT USB but now every time I try it just goes to a black screen and the charge light stays on until I do a battery pull.
toodazed said:
Well it may be bricked Earlier when I would plug the cable into the phone it would say like HBOOT USB but now every time I try it just goes to a black screen and the charge light stays on until I do a battery pull.
Click to expand...
Click to collapse
You could try and selecting fastboot and then plugging in USB. If you can get it in fastboot USB then an ruu can be run. But it sounds like it may be done for. Sorry
Sent from my Inspire 4G using xda premium
Gizmoe said:
You could try and selecting fastboot and then plugging in USB. If you can get it in fastboot USB then an ruu can be run. But it sounds like it may be done for. Sorry
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Yeah that won't work either. I can load up fastboot but as soon as I plug the cable in it goes to that black screen with the charge light. I just don't understand why earlier in the day it worked doing that and now it doesn't
Thanks for all your help
toodazed said:
Yeah that won't work either. I can load up fastboot but as soon as I plug the cable in it goes to that black screen with the charge light. I just don't understand why earlier in the day it worked doing that and now it doesn't
Thanks for all your help
Click to expand...
Click to collapse
Did it work after you changed the radio?
Sent from my Inspire 4G using xda premium
Gizmoe said:
Did it work after you changed the radio?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Yes after I flashed that radio that was not compatible for it It was letting me go into fastboot USB now it wont.
toodazed said:
Yes after I flashed that radio that was not compatible for it It was letting me go into fastboot USB now it wont.
Click to expand...
Click to collapse
Try removing your sd card and then try again.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Try removing your sd card and then try again.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Nope still nothing
toodazed said:
Nope still nothing
Click to expand...
Click to collapse
Well I'm out of ideas. Maybe just leave the battery out overnight and back up and clear sd card. Maybe tomorrow you can get to fastboot USB again. I wouldn't get your hopes up though. Do you have insurance cause they may replace it for you (for a fee of course).
Sent from my Inspire 4G using xda premium
Gizmoe said:
Well I'm out of ideas. Maybe just leave the battery out overnight and back up and clear sd card. Maybe tomorrow you can get to fastboot USB again. I wouldn't get your hopes up though. Do you have insurance cause they may replace it for you (for a fee of course).
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Ok, I'll do that and no I don't have insurance on it. Thanks for all your help man.
I'll post tomorrow morning and see if anything changes
Btw is it supposed to say No image or wrong image whenever I go to Boot Loader?
My phone died and i didnt realize it was low and now im not sure why it wont charge. Anytime i put it on the charge it reboots into recovery and keeps doing that. I tried holding down the vol down several times to get into bootloader but it wouldnt go nor will it boot back on
Recovery
I was having a similar issue with the phone booting into recovery while charging. I flashed the latest TWRP recovery and it solved that issue. However, I have not encountered the issue with the device not being able to power up. I hate to recommend a full wipe if you don't have a back-up, but you can try the recovery first.
Hard power-off offers a workaround
Jayster06 said:
My phone died and i didnt realize it was low and now im not sure why it wont charge. Anytime i put it on the charge it reboots into recovery and keeps doing that. I tried holding down the vol down several times to get into bootloader but it wouldnt go nor will it boot back on
Click to expand...
Click to collapse
I am experiencing this as well. Battery runs out of charge and when I plug it into the power outlet, the phone boots into recovery. Selecting "reboot" in recovery doesn't work and the phone boot loops back into recovery. Some have suggested that using the "clear storage" option in recovery seems to stop the boot loops but I don't really want to clear my data every time the battery runs out. What works for me is to let the phone stay plugged in for about fifteen minutes (so it gets a little charged). I then press and hold the power button for about ten seconds. This causes the phone to power off completely. I then press and hold the power button to power up the phone (cold start). The phone boots up correctly although I get a message something like "the device encountered an error on startup, would you like to report the issue to HTC?" I choose NO.
This is very annoying and I can't seem to find out if it is in the recovery or if it is in fact a problem in the stock ROM.
ROM: T-Mobile Stock 4.0.4
Software number: 2.35.531.10 710RD
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes
skardcat said:
I am experiencing this as well. Battery runs out of charge and when I plug it into the power outlet, the phone boots into recovery. Selecting "reboot" in recovery doesn't work and the phone boot loops back into recovery. Some have suggested that using the "clear storage" option in recovery seems to stop the boot loops but I don't really want to clear my data every time the battery runs out. What works for me is to let the phone stay plugged in for about fifteen minutes (so it gets a little charged). I then press and hold the power button for about ten seconds. This causes the phone to power off completely. I then press and hold the power button to power up the phone (cold start). The phone boots up correctly although I get a message something like "the device encountered an error on startup, would you like to report the issue to HTC?" I choose NO.
This is very annoying and I can't seem to find out if it is in the recovery or if it is in fact a problem in the stock ROM.
ROM: T-Mobile Stock 4.0.4
Software number: 2.35.531.10 710RD
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes
Click to expand...
Click to collapse
Its the crap recovery you using. Flash TWRP and you should never have that issue again.
I had that issue too. I had to leave the phone in recovery, charging, for a few minutes, then boot it without the charger.
It's a known issue with cwm though I thought it was fixed a while ago. Had that issue on my g2 but was fixed. I wish 4ext recovery was an option for this device
Sent from my HTC VLE_U using xda app-developers app
Anyone who is reading and is panicking, for future reference just hold down the power button to do a hard shutdown. Do this about 4-6 times until it successfully boots up. As a rule of thumb, I never install anything cwm anymore.
Sent from my HTC Vision using xda app-developers app
Spastic909 said:
It's a known issue with cwm though I thought it was fixed a while ago. Had that issue on my g2 but was fixed. I wish 4ext recovery was an option for this device
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Its not been updated for over 6 months and the new one has all the same bugs.
Eddy130306 said:
Anyone who is reading and is panicking, for future reference just hold down the power button to do a hard shutdown. Do this about 4-6 times until it successfully boots up. As a rule of thumb, I never install anything cwm anymore.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Actually, just leaving it charging for a couple of mins in recovery and then boot it without the charger works even better.
Goatshocker said:
Actually, just leaving it charging for a couple of mins in recovery and then boot it without the charger works even better.
Click to expand...
Click to collapse
From what I helped with that don't always work.
Darknites said:
Its not been updated for over 6 months and the new one has all the same bugs.
Click to expand...
Click to collapse
Well that's wack..they fixed it for the g2 a year or so...
As the old saying goes if it's not broke don't fix it .
Still wish we had 4ext recovery for our devices. Think that's the only reason I quit rooting.. I know it's a matter of opinion but that recovery is awesome
Sent from my HTC VLE_U using xda app-developers app
---------- Post added at 08:18 PM ---------- Previous post was at 08:11 PM ----------
I stand corrected looks like madmaxx82 is working on it. Woo hoo
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Well that's wack..they fixed it for the g2 a year or so...
As the old saying goes if it's not broke don't fix it .
Still wish we had 4ext recovery for our devices. Think that's the only reason I quit rooting.. I know it's a matter of opinion but that recovery is awesome
Sent from my HTC VLE_U using xda app-developers app
---------- Post added at 08:18 PM ---------- Previous post was at 08:11 PM ----------
I stand corrected looks like madmaxx82 is working on it. Woo hoo
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Not used 4ext and what you mean about madmaxx82.
Darknites said:
Not used 4ext and what you mean about madmaxx82.
Click to expand...
Click to collapse
He's the developer of that recovery
Worked on the G2 and amaze perfectly better than any other recovery I ever tried even twrp... And I mean no disrespect to the developers of that recovery but 4EXT is amazing . Look it up and see what you think
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
He's the developer of that recovery
Worked on the G2 and amaze perfectly better than any other recovery I ever tried even twrp... And I mean no disrespect to the developers of that recovery but 4EXT is amazing . Look it up and see what you think
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Looks alright as long he gets it working as well as TWRP.
Darknites said:
Looks alright as long he gets it working as well as TWRP.
Click to expand...
Click to collapse
Does twrp have full on touch screen capabilities?
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Does twrp have full on touch screen capabilities?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes and it makes more sense CWM.
dc211 said:
Yes and it makes more sense CWM.
Click to expand...
Click to collapse
Word
Sent from my HTC VLE_U using xda app-developers app
thanks for the help and debate i eventually got it working somewhat but the the phone sim card reader stopped working
Hello... I was using CM nightly then i wanted to overclock my phone so i flashed this http://forum.xda-developers.com/showthread.php?t=2061577 Then everything was working fine but i wasnt able to enable the Wi-Fi it was grayed out on disabled.Then i wanted to fix it so i flashed another kernel(i will post what kernel about tomorrow it probably is for ICS)(yes im a noob i realised that later with an awesome facepalm)so... now im stuck in a black screen and i cannot hear anything from my phone. i cant boot it into bootloader and/or TWRP recovery there is only a black screen i can see that it works cuz if i have it connected on my laptop the laptop makes the USB connection sound and/or disconnection one so it is probably working (i tryed holding the power button for 10 and then VOL down to put it on bootloader after the 10 sec's my laptop made a sound but i wasnt able to make it work...) so im stuck here.
P.S.:I would really apriciate your help.Sorry for F*cking English Grammar
Thanasis,15,Greece.
man, you need to reduce your font
and you flashed a kernel for the one x
sorry about your situation, but you are going to have to read more stuff and more carefully
this happened to someone else forget solution if any
try a google on flashing one x kernel on a one s, unless someone replies soon
---------- Post added at 08:03 PM ---------- Previous post was at 07:57 PM ----------
btw i never saw much advantage to overclocking for me anyway
if you get this sorted, i would stay with stock kernels for now. have a nandroid and sdcard bu on pc.
i prefer twrp recovery, but not the latest one as it has issues
read all OP pages very carefully and i read first/last 20 pages or so of the thread
always include System as part of your full wipes
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
also, hold vol- then pwr at same time until the soft keys blink 3 times. release pwr but continue holding vol-
hold it down til phone boots--give it a minute
you can try using adb if you have that set up on pc
rugmankc said:
man, you need to reduce your font
and you flashed a kernel for the one x
sorry about your situation, but you are going to have to read more stuff and more carefully
this happened to someone else forget solution if any
try a google on flashing one x kernel on a one s, unless someone replies soon
---------- Post added at 08:03 PM ---------- Previous post was at 07:57 PM ----------
btw i never saw much advantage to overclocking for me anyway
if you get this sorted, i would stay with stock kernels for now. have a nandroid and sdcard bu on pc.
i prefer twrp recovery, but not the latest one as it has issues
read all OP pages very carefully and i read first/last 20 pages or so of the thread
always include System as part of your full wipes
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
also, hold vol- then pwr at same time until the soft keys blink 3 times. release pwr but continue holding vol-
hold it down til phone boots--give it a minute
you can try using adb if you have that set up on pc
Click to expand...
Click to collapse
will do/try all of your tip's
about the vol- and then pwr... this just doesnt work cuz the second kernel i flashed was for ICS and they wont light up if they were lightning up it would be easy cuz i cound access bootloader and then all fixed :crying:
Sorry OP, but it sounds like you're bricked. You see QHSUSB_DLOAD when you connect your phone to the PC? You flashed a One X kernel, which is probably why.
You can try the steps in the development unbricking thread.
yeah, don't sound good
you didn't say is you know how to use adb from a command window on pc
you could try rebooting bootloader from there as a try before unbricking
or go the jtag route
well i tryed accessing adb even when unbricken but couldn't manage to make it work... (tryed enabling it from developer options&usb mode) i read somewhere that JB 4.2.2 has an extra security level and it wont be supported by cyanogenmod 10.1
you don't access it you need to have htc drivers on phone and install the adb and fastboot files onto your pc. put hem in a folder of your choice with only them there.
you then open a command window on pc and cd to that folder and type "adb reboot bootloader" with no quotes
if you meant that, sorry i misunderstood
most people install the android sdk if they plan on doing a lot of adb/fastboot commands
So im stuck?
So im stuck? i cant do anything else i mean i cant get into the partitions and edit'em... probably not so my phone is over had it less than a month :crying:
xakersas said:
well i tryed accessing adb even when unbricken but couldn't manage to make it work... (tryed enabling it from developer options&usb mode) i read somewhere that JB 4.2.2 has an extra security level and it wont be supported by cyanogenmod 10.1
Click to expand...
Click to collapse
Wait, how did you even manage to et into developer options if you're bricked??
Sent from my One S using Tapatalk 2
usaff22 said:
Wait, how did you even manage to et into developer options if you're bricked??
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
no i got in there before bricking the device
xakersas said:
no i got in there before bricking the device
Click to expand...
Click to collapse
OK then. Have you tried the unbricking thread in the Android Development forum?
Some of the steps you don't need, since you are already bricked.
Sent from my One S using Tapatalk 2
here is the second kernel i installed (it is a donwload link couldn't retrive the download page i got this from google sync) http://www.mediafire.com/?acu5fiil0c4o0gu
usaff22 said:
Sorry OP, but it sounds like you're bricked. You see QHSUSB_DLOAD when you connect your phone to the PC? You flashed a One X kernel, which is probably why.
You can try the steps in the development unbricking thread.
Click to expand...
Click to collapse
hello im back yes i can see QHSUSB_DLOAD what can i do?
Edit: i see i got at the unbrick thread but stuck at step step 4 (Enumerating) i dont know which one is my phone's
xakersas said:
here is the second kernel i installed (it is a donwload link couldn't retrive the download page i got this from google sync) http://www.mediafire.com/?acu5fiil0c4o0gu
Click to expand...
Click to collapse
Yes. You flashed an unknown kernel, which just says CM10.1 nightly without reading what devices the kernel is for! It would be a good idea to check if it is for the One S, or Ville, since CM10.1 is available for more than 20 devices!
xakersas said:
hello im back yes i can see QHSUSB_DLOAD what can i do?
Click to expand...
Click to collapse
You shouldn't be smiling too much, you have a bricked device
You will have to try and recover your device using the thread below. You can skip the "creating the brick" section, since you already have a brick. DO NOT USE THE UNLIMITED.IO tool to reset the phone, since it will not work and make the situation worse.
http://forum.xda-developers.com/showthread.php?t=1990043
Hey guys,
first of all, my powerbutton stopped working some weeks ago. I thought that not much of a problem, so I remapped this thing and perfect.
I noticed, if I turn off my phone, take battery out and back in, it restarts instantly. Seems to be stucked at "ON" or something.
Well I also noticed without touchrecovery, it's quite a problem to navigate through cwm recovery.
But there's still fastboot... naaah I couldn't find the phone in Windows to install drivers, thought that's a problem of Win8, but after that I tried same thing in ubuntu with manually installed drivers... still nothing.
Okay next thing, is, there are so many apps in the market, which install some recovery, autoflash stuff... Did that, (yeah I gave root access and so on) and still nothing happened, I'm still stuck with this cwm recovery and can't install new roms.
Now my Question(s):
Is there an Option to install some new recovery?
Is there a way to get Fastboot working?
Is there a way to get the Powerbutton in this state back to work?
Or kinda best worst case, is there an option to get my Nexus back to Stock and unroot to send it in, I still got warranty but this would require stock phone...!
Thanks!
30floh00 said:
Hey guys,
first of all, my powerbutton stopped working some weeks ago. I thought that not much of a problem, so I remapped this thing and perfect.
I noticed, if I turn off my phone, take battery out and back in, it restarts instantly. Seems to be stucked at "ON" or something.
Well I also noticed without touchrecovery, it's quite a problem to navigate through cwm recovery.
But there's still fastboot... naaah I couldn't find the phone in Windows to install drivers, thought that's a problem of Win8, but after that I tried same thing in ubuntu with manually installed drivers... still nothing.
Okay next thing, is, there are so many apps in the market, which install some recovery, autoflash stuff... Did that, (yeah I gave root access and so on) and still nothing happened, I'm still stuck with this cwm recovery and can't install new roms.
Now my Question(s):
Is there an Option to install some new recovery?
Is there a way to get Fastboot working?
Is there a way to get the Powerbutton in this state back to work?
Or kinda best worst case, is there an option to get my Nexus back to Stock and unroot to send it in, I still got warranty but this would require stock phone...!
Thanks!
Click to expand...
Click to collapse
Yes, yes, yes... and yes!!! What you need is a shop that repairs phones or a store that sells new phones...
Sent from my Nexus S using xda premium
Can you boot all the way up into your android os?.. If so, you can use NEXUS ROOT TOOL KIT to flash to stock and relock it so it's "stock" for waranty..
http://www.wugfresh.com/nrt/
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNFr16--8W0o1xpv2Qtf0lDDwdGYJA
Setting.Out said:
Can you boot all the way up into your android os?.. If so, you can use NEXUS ROOT TOOL KIT to flash to stock and relock it so it's "stock" for waranty..
http://www.wugfresh.com/nrt/
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNFr16--8W0o1xpv2Qtf0lDDwdGYJA
Click to expand...
Click to collapse
Well ADB works but when NEXUS ROOT TOOL KIT reboots into fastboot it looses connection... Tried that to change recovery... Seems to be the same with relocking isnt it?!
Sent from my Nexus S using xda app-developers app
30floh00 said:
Well ADB works but when NEXUS ROOT TOOL KIT reboots into fastboot it looses connection... Tried that to change recovery... Seems to be the same with relocking isnt it?!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Hmmm.... Ebay..
have you tried flash touch recovery with ROM Manager app?
---------- Post added at 03:08 PM ---------- Previous post was at 02:30 PM ----------
Edit:
Try capacitive buttons on your current recovery. On my current recovery the search button makes the same that the power button, so if in your recovery the button have the same behaviour then you can easily flash a stock rom
Okay, i just got told: "If the power button is always pressed, fast boot does not react on input from keys or over adb.."
Hope that's not the "notsolution" for my problem... ^^
mykos5 said:
have you tried flash touch recovery with ROM Manager app?
---------- Post added at 03:08 PM ---------- Previous post was at 02:30 PM ----------
Edit:
Try capacitive buttons on your current recovery. On my current recovery the search button makes the same that the power button, so if in your recovery the button have the same behaviour then you can easily flash a stock rom
Click to expand...
Click to collapse
doesn't work, too....
30floh00 said:
Okay, i just got told: "If the power button is always pressed, fast boot does not react on input from keys or over adb.."
Hope that's not the "notsolution" for my problem... ^^
Click to expand...
Click to collapse
On my recovery the capacitive buttons react even with the power button pressed...
Can you get into download mode ???if so http://db.tt/88pntL6T flash this twrp recovery in Odin make sure auto reboot is checked and not repartition it should boot you right into recovery and then do whatbu got to do .... if you can not get into download mode get a jig always a life saver with android I've had no power button for 3 years and when it dies I Odin the recovery every time :thumbup:
Sent from my Nexus 7 using xda app-developers app
okay guys, just flashed touch recovery via Flash_image
http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
hope it helps you, if you cant access fastboot, too.. It's a bit tricky, but totally worth it
I have a TF300T that I need to fix. It gets stuck in an infinite boot loop, and when I try to run the recovery kernel, it will not work. I'm trying to flash CWM or a new rom onto it to get it running again, but the bootloader is not unlocked. Is there any way that I can unbrick the tablet without needing to unlock the bootloader, or is there any way I can unlock the bootloader without running the apk file Asus gives? I can't get past the recovery menu.
I have the same issue with a tf300t after attempting to update it. It's stuck on the boot screen with text in the top-left corner reading "signature match". Nothing happens, I've rebooted multiple times using multiple methods, but nothing works. I did manage to get my pc to recognize the tablet for a short while, but it didn't recognize the device.
Please, is there anything we can do besides getting a new tablet?
Edit: I tried adb and fastboot. No success. My tablet won't boot into the required state for these methods. Is there any other way to get it back to working order besides sending it to ASUS?
So neither of you are able to get to the screen that has the three icons?
If you can get to that screen you should be able to do a cold reset. This is the wipe data option. In other words, you will lose all your data.
Also, you might be able to flash stock SKU if you can get to that screen.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 05:40 PM ---------- Previous post was at 05:40 PM ----------
Voidac said:
I have the same issue with a tf300t after attempting to update it. It's stuck on the boot screen with text in the top-left corner reading "signature match". Nothing happens, I've rebooted multiple times using multiple methods, but nothing works. I did manage to get my pc to recognize the tablet for a short while, but it didn't recognize the device.
Please, is there anything we can do besides getting a new tablet?
Edit: I tried adb and fastboot. No success. My tablet won't boot into the required state for these methods. Is there any other way to get it back to working order besides sending it to ASUS?
Click to expand...
Click to collapse
So you can't get to any screen on your tablet? What is your process? Which buttons are you holding?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
yourignhere said:
I have a TF300T that I need to fix. It gets stuck in an infinite boot loop, and when I try to run the recovery kernel, it will not work. I'm trying to flash CWM or a new rom onto it to get it running again, but the bootloader is not unlocked. Is there any way that I can unbrick the tablet without needing to unlock the bootloader, or is there any way I can unlock the bootloader without running the apk file Asus gives? I can't get past the recovery menu.
Click to expand...
Click to collapse
If you can get to the recovery menu, try doing a cold reset. It will wipe all of your data. You click to move over to wipe data and select it. Then you should be able to boot and install that app to unlock your tablet.
Sent from my SM-N900T using XDA Free mobile app
Well, I've used the power button & Vol Down in an attempt to cold boot it or to get to the other options. No luck even getting to that screen.
Voidac said:
Well, I've used the power button & Vol Down in an attempt to cold boot it or to get to the other options. No luck even getting to that screen.
Click to expand...
Click to collapse
Is your tablet charged?
Sent from my SM-N900T using XDA Free mobile app
andrewnelson23 said:
Is your tablet charged?
Click to expand...
Click to collapse
I've tried from plugged, unplugged. Full battery and letting it sit for almost a day to completely drain the battery.
andrewnelson23 said:
So neither of you are able to get to the screen that has the three icons?
If you can get to that screen you should be able to do a cold reset. This is the wipe data option. In other words, you will lose all your data.
Also, you might be able to flash stock SKU if you can get to that screen.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 05:40 PM ---------- Previous post was at 05:40 PM ----------
So you can't get to any screen on your tablet? What is your process? Which buttons are you holding?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
If you can get to the recovery menu, try doing a cold reset. It will wipe all of your data. You click to move over to wipe data and select it. Then you should be able to boot and install that app to unlock your tablet.
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
I was able to do a cold reset and the tablet's working fine now, just waiting on the wifi connection (which is taking abnormally long) to get going so I can unlock the bootloader.
Voidac said:
I've tried from plugged, unplugged. Full battery and letting it sit for almost a day to completely drain the battery.
Click to expand...
Click to collapse
So does it just go black or what?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
yourignhere said:
I was able to do a cold reset and the tablet's working fine now, just waiting on the wifi connection (which is taking abnormally long) to get going so I can unlock the bootloader.
Click to expand...
Click to collapse
Did you get it going?
Sent from my SM-N900T using XDA Free mobile app
andrewnelson23 said:
So does it just go black or what?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
Did you get it going?
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
It won't connect to wifi. It says "authenticating" and just stays there forever until I turn off the screen, then it says "not connected"
yourignhere said:
It won't connect to wifi. It says "authenticating" and just stays there forever until I turn off the screen, then it says "not connected"
Click to expand...
Click to collapse
You can try to flash the original SKU and see if that fixes it?
Sent from my SM-N900T using XDA Free mobile app
andrewnelson23 said:
You can try to flash the original SKU and see if that fixes it?
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Can't flash without unlocking the bootloader right? I can't unlock it without a network connection.
andrewnelson23 said:
So does it just go black or what?
Click to expand...
Click to collapse
Literally all I can get it to is the ASUS logo boot screen. Nothing else.
When I power it down (and it keeps automatically rebooting), I'll try holding the Volume Up button, then my computer recognizes it (but cannot find a driver for it). But it's the only way I can get the screen to turn off.
yourignhere said:
Can't flash without unlocking the bootloader right? I can't unlock it without a network connection.
Click to expand...
Click to collapse
You have to have unlocked boot loader to flash original stock SKU?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 04:32 AM ---------- Previous post was at 04:31 AM ----------
Voidac said:
When I power it down (and it keeps automatically rebooting), I'll try holding the Volume Up button, then my computer recognizes it (but cannot find a driver for it). But it's the only way I can get the screen to turn off.
Click to expand...
Click to collapse
I think that's apx mode for if you had the flatline blobs to unbrick your tablet. Since you don't know what it is, I doubt you made a backup of it...
Sent from my SM-N900T using XDA Free mobile app
andrewnelson23 said:
I think that's apx mode for if you had the flatline blobs to unbrick your tablet. Since you don't know what it is, I doubt you made a backup of it...
Click to expand...
Click to collapse
You are correct xD
I don't really care for modding my tablets or phones, mostly because I kind of need them? Maybe once I get a new tablet (Still waiting for the new version of the Nexus 10), I'll start messing with my old stuff. Android has always been a pleasure to use, so I never really cared about installing custom roms on the thing. (That and I didn't want to void the warranty).
How was I supposed to know installing a firmware update was gonna brick my tablet?
Thanks, Obama.
I restarted the tablet again, and the internet was working. Weird. Anyway, I think I have things under control from here. Thanks for all the help, guys.
bricked
Hello guys and gals, so i have hard bricked my tablet and can only access apx mode. So of course i understand that without a prior backup made with NVFLASH i am probably out of luck.
With that said, i do have a question for a seasoned developer. I understand the nvflash blob has to be for "your specific device" but is there a way to say, use the blob from someone elses nvflash blob if you change the serial number on your device to the one that the blob came from? I thought it may be possible becase i saw the command in the "help" section in NVFLASH "cmd #38" "--internaldata" "used to flash the sku-info, serial-id,mac-id,prod-id"
so i thought it may be possible to kinda clone the device the blob came from so that you can use the blob file through NVFLASH
does any of this make sense?
im just trying to think outside the box here ( i have no clue how the blob files are generated or what nvflash looks for when flashing a blob)
has anyone used this command before?
PS - i know this is in the wrong section but none of the "bricked" threads have been touched for a while so i felt i might get some attention here (bad or good)
I've contacted ASUS and I might have to mail my tablet into them :/ Not really looking forward to it bumping around in the mail for a week. Does it cost to send the tablet into them? If they break it, do they send me a new one? >.>
Regardless, I'm still struggling with finding a solution to my problem. Being unable to boot into Recovery Mode is really killing my chances of getting this fixed on my own.