Database Info

[Q] Can't enter recovery mode on Magic id7003 Tablet PC

Good day,
I've looked through lots of posts, but can't find one similar to my issue.
I bought Magic id7003. It's not my first Android. I root it through SuperOneClick program. I have used FwTool to install new phone program on it and after this my tablet screen died. Service center changed my screen (tablet was on guaranty), but another problem appeared - and this is my actual question: Now I can't enter recovery mode.
This massage appear: "The Device Enter Fastboot Mode, Please Connect USB TO PC or Reset The Device, Waitting...........".
Only restarting helps get rid from it. Hard reset doesn't help eather - it leads to the same massage.
Thanks a lot.

Broken Screen, how to get to my files? Need an android expert!

Hello everybody,
I know there are many threads with broken screens and so on, but I've been searching the internet the whole day & night and tried nearly every solution.
My Smartphone fell on the ground two days ago, I can see everything, but touch isn't working anymore.
Usually I'm rooting my phones but i didn't root my XZ5 so far (big mistake!), so I don't have a custom recovery.
I have USB Debugging activated, but I haven't connected my phone since it updated to the new firmware, so I'm getting RSA Fingerprint Message which I can't allow.
After my Z5 fell on the ground, the fingerprint didn't work so I had to restart my phone - now I'm forced to enter the key to unlock the system.
At first, I tried "Android Control" with adb, but when I connect my phone, adb says "unauthorized" - no remote control possible.
After that, I bought a OTG Cable and plugged in a mouse. This isn't working, because I have to search for a plugged-in USB device first in the settings (the phone doesn't recognize the USB device itself).
Fastboot & Flash Mode are still working.
Is there a possibility to skip RSA Fingerprint with USB debugging or deleting my lock screen? I thought of unlocking my bl and installing TWRP, but then the mobilephone would be wiped as far as I know.
Maybe someone of you knows a "temporary recovery" which can be booted from SD-Card or another way to get to my internal data..
It would be awesome, if someone could help me with this!
Many thanks in advance!

Only way i can think of are to downgrade to lollipop with flashtool without wipe.
Then the usb mouse should start to work directly if im not mistaken.
Atleast i think it was this they before mm upgrade.
Did you try to boot the phone with the mouse connected?
Skickat från min E6653 via Tapatalk

yes, unlocking would completely wipe your phone, including internal memory so it's not a solution.
Rsa key request means you cannot run any adb command right, included adb shell right?
Did you try to do an extensive google search with "broken screen rsa"?
Particularly, http://stackoverflow.com/questions/...b-rsa-key-with-broken-touch-screen-on-android
talks about rebooting in "recovery mode", so you could try to use adb commands in fastboot mode (or download mode)

bobrovsky35 said:
Hello everybody,
I know there are many threads with broken screens and so on, but I've been searching the internet the whole day & night and tried nearly every solution.
My Smartphone fell on the ground two days ago, I can see everything, but touch isn't working anymore.
Usually I'm rooting my phones but i didn't root my XZ5 so far (big mistake!), so I don't have a custom recovery.
I have USB Debugging activated, but I haven't connected my phone since it updated to the new firmware, so I'm getting RSA Fingerprint Message which I can't allow.
After my Z5 fell on the ground, the fingerprint didn't work so I had to restart my phone - now I'm forced to enter the key to unlock the system.
At first, I tried "Android Control" with adb, but when I connect my phone, adb says "unauthorized" - no remote control possible.
After that, I bought a OTG Cable and plugged in a mouse. This isn't working, because I have to search for a plugged-in USB device first in the settings (the phone doesn't recognize the USB device itself).
Fastboot & Flash Mode are still working.
Is there a possibility to skip RSA Fingerprint with USB debugging or deleting my lock screen? I thought of unlocking my bl and installing TWRP, but then the mobilephone would be wiped as far as I know.
Maybe someone of you knows a "temporary recovery" which can be booted from SD-Card or another way to get to my internal data..
It would be awesome, if someone could help me with this!
Many thanks in advance!
Click to expand...
Click to collapse
So I recovered my password from the dust and figured this is my chance to help..
Better be working..
I dropped my z3c while I was holding my newborn baby, it contained all the pictures from birth, ****ing fool I am for not backing up..
Get that short '.. to usb' - thing from the box. Use that to connect your Bluetooth mouse and tada that should work. Use it to unlock your phone and do you what you want to do.
It worked for me, hope I can help you.

Overmax Baseone 2 - how to recover/root/update without recovery mode?

AVE...
I've got an used Overmax Baseone 2 tablet running Android 4.1.1. It's based on Amlogic AML8726-MXL CPU. My problem is that the tablet is slightly bricked. Internal storage partition is "full", I can't install any apps, and after powering on the tablet starts with factory settings as if nothing was saved to internal storage. I found a solution here but I can't use it. I have no root on the device and I can't install it. Tablet has no physical buttons except power and hardware reset, so I can't enter recovery or bootloader mode normally. I can enter either mode using ADB, but without physical buttons I can't navigate. I tried "adb reboot sideload" but it doesn't work. Fastboot doesn't see the device when it works normally or with USB debug. I tried Root Guru software but it got stuck in the middle because after rebooting the tablet it was restored to factory settings again. I'll try KingRoot tomorrow, but I don't expect it to work. I even took the back cover off to see if there is any place for physical buttons. I found only a debug connections (4 pins for either serial or JTAG interface). I can provide the pictures of the board if required. Board is marked MID710-K MIAN VER1.1 2013-5-13.
Overmax provides firmware with instructions, how to load it but it doesn't work on my tablet. It just freezes. I tried to use AMLogic USB Burning Tool, but it fails to read img files from Overmax website.
Can anyone help me?

AVE...
Bumping up.
KingRoot apk didn't work. KingRoot PC app gave me root, but the fix from this topic didn't work...

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez

This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse

Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.

MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.

amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck

Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.

Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.

It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

Xiaomi Redmi 9A totally dead after PS Flash Tool

Hello there,
first of all excuse me if its wrong section to post such things.
My Redmi 9A won't turn on after i've flash it using PS Flash Tool , i've tried to charge it, button combinations and other things...
whenever i am connecting 9A to my PC it says "unrecognised USB device" and i am completely out of clue what can i do to bring it back to life.
any help will be appreciated

Got the same problem too i cant find a solution either, been searching for weeks

Same here after trying to unlock bootloader

Hi ! Same problem for me and I'm looking for a solution. I bricked my phone 2 months ago... there is 1 solution that I found but IMEI is lost (not a big problem, you can flash it) and mobile network connection is lost (this is my problem). So you can flash a custom recovery with SP Flash Tools and flash a custom ROM like Havoc OS through it and that's working excepted the mobile network connection...

I found the solution and fixed my friend's 9a. It seems that after doing stuff in brom mode, the phone gets stuck somehow and all hw buttons wouldn't work at all. What I did is I opened the phone and removed the battery cable and put it back to reset the phone state, then turned the phone on.

DummyCode said:
I found the solution and fixed my friend's 9a. It seems that after doing stuff in brom mode, the phone gets stuck somehow and all hw buttons wouldn't work at all. What I did is I opened the phone and removed the battery cable and put it back to reset the phone state, then turned the phone on.
Click to expand...
Click to collapse
Don't work for me

Rares656723 said:
Don't work for me
Click to expand...
Click to collapse
Try holding the volume and power buttons for more 2 seconds when connecting and bypassing