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...
Related
I have Lenovo Lephone S686 with following specifications. If anyone has any idea on how to root this phone, please reply.
CPU: Qualcomm Snapdragon MSM8225 Dual core 1.2GHz
GPU: Qualcomm Adreno203
Memory : RAM : 512MB / ROM : 4GB eMMC
Found already?
Am sick and tired of the stock....
tried 1-click root, king root, and all other root method and failed...
Anybody knows how to root this? bin4ry method did not work.
Hi everyone,
I found these instructions for rooting the Lenovo S686 from Chinese forums, you can try and see if it works. Below are the instructions which I translate from Chinese.
You need to install a 3rd party recovery, because S686’s original recovery cannot install unsigned update.zip. There are 2 kinds of update.zip, smaller one, about 1-2MB, is for obtaining root. The bigger one is for flashing the entire system. There is no 3rd party recovery for S686, but after looking at some other models’ recovery, I think we can use A765E recovery.
Turn on USB debugging. Connect USB wire. For desktop PCs, it is better to use the back USB port.
Download this: ht tp://pan [dot] baidu [dot] com/share [slash] link?shareid=415868&uk=4130114971
After uncompressing, you will get 2 files, update.zip and Lenovo_A765E_OneKeyTools.exe. Do not uncompress the update.zip. Just put it on the TF card.
Make sure the drivers are installed. Most of the time, if it doesn’t work, it is because of driver problems. You can check whether drivers are properly installed by going to Device Manager.
Installing fastboot driver: without disconnecting USB wire, turn off phone, take out the battery. While pressing ON and VOL -, connect USB wire. Most likely fastboot driver will install automatically.
Run 刷入中文Recovery (Chinese CWM recovery). Phone will reboot 3 times.
Entering recovery mode: Turn on the phone. Red LED will light up, before it goes off, press VOL + and -, hold until Lenovo logo appears. If you see Android recovery, it means the above steps did not work. If you see Chinese CWM recovery, flash in the update.zip that you put onto the TF card.
After this post on the Chinese forums, there were many people saying it works, and many people saying it does not work. I (tangys) could not get it to work with my S686. So either I am an idiot, or the guy who wrote the original post is an idiot. So please try it and post back here whether it works for you or not. Thanks.
sralli said:
i was also facing the same problem. i couldn't root my phone, at last i found solution on this page-
Mod Edit: link removed, it worked for me i hope it works for you, and it roots in just 5 minutes
Click to expand...
Click to collapse
just use framaroot i think it's downloadable on google play then use the gandalf exploit!
Just FYI I`ve noticed that you`ve mentioned Chinese characters in the previous text, let me know if you`ve met any translation problems, i`m the one can do the help
hi.from where i can find kernel or some ROM for lenovo s686.thanks
This following method worked for me. Got ride of the bloatware that Lenovo put on there.
got the files from
www lenovohome net/thread-137736-1-1.html
some detailed instructions to setup here
lenovo zol com cn/177/1763_1767961.html
I'm a noob at rooting/changing firmware so took some extra time.
Need to setup the ADB drivers. This was slightly involved as the drivers from the phone ITSELF showed up as not properly signed. So I had to go and turn off the win8.1 check to get it properly installed. You end up with Lenovo ADB Device in device mgr and a few other Lenovo items.
Basically, there's an exe that you run (name has chinese char in it.. so it may look strange). It's an automated CWM installer. My version now shows CWM 6.0.1.5. All the text in there is in chinese.
Lastly, you flash in the update_v2.zip and when done, you get a root enabled , bloatware removed CYANOGENMOD system.
One note: when done flashing and you choose reboot, there is actually a prompt for you to "repair root". I've found that you must say yes at this point. Otherwise, root is not working when rebooted. You'll have to repair root later.
That's the good side. Now the bad side:
This phone only has 3 keys (pwr, vol+ / -) so there's currently no way to get menu button.
There is also no store in the version flashed....no sure how to install any apps
Need to resolve these issues.
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
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!
I have a rooted S7 with TWRP recovery on it and i recently deleted my OS by accident as i was just trying to reset my phone to factory settings. Now the only thing i can do is boot into recovery mode and download mode, or i can just get stuck at a boot loop.
I have googled and googled and seen so many ways to try and fix this issue but nothing has worked for me. Heres a list of the issues i have and what i've tried so far. [Using Windows 10]
Installing Odin (3.12.3) and stock Samsung firmware from here.
Installing the necessary USB drivers from here.
My PC wont recognize my samsung device in either modes (recovery/download) and Odin wont recognize my phone either, as well as i cant find anything under "Device Manager".
Tried using ADB to transfer files to my S7 but when i activate ADB in recovery mode it just loads for a couple of seconds until it displays an error with no explanation.
I even tried downloading ADB drivers and necessary tools i got from this guide.
I also tried wiping Dalvik cache and cache.
I have tried three different USB cables on all available USB slots on my desktop PC and the one USB slot in my Surface and nothing works.
I have tried rooting previous phones but I'm still new to this rooting thing and there's a lot i don*t understand. Perhaps i downloaded the wrong USB drivers, or maybe I'm just unlucky. I just really need some help to understand how to fix this. If it can't be fixed is it possible to remove all traces of rooting on my phone?
The phone needs to be in Download Mode to use ODIN
The only sign it is connected is a COM port lit up at the top of the ODIN window
Add the .MD5 ROM to AP and hit start
A few months ago I bought a TV Box X88 Pro S 4GB RAM 128GB eMMC, Allwinner H616 CPU and Mali-G31 GPU. (e.g. TX6S / H40 / H96 Max / T95 / T98).
Despite an error here or there, it works perfectly. But I thought I could solve some errors if I reset to factory default.
Yes, I reset it, and some errors disappeared, the TV Box still works, however, I felt like changing the ROM, that's when I found out that after the reset, the recovery mode is now just a black screen. And I knew the mode worked normally before as I had already booted into this mode once.
As for the fastboot mode, I could only access it through recovery or through Magisk (the TV Box was rooted, in fact it was already like that and in the settings there was the option to enable or disable root, but this option no longer works since the reset also erased root.)
All my attempts:
(USB debug mode enabled and original ROM and also TX6S ROM)
1. Flash compatible firmware via USB. = Failed.
When connecting the TV Box to the computer and pressing the reset button on the AV input, the system did not install the device driver because it "didn't have a driver". Even searching the internet and installing what should be the correct driver, the TV Box was not recognized in "adb devices" or "fastboot devices".
2. Flash compatible firmware via SD CARD. = Failed.
The TV Box simply has the same black screen when trying to boot from recovery.
3. Flash a compatible firmware via WI-FI Debugging. = Failed.
TV Box doesn't even have that option in the "Developer Options".
Then that's it. Fortunately the TV Box still works normally. Don't know if you can consider it to be bricked. I was just wondering if anyone can give me an idea of what I should do to flash a firmware on a TV Box that won't boot into recovery or fastboot. Although I'm already hopeless. Or maybe someone can tell me what process I did exactly right. I do not know.
Excuse my bad english, thanks.