So I tried to flash android 10 so that I could flash android 10 roms but twrp kept giving me the ok but not actually installing the OS eventually I got stuck on fast boot (IDK why twrp is gone might have done something wrong in the process). So now Im trying to flash the stock rom on my Mi A3 but it wont work, using miflash gives me the miss matching image and device error which may mean the rom is not the right version (dl'ed rom is version 10.3.13, the version of my Mi A3 should be 10.3.14) but Im not sure if that's whats causing the error and I also cant find a zip for version 10.3.14 to test my guess. Hopefully someone can help me because I'm stumped on what to do.
Problem Solved Thanks @Valiko89
*Keep in mind you need to unlock the bootloader first ('fastboot falshing unlock' and 'fastboot falshing unlock_critical')
get the latest ver. fastboot rom according to your region (global/europe) then extract the TGZ, its an archive > inside you'll find another archive but TAR > extract it to and point miflash to that extracted folder
{
"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"
}
This is what I did in the past 48H hours to get back to stock:
Valiko89 said:
Well that was almost 48H wild ride
lol looks im too dumb to run adb shell as root cuz after adb shell I always got 'not found' also couldn't find the actual up to date ota on 4pda
So I got slightly older ver. ota gave up on the tune2fs step and headed on extracting the system.img from the payload.bin then flashing it blindly using 'fastboot flash system system.img' and when done got thrown back to yesterday - no phone at all just plain xiaomi logo yayyy fml!
But! on the same 4pda I stumbled upon the latest V10.3.17.0.PFQEUXM Fastboot recovery, and after poking around the web re-flashing the whole damn thing with the stock fastboot rom seemed like not such a bad idea at this point of my frustration.
By now the whole a/b slot tuned into one huge salad in my head so I went for sure and this is what I did:
1. boot to fastboot manually
2. 'fastboot flashing unlock' (holding vol down to return back to fastboot)
3. 'fastboot' flashing unlock_critical (holding vol down to return back to fastboot)
4. 'fastboot --set-active=a'
5. flashed the extracted tar folder with MiFlash and holding vol down near finish to return back to fastboot
6. 'fastboot --set-active=b'
7. flashed the same extracted tar folder again with MiFlash and holding vol down near finish to return back to fastboot
8. 'fastboot flashing lock_critical'
9. 'fastboot reboot'
And hooray! It booted to latest updated rom will have to wait for next OTA update to see if it works at all :cyclops:
Click to expand...
Click to collapse
Valiko89 said:
*Keep in mind you need to unlock the bootloader first ('fastboot falshing unlock' and 'fastboot falshing unlock_critical')
get the latest ver. fastboot rom according to your region (global/europe) then extract the TGZ, its an archive > inside you'll find another archive but TAR > extract it to and point miflash to that extracted folder
This is what I did in the past 48H hours to get back to stock:
Click to expand...
Click to collapse
Thanks, Although I already have my bootloader unlocked. I'll try flashing using the latest version
Edit: I just realized that when I initially flashed I had it set to lock the bootloader.....
Edit2: fastboot is weird
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe devices
47f092a82f41 fastboot
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Akubane said:
Thanks, Although I already have my bootloader unlocked. I'll try flashing using the latest version
Edit: I just realized that when I initially flashed I had it set to lock the bootloader.....
Edit2: fastboot is weird
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe devices
47f092a82f41 fastboot
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Click to expand...
Click to collapse
This one "FAILED (Write to device failed (Unknown error))" was weird.. have you tried a different usb cable and/or port?
Valiko89 said:
This one "FAILED (Write to device failed (Unknown error))" was weird.. have you tried a different usb cable and/or port?
Click to expand...
Click to collapse
Yeah, actually despite those errors I was able to flash stock rom. Its just those errors are really wierd.
Glad I was able to help by solving my own issue
Related
Hey.
So the other day I tried to flash another firmware to my ZU and everything was fine.
Everytime I'm on this, it takes me several times to get what I exactly want(e.g. successfully installing SuperSU, Xposed, flashing busybox and TWRP etc.).
This time I faced a big problem after a few times of playing about: I apperantly can't anymore use fastboot in order to install TWRP. This is what happens when I try to flash it:
{
"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 sought for similar errors in this forum and everyone seems to believe it's a bootloader problem. Hence, I checked it via Flashtool and this is what I get:
Would anyone kindly assist me on how to fix this issue?
My phone has got useless since this problem was faced.
Thanks in advance.
Try disabling USB debugging
sairaj rane said:
Try disabling USB debugging
Click to expand...
Click to collapse
It did not help sadly.
By the way, should it not be off by default before booting into Android for the first time just after an attempt of firmware flashing?
I used to install TWRP and, using that, SuperSU before the first boot and I would have no problems encountered then. Now I do have.
aliansahere said:
Hey.
So the other day I tried to flash another firmware to my ZU and everything was fine.
Everytime I'm on this, it takes me several times to get what I exactly want(e.g. successfully installing SuperSU, Xposed, flashing busybox and TWRP etc.).
This time I faced a big problem after a few times of playing about: I apperantly can't anymore use fastboot in order to install TWRP. This is what happens when I try to flash it:
I sought for similar errors in this forum and everyone seems to believe it's a bootloader problem. Hence, I checked it via Flashtool and this is what I get:
Would anyone kindly assist me on how to fix this issue?
My phone has got useless since this problem was faced.
Thanks in advance.
Click to expand...
Click to collapse
Use Androxyde Flashtool. Boot into fastboot and select TWRP as the kernel. That should work.
hector67 said:
Use Androxyde Flashtool. Boot into fastboot and select TWRP as the kernel. That should work.
Click to expand...
Click to collapse
Again, the same output:
30/022/2016 15:22:20 - INFO - Device connected in fastboot mode
30/022/2016 15:22:26 - INFO - Now plug your device in Fastboot Mode
30/022/2016 15:22:33 - INFO - Selected kernel (boot.img or kernel.sin): D:\Root\HOWTO\fastboot\twrp-2.8.7.0-togari.img
30/022/2016 15:22:33 - INFO - Flashing selected kernel
30/022/2016 15:22:33 - INFO - sending 'boot' (14018 KB)...
30/022/2016 15:22:33 - INFO - OKAY [ 0.452s]
30/022/2016 15:22:33 - INFO - writing 'boot'...
30/022/2016 15:22:33 - INFO - FAILED (remote: Command not allowed)
30/022/2016 15:22:33 - INFO - finished. total time: 0.455s
30/022/2016 15:22:33 - INFO - FASTBOOT Output:
sending 'boot' (14018 KB)...
OKAY [ 0.452s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.455s
30/022/2016 15:22:33 - INFO - Please check the log before rebooting into system
Click to expand...
Click to collapse
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Sithu Htun said:
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Click to expand...
Click to collapse
Hey.
Thanks for helping me.
Will you elaborate more on '[d]isabl[ing] MyXperia'?
How may I do it?
I've locked and then unlocked the bootloader using Androxyde's many times since. But no change.
Please guide me more because it hurts without phone for more than a week, you can imagine!
Sithu Htun said:
Disable MyXperia
Else, relock and unlock bootloader using Flashtool.
Click to expand...
Click to collapse
Hey.
Thanks for helping me.
Will you elaborate more on '[d]isabl[ing] MyXperia'?
How may I do it?
I've locked and then unlocked the bootloader using Androxyde's many times since. But no change.
Please guide me more because it hurts without phone for more than a week, you can imagine!
Try unlocking manually using command prompt
fastboot -i 0x0fce oem unlock 0xUnlockCode
Sithu Htun said:
Try unlocking manually using command prompt
fastboot -i oem unlock 0x0fce 0xUnlockCode
Click to expand...
Click to collapse
Error:
Sithu Htun said:
Try unlocking manually using command prompt
fastboot -i oem unlock 0x0fce 0xUnlockCode
Click to expand...
Click to collapse
Error:
sorry my bad.
fastboot -i 0x0fce oem unlock 0xUnlockCode
try minmal app from here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
Sithu Htun said:
sorry my bad.
fastboot -i 0x0fce oem unlock 0xUnlockCode
Click to expand...
Click to collapse
andro971 said:
try minmal app from here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
Click to expand...
Click to collapse
No help?
Finally I managed to partially solve this problem.
Steps:
- rooting my phone using Kingoroot
- restoring TA backup
- unlocking my bootloader
- flashing a ROM excluding TA partitions
No I don't get that error and I can successfully flash the recovery.
fastboot flash recovery twrp-2.8.7.0-togari.img
sending 'recovery' (14018 KB)...
OKAY [ 1.042s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.962s
Click to expand...
Click to collapse
But the new problem is that I can't boot into it. I used to boot into recovery mode by keeping volume down and power button simultaneously until the phone vibrates when I had to release the power button but still keep the volume down key. This doesn't work. I also tried fastboot command to reboot into recovery but no result.
Will anyone help?
aliansahere said:
Finally I managed to partially solve this problem.
Steps:
- rooting my phone using Kingoroot
- restoring TA backup
- unlocking my bootloader
- flashing a ROM excluding TA partitions
No I don't get that error and I can successfully flash the recovery.
But the new problem is that I can't boot into it. I used to boot into recovery mode by keeping volume down and power button simultaneously until the phone vibrates when I had to release the power button but still keep the volume down key. This doesn't work. I also tried fastboot command to reboot into recovery but no result.
Will anyone help?
Click to expand...
Click to collapse
Since your bootloader is unlocked try flashing the new xzu bootloader which Sony provided connect your device to Emma via flash mode and flash the new service
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"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"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
{
"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"
}
Please help.
Thanks
+1, same thing happening to me, halp
shraga1 said:
in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
Please help.
Thanks
Click to expand...
Click to collapse
So we could not be able to root this tablet?
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
simone81 said:
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
Click to expand...
Click to collapse
which drivers have you installed?
pabloluih said:
which drivers have you installed?
Click to expand...
Click to collapse
I did connect the tablet to the pc, the problem was in the cable, now i can enter in fastboot but i dont know wich command to use to unlock the bootloader, i tried fastboot oem unlock and it give me as a result failed because unknown command. I hope there will be a way to root it because its very good device. The drivers i used are available online here https://www.getdroidtips.com/root-teclast-p80x-4g/
Go on youtube and find "Teclast Root Process for Android Tablet"
I haven't found a solution but thought this might help.
I thought this might be of some use - however on their website putting in the P80X ID doesn't yield any firmware.
Perhaps you guys can make heads and tails of it.
How do you even get in the developer menu? The usual build number clicking doesn't seem to work on the P80X
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
few__ said:
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
Click to expand...
Click to collapse
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
delete
null
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
Click to expand...
Click to collapse
how did you unlock the bootloader?
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message.
Click to expand...
Click to collapse
That's great and all, but HOW?
Remember, forums are not only for you, but for others too. Share your knowledge!
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Texasblazed said:
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Click to expand...
Click to collapse
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
jwoegerbauer said:
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
Click to expand...
Click to collapse
wrong, its a qualcomm
So can this device be rooted or not? Correct replies only would be great.
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
{
"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"
}
like this?
krayzieiyian23 said:
View attachment 5351809like this?
Click to expand...
Click to collapse
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
(
I know little about Android development but I have the device it's not my daily driver so I can test stuff on it and if it goes south it's no big deal. Btw the revvl 4+ is the Qualcomm model, the 4 is the mediatek soc.
clintongsan said:
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
Click to expand...
Click to collapse
Have you had any luck on this yet???
I selected the first DSu , let it install and now the bootloader is corrupt. ( which im pretty sure means its inoperable) so the verity is definitly disabled. I can load into fastboot and baout to test the fastboot oem unlock.
clintongsan said:
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
Click to expand...
Click to collapse
I was bale to let it install. You gotta downgrade to the first firmware it came with and let the DSU install. My dm-verity is corrupted which is, Im pretty sure disabled, and im able to boot into fastboot
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Anyone found a stock firmware for this yet?
sketchscarz said:
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Click to expand...
Click to collapse
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
mfoster978 said:
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
Click to expand...
Click to collapse
when yourein fastboot d, in adb type fastboot reboot bootloader
sketchscarz said:
when yourein fastboot d, in adb type fastboot reboot bootloader
Click to expand...
Click to collapse
hmm this justs boots the phone back into the android os
then select reboot to bootloader when in fastbootd
or you can hold the volume up while plugging into your computer until you get fastboot mode at the bottom of the screen, you gotta select the dsu at least once to be able to enable orange state on tmobile boot screen
let it sit there forlike 20 minutes itll say android annd ot boot for a long time.... i let it sit there for about 15-20 minutes
im trying to figure out how to make a twrp for this device ow that the bootloader is unlocked
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"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"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello