Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
heinzelrumpel said:
Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
Click to expand...
Click to collapse
when I plug in the device when it ist shot off, I get this
c:\adb>adb devices
List of devices attached
SH19PV801767 recovery
Click to expand...
Click to collapse
When I try to do a "adb reboot -bootloader" oder " adb reboot -fastboot" only the HTC Logo with white background appears. Windows does not recognize the device. In device manger it only say "Android". I tried to give it another driver, but the system complain, that it is the wrong one. I have tried to install drivers from different sources. Nothing.
Are you s-off or s-on?
Sent from my HTC Sensation using Tapatalk 2
heinzelrumpel said:
Hi,
I have a rooted device and installed CM9 for testing. Then I went into recovery and wiped everything, set to factory defaults and erased sdcard. Now the Sensation boots and hangs when the HTC Logo appears. I cannot get into recovery anymore and when plugged into my computer the device is not recognized even though I have the fastboot driver installed and the normal usb_drivers.
How could I get my device working again? Thanks
Heinzelrumpel
Click to expand...
Click to collapse
if you are SON ..then after flashing the ROM ..do the extra 1 step from this guide
ganeshp said:
if you are SON ..then after flashing the ROM ..do the extra 1 step from this guide
Click to expand...
Click to collapse
Unfortunately that won't work, because the relies on the the fact, that I am in fastboot. I cannot get into fastboot. I read that EXTRA1, which suggests in my case to go to EXTRA4.
P.s. I do not now if I have s-on or off. Sorry, but I forgot to look it up before I wiped eveything
Sory, I was wrong. I am now in fastboot
Great. Everything works fine again. Thanks
My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? I CAN get into APX mode.
Yes, wiping the data will brick your device if you don't have a working recovery.
sparky28000 said:
Yes, wiping the data will brick your device if you don't have a working recovery.
Click to expand...
Click to collapse
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
jrfaulkin said:
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
Click to expand...
Click to collapse
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
jeroen.wit said:
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
Click to expand...
Click to collapse
Unfortunately, APX and nvflash is not available for the TF300T currently. As I understand it, you're required to record some information and your Secure Boot Keys (SBK) prior to bricking to be able to access APX. Otherwise, your only recourse is to contact Asus and start the RMA process.
I'm recording my developments over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=2 (my post is at the bottom)
I think I'm going to hold out until someone figures out the NvFlash process as described here:
http://androidroot.mobi/technical/tf-secure-boot-key/
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
gypsyshaw said:
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
Click to expand...
Click to collapse
The difference in your situation is that you were able to access the boot loader. My boot loader is wiped. I don't get the option to select Wipe Data/Fastboot, etc. I'm stuck in a mode where I think the only option is to low-level flash the bootloader after re-initializing all of the partitions.
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
So yesteday i decided to instal cyanogenmod in my nexus 5. I downloaded the latest nighly version in my phone (unlocked bootloader and rooted).I open twrp, i made factory reset and wiped cache partition and then went ahead to install cyanogen but unfortunatly i had an error:no md5 file found. I google it and i found that this may work with cwm. So i tried to install it with this one this time but again an error saying that i need a bootloader hhz12d but had hhz12f. So i flash the needed bootloader but my phone then couldnt open recovery mode (it reacted like i hadnt intall a custom recovery at all) so i wasnt able to intall the cyanogenmod. At last i flashed again my previous bootloader hoping that its gonna fix the prob but now i have stuck in fastboot unable to neither to boot or go in recovery mod.
Any ideas guys? Please help me Im disappointed i dont know what to do.
Have you tried flashing twrp or cwm again?
bitdomo said:
Have you tried flashing twrp or cwm again?
Click to expand...
Click to collapse
yes ... it's stuck saying : waiting for your divice and nothing happends
xalkias said:
yes ... it's stuck saying : waiting for your divice and nothing happends
Click to expand...
Click to collapse
That means you dont have the drivers installed or the windows have some driver issues or the usb port on the pc is broken or the usb port on the phone is broken or the usb cable is broken or the bootloader fails to change to usb port settings to bootloader mode.
Do you see any new device in device manager when you connect the phone in bootloader mode to your PC?
What is the new device's name? Is it unknown device? Is there an exclamation mark before the new device's name?
Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
maciumpek said:
Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
Click to expand...
Click to collapse
You have to kick your tablet back into the bootloader and you best bet for that is to use bootit.ko that we have thanks to _that.
Follow this: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Yes, that's a guide for the TF300 but this works just fine on the 700 too.
After you are back in the bootloader it's up to you if you follow lj's guide and fastboot flash the Asus stock blob and start from scratch or reflash your recovery and use that to format your cache and data partitions.
If you decide to flash the stock blob you'll have to get the latest firmware for your SKU from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
But you should be able to fix it without that once you have a working recovery and fastboot again.
Hi,
I have similar problem. My Tablet Stuck on blinking TWRP. When i power on my tablet, after asus logo it goes to " 4 Penguins images" then Twrp tlinking "TEAMWIN" logo.
Power + Volume Down buttons do not work. My problem is that my Asus TF700t could not be detected by PC, I have tried on several laptops with windows and linux, i`ve also tried two cables, but nothing - thread: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page8 is not helping me. Any ideas?