Related
Hi was wondering if any1 had a nanodroid image of the stock nexus 1 system i accdently deleted mine and now am stuck with a non working phone, ive tryed flashing different FRF files 1 boots but theres no screen.
if any1 can help thanks.
ok ive download the frf91 full but theres an issue when installing it it pops up with an error installing update. assert failed : !less_than_in and a long number, get prop("ro.build.date.ut"))
so what am i doing wrong ive reinstalled the started flash recovery
scoobyturbo said:
Hi was wondering if any1 had a nanodroid image of the stock nexus 1 system i accdently deleted mine and now am stuck with a non working phone, ive tryed flashing different FRF files 1 boots but theres no screen.
if any1 can help thanks.
ok ive download the frf91 full but theres an issue when installing it it pops up with an error installing update. assert failed : !less_than_in and a long number, get prop("ro.build.date.ut"))
so what am i doing wrong ive reinstalled the started flash recovery
Click to expand...
Click to collapse
i dont understand your last sentance.
do you have a working recovery ? if so, download whatever rom you like and flash it. wipe the phone first. should be fine.
ohgood said:
i dont understand your last sentance.
do you have a working recovery ? if so, download whatever rom you like and flash it. wipe the phone first. should be fine.[/QUOTe
yes i do have a working recovery i'm trying to get back to the standerd rom, but i cant seem to get it to install.
its a uk vodafone nexus 1 with unlocked Bootloader
Click to expand...
Click to collapse
You have Vodafone Nexus? Probably have SLCD? In that case, stock FRF91 won't work for you. You need Vodafone image. Or you could flash Korean version, KR_KT_... .
If you have unlocked bootloader, just unpack the ROM ZIP and do:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
You can also do it for FRF91, if you don't have SLCD version.
Jack_R1 said:
You have Vodafone Nexus? Probably have SLCD? In that case, stock FRF91 won't work for you. You need Vodafone image. Or you could flash Korean version, KR_KT_... .
If you have unlocked bootloader, just unpack the ROM ZIP and do:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
right big thanks to you phones now working again i ow u 1 spent the last 5 hrs trying to get it to work
once again THANK you very much
Click to expand...
Click to collapse
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
V2056A | PD2056 | 5G China variant
- PD2056B_A_1.11.13 HERE Android 11
thats good!
and how can i flash it?
My device is last week broken . is the rom flashable with fastboot? thx mike
How did you broken the device?
You can simply upload zip on device with adb command and flash by using stock recovery mode
adb push .....
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
88user88 said:
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
Click to expand...
Click to collapse
My PC is over adb unautorized, after the Factory reset...
I managed to get this full rom from Recovery, there is a option to download the full last rom and burn. I use another phone with photo google translator to navegate in the menu.
I know this option with the update from the WLAN - but this option is no longer available to me - after the search for a network is completed, no further networks are displayed. He doesn't find any networks.
And the second problem was - I cannot import this Update.zip into the main directory because the PC is unauthorized.
It wasn't just the MTK tool that was wrong.
I think our mistake was you mixed recovery and boot of another Rom. I did that many years ago with Huawei but for me it was a hard brick. Better not mix!
yes i think thatat too. first step now- i try to put the phone in EDL download mode. Then I could try the Qualcomm Flash Tool -. .. But thank you anyway.
with which command did you unlocked the bootloader? I can't find a way.
@88user88 : i wish you the best.
Do you see a way to flash the indian ROM?
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
DPMDP said:
with which command did you unlocked the bootloader? I can't find a way.
Click to expand...
Click to collapse
+1
wolfgart said:
V2056A | PĐ2056 | Biến thể 5G Trung Quốc
- PD2056B_A_1.11.13 TẠI ĐÂY Android 11
Click to expand...
Click to collapse
hello i am a new user in vietnam, can you guide me in detail how to install . Thank you very much
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out.
DPMDP said:
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
Click to expand...
Click to collapse
OK, if we manage to restore my device, I'll give you instructions on how you can unlock your bootloader. then at least I know that in an emergency you also have the option to restore your device.
otherwise it would be too unsafe for me ...
ok?-now you come!
astrofahim said:
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out. YouTube Vanced also always failed to open.
Click to expand...
Click to collapse
same here, my device is iqoo 7 cn origin os i downloaded from android 12 website, failed to upgrade in recovery mode when in hardware check.
both on funtouch os and android 12
Hi, does anyone know where it is I can find this PD2056C_A_1.14.1 firmware
the command menu of the recovery mode of the Chinese version and in Chinese or English
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
forget this..i've got ROOT check the other thread !
How do you fix it?
simika said:
forget this..i've got ROOT check the other thread !
Click to expand...
Click to collapse
How did you managed to fix this?
by reading lol.. check the other thread all written
For reference to whoever that are confused about where to look for the solution.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Download the vbmeta and flash it via fastboot to get rid of the dm-verify.
simika said:
by reading lol.. check the other thread all written
Click to expand...
Click to collapse
Could you reference a link or give me a little how to?
I tried a lot now:
- Installed a new Firmware trough Fastboot
- Using MsmDownload Tool
nothing helped so far.
So it would be great if you could assist in any way.
simika said:
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
Click to expand...
Click to collapse
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?
if you can enter in fastboot mode, reflash stock boot and vbmeta
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
How can I do? Miflash says:
error:Writing 'crclist' FAILED (remote: 'not allowed in locked state')
bro you have relock bootloader, this is a fatal error. the only way is try to unlock with an mtk tool that do this via pc. you can find on internet. search unlock all mtk devices. i think there a link also on xda
Just realized that the M3 thread, my phone is a M4.
.
@simika how are you sending this question?
1. Hello friends, there are two ways to fix this problem, first you need Root, I read your Root tutorial, your tutorial is very good, and after using Root, you need to download any file manager, give Root Permissions, you need to backup your baseband, nvram nvdata nvcfg backup and save, you also need an MTK Bypass, you can search for MTK Auth Bypass Tool through Google, you also need to use SP Flash to flash the machine, you need to download the official firmware package, which can be downloaded from xiaomirom.com , download the corresponding version, use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, But you have backed up. Boot through fastboot to unlock the BL lock, perform fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. Congratulations The baseband is back, I'm a novice, my instructions are not comprehensive, such as where is the baseband location, but I have too many characters, I will list the baseband location. 2. Replace a new motherboard, all mobile phone problems are all solve.
Hope to help you.
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
Thanks. This worked on my Umidigi A11 phone.
xdadev_user11 said:
Thanks. This worked on my Umidigi A11 phone.
Click to expand...
Click to collapse
nice!
hello i got the same problem today, my phone is redmi9a can some help me regarding to this error ?
i had this problem even though i never unlocked my bootloader so i couldnt flash anything to fix it. but when i got the miui 13 update it fixed it for me
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
What if you cant enter fastboot?