Database Info

Installed the wrong ROM

Recently I installed a custom ROM that is meant to be installed on a Huawei P8, for my Huawei P8 lite as my new OS because I accidentally deleted my whole OS. When I plug my mobile phone to a power source it shows the Huawei logo, I cannot get it into fastboot/rescue mode. If I try the dload folder to sd-card method it will not do anything. Does anyone know what to do.

Flash the stock firmware. I'm 100% sure your problem would be solved.

munimjaffer said:
Flash the stock firmware. I'm 100% sure your problem would be solved.
Click to expand...
Click to collapse
How do I flash it without fastboot?

pim8181 said:
How do I flash it without fastboot?
Click to expand...
Click to collapse
What do u see when u try to enter fastboot?

munimjaffer said:
What do u see when u try to enter fastboot?
Click to expand...
Click to collapse
When I try to enter fastboot I just see the Huawei logo

pim8181 said:
When I try to enter fastboot I just see the Huawei logo
Click to expand...
Click to collapse
Ok can u enter into recovery mode?

munimjaffer said:
Ok can u enter into recovery mode?
Click to expand...
Click to collapse
Nope....

Your phone got hardbricked with flashing a wrong rom,hardbrick is really hard to unbrick,
i already have one phone that got hardbricked due to flashing a wrong rom,since now i can't find the solution to unbrick it,
hope you find the solution soon..

pim8181 said:
Nope....
Click to expand...
Click to collapse
Is the device recognized by PC? If not, what is device manager labeling the device as?
If it connects to PC and is recognized you can.........
Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:
adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)
If that doesn't work try typing:
adb reboot fastboot (press enter).
If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:
adb devices (press enter, if it returns a serial number the device is recognized)
Then type:
adb reboot bootloader (press enter and it may boot to fastboot)
Or type:
adb reboot fastboot (press enter)
Or type:
reboot fastboot (press enter)
If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.
Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.
You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.
There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.
I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.
If the confused you then I might have confused myself typing it, lol.

Fastboot, ADB and MiFlash don't recognize device

hello guys,
I wanted to do a clean flash of my poco f2 pro. Installed MiFlash, put the device in fastboot mode (it got recognized) and then klicked flash. the device immediately disappered from miflash and nothing was flashed. I can still boot into rom (Evolution X 4.7) but I have following symptoms:
1. Wifi does not work anymore
2. ADB, Fastboot and MiFlash do not recognize the device
3. TWRP (Chinese One) does not ask for unlock code and shows no sdcard contents (but Its there bc I can boot normally with data) --> DATA Partiton is not found.
4. TWRP Nandroid Backup is gone
I tried multiple Computers, Cables and ADB`s... What is the problem?
Could it be a faulty partition? Which one?
Please help me

Which version of Miflash?

NOSS8 said:
Which version of Miflash?
Click to expand...
Click to collapse
newest (20181115)

is the phone boot in fastboot?
check drivers in miflash.

NOSS8 said:
is the phone boot in fastboot?
check drivers in miflash.
Click to expand...
Click to collapse
Phone does boot in fastboot. It just does not get recognised by MiFlash

What happens when you press power and volume + or volume -?

NOSS8 said:
What happens when you press power and volume + or volume -?
Click to expand...
Click to collapse
Boots into Fastboot/TWRP. I did a full reset in twrp now and pushed a rom over via mounting and flashed it. hopefully it works...

Remenber TWRP backup does not work

NOSS8 said:
Remenber TWRP backup does not work
Click to expand...
Click to collapse
It just boots endlessly now I think.
Data loss is not important to me. I want fastboot to work

If fastboot work flash with miflah.

NOSS8 said:
If fastboot work flash with miflah.
Click to expand...
Click to collapse
You dont understand....It boots into fastboot but miflash wont show the device!!

is the pc see the device?
try repair in twrp

NOSS8 said:
is the pc see the device?
try repair in twrp
Click to expand...
Click to collapse
does not boot into twrp anymore... only fastboot. and fastboot des not get recognized

Maybe here https://forum.xda-developers.com/t/...ution-on-forums-google-friends.4199267/page-7

NOSS8 said:
Maybe here https://forum.xda-developers.com/t/...ution-on-forums-google-friends.4199267/page-7
Click to expand...
Click to collapse
thank you for your help but I think I am stuck here. No way to connect to fastboot and it does not boot into sth else than fastboot

If adb work try reflash twrp.
Is your phone rooted?
And power +volume -? volume +?

Premaider said:
hello guys,
I wanted to do a clean flash of my poco f2 pro. Installed MiFlash, put the device in fastboot mode (it got recognized) and then klicked flash. the device immediately disappered from miflash and nothing was flashed. I can still boot into rom (Evolution X 4.7) but I have following symptoms:
1. Wifi does not work anymore
2. ADB, Fastboot and MiFlash do not recognize the device
3. TWRP (Chinese One) does not ask for unlock code and shows no sdcard contents (but Its there bc I can boot normally with data) --> DATA Partiton is not found.
4. TWRP Nandroid Backup is gone
I tried multiple Computers, Cables and ADB`s... What is the problem?
Could it be a faulty partition? Which one?
Please help me
Click to expand...
Click to collapse
Hey, I am having the same issue, were you able to find a solution?

