Hello Guys, im fighting with Kiano slimtab 7 3gr for a few days.
First of all i made a root form this solution: http://forum.xda-developers.com/android/development/mod-t3175515 and it worked.
Now i want to unlock bootloader and install TWRP, but there are some problems. I have estabilished ADB and Fastboot connection with no problems. But when i go into fastboot mode and im trying to unlock bootloader via fastboot oem unlock commad it doeasn't work. Could someone help me?
Code:
[email protected]:~# fastboot devices
0123456789012345 fastboot
[email protected]:~# fastboot flash recovery recovery.img
(bootloader) recovery partition type: raw
target reported max download size of 1019215872 bytes
sending 'recovery' (14090 KB)...
(bootloader) Device is locked, cannot perform flash in fastboot
(bootloader) Please use the below command to unlock first:
(bootloader) > fastboot oem unlock
FAILED (remote failure)
finished. total time: 0.026s
[email protected]:~# fastboot oem unlock
...
FAILED (remote: couldn't change state!)
finished. total time: 0.022s
[email protected]:~#
ok I've got it. There was and option to unlock oem in debugging mode settings. So after that fastboot commands suceeded. Botloader is unlocked but i guess i crashed it
I've uploaded recovery.img file and after reboot android doesn't work. I can only send fastboot commands. Could sb help me?
Did you solve your problem? I also crashed my slimtab after I unlocked the bootloader.
Yes, I've solved a problem. I threw it to trash and bought Galaxy Tab A
Did you have green screen in fastboot, or after reboot some lines on black (green, red lines). There is possibly text, but you can't read it squares. Have someone original Kiano Slimtab 7 3GR recovery.img to flash?
Здравствуйте. Дайте оригинальную прошивку или бекап. Прошивка Chuvi не подходит
Related
Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked
I tried to restore and reinstall ROM in numerous ways, including adb, fastboot and sdcard. I even tried Funky Huawei.
Currently I can get to eRecovery and to TWRP. Fastboot works without problem. But that's about it, boot sometimes goes to Lineage boot splash, which I used prior the Magisk update.
Thanks for help in advance
Here is info from fastboot:
fastboot oem get-product-model:
<bootloader> CMR-AL09
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem get-build-number:
(bootloader) :CMR-AL09 8.0.0.122(C432)
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-system_version
FAILED (remote: The reason of failed input oem_nv_item error!)
help do not know why this happen cannot boot up.thanks for any help.
Hi , it means that you have enter into FastBoot mode , and also your Software is not official !
Anyway to exit from fastboot mode just press 5 times Vol + and One time power key . Now again turn On your device and it should boot up normaly . Good Luck
Teddy Lo said:
Hi , it means that you have enter into FastBoot mode , and also your Software is not official !
Anyway to exit from fastboot mode just press 5 times Vol + and One time power key . Now again turn On your device and it should boot up normaly . Good Luck
Click to expand...
Click to collapse
Thank you for your reply but still will not work here is the screen shot of what happens when i do what you have said..Thanks again
So for you the problem is probably corrypted OTA updates which didn't go well because your battery in that moment didn't had enough energy .
Anyway to bring your device in working condition you need:
1. PC with working internet
2. USB cable
3. Download REpair Assistant https://www.verizonwireless.com/support/knowledge-base-116950/#windows
https://www.verizonwireless.com/support/knowledge-base-116950/#windows
Install this tool on your pc once you installed reboot your PC and once boot is finish plug your device with usb cable inside the PC , run the Repair Assistant and follow instructions .
Good luck
thanks again
Teddy Lo said:
So for you the problem is probably corrypted OTA updates which didn't go well because your battery in that moment didn't had enough energy .
Anyway to bring your device in working condition you need:
1. PC with working internet
2. USB cable
3. Download REpair Assistant https://www.verizonwireless.com/support/knowledge-base-116950/#windows
https://www.verizonwireless.com/support/knowledge-base-116950/#windows
Install this tool on your pc once you installed reboot your PC and once boot is finish plug your device with usb cable inside the PC , run the Repair Assistant and follow instructions .
Good luck
Click to expand...
Click to collapse
no luck
Hi , tell me full model name for your device so I can send you firmware which you can flash with fastboot terminal ...
motog 1540
Teddy Lo said:
Hi , tell me full model name for your device so I can send you firmware which you can flash with fastboot terminal ...
Click to expand...
Click to collapse
I have the original software but i need to know the steps i need to do through fastboot in terminal.When i say abd devices it shows no device?Here are 3 screen shots from recovery i chose update from sd card then also wipe all data then reboot shot.thanks for your help..
Hi , download this firmware :
https://androidfilehost.com/?fid=889764386195908045
Once the downloading file is finished , put firmware to the ADB folder ( directory where is your minimal adb & fastboot installed) for example :
C:/ADB/
Now to get your device into adb mode you need to select Apply update from ADB and then wait for adb drivers to be instaled if is not .
Next write adb devices and you should see your device and sideload inside terminal ...
Now flash this firmware with command:
adb sideload osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip and press Enter .
Good luck
Teddy Lo said:
Hi , download this firmware :
https://androidfilehost.com/?fid=889764386195908045
Once the downloading file is finished , put firmware to the ADB folder ( directory where is your minimal adb & fastboot installed) for example :
C:/ADB/
Now to get your device into adb mode you need to select Apply update from ADB and then wait for adb drivers to be instaled if is not .
Next write adb devices and you should see your device and sideload inside terminal ...
Now flash this firmware with command:
adb sideload osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip and press Enter .
Good luck
Click to expand...
Click to collapse
Thanks again for your help but adb devices cannot find any devices or emulators and i cannot get inside of android to enable usb debugging is there a way using fast boot to flash the recovery because fastboot devices comes up with my serial number?
Try the same file osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip with command :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip
And see what is happening .
Teddy Lo said:
Try the same file osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip with command :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update osprey_retasia_ds-user+6.0.1+MPIS24.107-55-2-17+19.zip
And see what is happening .
Click to expand...
Click to collapse
Another sreen shot before i rebooted still nothing ,You area very patient man.Thanks
klassic1 said:
Another sreen shot before i rebooted still nothing ,You area very patient man.Thanks
Click to expand...
Click to collapse
Hi , I need little more information .
1. What is full model name ? ( open the battery cover and see what model is or send me private imei to check )
2. For which carier is your device ? ( SPRINT , USC , Retus )
Teddy Lo said:
Hi , I need little more information .
1. What is full model name ? ( open the battery cover and see what model is or send me private imei to check )
2. For which carier is your device ? ( SPRINT , USC , Retus )
Click to expand...
Click to collapse
Thanks again for your patients.
The carrier is Telus here in Canada and here is the info you requested.
Great , now once we know the right information you can finaly rest ^_^ .
Download this firmware:
https://drive.google.com/uc?export=download&id=0Bw_NsGJYGFyVaXc3dFMxYUNxaEk
Once you downloaded extract all files inside location where minimal ADB & fastboot is installed .
For example C:/ADB ...
Now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck , and let me know if you fixed or not .
Teddy Lo said:
Great , now once we know the right information you can finaly rest ^_^ .
Download this firmware:
https://drive.google.com/uc?export=download&id=0Bw_NsGJYGFyVaXc3dFMxYUNxaEk
Once you downloaded extract all files inside location where minimal ADB & fastboot is installed .
For example C:/ADB ...
Now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck , and let me know if you fixed or not .
Click to expand...
Click to collapse
Did all you asked first shot show no slots did that for all.then second picture of what it said at reboot
Hi , you did it wrong !
This file XT1540_OSPREY_RETCA-TELUS_6.0_MPI24.65-33.1-2_cid14_subsidy-TELUS_CFC.xml.zip you need to extract to minimal adb and fastboot directory !
So if you didn't understand
1. Uninstall minimall adb and fastboot toll completely .
2. Download this minimal adb & fastboot terminal and instal normaly into C: directory
https://androidfilehost.com/?fid=745425885120698566
here is example how to install just click on next ... Make sure is on C partition.
https://forum.xda-developers.com/showthread.php?t=2317790
Once instaling is finished go to C: partition and you will see one folder with name "ADB" that is your minimal adb & fastboot directory.
3. Extract with 7-zip XT1540_OSPREY_RETCA-TELUS_6.0_MPI24.65-33.1-2_cid14_subsidy-TELUS_CFC.xml.zip to the ADB folder .
If you don't have the 7-zip download grom here :
https://www.7-zip.org/download.html
4. Once you extracted all , put your device into bootloader mode and now put your phone to Bootloader mode then open Minimal ADB and Fastboot terminal and write one by one commands:
fastboot devices and press Enter ( just to make sure that your device is recognised )
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase logo
fastboot oem fb_mode_clear
fastboot reboot
If you are still facing same error you should unlock bootloader :
write command :
fastboot oem get_unlock_data
it shloud look like this something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
just copy and paste here all stings like this example .
This is what i get ..
D:\platform-tools-latest-windows\platform-tools>fastboot devices
TA391006KH fastboot
D:\platform-tools-latest-windows\platform-tools>fastboot flash partition D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.393s
D:\platform-tools-latest-windows\platform-tools>fastboot flash bootloader D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.155s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.637s]
finished. total time: 1.805s
D:\platform-tools-latest-windows\platform-tools>fastboot flash logo D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.081s]
writing 'logo'...
OKAY [ 0.116s]
finished. total time: 0.204s
D:\platform-tools-latest-windows\platform-tools>fastboot flash boot D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 0.985s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.702s
D:\platform-tools-latest-windows\platform-tools>fastboot flash recovery D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 0.961s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.728s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (257199 KB)...
OKAY [ 5.813s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.232s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (255632 KB)...
OKAY [ 5.848s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.917s
D:\platform-tools-latest-windows\platform-tools>fastboot flash system D:\XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml\system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (255866 KB)...
OKAY [ 5.851s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.920s
Only this is someone else's but mine does exactly the same...with telus zip
Hi
I'm stuck in my Xiaomi MI A3 bootloader, can't boot to recovery and system.
After flashing my stock firmware.
Here is my oem device info
PS C:\platform-tools> ./fastboot oem device-info (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
Finished. Total time: 0.006s
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
bgsebiosjr said:
Hi
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
Click to expand...
Click to collapse
Change current-slot to 'a' and reboot.
PS C:\platform-tools> ./fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.005s
PS C:\platform-tools> ./fastboot flashing unlock FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
How can i use EDL?
Sapper Morton said:
Since your bootloader is locked, and there's no proper system.img in slot B, you must change it to slot A; however it's not possible in locked state, first check if it's possible to unlock, by running:
Code:
fastboot flashing get_unlock_ability
If the output is 0, you cannot unlock, and EDL is a must, otherwise, the output will be 1, therefore, unlock is possible, then proceed with the following steps:
Code:
fastboot flashing unlock
Code:
fastboot set_active a
Code:
fastboot flashing lock
As explained above, it's not possible to change slot without unlocking the bootloader.
Click to expand...
Click to collapse
msatyanarayana said:
Change current-slot to 'a' and reboot.
Click to expand...
Click to collapse
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
bgsebiosjr said:
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
Click to expand...
Click to collapse
EDL mode and authorized Mi account. You should contact your nearest Xiaomi service center or use some online service (you might need to open your phone yourself in such case).
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i_plevra said:
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Click to expand...
Click to collapse
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
alonsoj636 said:
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
Click to expand...
Click to collapse
This smartphone is a Japan-only model for a company called au, but probably a global version is available. The size is a little different but the base is redmi note 10 5g I just checked and it seems to be 5g I'm not confident I'll use miflash. It's a hassle to borrow a phone from a family member, stick a sim in it and have to receive an authentication SMS.
pihpih95 said:
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
Click to expand...
Click to collapse
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
now I can't use Windows for some reasons so am using m1 mac, this pc can't use the miflash so am trying GSI boot in a while
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
big problem...
your device is locked which means that flashing anything (vbmeta , recovery) or use MiFlash Tool will not be possible because unlocked bootloader is compulsory
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
do you still have mi recovery, or only have fastboot?
LR7875 said:
do you still have mi recovery, or only have fastboot?
Click to expand...
Click to collapse
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
i_plevra said:
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
Click to expand...
Click to collapse
and does fastboot oem unlock or fastboot oem unlock_critical work
LR7875 said:
and does fastboot oem unlock or fastboot oem unlock_critical work
Click to expand...
Click to collapse
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
have u apply to unlock bootloader through official method ?
i_plevra said:
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...oken-verify-failed-reboot-the-device.4300755/ this is for redmi note 10 pro but is worth to read. maybe it can help