Database Info

Unable to flash ROM - Erisin Mini Cooper

Greetings from Portugal,
I need your help because I probably messed up.
I have an Android Unit on my Mini Cooper. It's from ERISIN (At least the software was, because the booting logo used to be from Erisin).
{
"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"
}
The unit has USB and two microSD slots (one is the GPS slot)
Here are the specs from my unit (I took before messing up):
The background story - I contacted ERISIN asking them for a new MCU firmware and ROM, because mine was from 2016. They sent me the files (They sent me an MTCE LM firmware - even though mine was KGL and they also sent an Android 10 ZIP file). I'm a new to this kind of android "programming" so, naive of me, I tried to install it.
In the settings I was able to upgrade the MCU firmware. But unable to to the same with the ZIP file. So I tried from the android recovery - boot from USB and Erase All. The recovery was able to read the MCU file in the usb but not the ZIP. Then I probably ended up recovering from backup (or something like that) because I ended up with a version of the software which did not have working driving wheel buttons nor the front physical buttons. I PANICKED :laugh:
I then got the "yandex disc" version of a KGL MTCD version (similar to the one I had before flashing) and also downloaded the update.img of android 5.1 for PX3 KGL (rk3188, my rockchip) - I wanted to get as stock as I could.
Long story short - I'm stuck with recovering, something went wrong because I get the loop on the lollipop booting screen and wont pass from there.
On Recovering, the GPS microSD is not mounting (and I know It's advised to flash from that slot). The USB is working (I can flash the MCU version from USB but the ROM image gets errors every time I try to flash it.
What I've tried:
- Format microSD in Fat32, ExFat, NTFS to see if the GPS Slot would recognise it. Didn't succeed. Tried with a 1GB and a 4GB card.
- Tried to make a "Boot" SD and USB with "Rockchip Create Upgrade Disk Tool" Software (Following Malaysk posts), but both didn't work.
- Tried to disconnect battery from car, inserting MicroSD in GPS slot and then connect the battery to check if the unit would recognize it.
The ROM update from USB always starts, but after 30 seconds it gives me a bunch of errors (cant mount cache... cant open cache... block device required... and some rknand errors.
The Malaysk ROM is named dupdate.img Should I try to rename it to update.img ? Would that work?
Please help. And thanks in advance.
I leave you the errors:

Your unit isn't [Android Auto] but the good news is that it is a well known [MTCD] type, as seen from the MCU type code.
Ive requested mods move your question to the MTCD Q&a, but as a suggestion, take a little time to read the forums then post. There's a wealth of info, and your issue can be found in the forums.

marchnz said:
Your unit isn't [Android Auto] but the good news is that it is a well known [MTCD] type, as seen from the MCU type code.
Ive requested mods move your question to the MTCD Q&a, but as a suggestion, take a little time to read the forums then post. There's a wealth of info, and your issue can be found in the forums.
Click to expand...
Click to collapse
Thanks in advance. Yes, I did find some post - even 1 or 2 related to KGL version and similar error codes as mine - that's how I started trying some of the solutions I mentioned. Unfortunately it has not worked so far.
Maybe if I try to flash the ROM with RK Batch tool I can get it to work? I'm afraid that with the error codes I have maybe the unit is beyond salvation.

amc90 said:
Thanks in advance. Yes, I did find some post - even 1 or 2 related to KGL version and similar error codes as mine - that's how I started trying some of the solutions I mentioned. Unfortunately it has not worked so far.
Maybe if I try to flash the ROM with RK Batch tool I can get it to work? I'm afraid that with the error codes I have maybe the unit is beyond salvation.
Click to expand...
Click to collapse
Wipe storage first? Put it this way, never had a single SOM that was unrecoverable. Becareful upgrading to Android, does your BT support it.

Just tried to connect the unit with my PC to use with RK Batch tool.. but the PC doesnt recognize the Unit (yes, I've already used the RK Driver Assistant, and it tells me it succeeded to install drivers).. Even so, RK Batch tool does not recognize it. But 2 USBs appeared in "other device" in windows device manager (dont know if it is the unit being recognized, but it's strange that it lists 2 devices there) .

Flashing wrong recovery killed all of my partitions — Help!

Hi all,
I'm going to make a long story short and say that my brother's phone has a cracked screen, so I tried to use TWRP to backup everything through ADB. But googling SM-J530F TWRP brings 'j5lte' as one of the first results, I went and flashed it under the wrong assumption that j5lte was SM-J530F's code name (it was not) and that caused severe bootloops.
I flashed correct TWRP, but USERDATA would not mount. I panicked and the crystal bleeding was progressing fast, so I pulled the entire mmcblk0 to dump a raw image of the phone's NAND.
This was the right move, as the phone is completely dead now. Crystal bleeding has made the screen completely dead, but the phone still works.
All I'm left with is the raw NAND backup.
The first thing I did was inspect the image with fdisk. It can recognize the GPT partition table and structure. The USERDATA partition is at the very end.
{
"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"
}
GDISK is also recognizing it no problem. It seems like the partition table is in good condition:
GPARTED is also recognizing partitions, but it does not look good:
Looking at more information:
For the record, e2fsprogs is installed. It's always installed by default. GPARTED here is complaining about the superblock, but I can see that its looking to open the partition through /dev/loop0p24 which is no good. The kpartx tool is giving me access to all the partitions of the image through /dev/mapper/loop0p24, so that explains the errors.
Superblocks seem to be present in USERDATA:
I tried mounting the partition with a backup superblock, but...
I was at a loss at this point, so I tried mounting the SYSTEM partition just to see what happens and... it worked?
This proves what I said: This partition is fine, GPARTED was complaining simply because its trying to target them through the wrong device path.
But this raised the question: What the heck is wrong with the USERDATA partition? Why is it ext2 (Isn't that SUPER old?) and could it be that its not corrupted at all, and I'm just trying to mount it the wrong way or something? TWRP couldn't mount it though (Why?).
Being at a loss, I tried repairing the ext2 USERDATA partition using `fsck.ext2 /dev/mapper/loop0p24` and it found so many errors (including a corrupted journal) the file I redirected stdout to (console output) ended up being 78MB. Here it is if you want it (obviously can't post here).
So anybody knows what I can do? Is there any hope? I'm positive that the recovery image couldn't have corrupted the USERDATA partition (How could it? I still can't find a possible explanation). And even if it did, it couldn't overwrite the files. The file data should STILL be in that partition completely in-tact (There's NO WAY the recovery image overwrote them) though the journal is gone, so I can't use a tool like extundelete to recover them.
I tried to flash the phone with a stock rom through download mode to reconstruct everything with a healthy structure. This was so I could flash TWRP again and pull another NAND raw dump to have as a healthy reference I could use, but this doesn't work. Odin fails and I don't know why because the screen on the phone is dead.
Is there some place where I could get this maybe?
Is there something you can suggest I do?
Thanks!

Boot Loop / Checksum Error when trying to root (Umidigi A7 Pro).

Spoiler: Phone Data:
{
"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"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted

Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.

Guide to Test Android 13 DP1 (lvm600am)

This restore process is intended for the AT&T V60 (lmv600am) model and will most likely WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to Pixel P4a a13 dp1. I’ve dumped all the required partitions from my lmv600am which has been running this rom for about a week now. I have yet to find any problem at all. To me it seems smooth and fast. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there for that but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently wanting to try Google’ new Android a13 dp1 release. I have only this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from an Android 10 rom but I haven’t tried it.
I strongly suggest that you run the “reset option” option from Settings>System>. This will completely reformat and wipe your userdata when completed. No need to go thru the setup process just put phone in edl (9008) mode.
Steps
Download “Lmv600am a13 dp1 P4a Restore Partitions.7z” file from here and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version. The correct version of Qfil is important as there have been problems with older versions.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
If you wish you can Qfil load both the eng alb file to abl_a – abl_b which will give you Flashboot mode and your magisk modified boot.img to boot_a – boot_b to give you root. I have both.

When I click download it just gets stuck. There is no ulf storage type on my qfil. Maybe I have the wrong one? I only get ufs and a few others.
edit I guess I bricked it, my other lg v60 works fine lol
nvm again used my laptop. that fixed it. Nice build

does the qdac works?

I update Android 13.How can I restore to origin lg system? It can't work as update steps.
{
"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"
}

ck5524209 said:
I update Android 13.How can I restore to origin lg system? It can't work as update steps.
View attachment 5562119
Click to expand...
Click to collapse
If you wish to restore to the original AT&T a11 system for lmv600am go to the guide in this forum which I provided. It is meant for this exact circumstance, to enable those that wish to test what they like when they like and then return to a stock a11 environment when they wish.

Question Unbrick Nokia 2.2

Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?

kevriveroc said:
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
Click to expand...
Click to collapse
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.

djinc91 said:
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
Click to expand...
Click to collapse
I have just tried to do so, but to to no avail. I keep getting the following error message:
STATUS_STOR_LIFE_EXHAUST (0xC003001D)
The storage on your device has reached end of life, please change to use new device to do operations
I used the DA bundled with SP Flash Tool and drivers linked in one of the folders, apparently MTK ones.
Here's a screenshot of the error message:
{
"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"
}

I was able to download the firmware again after unchecking the Storage Life Cycle Check box within SP Flash Tool's options, and the phone is now up and running, no troubles up so far.
Thank you very much for your help djinc91!

Uhm Ur phones storage chip is literally dying
Thats emmc for u

areallydumbperson said:
Uhm Ur phones storage chip is literally dying
Thats emmc for u
Click to expand...
Click to collapse
I've had no trouble with my storage during all the years I've owned this phone. Never experienced slowdown, errors, loss of data, etc, not now, not before.
Even so, this is just a backup/2nd device used for nothing important, so it doesn't bother or worry me in the slightest. I'll just keep it using it as is until it dies or I just can't make it usable anymore.
Thank you for your heads up, though.