[REQ] Stock emmc binary image/phone image for the M2 - Sony Xperia M2

Hey everyone!
I've gotten myself into a quite a situation, bricked an M2 (it's in qdloader mode at the moment), tried flashing various phone/emmc images on it from devices using the the same SoC (Moto G, Redmi 1s) but those do not work (well, they do to a certain extent, still experimenting with that), I suspect mostly cause of Sony's non-stock partition layout.
I'd like to get the phone back to at least a bootable state but I figured that won't be possible without Sony's modified MSM8x26 binary image or at least a partitions.xml from a working phone.
So, in short, I'm looking for either an 8x26_msimage.mbn or partition/singleimage binary or a partitions.xml that fits this device.

Flash a FTF

The phone has no bootloader at the moment, it's recognised as a QDloader port when connected to a PC, and as far as I understand, unless I flash the stock partition system and stock bootloader back using QPST, I can't get it into flashmode to flash any firmware through normal means. (The usual startup methods do not work, no Volume down for flashmode or vol. up for fastboot)

Hmmm, I didn't know the existence of that mode, it's seems that your bootloader is damaged, where is located partition binary?
BTW, what did you do to brick your device?

Ask @srl3gx, I think he might help you a bit because long time ago he had bricked his Tipo and tried to fix it.
Start reading from this page then he says he bricked Tipo.
http://forum.xda-developers.com/xperia-j-e/orig-development/tapioca-cm11-kernel-3-4-t2581726/page38

Related

Help bring my G3 back to life!!!

