Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
Hello,
I tried to update the radio and the SPL version on my Tattoo. Everything went fine until I had to reboot my phone. It shut down alright, but it never powered on again.
These are the following problems I am having with my Tattoo at the moment:
Cannot power on phone.
Cannot boot into recovery mode.
Cannot boot into FastBoot.
When I connect it to my computer via USB, nothing happens.
The only thing that it's responding to is when I connect my it to my charger.
Does anyone have a solution or is my phone dead forever?
Thanks ahead!
bump? anyone?
Send it back to HTC. If anyone can do anything about it they can. There's nothing else you can do. Sorry
boo.. that sucks..
Well, thanks anyway
Ehm, I don't want to post a New Thread so I'm gonna ask here:
Does anyone have the pinout for the Tattoo?
Take a look at this. I guess they fix such things (but you never know if they just are after your money. http://www.ort-jtag.com/index.php
Yeah I saw that already. Also, there is a file name Tattoo Jtag on their website in the Support section. However, to access that section you have to enter your products serial number (which is I'm guessing the phone's serial number). I have tried several serial numbers (including mine) and all of them were 'invalid' so I never checked the files out.
Also, they only have one thing in the shop which is a kit and it costs $330 so no thanks
I have a similar problem, I would like to share my knowledge although I must be completely out of way.
My experience is based on the BeagleBoard and Angstrom so I really don't know the HTC HW and Android at all...
- The device boots from an xloader that instructs the device how to proceed with the boot
- the bootloader takes place (great u-boot in the beagleboard ?? in the HTC phone) the bootloader allows for ROM or kernel+rootfs flashing and much more
- now the kernel is loaded.....
User mode applications do not allow to have access to the memory area where xloader and u-boot lie so they should be safe all the time to allow for device reflashing.
So we should have access to the device via bootloader anytime if we knew how... maybe somebody can help us further.
Fabio
Same here...Exact same issue...No Recovery mode...No USB Connectivity, Screen turns on but is blank, alhough I did see Tattoo popping up initially but not any more...All I can see is the LCD back light turns on...Battery does charge...Also when I try to enter Recovery mode screen keeps blinking as if it is trying to restart again and again...Someone help
similar problem here, but i get absolutely no response from the phone, it doesn't even recognize the charger. do i just throw it away and buy a decent one or is there a solution?
Sparky the only way for now to fix that click is to bring it to some service point that have that ort jtag, because only way to fix that is to writte new boot sector on phone . Im sure that i know at least 2 services that have ort jtag in Novi Sad . Look for marvel *Miroslav in Ns, or send me private message
same thing happened to me
just this morning, and in desperation I tried hard to remove the batt cover (prob pressed some of buttons, I felt a jerk and ho it was back in amon ra`s recovery, nect time I just removed the battery waited for 30 secs, then press off&home and hold it till recovery came back) but for good half hour NO REACTIONS , ABSOLUTE BRICK, nothing when I put the usb in PC or in socket, dead screen, no sounds and no reaction to ANY combination of keypress. I guess you could call me lucky (in last few days I flashed at least 3 versions of froyo roms, this afternoon I bought =8GB class4 Kingston, formated it in PC FAT32 default size, copied EVE. from my 2gig rom then just turned it down (yes I am brave) and put the 8gig in tattoo, it works like a charm (finger crossed it will continue)
So is there an available Jtag for the Tattoo yet?
I'm in the same situation. No recovery no fast boot, Damm!
I`ve update psfreedom with psgroove_hermes_v4 zip file then my tattoo reboot and now I only get the Tatto title screen but nothing happends.
Somebody have clue to give back life my phone.
Thanks!
if you can get to the title screen, that means you can connect it to your pc via USB and recover from a backup (I hope you made one)
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
payasi35 said:
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
Click to expand...
Click to collapse
You have to enter in fastboot.
Hold volume down and turn on phone.
Cheers
Sorry but as i said before, I can't access to recovery menu neither fast boot menu.
Hey, I've searched both here and on CM forums and even tho Firerat was the only person who gave coherent advice to the people with similar problems I figured I'd ask.
I have a Google Ion as my backup and I've been playing with the 2.2 T-Mobile OTA on it, but since it required non-engineering SPL I've decided to bring it back to CM side. I've made the goldcard and flashed the 1.5 Magic ROM using goldcard. The 1.5 booted fine on it and I've verified S-OFF in the fastboot.
I then downloaded the 1.6 OTA/recovery file for Ion from developer.htc.com and flashed it using built-in recovery (didn't flash custom recovery via fastboot first which I regret now).
Now the phone is stuck in the splash -- I've tried booting it in either recovery or fastboot and it doesn't work -- it goes into splash and stays there.
I've tried both back and Vol Down together with power to get into fastboot -- neither worked.
Did I brick it? Is there still a way to get into fastboot? Any advice/help you guys can lend?
Thanks!
stangri said:
Hey, I've searched both here and on CM forums and even tho Firerat was the only person who gave coherent advice to the people with similar problems I figured I'd ask.
I have a Google Ion as my backup and I've been playing with the 2.2 T-Mobile OTA on it, but since it required non-engineering SPL I've decided to bring it back to CM side. I've made the goldcard and flashed the 1.5 Magic ROM using goldcard. The 1.5 booted fine on it and I've verified S-OFF in the fastboot.
I then downloaded the 1.6 OTA/recovery file for Ion from developer.htc.com and flashed it using built-in recovery (didn't flash custom recovery via fastboot first which I regret now).
Now the phone is stuck in the splash -- I've tried booting it in either recovery or fastboot and it doesn't work -- it goes into splash and stays there.
I've tried both back and Vol Down together with power to get into fastboot -- neither worked.
Did I brick it? Is there still a way to get into fastboot? Any advice/help you guys can lend?
Thanks!
Click to expand...
Click to collapse
If you turn on your phone and connect the usb to your computer to you see a red box pop up at the top saying fastboot usb?
cloths55 said:
If you turn on your phone and connect the usb to your computer to you see a red box pop up at the top saying fastboot usb?
Click to expand...
Click to collapse
Nope, the phone stays in the splash screen, usb connected or not. I can get to a blue led but that's pretty much it.
well your phone is probably bricked then. If you cannot get to fastboot, recovery, or boot up then your phone is pretty much dead (it has happened to me recently too)
since your radio works (blue led) you can use a jtag adapter if you want and shock device back to life.
I am pretty sure that is your only option at this point
I thought as much, but was hoping there's an easier way to trick it to take spl and run it in a fastboot.
What did you do with your phone? Is there anyone on this forum who has the jtag cables/software to bring it back to life?
My phone is still bricked. my plan is to use a jtag adapter to save it, eventually.
Many people I am sure have the necessary hardware to get your phone in working order, and the software is free.
I have too low of a post count to post links but there are tutorials around the forums to debrick your phone with jtag adapter.
look in the dream development forum for the thread on how to debrick your phone. Also look in the general tab on the sapphire forum for the wiki page which has a link at the bottom of the wiki page to bebrick your phone.
I've read from another user that you can buy cheap jtag adapters off ebay.
It's obviously a harder process to debrick your phone than to root it but maybe its worth it to you, idk.
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?
I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.
Have you tried any of the suggestions in the thread you linked in the OP?
EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped
b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Click to expand...
Click to collapse
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again ?
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
ldeveraux said:
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
Click to expand...
Click to collapse
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
python_rocks said:
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
Click to expand...
Click to collapse
assuming windows, check that your drivers are detecting the recovery module
ldeveraux said:
assuming windows, check that your drivers are detecting the recovery module
Click to expand...
Click to collapse
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch)...
Click to expand...
Click to collapse
Cool. Are you doing a Halium port for this device?
Yahoo Mike said:
Cool. Are you doing a Halium port for this device?
Click to expand...
Click to collapse
I'm not a Halium dev but I'm trying to flash the device. Me and another member of the community have our tablets dead after flushing it with supposedly Android 9 ROM. Not even Lenovo's Rescue Tool is helping now.
python_rocks said:
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
Click to expand...
Click to collapse
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
ldeveraux said:
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
Click to expand...
Click to collapse
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
python_rocks said:
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
Click to expand...
Click to collapse
Oh i misunderstood completely! That is worse, i have no clue how to fix it...
python_rocks said:
The tablet won't power on at all.
Click to expand...
Click to collapse
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Yahoo Mike said:
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Click to expand...
Click to collapse
Yeah, I've ordered opening kit. I'm going in. Quite a few people got their devices working by disconnecting the battery and connecting it back. I've noticed that no matter how long the
tablet is on charger the LED stays red, it doesn't change to orange or green.
This same problem has happen to two more members of the community. Same tablet.
We had to flag that ROM as it bricks the tablet.
python_rocks said:
We had to flag that ROM as it bricks the tablet.
Click to expand...
Click to collapse
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Yahoo Mike said:
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Click to expand...
Click to collapse
Thank you for trying to help.
The flash tool doesn't do anything when I click Download and plugging in the tablet while holding the volume down button. Dropdown option was set to "firmware upgrade" as advised.
The guide suggests that it's for people who can at least power on the device. It says "switch off the phone ..." which I don't need to do since I can't even switch it on
python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again
Click to expand...
Click to collapse
Did you mange to fix it?
A. Alaska said:
Did you mange to fix it?
Click to expand...
Click to collapse
You need to use a rework station heat gun or maybe a hair blow dryer might work to heat the sides of the screen to remove it.
I recommend cutting a water bottle in a square or rectangle shape then using the corner to slowly pry the screen off. After that remove the battery ribbon and hold the power bottom for 20-60 seconds to fully drain the charge.
Then recconect it and turn it on 100 percent works.
Just remember you must have the flash tool app and firmware ready in upgrade or download mode while holding down vol. It will reflash the tablet and bam will unbrick.
Just to note down my experiences here as well. I now also got into the same trouble. I tried
TB-X606F_S100015_191127_BMP.zip and also TB-X606F_S300091_201215_BMP.zip
It turns out that with these two you cannot start up the device anymore. Just as the thread-creator described. In my case pluging out and in again seems to give the SP FalshTool the chance to flash again (put it in "Download"-Mode before). So the latest firmware by today - TB-X606F_S300429_21110_BMP.zip - helped me to revive it again.
For me this is nice, but I also wanted to put Ubuntu touch on it just as described here: https://gitlab.com/ubports/community-ports/android9/lenovo-tab-m10-fhd-plus/lenovo-x606 ... unfortunately I am blocked now due to not being able to bring Android 9 on it. btw: There is no proposal on the site which firmware-version is even Android 9. I just guessed from the date.