Related
Okay, first of all, I feel quite stupid now... What happened?
0. I rooted my prime (motorchopper) and used the unlock-tool
1. I installed Clockwork mod (and upgraded it)
2. I tried to backup the stockrom (the latest version from Asus itself: 4.1.1): this did not work
3. Clockwork seemed to work, though I was still struggling with the tether-app
4. I could enter the fastboot menu, but it did not boot unless I did nothing (then it used the stock-rom)
5. then the accident (yes, it was an accident...) happened: I went through the options in the (still standard) menu and choose to flash the rom. I tried to cancel that, but by accident I hit volume up (and not down...)
ouch...
6. the tablet reboots, but the only things I see are:
- upper left corner: "device is unlocked"
- centre: Asus-logo
- right under corner Nvidia logo
7. when I connect the tablet to my PC and hit volume up + power, the PC 'recognizes' the tablet as an APX device (in device manager)
(this gave me some hope). Power + volume down gives the same as under 6.
8. I installed the ASUS USB-drivers and Windows 7 (on my laptop) recognizes the tablet under devicemanager: "Asus Transformer Prime APX interface" (the tablet has a black screen and seems to be turned off). When I turn it on, the same logo and connection is lost
9. I tried this topic (as Leipy did in this post).
10. the only response I get from fastboot / adb is: < waiting for device > (when using fastboot) or "error: device not found" (when using ADB) (on any of the commands I give)
11. I'm posting this as a last resort. I cannot post under development (not enough rights), so I post it under troubleshoot.
the question:
- is there still some hope for my tablet?
Thanx for any help you can give me (or some suggestions for a new tablet... )
Govermans said:
Okay, first of all, I feel quite stupid now... What happened?
0. I rooted my prime (motorchopper) and used the unlock-tool
1. I installed Clockwork mod (and upgraded it)
2. I tried to backup the stockrom (the latest version from Asus itself: 4.1.1): this did not work
3. Clockwork seemed to work, though I was still struggling with the tether-app
4. I could enter the fastboot menu, but it did not boot unless I did nothing (then it used the stock-rom)
5. then the accident (yes, it was an accident...) happened: I went through the options in the (still standard) menu and choose to flash the rom. I tried to cancel that, but by accident I hit volume up (and not down...)
ouch...
6. the tablet reboots, but the only things I see are:
- upper left corner: "device is unlocked"
- centre: Asus-logo
- right under corner Nvidia logo
7. when I connect the tablet to my PC and hit volume up + power, the PC 'recognizes' the tablet as an APX device (in device manager)
(this gave me some hope). Power + volume down gives the same as under 6.
8. I installed the ASUS USB-drivers and Windows 7 (on my laptop) recognizes the tablet under devicemanager: "Asus Transformer Prime APX interface" (the tablet has a black screen and seems to be turned off). When I turn it on, the same logo and connection is lost
9. I tried this topic (as Leipy did in this post).
10. the only response I get from fastboot / adb is: < waiting for device > (when using fastboot) or "error: device not found" (when using ADB) (on any of the commands I give)
11. I'm posting this as a last resort. I cannot post under development (not enough rights), so I post it under troubleshoot.
the question:
- is there still some hope for my tablet?
Thanx for any help you can give me (or some suggestions for a new tablet... )
Click to expand...
Click to collapse
That is hard bricked.
The links you posted could be fixed because they could still enter the bootloader and fastboot.
You can only access APX which is useless without Nvflash Backups.
Search is a wonderful thing, they say...
http://forum.xda-developers.com/showthread.php?t=2427710
Govermans said:
Okay, first of all, I feel quite stupid now... What happened?
0. I rooted my prime (motorchopper) and used the unlock-tool
1. I installed Clockwork mod (and upgraded it)
2. I tried to backup the stockrom (the latest version from Asus itself: 4.1.1): this did not work
3. Clockwork seemed to work, though I was still struggling with the tether-app
4. I could enter the fastboot menu, but it did not boot unless I did nothing (then it used the stock-rom)
5. then the accident (yes, it was an accident...) happened: I went through the options in the (still standard) menu and choose to flash the rom. I tried to cancel that, but by accident I hit volume up (and not down...)
ouch...
6. the tablet reboots, but the only things I see are:
- upper left corner: "device is unlocked"
- centre: Asus-logo
- right under corner Nvidia logo
7. when I connect the tablet to my PC and hit volume up + power, the PC 'recognizes' the tablet as an APX device (in device manager)
(this gave me some hope). Power + volume down gives the same as under 6.
8. I installed the ASUS USB-drivers and Windows 7 (on my laptop) recognizes the tablet under devicemanager: "Asus Transformer Prime APX interface" (the tablet has a black screen and seems to be turned off). When I turn it on, the same logo and connection is lost
9. I tried this topic (as Leipy did in this post).
10. the only response I get from fastboot / adb is: < waiting for device > (when using fastboot) or "error: device not found" (when using ADB) (on any of the commands I give)
11. I'm posting this as a last resort. I cannot post under development (not enough rights), so I post it under troubleshoot.
the question:
- is there still some hope for my tablet?
Thanx for any help you can give me (or some suggestions for a new tablet... )
Click to expand...
Click to collapse
Mine is in a similar situation, but I got there completely differently. I had unlocked the bootloader, rooted, and install CWM from ROM Manager. Rebooted, held down the volume + power button, selected wipe data by mistake, and waited.. and waited... when it didn't do anything for almost an hour I figured it must have been done, or I was screwed. Rebooted, and it's at the Asus screen. The rest is the same, as far as the APX device and whatnot. A new motherboard is the only option here? I have a hard time believing that.
Govermans said:
Okay, first of all, I feel quite stupid now... What happened?
0. I rooted my prime (motorchopper) and used the unlock-tool
1. I installed Clockwork mod (and upgraded it)
2. I tried to backup the stockrom (the latest version from Asus itself: 4.1.1): this did not work
3. Clockwork seemed to work, though I was still struggling with the tether-app
4. I could enter the fastboot menu, but it did not boot unless I did nothing (then it used the stock-rom)
5. then the accident (yes, it was an accident...) happened: I went through the options in the (still standard) menu and choose to flash the rom. I tried to cancel that, but by accident I hit volume up (and not down...)
ouch...
6. the tablet reboots, but the only things I see are:
- upper left corner: "device is unlocked"
- centre: Asus-logo
- right under corner Nvidia logo
7. when I connect the tablet to my PC and hit volume up + power, the PC 'recognizes' the tablet as an APX device (in device manager)
(this gave me some hope). Power + volume down gives the same as under 6.
8. I installed the ASUS USB-drivers and Windows 7 (on my laptop) recognizes the tablet under devicemanager: "Asus Transformer Prime APX interface" (the tablet has a black screen and seems to be turned off). When I turn it on, the same logo and connection is lost
9. I tried this topic (as Leipy did in this post).
10. the only response I get from fastboot / adb is: < waiting for device > (when using fastboot) or "error: device not found" (when using ADB) (on any of the commands I give)
11. I'm posting this as a last resort. I cannot post under development (not enough rights), so I post it under troubleshoot.
the question:
- is there still some hope for my tablet?
Thanx for any help you can give me (or some suggestions for a new tablet... )
Click to expand...
Click to collapse
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
Hi there,
Iam freshly new to this forum and tweaking android devices aswell. Yesterday with not to much trouble i installed linageOS on my Oneplus X and it made me verry happy.
So, i wanted to take a next step: I have an Android tablet Denver TAQ-10153 wich i want to update to Ubuntu Mobile.
So far so good. Until i noticed that once in developper mode, enabeling USB debugging there was no confirmation prompt on my tablet to autenticate. Then i dicited to not make a backup cause (the stock ROM is not important to me, tablet is a spare one) and go straight to the bootloader unlock.
When i reboot in fastboot mode i give the command: sudo fastboot oem unlock.
Then on the tablet is see a confirmation. I have to confirm with volume UP or decline with volume DOWN. But the tablet is unresponsive! it freezes completely. Even the powerbutton does not react anymore... Ubuntu terminal is unresponsive to.
The only thing i can do is put a paperclip in the reset hole to reboot again. Can someone tell me if iam overseeing anything?
Thanks for any input. Greetings, Erik.
Dear users, I am desperate!
I have a Huawei P9 Lite Mini. The screen is broken and black, is impossible to interact and nothing appears. The device is not in debug mode. I can not interact and confirm on the popup which usually appears during the use of the most common data recovery software. How can I recover all data inside my phone?
1) I already tried all recovery software as Dr. Fone, Mobilke go and so on (I cannot confirm on popup on device);
2) I already tried OTC Cable but nothing happens;
3) The device has not root power;
4) Obviously, without any interaction, is impossible to activate the debug mode;
I also tried "adb", but by "adb devices" in command line the device appears as "unauthorized"; maybe this is the good way? How can I see my device in the terminal list, but as authorised?
Thank you very much, for me is a real emergency!
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Probably stupid question, but have you tried the keys: Power and Volume+ while powering up?
That should bring you into recovery mode as far as i know.
When I press the power and volume up it just keeps rebooting With the volume down combined it goes to the boot loader, but there's no recovery option there either.
Did you try to boot without any SIM card and SD card?
rtau said:
Did you try to boot without any SIM card and SD card?
Click to expand...
Click to collapse
Yes I did and did not resolve the issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
YOU'RE OUT OF LUCK, IT'S EFFECTIVELY FULLY BRICKED UNLESS YOU BRING IT TO THEIR CUSTOMER SERVICE.
HMD's known for blocking people out of bootloader unlocking, and even if you beg them, they can't anyway (they released incomplete bootloaders for their retail units.) I'd say "call Hikari_Calyx" or something, but I don't think he can help with this issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
Give it a try> Maybe this tool can help here
mvikrant97 said:
Give it a try> Maybe this tool can help here
Click to expand...
Click to collapse
is it really okay to use tools for a device on a whole different device though???
WilliamMike said:
Yeah! Its helpful whenever my phone got stuck or displaying black screen ..
Click to expand...
Click to collapse
what's your model, then? Those kinds of phones from Nokia/HMD are never able to enter fastboot/recovery mode though.
AltFantasy said:
is it really okay to use tools for a device on a whole different device though???
Click to expand...
Click to collapse
It is based on ADB commands you can use it
mvikrant97 said:
It is based on ADB commands you can use it
Click to expand...
Click to collapse
but I couldn't use ADB on my X10...