So, here's the story: I wanted to root my d850 on LP version D85021R, Tried all methods posted here, including this, this, and this. None worked. So I decided to downgrade to KK using tot/kdz method by hyelton. Downloaded LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot file and LG flash tool 1.8.x and flashed the tot file. Progress went above 85% and then phone rebooted, but never came back to life; super-bricked, no led, no boot screen, no download mode, no recovery mode, NOTHING! except that it identified as QHUSB_BULK in Win7, which upon installation of drivers turned to qhsusb_dload 9008. Tried all unbricking methods including Board Diag, Flashtool ,etc. none worked. So I took it to a repair guy, who probably used octopus box to copy image from another g3 (at least that's what I think, he would not let me see but i sort of glanced over). After copying that image to my g3, it turned back to life, i.e., boot screen appeared and download mode/recovery mode worked, but it was in a boot loop. however, that guy also tried flashing V10D using flashtool, and same thing happened, i.e., super-brick again. After a day of trying he gave up on it but was kind enough to give it back half alive. So now boot screen appears, download mode works, gets recognized as LGE Mobile USB Serial Port, and LGE Android MTP Device with a yellow triangle. I cannot access fastboot mode due to locked bootloader, or else I would have tried flashing partition images through fastboot, as bootloader and boot partitions are intact, so I would not touch them but could try flashing other partitions. LG Flashtool flashes the whole package so the boot sector also gets over written, which somehow is not compatible with stock rom. One thing which I have not mentioned is that I did not buy it new but refurb one, so may be some part was changed, but which one, no idea. I tried to get it recognized it in linux, but does not work; shows up as libmtp-1-1 in /dev, which is not mountable. However I was able to pullout one interesting fact, which might give some hint. dmesgs shows a serial number for this device which starts as LGD855xxxxxxx, whereas the serial number printed on the back is different, where it shows as d850 and serial number is also different, i.e., 406KPXVxxxxxx.
Now I am out of options. Can someone please suggest what else to do. Also, can someone confirm that the serial number shown in dmesgs when connected to USB port, starting with LGD855xxxxxx can be a d850?
Any help is welcome
First off when flashing almost every time it'll fail at 85%. That's normal. Anything after80% is just rebooting of the phone.
Now what your having is not normal. Maybe whatever the repair shop did changed the serial? And your issue usually means your bricked completely sadly.
Before your downgraded, was your phone booting normally or did the root do something to make it originally boot loop before trying to downgrade ?
Sent from my iPhone using Tapatalk
Thanks for replying hyelton. I fully understand that and also that rebooting should bring the phone to blue reset screen, but it didn't. Instead it died.
The serial number and IEMI fortunately are intact, and are read by firmware when present. Sadly I tried to flash the firmware again through Board DL option, but failed again, so back to QLoader 9800 mode. On WinXP, smart boot diagnostics recognized it and proceeded to flash boot/recovery, but sadly the accompanied AP_Chip file neither has D850 nor D855 Smart_Boot.bin files. So I flashed EUR xxxx.xxx version. Phone still dead, but no Qloader 9800 mode, instead Android Phone device started showing up, which had no supported drivers. After some effort, Windows 7 download drivers and it got recognized as AlCatel Android Phone, lol! No adb and fastboot in Windows, and no Serial communication was possible. I tried linux and there fastboot was showing a device without id, like ??????????, but it did allow me to flash individual mbn paritions extracted from D850 tot to their respective partition, but I discovered I cannot flash through fastboot files larger than 2GB, so no system and no userdata; those were erased only. Upon reboot and return to windows, phone is still dead (without any life) and back to Qloader 9800 mode.
So now I'm stuck due to lack of firmware files. I am afraid to flash a boot or recovery partition extracted from any other firmware, but can try D855 since it worked partially to bring download/recovery partitions and LG logo was also displayed upon turning on. I think it even booted basic kernel in download mode, because I was able to send reboot command through Send_Command.exe and it rebooted. So scripting was also a possible option, but not anymore.
Is the partition layout of D850 and D855 available somewhere? I tried to find but could only find for D851. If someone having these variants is willing to help, I'll post the commands to get partitions layout, or even partition images could be created using dd command if phone is rooted.
To your question, no, the rooting methods did nothing. It was working normal. But somehow I came across a lot of threads that suggested hassle-free downgrading to KK for rooting, and pointed to your guide which surely is hassle-free but not for a troubled phone like mine
BTW, I do have Flashtool log files for original downgrade and then reflashing yesterday. If someone wants to take a look...
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
unikorn74 said:
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
Click to expand...
Click to collapse
Flash it to D855 Lollipop version via octopus than write DUMP
It does work, indeed. We did it together, didn't we, aamszia?
To elaborate further, Aamir helped me out by writing D855 bootloader through octopus box. That was done before but flashing a KK rom again bricked it. Only this time, he flashed a d855 lollipop kdz rom (v20g, if I remember correctly). That made it functional; everything worked, except radio. Flashing a d850 LP radio would not work; flashing a KK radio would brick it. So I took a dump of mmcblk0 from a fully functioning, rooted, recovery flashed LP d850, via terminal using dd command (I chose to write only first 4gb or so due to smaller sdcard I had. That covered all partitions except cache and userdata, which were not needed anyway). Then I wrote back the dump on the bricked d850 using dd command from terminal. I tried flashing TWRP on it first, but somehow it did not work, and gave secure bootloader error. So I had to do it via terminal. I knew once it starts writing, the system would become unstable due to overwriting of partition table, kernel, system, and stuff, but I had to give it a try, and it worked! Screen went off immediately, but I touched it again after half an hour; pulled out and reinserted the battery; tried recovery and there it was. Rest was easy. Just formatted cache and data, and my phone was back to life.

[Completed] HELP!!! Unbrick Xperia S (bootloader problem no flashmode)

I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.

How Motorola changed my opinion about Moto Phones[Also Unbrick guide]

