Related
Ive been trying to get root on my phone but unfortunately the person who sold it to me unlocked the bootloader so i cant use the one click root option (the program unlocks the bootloader first and since mines already unlocked it just hangs there) my only other option is adb which i used to root my xperia x10 a year ago but now i have a new windows 7 laptop and adb is extremely difficult right now for me to get working, any ideas to help?
btw idk if this helps but when i try booting into the recovery i get an error signal
thanks in advance!
1 click works. I had the same issue. After it does the bootloader unlock it should restart phone, then boot back into bootloader and continue for root. Wrong forum btw, use q& a.
Sent from my Nexus S 4G using Tapatalk
ok id move it but i dont think i can
and i tried that and it doesnt work, it says "waiting for device" it wants me to accept my bootloader being unlocked but since mine already is i go straight to the fastboot, rebooting to fastboot does nothing to continue the process
Learn to root without using a one click method. You will learn important things about your phone that will help you in the future.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Learn to root without using a one click method. You will learn important things about your phone that will help you in the future.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
This is why I hate 1-click roots. I root all of my phones manually because this advice is so true.
well ive taken your advice and i have adb devices showing my serial number so i have that working, but now when i try rooting through fastboot i get a message saying fastboot is not recognized *sigh* any help?
fatboot solution (possibly)
fightingroost12 said:
well ive taken your advice and i have adb devices showing my serial number so i have that working, but now when i try rooting through fastboot i get a message saying fastboot is not recognized *sigh* any help?
Click to expand...
Click to collapse
I've been going through the same thing and I believe I may have found the solution to adb issue. Waiting on phone to charge now so that I can try it again.
From what I've found, you have to download fastboot separately and place in the same file containing adb.exe
hope this helps
fightingroost12 said:
well ive taken your advice and i have adb devices showing my serial number so i have that working, but now when i try rooting through fastboot i get a message saying fastboot is not recognized *sigh* any help?
Click to expand...
Click to collapse
Open a command prompt from the one click root folder. It has ADB and fastboot support.
Sent from my Xoom using xda premium
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
So I've read a few things on the forum about signal drops and have tried a few solutions but I wanted to get some additional feedback before I go the ATT:
Just in the past few days, I have had increasingly frequent signal drops. This has become really annoying for me, as it always seems to happen when I am using mobile data or sending a text message. The signal drop is transient and only lasts about 30 seconds before it re-connects to my network. I haven't noticed much correlation with when it actually happens but I have attached a picture just so you all can see how frequent these signal drops are. Happens when phone is asleep or in use. These are the things I have tried:
1) Originally was running KingCobra 1.5 and thought it may have been the ROM so I flashed CM10
2) Flashed radio 2.09 for ATT - this showed no improvement / did not make it worse
3) Wiped cache / Dalvik - no improvement
My next course of action was to go to ATT and get a new SIM card. Is it possible that a faulty SIM over time could cause this? And would replacing the SIM likely help in the experience of this community?
Thanks a lot for the input, and if there is something else I can do that I haven't already tried please let me know!
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
redpoint73 said:
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
Click to expand...
Click to collapse
Can this sort of thing spontaneously happen? One day the SIM just starts getting derpy?
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
area51avenger said:
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well I got a new SIM from AT&T and I'm still dropping signal. They did say that they just put up LTE towers here where I'm at 2 days ago, which, coincidentally is when I started getting signal drops. I suppose all that is left is for me to RUU? I don't know how to so it should be fun reading up lol
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Edit: Could someone enlighten me a little bit on the process of the RUU -- The only thing that is cloudy here is that I am currently running CM10, would I be able to run the executable RUU if I was running a stock odexed/deodexed ROM after re-locking the bootloader? I have looked at this (http://forum.xda-developers.com/showthread.php?t=1814217&highlight=ruu) and the associated guide but this all assumes that I'm already on a stock image right? I've tried doing some reading but I am drawing a blank on the RUU process
TheEmpyre said:
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Click to expand...
Click to collapse
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
superchilpil said:
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
TheEmpyre said:
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
Click to expand...
Click to collapse
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
superchilpil said:
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Edit: Forgot that when you unlock bootloader you do it through fastboot with "fastboot flash unlocktoken Unlock_code.bin so ultimately I would be able to re-flash my recovery etc
TheEmpyre said:
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Click to expand...
Click to collapse
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token, flash twrp, and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
superchilpil said:
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
TheEmpyre said:
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
Click to expand...
Click to collapse
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
superchilpil said:
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
TheEmpyre said:
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
Click to expand...
Click to collapse
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
superchilpil said:
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
What my screen looks like here before and after selecting bootloader with the power button
Sent from my Nexus 10 using Tapatalk 2
TheEmpyre said:
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
Click to expand...
Click to collapse
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
alright, in fastboot run fastboot oem rebootRUU
then run the ruu.exe
superchilpil said:
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
Click to expand...
Click to collapse
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
TheEmpyre said:
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
Click to expand...
Click to collapse
try my method above, ive tried it with fastboot... the ruu just ignores it
That method should work, the ruu should pick it up and wipe it clean
ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb
glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?
bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?
would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.