Related
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
US needs this terribly.
m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.
i could do with the Blue and Red boot logo now
Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?
Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?
Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.
So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.
It seems like there are a few people having trouble going back to stock and getting everything working.
As always, this requires an unlocked bootloader. If you don't have an unlocked bootloader then search google for a $5 service that does. It is what I did.
I flashed Project treble on my TA-1054. It worked great except it kept saying "insert SIM" when there was already a sim card inside, so I could not use it.
I tried to go back to stock but that firmware file on that google drive thread was corrupted, bad upload. Took me a few days to source this original firmware.
There is a tool called OST ( around 115MB), and a patch that comes with it (the smaller file less than 1MB)
The firmware is almost 2 GB
Download everything, including firmware.
1. Install the OST tool.
2. Replace the EXE file in the program files with the patch file you downloaded.
3. Delete the Onlineupdatetoolexe.config file. If you don't do this, the program will not start correctly.
4. Put phone into download mode ( either by powering it off, pluging into USB cable and immediately hold power and volume down. Or if you can boot into android with ADB debugging, just do a adb reboot bootloader.
5. Pick firmware file and click next.
THe first 2 times I tried this, It hanged at the last second. Third time was a charm. Give it time. Use a good USB cable.
I assume that this is the same way to flash other firmware files for other devices.
As soon as i get my hands on a android one firmware, I will flash it.
Or if anyone can guide me on how to extract the firmware on my TA-1045 USA version and flash it to my TA-1054 Chinese , let me know. Cheers.
Google drive folder with all the files I uploaded.
https://drive.google.com/open?id=1NbzO6lfSGacjM2wqrtBg3jMpljsZswne
Thanks bro...I am downloading it.
PL2-2380-0-00WW-B01.NBx.zip is global firmware name. firmware size is 4gb.
thanks! for extract is with nb0 tools FIH Mobile v3.4
https://drive.google.com/open?id=1cSgjrZUxIsN7oLbo7AP-RnILDZdswmB-
its android one firmware. I have no tool for flash...plz try and let me know
Flashing now. Will report back after flashing is done. thanks!!
Edit: Looks like the version I have for OST does not read NBX files. Will try to update that and report back. I have ntool but no working username password
I cannot flash the NBX file. I changed it to nb0 but OST LA says cannot read firmware. Is there any other way to flash?
EDIT: I went ahead and purchased a bunch of credits for NTOOL.
I will flash and see if it works!
It fails with the mdtp.img partition (no such partition) . I would think that it would just skip that partition but it did not. I will later try to extract and flash separately
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
stealthj said:
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
Click to expand...
Click to collapse
can u flash my chinese rom which is nbo format via ntool. I have have ntool but i dont have user name,password, i downloaded rom which u provide.my device still cant connect to mobile data.
NBX format only works on Ntool. but Ntool needs working user name and password to works. OST cant read or flash Nbx format.
if u get Ntool with working user id .. then plz flash my device also via remote mode like teamviewer.
Ntool Bricked my device. the only real restore you can do is by using ost with the stock chinese firmware. edit your apn. why is your data not working?
Global rom cant flash via ntool in Ta1054..showed error in partition. if it will be solved then china to global will be easy process..
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
safron35 said:
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
Click to expand...
Click to collapse
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
stealthj said:
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
Click to expand...
Click to collapse
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
TheImpulson said:
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
Click to expand...
Click to collapse
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
stealthj said:
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
Click to expand...
Click to collapse
How to flash it?
Edit: Also OnlineUpdaterTool in your 1st post asks for a password. What's the password?
nooby_pls said:
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Click to expand...
Click to collapse
I put the original chinese firmware on the first post.
There is an option to install google play store, but that would make your rom unable to receive updates.
Just read the news https://www.xda-developers.com/android-12l-developer-preview-1-lenovo-p12-pro/
It looks like it's still on early stage but here is the link for instructions and download:
DPP
dev.lenovo.com
The first large screen optimized Android OS with new APIs for application developers to provide a better app usage
experience in landscape mode, including easier multitasking, system UI optimization and more.
Security patch updated to 2021-11-01
Android 12L DP1 image is available.
Click to expand...
Click to collapse
WORD OF WARNING!!
DO NOT USE THE LENOVO SMART RECOVERY ON THE CHINESE XIAOXIN VARIENT. If you flash the P12 firmware to the XIOAXIN Variant you will be stuck in the boot loader with no access to Recovery or ADB.
I actually did use the Lenovo RSA (Recovery and Smart Assistant) on my Xiaoxin variant trying to get it to something more English-based. Didn't work w/ what RSA downloaded which was TB_Q706F_USR_S211043_2111300010_Q00243_ROW which showed up recently. Flash happened w/o problems but upon reboot it was not happy and said H/W was incompatible and then powered off. I got it back into fastboot and was about to reflash 12L.
I was able to get into recovery and my Linux laptop was able to push 12L to it even though adb said device was unauthorized. Maybe that was because I had used it on that laptop before? Idk, I just used recovery to go into fastboot mode and then all the fastboot flash/erase commands worked fine.
Slimerang said:
I actually did use the Lenovo RSA (Recovery and Smart Assistant) on my Xiaoxin variant trying to get it to something more English-based. Didn't work w/ what RSA downloaded which was TB_Q706F_USR_S211043_2111300010_Q00243_ROW which showed up recently. Flash happened w/o problems but upon reboot it was not happy and said H/W was incompatible and then powered off. I got it back into fastboot and was about to reflash 12L.
I was able to get into recovery and my Linux laptop was able to push 12L to it even though adb said device was unauthorized. Maybe that was because I had used it on that laptop before? Idk, I just used recovery to go into fastboot mode and then all the fastboot flash/erase commands worked fine.
Click to expand...
Click to collapse
That's great news at least you're tablet isn't useless?!
I believe they may be releasing the final updated for android 12L via ota. (there is a post on the Lenovo forums). If you're lucky this may be a back door to an eventual better rom than the Chinese junk. To clarify it's not the fault of the language that is the issue with the Chinese rom it's the problems with the security app, lack of open CL, broken sound in key apps (JustPlayer) and missing DTS codec which is present on the 2021 Pad Pro 11"
I am wondering if there is any possibility to get an official Stock Rom (europe) of android 11 for xperia 5 ii. I tried to load version 58.1.A.5.530 with emma, but the install process aborted all the time. I was able to reinstall A12 via Xperifirm and new flasher command line tool and I'd like to install now A11 in the same ways. Any help? Thanks in advance
This is also my question! A12 is really frustrating me at the moment (calls dropping, bluetooth connect issues and also bluetooth volume control not working). Also the UI is just to gimmicky in my opinion. Spend the last 30 min to find a download for the official firmware for A11 europe, but wasn't able to track it down...
With more searching, I found a website with an archive of firmware files for the xperia 5 ii: https://support.halabtech.com/
It has the XQ-AS52_58.1.A.1.178_EE UK firmware. This should be it, right?
Firmware XQ-AS52 - Google Drive
drive.google.com
I'm a bit scared of bricking the device, so please let me know if this is the one for rolling back to A11
I don't know. It's definitely not the latest A11. I am not sure if there is a difference between UK and other Europe.
Any help?
I also see
XQ-AS52_EE UK_58.1.A.5.330.zip
and
XQ-AS52_Customized EEA_58.1.A.5.330.zip
these are more recent (aug 2021). Will download these two also and put those in the folder as well. Still not sure which version we need.
Check
https://www.reddit.com/r/SonyXperia/comments/tjpkgx
According to this guide 58.1.A.5.530 is the latest A11 and the author was able to reinstall it. Unfortunately I wasn't able to reinstall it via Emma flash tool but I may try via NewFlasher again, if I have the complete A11 stock rom
Check
https://www.reddit.com/r/SonyXperia/comments/tjpkgx
According to this guide 58.1.A.5.530 is the latest A11 and the author was able to reinstall it. Unfortunately I wasn't able to reinstall it via Emma flash tool but I may try via NewFlasher again, if I have the complete A11 stock rom
NewFlasher: Here
Guide for NewFlasher: Here
I wasn't able to get Emma working for some reason, but will try again. The website I found doesn't have the .530 version for EE_UK, only for RU and Vodafone and Orange phones.
Let me know when you get it working. Good Luck. At the moment my phone runs stable on A12. No freeze since 48 hours
But I think I need the get back on A11 anyway
OK, do NOT use the EE UK firmwares! We need the CUSTOM EEA.
Flashing the wrong one gave an error on booting.
I am now trying to get the 58.2.A.2.80 working again, but am stuck in a bootloop atm. Any ideas?
Try to install xperiafirm and use it to download the right firmware (Android12 only) then use newflasher and the guide I published to reinstall A12 - still better than bootloop
Try to install xperiafirm and use it to download the right firmware (Android12 only) then use newflasher and the guide I published to reinstall A12 - still better than
sociald27 said:
NewFlasher: Here
Guide for NewFlasher: Here
Click to expand...
Click to collapse
with the latest firmware reflashed I am now stuck in a bootloop. Factory reset does not work.
I can get into the recovery menu, but after a couple of loops it says 'device corrupted'
Ok, sorry to hear that. I guess then I was lucky with a NewFlasher Resetup
A12 running again via the official Xperia Companion app
I think I will just stick with it atm
I got another Update today. Build 58.2.A.4.52. I hope it's better now...
The latest Android 11 Europe ROM for Xperia 5 II can be downloaded here:
https://forum.xda-developers.com/t/looking-for-latest-android-11-firmware.4412601/
I have manually reverted it from the FTF format, so it can be used with the Newflasher, you can download it here:
http://koprajs.mx-net.cz/XQ-AS52_Customized EEA_58.1.A.5.530.zip
But if you've already installed Android 12, you cannot probably go back because of the "rollback protection" feature of the bootloader. The only way is to unlock the bootloader and reset the rollback index.
Thank you very much. It freezes all the time, I think I am going to try this.
Hi, guys, I am really needing help.
I have bougth a chinese android tablet model tb128fu. I was worried with the safety of the tablet's ROM, I was suspecting it was a shop ROM. So, I downloaded LMSA (Lenovo Rescue and Smart Assistant) to flash an another ROM (even I have read in LMSA app that flashing ROM mustn't be done in chinese devices - I was very stupid) and it bricked my tablet. Tablet entered into a reboot mode loop: any chosen option was conducting to lenovo's logo and, after it, reboot menu again.
I have posted a question about it here in forum and people suggested to use ROM2box app. I tried to use it and I think it would solve my problem, but during ROM flashing in ROM2box my pc turned off (due to a residencial blackout) and now my tablet is completely died. VOL UP and DOWN and power off buttons are not working, and the screen doesn't show anything, in any situation (even during battery charging).
Please, help me!!! I think I have lost my tablet.
In PC's devices manager tablet is showed as Qualcoom HS-USB QDLoader 9008 (COM3). Does it help anything to solve my problem?
I have also tried to flash some chinese ROM in tablet using QFIL, but all times it shows the follow error:
"Download Fail:Sahara Fail:QSaharaServer Failrocess fail"
I am thankful anyway. Thank you for your attention.
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
xXx yYy said:
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
Click to expand...
Click to collapse
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
joaovitorjvbjvb said:
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
Click to expand...
Click to collapse
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
simplepinoi177 said:
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
Click to expand...
Click to collapse
OWWWW DUDE!!!
I am really thankful . Thank you very much )
Using your download link I got it! I could flash ROM (using QFIL) in my tablet again. My tablet is finally back. Thank you!!!