Hi Guys,
I got a Moto Z from US recently(I live in Asia).One day I was charging my phone.I got uncomfortably hot.So I decided to power off my device and when i restarted it,it got stuck on bootloop.I did try factory resetting my phone and then went to Motorola Service Center.Even though it was under warranty they refused to service it because it is from another country(Even though I agreed to pay $300 they were charging for a MoBo replacement.
After any hope of getting the device up and running,I tried to update the device in fastboot mode.I made the mistake of using an older firmware thereby Hardbricking my device
I did manage to get it to back to life by using this file
https://forum.xda-developers.com/mo...-to-unbrick-moto-z-hardbricked-t3590133/page2
(post#18)
Step 1: If your PC detect the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.(thanks to:manish54 ,benzinerwin)
Then I started to update the stock ROM.But it wont take any gpt.bin(GUID Partition Table) files.
(error)Preflash Validation failed
Without GPT I cant update anything at all.If anyone can help that would be great.

XZ Root/TWRP/ROM Help

Hi XDA,
It's been a while since I've done any work on any phones, I've previously used roms on Galaxy S and SIII. But those are a while ago as you can see. I've got an Xperia XZ, the bootloader is currently unlocked. But I cannot, for the life of me, get any further despite following several guides and programs. So I'm at a loss.
At this exact moment, I have my XZ connected to my pc with the blue light on. CMD in ADB/Fastboot cannot detect the device. My understanding is I need to flash the kernal and recovery first, then I can consider flashing a custom rom.
Would anybody be able to assist me? I dropped this project a few months ago, so I'll need to check what rom I was going to use and update the img files I have.
Thanks
Installed fastboot abd on pc?
Yep, that's been installed. I do have an issue which I thought/think is driver related as the daemon doesn't always start, and doesn't detect the phone correctly either.
What OS is on your computer?
Windows 10, I also tried Linux Mint but didn't get much further.
Have you disable the drivers vetification?
Yep!
Can flashtool detect your device? Sorry for all the questions but got to start somewhere and have you tried changing USB ports and cables?
No, the questions are good. There will be something wrong that I can't find, so we need to work it out somehow.
Flashtool doesn't consistently detect the device. The computer does, flashtool doesn't. I have changed the cables with some success, but that hasn't helped me progress much further.
Hmm, have you install the drivers from Sony developer site? Also try it on another computer..i wonder if you have a bad connection port on your phone thus the reason I asked about another computer.. Try reinstalling fastboot and adb, drivers etc. with your anti-virus disable.. And does Sony companion work? USB debugging turned on?
Sounds silly but sometimes we forget, like redoing doing your phone from scratch and you can't delete some stuff and only to remember later that you forgot to install busybox or mount your system partition.. lol
Thanks Lilbrat,
I'll be doing a fresh install, hopefully this weekend. And will cover what you have mentioned and report back. Thanks!
since this is your first Xperia device, you must first familiarize yourself with the ENVIRONMENT and TOOLS in which SONY Xperias can be played with !
some basics I wrote for X, but applies for XZ also , please read as it will be helpful!
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
now
since your boot is already unlocked so I can safely assume that you don't have TA.img file at all!
this leaves you with only two solutions
1. install 3rd part ROMS
2. flash sony STOCKROM and flash MODDED kernel (most of us do this)
your XZ has project name by SONY called KAGURA, your device on xperifirm is recognized by this name, dual/single you have to specify
from flashtool, xperifirm, download latest firmware 41.3.A.2.157 under KAGURA, close xperifirm and FLASHTOOL will start creating FTF file AUTOMATICALLY, click OK to any script question. and let it create ftf for u
flash it on your XZ,
send me kernel for 41.3.A.2.157, i will patch it for u! (patching guide is given in this forum but at this point i think it will be too much for you, so i will fix the kernel for u)
KAGURA twrp can be found at https://dl.twrp.me/kagura/ ( unlike SAMSUNGS, sony Xperias don't have inbuilt RECOVERY )
flashing recovery is MUST!
when device is switched off, connecting USB CABLE to PC and MObile while
1. HOLDING VOLUME UP KEY (blue LED) is FASTBOOT MODE (used mainly for sending twrp and kernels )
2. HODLING VOLUME down KEY (GREEN LED) is FLASHMODE (used mainly to FLASH stock roms using FLASHTOOL
you must install
1. Xperia Companion
2. flashtool ( www.flashtool.net) (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ)
3. install minimal adb and fastboot 1.4x from XDA (google it)
4. using these TOOLS you can
a-flash firmwere
b flash recovery
c flash modded kernel
d boot in to recovery (twrp) and flash MAGISK 16.x .zip from twrp + drm patch files! ( i will give you later with modded kernel)
e reboot and your device will wakeup ROOTED having DRM FIX! ---- switch off the SOFTWARE updater using any ROOT APP FREEZE app from playstore!
Currently working through a reinstall of flashtool etc, I can detect the phone using the Sony Companion tool, so thats positive. I haven't seen any notification that drivers have installed, but I do have the XZ drivers unzipped here.
Edit1: It doesn't detect or anything when the blue or green lights are on phone either. Not sure about them at this point.
Edit2: Just going through your guide as well Yasu, I cannot locate "sony Xperia X motherboard drivers (sa0107)" or anything similar to my device. Just throwing that out there. Installing the two common results in Sony Mobile Communications (ggsomc( USB (11/10/14 3.1.0.0) installing, but Google. Inc (WinUSB) AndroidUsbDeviceClass (12/06/10 4.0.0...) failing.
Will continue. Derp, just noticed I have a completely different flash tool. Sony Mobile Flaster by Androxyde, v0.9.25.0 but atleast it detects the connected device more than previously.
21/004/2018 13:04:44 - INFO - List of connected devices (Device Id) :
21/004/2018 13:04:44 - INFO - - USB\VID_0FCE&PID_0DDE\CB512CK84Q Driver installed : false
21/004/2018 13:04:44 - INFO - List of ADB devices :
21/004/2018 13:04:48 - INFO - - none
21/004/2018 13:04:48 - INFO - List of fastboot devices :
21/004/2018 13:04:50 - INFO - - none
Edit 3: Right, forgot to disable Win10's driver signature. Fixed that part again.
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
AVeers said:
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
Click to expand...
Click to collapse
1. as i mentioned " (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ) "
2. once these drivers are installed, you will get SOMC notification when very first time you connect your XZ in any MODE (volume up / and /or / volume down)
3. while flashing firmware, if you didnt tick WIPE areas, you will get encryption error , you must perform CLEAN FLASHING
4. before booting in to twrp, you must flash MODIFIED KERNEL - you can take modded kernel from my post in this forum
5, boot into twrp, flash drm fix files, flash magisk and wipe delvik cache/ cache and Reboot!
Yep, I see what you mean now. I missed the options on the flash screen, I thought it was odd that the time it took didn't match anything close to the times you described.
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
AVeers said:
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
Click to expand...
Click to collapse
did you flash the modded kernel?
if you simply flash magisk on original kernel!
you will be stuck on SONY LOGO
OK, I still following this with some interest, as a bit of clarification seems to be needed.. Now granted for some reason Flashtool doesn't have the XZ drivers even the newest version but there are mb drivers on Sony Developer site.. https://developer.sony.com/develop/drivers/ . (see pic)
@AVeers, more computer questions reason being you said Flashtool is seeing your phone a bit better, which leads me to believe you're still having driver issues.. Are you on a laptop or a desktop? If it's a desktop have you tried plugging your USB into the rear panel, straight into the mb also have you tried disabling your anti-virus when installing your drivers? Oh, and where are you located as your firmware is for the middle east, if I remember correctly..
Hi Mate,
I won't be able to work on this further until the weekend. But I do have those drivers from Sony here. And have been using firmware as per Australia (generic). Which is correct for my location.
The phone is plugged into the mobo via rear panel, and this is a desktop running Win10. I'm in test mode to eliminate the driver signing issue. I have not disabled the anti-virus, but I haven't had issues before.
When I run the flash for the firmware, boot.img or twrp.img, it takes seconds to complete, generally less.

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.

Categories

Resources