Hi.
We are discussing on the Lenovo Forum about bricked Thinkpad Tablets and for the moment we got some attentions from Lenovo moderators and technical people.
We need help on reporting everything we can found about this problem on the Lenovo forum:
http://forums.lenovo.com/t5/ThinkPa...1-Errors-on-Recovery-Menu/td-p/1055573/page/2
If you have a Thinkpad Tablet that can not be restored because :
1) The "factory reset" is not working (keeps looping on the Lenovo Animation)
or
2) The "Android system recovery <3e>" is not working. You can not access it (freeze on Booting Recovery Kernel Image") or if you can access it is showing errors and can not be used.
Please visit the forum and post your problem. Also send to the Lenovo user NINE your problem description.
http://forums.lenovo.com/t5/ThinkPa...1-Errors-on-Recovery-Menu/td-p/1055573/page/2
I can not guarantee that Lenovo will solve our problems, but we have to take the opportunity to show them the problems we are having.
Regards
Martin
By the way, I'm trying to document as much as I found about this Tablet on the XDA Wiki
http://forum.xda-developers.com/wiki/Lenovo_ThinkPad
Any help, more information or spell check on the Wiki is also welcome too.
Related
deleted wrong forum
I wasn't aware Lenovo made a "Kindle". Where can I get one of these Lenovo Kindles?
Sorry for my poor English. My lenovo k1 can't start up!!!
I have upgraded my lenovo k1 to 4.1.2 and it is working smoothly.
However, since I want to use a app that need to modify the model,
I rooted k1 by modifing the model message in build.propin system file.
But the app was still not work, I directly use the original build.prop to cover the modified one.
After that, I restarted my k1, it stoped after the lenovo logo appearing. It couldn't enter the UI.
But it could still enter APX model.
Can anyone provide me a downgrade rom? Thank you very much!!~~~~
I currently have the 20C3 Lenovo Thinkpad 10 Tablet, I have searched everywhere and cant seem to find the firmware for enabling 3G Call option.
Would there be any solution here ?
Many thanks.:good:
Maybe you've found a solution in these years, but here's my two-cents for someone else searching for this (if)
I'm not sure what your problem is exactly, but if device manager and Lenovo Vantage don't get you your driver/ software, go to Lenovo Support site, navigate to downloads section of your device, and manually download the drivers/ utility you require. If none of these work, chances are you don't have a 3G modem installed.
Device: Asis Zenfone Max1 Pro- ASUS_X00TD
On booting the device, I am getting the following error message " Your device is corrupted. It can't be trusted and may not work properly"( picture attached) " . The device boots if I keep on pressing the power button. From the research I did on this it seems, the software ( image ) was corrupted and I needed to install the software from the brand website. So I downloaded the image file and installed it following the recommended procedure. However the error is still persisting.
Is this error only due to a software problem or it can be a hardware related problem as well? If it is a software related problem only, how do I resolve the problem?
Thanks in advance for any help.
PS: Mods if this is not the correct forum for this question, kindly point me to the relevant forum and will post the question there. Thanks.
Problem becomes more problematic
Am bumping this up as this problem is becoming an unmitigated disaster.
Contacted ASUS customer care with the problem as detailed in OP.
Their support rep gave a solution which involved going back to a previous version of the image. Reason he gave was that the image I had flashed after d/loading from their website was a beta version and not stable.
Followed the process.
End result ? Now the device is asking for a password which feature ( password security ) I did not activate at all.
I will appreciate if someone can help me fix this mess.
TIA
aCs_ND said:
Device: Asis Zenfone Max1 Pro- ASUS_X00TD
On booting the device, I am getting the following error message " Your device is corrupted. It can't be trusted and may not work properly"( picture attached) " . The device boots if I keep on pressing the power button. From the research I did on this it seems, the software ( image ) was corrupted and I needed to install the software from the brand website. So I downloaded the image file and installed it following the recommended procedure. However the error is still persisting.
Is this error only due to a software problem or it can be a hardware related problem as well? If it is a software related problem only, how do I resolve the problem?
Thanks in advance for any help.
PS: Mods if this is not the correct forum for this question, kindly point me to the relevant forum and will post the question there. Thanks.
Click to expand...
Click to collapse
ASUS OTA updates corrupting device software & hardware both
*****Problem Solved*****
The problem not just with the software but also the hardware was caused by ASUS OTA updates.
Problem #1
The device got corrupted. Whether it was corrupted or whether it was just an erroneous error message is a matter of enquiry/research. Neither am I interested nor do I have the time to waste any further on this disaster.
Problem #2
The mic stopped working. This was remedied solely by rolling back to a prior version as advised by the customer care rep of ASUS.
Long story short which is still quite long ( apologies for being long winded )
After applying firmware rollback as advised by ASUS call center rep, the device got stuck at asking for a PIN/Password.
Given my illiteracy of technical issues, I did not have the foresight to do a simple factory data reset and move on.
So, I wrote to ASUS customer care. The incompetent people at ASUS customer care asked me to go to a different version of the firmware. That did not solve the problem. They then responded that I have to get a PAID service done to remedy the problems which would include service charges both for software and hardware issues SEPARATELY.
I gave up in disgust and decided I would purchase a new handset.
As luck would have it, Youtube referred me to a video on the issue.
Following the process shown in the video I was able to remedy the device corrupted error message.
Now I inserted a SIM card in the phone to see if it was working. It was still not working properly.
Then I googled for mic related issues. I came across links which suggested that mic functionality in these devices had been messed up by OTA updates.
So, I decided to go back to the firmware dowgrade.
I installed the downgrade firmware.
I did a factory data reset.
I activated the device.
The device is now functional.
Learnings from this disaster:
ASUS personnel are either grossly incompetent
OR
the company i.e. ASUS is running it's business in an unethical way.
Resources used to solve the problem:
Firmware applied to get the device functional
UL-ASUS_X00T-WW-16.2017.1912.060.999-user
Link: https://dlcdnets.asus.com/pub/ASUS/...272.532609309.1588748286-143972924.1567247258
Youtube video link
https://www.youtube.com/watch?v=qfFt0eKDFfU
For the moderators of the forum:
Can you kindly amend the subject of the thread to " ASUS OTA updates corrupting device software & hardware both". Thanks for your help.
Hello all,
my company have buy a lot of Lenovo m10 tablet, with a contract with LENOVO Inc.
Our tablet have receive from factory a personnalised boot screen, a personnalised background, from Lenovo. (after a hard reset the personalisation stay)
All our personal receive a m10 and set a lock schema and a personnal google account.
Now a lot of people have quit my company and i want to reset all the m10 tablet, but they have don't unlock their m10 and i don't have the schema ...
I try a hard reset but the tablet ask me the schema even after the hard reset.
Today i call LENOVO and they said "it's impossible to restore your tablets, you have to change the motherboard ..."
Are you agree with this ?
Thanks for answers.
It depends on how Lenovo customised the tablet. If the bootloader or Trust Environment are customised, then you'll have to replace the motherboard.
But here are some ideas to try. Be warned: if you try these ideas and they fail, then you might brick the tablet. So only experiment on one tablet.
Try restoring the tablet using LMSA (power off option). It wipes and resets the tablet, then flashes the stock ROM. LMSA is available on the Lenovo website.
If LMSA refuses to rescue the tablet, use QComDLoader to flash the stock ROM of a similar M10. LMSA will download any tablet's ROM. Look in your c:\ProgramData\LMSA directory for the files. QComDLoader is also in there.
Thank you for your help.
If i win trying to install Stock ROM (witout personalised screen ...)
I've a lot of tablet unlocked, could i download the bootloader from this tablet and re install it on my "stock rom" tablet ?
gcooo said:
... could i download the bootloader from this tablet and re install it on my "stock rom" tablet ?
Click to expand...
Click to collapse
Wait! You might not need LMSA or the stock ROM.
Is your problem:
I do not know the lock password; or
the tablet won't accept a different Google account after I factory reset ?
If it is the first, then factory reset should fix it. Only use LMSA if everything else fails.
If it is the second, then you have an FRP problem. It is a Google anti-theft feature. You do not need LMSA or the stock ROM. Watch this to fix.
Hello,
my problem is :
I do not know the lock password; or the google account of the previous owner
But after a factory reset (Wipe data, factory reset), the first thing after the reboot is to unlock th tab with the previous owner ... ands only after that the tablet will be reset
I've messaged you with more information.
Thanks you for your message !
I've seen the vids you indicate to me :
Watch this to fix.
but my tablet is up to date so it doesn'ty work.
But in the comment i found 2 others vids and the last one is the good one :
thanks a lot !
gcooo said:
Thanks you for your message !
I've seen the vids you indicate to me :
Watch this to fix.
but my tablet is up to date so it doesn'ty work.
But in the comment i found 2 others vids and the last one is the good one :
thanks a lot !
Click to expand...
Click to collapse
Excellent. So it was an FRP problem. Great to hear it worked.