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.
Related
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.
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.
Hello, I'm new to this- all of it, I've only just recently got into rooting and such things, but I'm progressing and that's what matters, no?
Anyway, I've successfully managed to root this phone via Magisk, that no one probably cares for anymore through trial and error and I'll do my very best to explain my method, and give updates as this is very on-going, there are certain issues and things I need to work out, but I appreciate any help, pointers, and such as before mentioned, I am new.
{
"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"
}
ALCATEL A30 FIERCE - Specs, and Specifications.
This phone was released in August, 2017.
Display - 5.5inches, 1280 x 720
Camera - 13 MP (Single Camera)
Hardware - MediaTek, 2GB RAM
Storage - 32GB, microSDXC
Battery - 3000mAh
OS - Android 7.0 Nougat
My own notes about this device.
Lots of MetroPCS Bloatware, can be a bit janky, but it's manageable.
It does not have a traditionally accessed Bootloader, no "adb reboot bootloader", this command just restarts the device to system.
Fastboot is odd, I managed to access Fastboot by some way I don't entirely understand, I'll go about what I did to get there later on in this post and try to recreate it later on as this post updates.
This device has colour states (if that's commonology), meaning, once the Bootloader is "unlocked", you will get an "Orange State" message before starting your phone that gets in the way of some things, I have yet to fix this, but I imagine we will if this gains traction, there will be a quicker fix!
No TWRP yet, as of posting, flashing a ported twrp.img through MTK_TWRP, or the TWRP_Port has not worked, and after flashing, neither will flashing the stock recovery but I've a quickfire way of getting around to fix this, if I can.
MTKCLIENT - https://github.com/bkerler/mtkclient
My Process, in the system, press the build number seven times to enable developer options - enable OEM Unlocking.
Then enable USB Debugging, and make sure you've installed adb and fastboot, as well as the correct drivers.
Through that link, follow the instructions specific to your operating system (I use POP OS and WINDOWS 11, YOU DON'T HAVE TO USE THE SAME AS ME), you may use the mtkclient_gui for an easier experience.
To unlock the bootloader, which will trigger "Orange State", open your terminal in the directory of the mtkclient and run python "mtk e metadata,userdata,md_udc", then, with your powered off device, and it will say something along the lines of "Preloader - Waiting for Device", with your USB Cable, and your wits about you, hold the volume down button (if this doesn't work for you, hold both volume buttons in" and plug your device into your PC with that command running. If the command completes, then run "python mtk da seccfg unlock", and this will unlock your bootloader.
WARNING: Unlocking the bootloader wipes the data of your device!
After this, dump your boot vbmeta with the commands in the mtkclient instructions, if this does not work for you with python or python3, I will provide the required files below.
Then, power your device back up, and install the patched magisk-app and push it to your sd card through adb, or traditional file transfer.
If you have your boot.img, push it to your sd card and patch it with magisk, then retrieve it from your phone - this is where my tutorial and mtk's tutorial take a bit of a turn!
I had a problem with the "reconnecting to preloader" phase, as it would not go through, or an error labeled [Unpack Requires A Buffer Of 12 Bytes] would crop up which prevented me from flashing the required files through "python mtk w boot,vbmeta boot.patched,vbmeta.img.empty". Let's go through some cautionary steps, what I did to achieve perma-root.
Create a funny-named file in the mtkclient directory labeled "DUMPY", do "python/python3 mtk_gui" and connect your powered off phone through the previously mentioned volume holding until it connects you in BROM mode. Under "read partitions", select all partitions, then "read partitions" and make sure the output is that "DUMPY" folder. This process will take awhile!
Once it finishes, rename your patched magisk-boot from [magisk.img name] to "boot.patched.bin" and under "write partitions", select the boot partition and write the boot.patched.bin to the boot partition! Once finished, start your device and install a root checker! It should be working!
If there are any errors, I will do my best to try and help you but keep in mind, I am very new to this, I hope it works for you too!
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.
Guide to Remove Orange State Error Fix
Tested on Indian region
(May not work on another region)
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS IS DONE BY YOUR OWN JUDGEMENT IF YOU WANT TO DO THIS OR NOT.
It's possible to flash. Modified partition/image file without a bootloader unlock but I'm not 100% positive. .
Requirements:-
Qfil Tool (QPST)
Qualcomm EDL Mode Drivers
Firehose Programmer SDM870
abl.img (new edited)
Steps:-
Step 1: Download the given files.
Step 2: Install Qfil (QPST)
Step 3: Make sure you go to configuration then firehose settings and change from emmc to ufs and do the same as shown in below image.
{
"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"
}
Step 4: Turn off your phone and boot into edl mode
Step 5: Install the Qualcomm drivers by right clicking on the qbulkhub thing and click properties then the driver tab click update then search automatically.
Step 6: Open Qfil tool then load the firehose file in programmer path
Step 7: don't worry about the XML path and stuff just go on the top click tools and partition manager
(NOTE: if there's no port open or the partition manager won't open, try rebooting into edl mode again)
Step 8: Window should pop up with a list of partitions, right click on the abl that you want to flash and then click on Manage Partition Data option then click on Erase option (abl partition will be erased) then click on load image and select and load the given abl.img file
Step 9: Exit from the Qfil tool
Step 10: Reboot your phone
Enjoy!
@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
nikoum said:
@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
Click to expand...
Click to collapse
What firmware version were you on before you fixed orange state?
ESD444 said:
What firmware version were you on before you fixed orange state?
Click to expand...
Click to collapse
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09
nikoum said:
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09
Click to expand...
Click to collapse
So following this post you got rid of orange state?
ESD444 said:
So following this post you got rid of orange state?
Click to expand...
Click to collapse
He is saying he got orange state after updating to rui 4 Android 13 "not in Android 12"
Just to inform anybody, I received a new update RMX3370_11_F.03 and after the update I got the orange state warning back again. So I had to apply the fix again.
Yes you have to apply it again
hi,
i'm triying to fix this orange state problem but can't find abl partition in partition manager, can you please tell me what is the partition i have to erase and flash?
Edit: Ok in fact i don't have to check "customize fysical partition" in configuration. abl is in LUN 4 but i only seen LUN 0 when this case is check.