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!
Related
in brief:
the data should be there on the phone, so there's hope it should be easier to recover than deleted data but i run out of ideas how to get adb to find and pull it... maybe a more advanced user has better knowledge (better commands or tools)
adb devices and fastboot devices communicate with phone, so i have all drivers installed, i can only tackle with it via usb from windows 7 based computer
the detailed story:
i have a huawei g620s-L01, stuck in bootloop (just loading huawei logo forever or until battery empty but does not restart) and also "volume down" button does nothing... the bootloader is locked and huawei seems to have stopped providing unlock codes...the touch works but is shattered so i was told repair the button is not an option...
i can boot it into recovery mode using "volume up + power" but i can't use the recovery menu due to the dead "volume down"
from recovery menu i can only "reboot system now" but that re-enters the bootloop,
also i get bootloop if i try to boot into download mode via adb command
i can use some adb commands (i say some because some return errors, others say i don't have permissions)
i can boot into fastboot via adb command too...i can not find my dcim folder or any data folder to use the pull commnad, i tried the generic commands to pull sdcrd or dcim or all files with *.jpg
the user data is not accesible, i could browse some system directories but they did not contain my files via cd commands
i found some threads saying maybe i need mount or root commands
but trying to mount partitions or access su via adb also gives errors
su is not found, i do remember there was a su when android was working on the devices but is useless if i can't find/access it
i found the factory rom and some tools to try to restore rom to the phone due to claims that same rom might find my data, but the tools failed to start due to locked bootloader
i also tried several versions of full android sdk (old and new) trying to find "monitor or file browser" tools but the menu is not there...perhaps it will not activate those tools when device is in fastboot/recovery modes
{
"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 also found a 3rd party full android browser but can't connect with it either
also recovery softs are useless, they need a working android to try to recover anything...some recovery softs claimed they can fix bootloop but don't support my device
free tools that try to unlock bootloader also failed
so at this point i am running out of things to try
this is what i figured so far: i can see my data but can't touch it
i seem to have 4 partitions on the device:
1 is called sdcard but has nothing accesible on it, could be the feature for external card
2 is called ext , total size is 711,49mb , used 124,98 and available 586,5
3 is called system , total size 1,64 gb, used 1,23gb, available 418,1mb
4 is called data, total size 3,96gb, used 3,75gb, available 218,16mb
clearly the data partition is still keeping my data
i can not see my installed apps, so i guess they are also on that partition
i can see some system apps, namely 49 out of 146
so i'm guessing the issue is with one application, likely system app since i can't see them all
the phone may be partly rooted, the android may have some rooted features but the adb on it is not rooted
so i can not use the adb root command to get to my data
and i can not try to flash recovery or rom or custom boot img from adb due to bootloader locked and asking for unknown code
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.
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.
I tried Graphene OS for the past week and decided to go back to original.
- bootloader is unlocked
- am using Android Flash TOOL from here https://flash.android.com/
- Removed non-stock key prior to proceeding with Flashing
- i got to FastBoot screen during the Flash and the browser provided the following warning : '' Your device is being used by another program'' and then the Flasing process stopped.
- Am now back at the main Google screen.
- I believe Graphene OS already removed from device.
- Trying to initialize Android Flash TOOL once again, i accept ADB / Grant access to ADB keys - device does not show up in the tool anymore to flash stock OS. (see attached screenshot)
When I'm stuck at the main Google screen, I decided to factory reset.
Turned device off > Pressed Volume down > highlight “Recovery mode.” > “Wipe data/factory reset” > After reset completed, pressed the Power button to select “Reboot system now.”
{
"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"
}
Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.
-in fastboot, fastboot flashing unlock, reboot then reconfig of the phone.
-switch back to developer mode + USB debugging + USB connection to PC.
-adb reboot bootloader then adb kill-server (on the PC).
-connect to Android Flash Tool then do as if I was going to flash the original Rom (to make the phone recognized by Google) and stop the process before flashing.
I don't know if it's really useful to do all this but recently with 2 phones (Google 4A5G and Google 5 under GrapheneOS) putted back the ROM from Google before re-flashing on the 2 CalyxOS (support planned until January 2025) without any problem.
Last possibility for you, download the ROM factory, unzip it and launch the flash-all.bat in fastboot.
Tintin62 said:
Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.....
Click to expand...
Click to collapse
@yycDAAN This is the best solution: doing this stuff manually and not using a tool/site to automate things =).
But anyway, ensure that you have USB Debugging enabled. If you don't, then no image flashing will work manually or through sites that tackle it all for you - as they won't be able to detect the device (which appears to be your current problem).
Thank you guys for taking the time to help - much appreciate it
got into Fastboot mode. Android Flash TOOL recognized device and was able to install the original OS . When i restart phone, get the warning page :
''Your device is corrupt. It can't be trusted and may not work properly'' . I click CONTINUE and everything loads normally.
Is there anything I can do to ensure that ''Your device is corrupt.'' page stop showing up on Boot ?
EDIT : appears once bootloader is Locked, screen disappears
Leaving Thread up for reference.
Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"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"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?
Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...
it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.