Hello,
I've recently hardbricked my Redmi Note 9
I've tried shorting some of the pads to see if I can flash it through the communication ports using EDL. I've shorted some of the pads and the flash tool shows these logs..:
[17:54:15]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:54:15]:ls ubs :Communications Port (COM1)
USB Serial Device (COM5)
[17:54:15]:GetScriptDevices
[17:55:24]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:55:24]:ls ubs :Communications Port (COM1)
How do you get the flash tool to recognize the communication port as a device?
Redmi Note 9 uses MTK if I remember correctly.
I hardbricked it while trying to flash the most recent ROM.
One of 2 things could've gone wrong:
Either the fact that I was jumping from Android 10 to Android 11 ( I was using the fastboot ROM)
Or the fact that I accidentally clicked "Clean All and Lock", and then something went wrong there.
However one thing is for sure, the preloader is corrupted. I don't think FRP is gone though.
Any tips?
-Thanks
FriendlyChemist said:
Hello,
I've recently hardbricked my Redmi Note 9
I've tried shorting some of the pads to see if I can flash it through the communication ports using EDL. I've shorted some of the pads and the flash tool shows these logs..:
[17:54:15]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:54:15]:ls ubs :Communications Port (COM1)
USB Serial Device (COM5)
[17:54:15]:GetScriptDevices
[17:55:24]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:55:24]:ls ubs :Communications Port (COM1)
How do you get the flash tool to recognize the communication port as a device?
Redmi Note 9 uses MTK if I remember correctly.
I hardbricked it while trying to flash the most recent ROM.
One of 2 things could've gone wrong:
Either the fact that I was jumping from Android 10 to Android 11 ( I was using the fastboot ROM)
Or the fact that I accidentally clicked "Clean All and Lock", and then something went wrong there.
However one thing is for sure, the preloader is corrupted. I don't think FRP is gone though.
Any tips?
-Thanks
Click to expand...
Click to collapse
Not EDL exactly, devices with MediaTek SoC don't use EDL (this is for Qualcomm), MTK uses Preloader (download) and BROM modes, the preloader is usually inaccessible in newer models or at least useless, so you can use an exploit to bypass the BROM restriction, follow carefully this thread https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
SubwayChamp said:
Not EDL exactly, devices with MediaTek SoC don't use EDL (this is for Qualcomm), MTK uses Preloader (download) and BROM modes, the preloader is usually inaccessible in newer models or at least useless, so you can use an exploit to bypass the BROM restriction, follow carefully this thread https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
Click to expand...
Click to collapse
Interesting, thank you very much..
But here's the thing, whenever I plug it in it still loops, even with the battery being disconnected from MB.
Do I need to let it just... stay put for a very long time? I've done that for 2 weeks and it still loops.
(Windows disconnect / reconnect sound, even when the OS does not recognize any new device)
One more thing, is there a possibility for this method to corrupt the firmware even more? Or is this some real bare-metal stuff that as long as you do correctly you should be fine?
Try this place first
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN 🤓 (Redmi Note 9 / Redmi 10X 4G)
DISCLAIMERS: This help is specific for MERLIN devices only ! (Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G) Keep atention. This is an UNOFFICIAL thread. This thread was based on the thread by Agent_fabulous. Thank you very much ! DON'T ask by PM...
forum.xda-developers.com
that doesn't give you the insight you need LMK
FriendlyChemist said:
Interesting, thank you very much..
Click to expand...
Click to collapse
I missed that thread, I used in the past within other threads/guides, the link provided by @L!V3_4_XC3SS has the steps better done, or at least is more comprehensive.
FriendlyChemist said:
But here's the thing, whenever I plug it in it still loops, even with the battery being disconnected from MB.
Click to expand...
Click to collapse
You need to power it off completely by pressing the three buttons, in the short period you see device is off, then release the PWR button and keep pressing the two volume buttons to enter to BROM mode while you connect to the PC, run first the bypass bat.
FriendlyChemist said:
Do I need to let it just... stay put for a very long time? I've done that for 2 weeks and it still loops.
Click to expand...
Click to collapse
If the trick doesn't work instantly then waiting is no sense, try again.
FriendlyChemist said:
(Windows disconnect / reconnect sound, even when the OS does not recognize any new device)
One more thing, is there a possibility for this method to corrupt the firmware even more? Or is this some real bare-metal stuff that as long as you do correctly you should be fine.
Click to expand...
Click to collapse
Always that you use the Download option you are safe, if preloader is un-ticked from the partitions and if the option Format Whole Flash except Bootloader is ticked too in the Format tab then you are totally safe.
How do I know my device is in BROM mode?
I've tried to first power it off, then pressing the 2 vol buttons. It just.. reboots and keep bootlooping.
FriendlyChemist said:
How do I know my device is in BROM mode?
I've tried to first power it off, then pressing the 2 vol buttons. It just.. reboots and keep bootlooping.
Click to expand...
Click to collapse
Read carefully the thread linked and follow one-by-one all the steps, if you run first the bypass.bat then you will see a message that the DA/SLAA protection was disabled. This way, you'll go to know that you are now on BROM mode.
SubwayChamp said:
Read carefully the thread linked and follow one-by-one all the steps, if you run first the bypass.bat then you will see a message that the DA/SLAA protection was disabled. This way, you'll go to know that you are now on BROM mode.
Click to expand...
Click to collapse
So the payload launches on COM5 correct?
Also I have no way to stop it from bootlooping. I've tried shutting it down, same thing,
Like I said before.
While it's online, it's detected as a USB serial device on COM5.
FriendlyChemist said:
So the payload launches on COM5 correct?
Also I have no way to stop it from bootlooping. I've tried shutting it down, same thing,
Like I said before.
While it's online, it's detected as a USB serial device on COM5.
Click to expand...
Click to collapse
You have to achieve here two main things; install the USB MediaTek preloader using the LibUSB device filter and the second, get your device detected to BROM mode.
For the first thing just connect your device without pressing a button, open the device filter window and see the variants, when a new item appears quickly press on it to install the drivers.
For the second thing, although your device is trying to rebooting this doesn't matter if you learn to make the right combination buttons variables at the right time, wait the exact time that device gets off and press the two volume buttons to attach it to the PC, but first launch the bypass.bat. Be sure that you are understanding what is written here, I had the same issue in two devices and got to sort it anyway.
SubwayChamp said:
You have to achieve here two main things; install the USB MediaTek preloader using the LibUSB device filter and the second, get your device detected to BROM mode.
For the first thing just connect your device without pressing a button, open the device filter window and see the variants, when a new item appears quickly press on it to install the drivers.
For the second thing, although your device is trying to rebooting this doesn't matter if you learn to make the right combination buttons variables at the right time, wait the exact time that device gets off and press the two volume buttons to attach it to the PC, but first launch the bypass.bat. Be sure that you are understanding what is written here, I had the same issue in two devices and got to sort it anyway.
Click to expand...
Click to collapse
I tried running the bypass,
I followed all the steps, installed the drivers, and the filter lib usb thingy.
I got an error while running the first bypass:
Traceback (most recent call last):
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 213, in <module>
main()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 44, in main
config, serial_link_authorization, download_agent_authorization, hw_code = get_device_info(device, arguments)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 136, in get_device_info
hw_code = device.get_hw_code()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 178, in get_hw_code
self.echo(0xFD)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 110, in echo
self.check(from_bytes(self.read(size), size), words)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 88, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0xfd got 0xfe
FriendlyChemist said:
I tried running the bypass,
I followed all the steps, installed the drivers, and the filter lib usb thingy.
I got an error while running the first bypass:
Traceback (most recent call last):
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 213, in <module>
main()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 44, in main
config, serial_link_authorization, download_agent_authorization, hw_code = get_device_info(device, arguments)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 136, in get_device_info
hw_code = device.get_hw_code()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 178, in get_hw_code
self.echo(0xFD)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 110, in echo
self.check(from_bytes(self.read(size), size), words)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 88, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0xfd got 0xfe
Click to expand...
Click to collapse
Don't worry, this message usually appears, just keep it trying, you need to get device in BROM mode, and it'll work. Also, you can check for this thread, if you are lacking or missing some info https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
Hello guys, I have a problem with the Redmi note 9 phone. You know that the Xiaomi interface has more negatives than the stars of the universe, but the Indonesian ROM has no problems, so I tried to change the phone from the world version to the Indonesian one, but in a way somewhat like a loophole, which led to the phone restarting itself Over and over again, I went to the phone maintenance specialists, and they told me that it needed a memory ic, but someone was able to download the Xiaomi system, which resembles a little Nokia, but through it I entered a new Xiaomi version, but the only remaining problem is the lack of service. I cannot call or receive calls or data, but all Something other than this works, so I understood from a phone specialist that the files in the memory ic have been corrupted, so the service does not work, so is there a solution
NB
The phone is rooted, but I can remove it​
The Wi-Fi is working and the Wi-Fi IP address is working​
the IP address of the network tells me that it is not there​
The serial number of the phone itself is not with me, but I think that if the Indonesian version has the serial number, I can find it​
I welcome any risky method​
Sorry for the weak language​
OMAR1.zx said:
Hello guys, I have a problem with the Redmi note 9 phone. You know that the Xiaomi interface has more negatives than the stars of the universe, but the Indonesian ROM has no problems, so I tried to change the phone from the world version to the Indonesian one, but in a way somewhat like a loophole, which led to the phone restarting itself Over and over again, I went to the phone maintenance specialists, and they told me that it needed a memory ic, but someone was able to download the Xiaomi system, which resembles a little Nokia, but through it I entered a new Xiaomi version, but the only remaining problem is the lack of service. I cannot call or receive calls or data, but all Something other than this works, so I understood from a phone specialist that the files in the memory ic have been corrupted, so the service does not work, so is there a solution
NB
The phone is rooted, but I can remove it​
The Wi-Fi is working and the Wi-Fi IP address is working​
the IP address of the network tells me that it is not there​
The serial number of the phone itself is not with me, but I think that if the Indonesian version has the serial number, I can find it​
I welcome any risky method​
Sorry for the weak language​
Click to expand...
Click to collapse
Don't take to "specialists" if you hope for a solution when it has nothing to do with hardware, they know no more than a little about software, it is very risky to let it people that can make more harm than good.
The serial number is always there, but the issue may come from an altered IMEI, or a lost baseband connection. Take your IMEI, dialing *#06# and put it here https://imei24.com/imei_check/Samsung/ to see if it matches with your device, then check if your baseband is there.
And ask the service center in-charge, which method they used to flash the software, an incorrect one could make the issue be triggered.
good forums. I'm new to the forum and I have a problem. My research to solve this has brought me here. I couldn't find the exact answer and wanted to ask you guys. I have a redmi 9c (m2006c3mg) device and I took this device in a mode from test points with a request to flash it. But I don't know exactly this mod I bought. The phone appears as Mtk Com Port in my device manager, but I could not boot my device normally with any key combination, battery removal and removal. All I want is to boot my device normally thanks for your help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your main window should look like this:
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
For whatever reason, my devices isn't showing up when writing "fastboot devices" but shows up in QFIL. Any suggestions?
Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Ale_ax said:
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
Yes, this one is weird. Some people are able to lock it, and some are not.
To my understanding you need to lock it to get OTA's. It's still possible to update, though, through downloading the newer update and installing the update in .zip format on stock ROM.
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Joncka said:
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Click to expand...
Click to collapse
Thank you, btw they are for the "TB-J716F" Xiaoxin pad pro 2021n, Legion Y700 is "TB-9707F"
Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Just for anyone else having trouble getting into EDL mode (my Y700 wasn't bricked, I just wanted to restore stock rom):
When the tablet is running normally, go to developer options, enable USB debugging, then go to the platform-tools folder on your PC and open a command prompt there, then type "adb reboot edl". Then you'll see the "Qualcomm HS-USB QDloader 9008 (COMxx)" Port under Ports in Device Manager.
To re-lock, I believe you can use these instructions. The command "fastboot flashing lock" brought up the menu on the Y700 screen to re-lock, but I didn't do it because I didn't want to delete my user data (I'd just spent time setting up all my apps!)
When I was in fastboot, the tablet was showing up with an exclamation point and just called, "Android device" in Device manager, I used the drivers from here to get it to show up as "Android Bootloader Interface".
Don't do what I just wrote!! I did it and now I'm stuck and it won't boot, and I can't get to EDL mode.
I don't have time to work on it now but my tablet is effectively bricked.
I'm in a bootloop to the fastboot screen, and it shows up in Device Manager as "Android Bootloader Interface". I can't flash in QFIL as described above because it just says "No Port Available". I can't get to EDL mode as I did before because I can't boot the tablet as usual to enter the "adb reboot edl" command.
"adb devices" doesn't show the Y700.
Can anyone tell me how to get to EDL mode when I can't get adb to work?
Ale_ax said:
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
That's what happened to me! How did you get it back into EDL mode after unlocking?
Mine isn't showing the Qualcomm device under Ports in Device Manager anymore, so I can't get the port to show in QFIL!!
Got it to work getting to EDL mode, phew!
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
Click to expand...
Click to collapse
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
shahrul5689 said:
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Click to expand...
Click to collapse
Yep, I can get ota with that vpn
gnoted said:
Got it to work getting to EDL mode, phew!
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
Click to expand...
Click to collapse
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Ale_ax said:
Yep, I can get ota with that vpn
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Click to expand...
Click to collapse
Haha, maybe I should read more of the comments before assuming things.
Hic, I just got a second hand Y700, it had an original Zui 13 chinese rom, and I started to OTA update upto ZUI 14. Then the Google Play disappeared, also the PC mode. I tried to downgrade to ZUI 13 with this guide WITHOUT enabling usb debugging nor oem unlock. The flashing process succeeded, but when the tablet reboots, it shows for the first time "Your device is corrupt, It can't be trusted and will not boot", after that keeps showing bootloader menu.
Please help me what to do from this step?
I'm in a different state from others here, I think; my Y700 appears to be totally bricked. It's plugged in to charge and nothing's happening at all. I originally installed crDroid on it, but ran into Widevine issues and was going to revert. I don't remember the last steps I took on it (it was a month or so ago), but when I picked it up again a few days ago, turning it on showed only a black screen (only detectable by seeing the backlight), so I let it discharge the battery entirely planning to try and fix it via reflash later. Now, however, it's doing... nothing.
I'm going to let it charge overnight and see if that changes anything, but if anybody has ideas what might have happened or things to try to get out of this, I'd appreciate it!
Hi, I'm stuck after flashing the Chinese stock rom on my legion y700. I was first successful except for upgrades which were proposed and installed but wouldn't show after reboot. I decided to flash again hoping that would solve the problem. But now my tablet remains in EDM mode and won't start. The final message in Qfil was 'download successful'. It is fully charged
Any idea on how to solve this issue?
I am in yet another state. I only run Linux (Mint 21), and have not been able to get any version of wine working, so I cannot use QPST or QFIL (windows .exe's). I CAN access my Y700 via adb or fastboot, and it is now unlocked. It was unsealed when it arrived, but does NOT have any google stuff on it.
I have downloaded all of the components needed from apkmirror, and followed instructions in the Y700 topic to activate them, to no avail.
Sadly, since I do not read Chinese, and the use requirement needs google, it might as well be a brick.
Further, despite more than 40 years doing technical support on all sorts of computers, I have never yet flashed an android device. Can it be done from adb or fastboot? If so, how do I specify which partition to flash? Does anyone have a guide to help me get started? I wish to put cdroid on it, do I use the .xz file or extract the .img?
OK, I've just found something I missed, but it doesn't work for me. My terminal is in the same folder as the .img
fastboot flash boot crDroid-8.10-arm64_bgN-Unofficial.img
Sending sparse 'boot_b' 1/15 (262088 KB) OKAY [ 8.186s]
Writing 'boot_b' FAILED (remote: 'Value too large for defined data type')
fastboot: error: Command failed
What am I missing (apart from a brain!) is this the correct partition to write crDroid to? is there an option to set the data type size? if so what?
Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
A lot of this does not seem to work on Linux (Mint 20.3).
fastboot flashing unlock
worked for me, and while I have no problem getting into recovery or fastboot modes on my Y700, I never see anything I recognize as EDL. On a machine with 'wine' installed and working, QTSP installs and appears to run OK, as also does QFIL. I can select the "rawprogram" and "patch" files OK, but it cannot find a port.
Both adb devices and fastboot devices report the correct device when it is in the appropriate mode, and
fastboot flash system crDroid-8.10-arm64_bgN-Unofficial.img appears to have successfully flashed correctly, but it is still unable to communicate with Google servers. All good (tear hair out type) fun!