Alcatel TCL A502DL/A501DL root/custom recovery/custom roms?

Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?

lehmancurtis said:
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
Click to expand...
Click to collapse
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.

lmgnsa said:
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
Click to expand...
Click to collapse
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.

lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me

@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!

fliproc said:
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
Click to expand...
Click to collapse
Use a tool that controls bootmode. Mtk-mode-selector

lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Please help, it says "waiting port" forever

Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!

lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.

@lehmancurtis I feel like you might be lying about whether or not your method works, as the boot mode tool does not work. @lmgnsa did it work for you?

I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.

williamhancock328` said:
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
Click to expand...
Click to collapse
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.

Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool

mickeybeats said:
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
Click to expand...
Click to collapse
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.

T
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
lmgnsa said:
To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
Click to expand...
Click to collapse

sj78 said:
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Click to expand...
Click to collapse
It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.

lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.

Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
Code:
fastboot oem unlock-go
Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
Code:
fastboot flash recovery ./recovery.img
Code:
fastboot oem reboot-recovery
That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.

Regular drivers are built into the phone but you may need vcom drivers. I'm going to attempt to repair mine enough to reset and flash again. I'll probably have to nav my screen via commands, but I will attempt to capture the process and show you.

I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off
im going nut that fastboot isnt working with this device.

Unbrick your Realme C12

What is a brick?​If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?​It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?​Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?​Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?​MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux Users​For Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows Users​For Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructions​See Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Credits​xyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References​- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359

MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com

Reserved

I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.

Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip

DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?

HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.

How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?

youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!

DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks

HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11

DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.

I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.

Thanks for your works sir, you are super awesome!

I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?

Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks

Question my device is going in to the bootloader and wont boot normaly

i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7

blocky3321 said:
i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7
Click to expand...
Click to collapse
Do you have an error message on your bootloader screen?

V0latyle said:
Do you have an error message on your bootloader screen?
Click to expand...
Click to collapse
This is what i boot in to every time i turn on the device and if i press start i puts me back here

blocky3321 said:
This is what i boot in to every time i turn on the device and if i press start i puts me back here
Click to expand...
Click to collapse
No error message. Hm. What exactly did you do to get to this point?

V0latyle said:
No error message. Hm. What exactly did you do to get to this point?
Click to expand...
Click to collapse
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
and after flashing everything its like this

blocky3321 said:
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
and after flashing everything its like this
Click to expand...
Click to collapse
Are you able to reflash the factory firmware?

V0latyle said:
Are you able to reflash the factory firmware?
Click to expand...
Click to collapse
Ok i can using qpst right?

blocky3321 said:
Ok i can using qpst right?
Click to expand...
Click to collapse
To be honest I have zero experience with Lenovo devices; I'm familiar with ADB and Magisk but I'm not familiar with QPST/QFIL.

Can u not use fastboot?

Arealhooman said:
Can u not use fastboot?
Click to expand...
Click to collapse
now no it doesnt show up in fastboot devices

But you can get into fastboot mode? Try draining it and powering it and getting into fastboot

Arealhooman said:
But you can get into fastboot mode? Try draining it and powering it and getting into fastboot
Click to expand...
Click to collapse
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader

blocky3321 said:
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader
Click to expand...
Click to collapse
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.

Install RSA from Lenovo.
Following the instruction to rescue your unit as well as getting boot.img for patching
Moreover, install latest Android Platform Tools
Copy boot.img to your unit and patch with Magisk, and copy the patched_boot.img back to host PC.
Then reboot in fastbootd (adb reboot fastboot) and flash patched_boot.img

LSS4181 said:
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.
Click to expand...
Click to collapse
It does not show up in fastboot and i have quite new adb and fastboot installed

blocky3321 said:
It does not show up in fastboot and i have quite new adb and fastboot installed
Click to expand...
Click to collapse
Well, get newest. Check drivers.

Arealhooman said:
Well, get newest. Check drivers.
Click to expand...
Click to collapse
ok got somewhere got back recovery but still goes back to the screen in the picture. Any way to flash the whole firmware.

blocky3321 said:
but still goes back to
Click to expand...
Click to collapse
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.

f1tm0t said:
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.
Click to expand...
Click to collapse
nope still doesnt work

V0latyle