How To Guide [ROOT] [FLASH STOCK]
- Thread starter R41N MuTT
- Start date
I was just toying around with it, but realized the issue was because the tutorial misses a step in the unlocking process after looking back at the process outlined by the development team.
Erase metadata and userdata (and md_udc if existing):
python mtk e metadata,userdata,md_udc
Appreciate your work though as I have had this phone for awhile and thought T-Mobile approval would be required to unlock it. Sometimes you don't know until you look.
Erase metadata and userdata (and md_udc if existing):
python mtk e metadata,userdata,md_udc
Appreciate your work though as I have had this phone for awhile and thought T-Mobile approval would be required to unlock it. Sometimes you don't know until you look.
You say this guide omits this? Check step 3. It's at the bottom, commands are typed in red. Or are you saying I missed something else? Because that would explain a lot. Thanks, by the way. Figuring this stuff out and quoting so many other resources accurately and clearly takes editing skills I didn't have before. Lol
I figured out the real problem as there was one step that needed to be done before unlocking according the the d
I missed that step, but after looking at the developers documentation, I just did the two commands consecutively as they suggested, then start phone and reset. Maybe consider some people might be color blind
Hmm.. I didn't consider that. I was all trying to be clever.. I'll add bullets or something. Hope nobody is bullet blind.I figured out the real problem as there was one step that needed to be done before unlocking according the the d
I missed that step, but after looking at the developers documentation, I just did the two commands consecutively as they suggested, then start phone and reset. Maybe consider some people might be color blind
But seriously though, the issue that's been going on is spflash error saying it doesn't support mt68xx when it clearly does. And another is not being able to use WiFi after root...
The spflash you have is not the correct one Hollywood gave me the correct one but because usb is being weird I can't use it
That's good to know. Do you have the link to that spflash? I'll add it to my post for others who have a similar problem. The spflash link in my post works fine for me, and others have had success. I don't know why one works for some and the other works for others. But I need to include them both
You said you are no longer able to connect to wifi. Do you know how to system trace through developer options, enabling USB debug, and scrolling farther to start a trace? Or are you able to use $ adb shell getprop? You say you are rooted, of course has to be magisk. Download the BusyBox and toybox modules from GitHub, install them, and then $adb shell, $su. From there you will be rooted and can use the BusyBox and toybox shell commands to gather quite a bit of info, I'd start in the proc folder after the su command. Make sure your symbol is # and cd proc, then # ls -la, you will have a nice long list of properties to explore your issue with. Each partition has a build.prop file, when you do the ls -la command the list you see will be separated hopefully by color, you'll be able to tell which is a file, or script, and which is a directory. Use the cat command (#cat {property or script name in the current directory} ) you will pull ALOT OF INFO that way. Don't worry feel free to explore; the system is read only for now so you can't damage a thing. Another alternative use terminal emulator on your device and when open do the $su command and then # magisk resetprop that will list your important props. I need to see at least one of these things. Another is to go into shell as su and type the command dumpsys, and cp that to your download folder post it here I'll try and help you. Sounds like you flashed the right chipset wrong device boot image. Or your props are out of whack.
What about spflash can't you get to work? You honestly don't need it you can flash what you need just fine through mtkclient. That eliminates the need for the scatter. If you want spflash to pick up your phone, you must do the mtkbypass tool from bkerley on GitHub, right after you complete stage 2 and load the payload I enclosed on the other thread, and are still connected after the da exploit you can then without closing the command window from mtkbypass use spflash. Stop the connection with the bypass and spflash will not pick the phone up scatter or not.
Did you unlock your bootloader first? And then WIPE YOUR PHONE RIGHT AFTER, THAT IS A CRUCIAL STEP. also try this if you can still get to the bootloader fastboot. Not fastbootd. The command set active=(a or b) that trips people up because when you flash, usually the system boots from the opposite slot than the one you flashed. That very well may be the issue. Try both. And also you installed that boot img, sometimes you have to reflash the vbmeta, vbmeta_vendor, and vbmeta_system as well, all of them with the structure 'fastboot flash vbmeta_a(or b or system whatever) --disable-verity --disable-verification (path to your file.bin or img) when you are flashing with fastboot, always make sure your file names are as they are in the scatter or as they are originally named, make sure it's the BOOTLOADER fastboot not fastbootd or recovery. Want to use spflash tool you have to use mtkbypass.
One more thing boss. BEFORE YOU UNLOCK THE BOOTLOADER REMEMBER USE THE MTK BYPASS TOOL TO PATCH THE DAXFLASH AND PRELOADER AJD ALSO TO TAKE A BACKUP BEFORE YOU USE MTK CLIENT. YOULL GET TO KEEP YOUR WIFI THAT WAY. AND ALSO USE THE FASTBOOT FROM THE BOOTLOADER DO NOT ATTEMPT TO USE FASTBOOTD AND EACH FILE BEFORE FLASHING USE THE --DISABLE-VERITY AND -- DISABLE VERIFICATION ARGUMENTS.
GREAT JOB AND THANKS FOR CONTRIBUTING TO THE COMMUNITY AND KEEPING ROOT ALIVE AND FUN! -CHANCESo i see towards then end of the how to it states to flash your modem.img from the stock rom. unless im blind which i might be i dont see a modem.img in the rom files. im sure it would fix the wifi issue if it was there.
i tried flsahing the meta images indivually per fast boot as well and i was getting an a ANDROID_PRODUCT_OUT not set. cant wrap my head around that one either
Ok. So update on your so far complete guide. i was able to reflash my phone with absolutely no issues.. followed it step by step, and it even fixed my wifi issue after flashing complete a/b rom set. idid however run into a problem towards the end of my really long night of figuring out what to do with ,y now bricked phone. i removed the root and relocked the bootloar and on a reboot to normal it weent into a boot loop, and everything i tried to unlock it again, all the up down and power combos no touch plugin, no meta , no nothing and then a black screen flashing over and over. TURNS OUT.. This particular model of MT has a really easy to get to reset that most would probably not think of.. At the top edge of the phone theres a pin hole(looks like second mic). i assure its not i tested it twice to make sure i wasnt trippin from the lack of sleep of roming. anyhow. i held my sim tool down in ther slightly for a few seconds and wahlah. took it out of boot loop and aven re unlocked my bootloader. what a trip. i have never seen a phone with this feature. but wth i had nothing better to do with my time at that point in the F*** i broke my phone moment to try ome stupid ideas. hope this information helps others with this model. cheers.
Voila. It's voila, not walah. In fact, there are so many things wrong with this post that I don't know where to begin. I'm so tired but when I seen this craziness I snapped bolt upright. First of all, those holes on the outside of your phone are for reception clarity and nosie cancelling microphone. If you damage either one your phone experience will take a major hit. Do not jam anything into either hole. They haven't put a reset button on an Android phone for 15 years. If you have an issue with your phone not booting, be patient, we can help you. If you had a success but don't understand how you did it (I've totally done that before) that's one thing. But please try to refrain from posting this bizarre tabloid-news-esque gobbledegook. This post is a mess as it is. I already have so much to fix. Thanks for the help, everybody. Kaliman, you're awesome. I'll get to this post again as soon as I can. Good luck and hang in there everybody.
well i just so happen to manipulate it a 3rd time a little bit ago. amd i made some research there are some international made phones with resets in them. i know what most of the ir and ics do internally and where they are on the pcbs. i have to say this one is real. i can see why you would not beleive the story but its there and it works. anyhow.. im running smooth now. just need to figure out how to get my imei back in place.
I've had this phone on a reworking station. I've looked it up and down. I know what every single port goes to, I'm aware of the order of every pinout: fingerprint scanner, camera, sensors, charging port, microphone, voltage regulator, etc. There is no master reset button on this phone, you're mistaken. *Edit* in fact, I reworked the USB c and swapped the charging port, I also swapped the camera where my original had a cracked glass. I had to resolder a 2 pin connector that popped off the board... Give me a break
nice. i beleive what your saying. but everytime i puncjh in on that spot it resets it. so i dont know. it weird. anyhow. you wount happen to know where i can find an image of the modem/network peices. or if it in those files which one it is so i can reflash it?
Top Liked Posts
-
There are no posts matching your filters.
-
2DISCLAIMER:
Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding.
***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A BACKUP. LET THIS APPLY TO EVERYTHING. WHENEVER THE OPTION TO BACKUP IS AVAILABLE IT WOULD BE WISE TO DO SO. FAILURE TO BACKUP YOUR DEVICE WILL RESULT IN LOSS OF DATA***
ALL LINKS ALLOWED, APPROVED AND/OR UTILIZED BY XDA. SPECIAL THANKS TO ALL THE DEVS WHO CREATED THE TOOLS WITHOUT WHICH THIS WOULD NOT BE POSSIBLE. I DIDN'T BUILD ANY SOFTWARE MENTIONED IN THIS POST. IF YOU BRICK YOUR PHONE, DO NOT BLAME ME. I'M NOT TELLING YOU HOW TO DO IT, BUT NARRATING A GUIDE TO HOW I DID IT. YOU HAVE BEEN WARNED
REVVL V+ 5G TMOBILE VARIANT ANDROID 11
IT SHOULD BE NOTED THAT SOME PEOPLE ARE REPORTING LOSING WIFI AFTER ROOT, AS HAVE I. I HAVE NOT YET FIGURED OUT HOW TO FIX THIS. I'M THANKFUL FOR ANY ASSISTANCE. FLASHED STOCK BOOT_A DIDN'T FIX IT, ONLY FLASHING BACK TO STOCK ROM. ON ANOTHER IDENTICAL PHONE DIDN'T LOSE WIFI. YOUR GUESS IS AS GOOD AS MINE. LOOKING INTO IT, NO PROMISES
Without further ado, let's start at the unboxing.
1) PREP PHONE:
power on. navigate to settings>about phone and tap "build number" seven times to enable developer options.
navigate to settings>system>developer options and enable "USB Debugging" and "OEM unlock"
FIRST disconnect the device from your comp THEN power the device off.
2) DONWLOAD PYTHON & DRIVERS:
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
3) BOOT INTO B ROM MODE:
This is kind of tricky when you don't know it. The screen will will be black. Sometimes, the device will not even vibrate. There's no sunbathing android, no "No Command", no fastboot, no download mode, no recovery- nothing, nada, zip, zilch, goose egg.
Make sure you unplug the device entirely from charger and pc BEFORE you power off. Now that you properly powered off, hold ONLY BOTH volume + - keys while you connect it to your PC. Try to be quick about it. DO NOT TOUCH THE POWER KEY. Continue to hold the volume keys until you know your device connected. When you hear your device connected jingle immediately let go. The screen will remain blacked out and unresponsive. It's normal.
Let's make sure we did it right. Enter the following command without ":
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation.
4) PREP PHONE AGAIN (STEP 1):
5) UNLOCK BOOTLOADER:
Enter the following command without ":
"python mtk da seccfg unlock"
~To relock the bootloader in the future use command "python mtk da seccfg lock". If you flash a custom recovery/ROM and want to return to stock, then you must unroot with magisk first, then flash stock ROM with SP flash tool at the end of this post~
Power on. On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds."
This will happen each time you boot the device because your bootloader is now unlocked.
6) PREP PHONE AGAIN (STEP 1):
7) ENABLE ADB FASTBOOT COMMANDS:
Download sdk platform tools here:
sdk platform tools
Extract.
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
First you'll see a random, arbitrary number. Second time you should see your device serial number and "Authorized", "Allowed", or "Device".
Keep this cmd window open.
8) DOWNLOAD MAGISK AND PATCH BOOT IMG:
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Download firmware from here:
T-Mobile_REVVL_V%252B_5G.zip
Unzip and move boot_a to the downloads folder on your phone.
On your phone, open Magisk and click install and choose boot_a.
Make sure magisk_patched file is in your phone's download folder.
In your platform tools cmd window enter the following command without ":
"adb pull /sdcard/Download/magisk_patched_[numbers].img"
9) ENTER FASTBOOT MODE:
Disconnect device and power off. Hold Vol - and power to enter fastboot mode.
Connect device to PC.
10) ACHIEVE ROOT:
***NOTE: IN THIS STEP YOU MUST LOCATE THE PATCHED FILE ON YOUR PC AND COPY AS PATH. PASTE IT IN THE CMD WINDOW IN PLACE OF "[path to patched file]"***
In the platform tools cmd window enter the following command without ":
"fastboot flash boot [path to patched file]"
Now that you've achieved root, you can play around a little bit. But be careful what you go deleting if you get debloat happy like me and delete your NVRAM & wifi. Just in case you do, here's how to return to stock.
NVRAM backup. This video makes it look easy as pie. (It IS easy)
NVRAM Backup Tutorial
Now we have to bypass DA else SP flash tool will not be able to flash ROM.
Open cmd window and type the following without "":
"python -m pip install pyusb pyserial json5"
Then, update by entering the following command without "":
"python.exe -m pip install --upgrade pip"
Download LIBUSB:
LIBUSB
Run LIBUSB Win 32 filter installer and select Mediatek driver
Enter B ROM mode and connect to PC
Navigate to bypass tool and open "brom.bat"
Close cmd...
Run "flash_tool.exe" in sp flash folder
Options>options>connection tick UART
That's it. Now you can flash with sp flash without encountering error
Here is a helpful link that came from a senior mod:
mtk tool
Download SP Flash tool here:
SP Flash
Extract and launch flash_tool application
Download scatter mt6833 here:
MT6833_scatter.txt
Download bypass tool from here:
bypass tool
download rom2box:
rom2box
Download OTA and use a payload dumper to extract boot and scatter. You can also get DA, but it does nothing. You must bypass DA in order to flash ROM.
OTA
THIS SECTION IS FOR LATER REFERENCING, DISREGARD ANYTHING BELOW THIS
[A13 ota news https://www.t-mobile.com/support/devices/software-updates/t-mobile-revvl-v-plus-android-update]
[Twrp https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/?_ga=2.195721068.1777813512.1675477697-1767133243.1662515191]
~fastboot set_active other
~fastboot flash recovery_a twrp file
~fastboot flash recovery_b twrp file
[Sprout https://dl.twrp.me/sprout/]
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
https://www.mediafire.com/download/sxq4cz8bddmr49
https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file
https://download1526.mediafire.com/ih0pus48i1kg/mwl6h20noutg005/revvplus.zip
[Patched boot_a pending verification https://forum.xda-developers.com/attachments/magisk_patched-25100_hiu69-img.5648347/]
[FLASH STOCK MODEM FILE]
My next guide will be how to use assurance wireless with ANY phone. I'm using assurance wireless on my Oneplus N200 (DE2118).2The guide is fine, but not perfect. If it was, I'd be suspicious as to its authenticity. To further elaborate: Would I, objectively speaking follow this guide? No, I would not, although my reasons would be for my interest in the scene as a whole, my drive to learn and my mission to find my own way to root and/or mod my device, and not for the lack of accuracy in this guide or any perceived incompetence of OP. The very nature of these processes call on one to outline themselves with the basics , and to soak up all the anecdote and documentation they can. You do that so that ultimately, you FIND YOUR OWN WAY to accomplish your goal. You learn nothing by following guides step by step, and I've been at this long enough to know that NOONE creates a perfect guide, haven't seen it yet unless refined by the support of other members who come together and sometimes create definitive instructions, and even then, due to the dynamics of each particular users device state, it will never be the same road to root for everyone. That is what we are all here for though, right? Also that's the fun of it all. People who come to platforms like these to follow the guides exactly, don't learn anything and when their device INEVITABLY bricks (TRUST me, that also comes with the territory) they are stuck trying to find a guide to again follow it word for word only to exacerbate their problem and at the end still have not learned a thing. So, after reading that, do you still want to root your device? Should you follow the guide? That is a question that none of us here can answer. Good luck! (Shout out to OP, it takes time to create guides here and we do not get paid for it. GOOD JOB.)
try the command: fastboot getvar all That will show you a list of all variables as well as which partitions you need to flash.111
