[Q] Can't enter recovery mode on Magic id7003 Tablet PC - General Questions and Answers

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.

Related

[Q][HELP] Pantech Sky Vega A760s Unbrick

I accidentally bricked my a760s.
here's what happened:
-the phone won't open unless connected to pc
-when connected, it will only go to charging mode
-when i try to enter recovery mode, this shows up:
"your phone will restart due to error occurred while running application "
i cannot access recovery mode, the only thing i can access is the s/w upgrade mode, which i don't know how to use since i'm not korean
and i can't understand pantech's website.
How can I unbrick my phone?
PLEASE HELP. THANK YOU IN ADVANCE.
i also have same problem... did u have and solution of this???

Help Please Please with my bricked Alcatel Ot 5020 (Evolve)

This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
you found any solution i have the same problem ?
:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me
So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.
any luck with a solution? How close to one have you got to...
ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.
Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.
Alcatel 5020t T-Mobile plis help flshe file
please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks

[Q] Samsung Galaxy Gio S5660 - Bricked, no Boot, no Recovery, Undetectable in DL-Mode

Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
x6XceS6x said:
Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
Click to expand...
Click to collapse
Try with heimdall, an alternative to Odin : http://glassechidna.com.au/heimdall/ . For the emergency download mode, you won't be able to do anything with it. And make sure you have the samsung usb drivers : http://developer.samsung.com/technical-doc/view.do?v=T000000117
Tried, same result
Dear TheIcE65,
Thank you for your quick response.
I've tried the USB Drivers you supplied, clean install
Unfortunately these drivers result in the same problem. While the Phone is in Download Mode, once connected windows still throws up a "USB Device not Recognized" error.
Heimdall also does not recognize the device, as Windows doesn't either.
Please help, I'd like to get this Phone un-bricked!
Kind regards
Anyone found a fix for this ?
Exactly the same issues here
same issue
facing the same issue. cant find any solution anywhere. hoping someone can help

[Q] I think I softbricked my One X

Hello everyone.
Just to get it out of the way, I am very inexperienced with android products. At the moment, I'm having trouble getting my HTC One X (at&t) version to turn on. It all started when I decided to update the android version from 4.1. something to 4.2.2. I went to this site, the HTC website (www . htc . com / us/support/htc-one-x-att/news/) and downloaded the executable file and ran it . Once installation was done a message popped up on my computer stating an error occurred. I look at the phone and it shows the HTC splash screen for a few seconds and it shuts off and immediately turns back on with the HTC splash screen again, a bootloop. I then found out that I can restore the device by entering fastboot and selecting the factory restore option. This didn't restore the device but just entered the bootloop process again. I entered fastboot mode again and this time I selected the recovery option which also failed. I hook up the phone with USB 2.0 to the computer to transfer a stock ROM but computer doesn't recognize the phone anymore ( the computer did at first recognize the phone during installation of 4.2.2). After various attempts to get the phone to be recognized by computer, I gave up and called it quits and decided to power it off through the fastboot option. And now I can't even turn on the phone at all. I plug it to the computer to see if that will prompt the phone to turn on but all that does is charge the battery. The computer does recognize that something is connected to it but fails to recognize the phone.
Is there anything I can do to get this phone working again? I would much appreciate any help with this.
Ok guys I managed to get the phone to turn on again, buts its still in bootloop. Once the phone turns on, the computer notices that the phone is connected and tries to install the drivers but fails as soon as the phone restarts. Essentially the computer is unable to finish installing the proper drivers in time. The driver that its trying to install is "HTC MTP Device".
Put the phone into bootloader mode and run the RUU executable again.
Transmitted via Bacon
Ok its finally working. Thanks for the help!

Wiko rainbow 4G bootloop

Today I got a message that I could update my telephone. So downloaded it, restarted and just near the end of the update install it gave an error.
I tried to restart but didn't get past the boot screen. I can get into the selection menu of recovery mode/ factory mode.
But when I choose factory mode I don' t get past the boot screen and in recovery mode I get a "dead android with: no command" and there is nothing I can do. (I wiped the cache etc. but nothing helped) (ALPS.KK1.MP3.V1)
And I can' t apply an update from ADB because when I connect it to my PC (windows 10) I get the message its not recognized.
Device manager gives this error: Unknown USB device (Device Descriptor Request Failed) Error Code 43.
If I connect my telephone via USB using ubuntu (15.10) it isn' t recognized at all not even when i check with the lsusb command.
I hope someone has an idea to steer me on the right way!
solved
Well.. seems like trying a different cable, trying many usb drivers and reading a bit better also helps! So if you read this and have the same problem: keep trying/ searching/ reading!

Categories

Resources