Database Develop

Not able to find "OEM unlocking" in the developer options

Hi guys,
I am trying to root my BLU R1 HD and I read many articles all of which says I need to turn on "OEM unlocking" in the developers options.
However, I can not find such option on my phone.
So I skipped this step and then failed to unlock the bootloader.
So can anyone help to point out what should I do?
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: no devices found
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.125s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot devices
OBDQY9J7KVBIYPTW fastboot
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 10.695s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 59.152s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>
Thanks,
Yun

Yun Wu said:
Hi guys,
I am trying to root my BLU R1 HD and I read many articles all of which says I need to turn on "OEM unlocking" in the developers options.
However, I can not find such option on my phone.
So I skipped this step and then failed to unlock the bootloader.
So can anyone help to point out what should I do?
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: no devices found
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.125s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot devices
OBDQY9J7KVBIYPTW fastboot
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 10.695s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 59.152s
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>
Thanks,
Yun
Click to expand...
Click to collapse
Well hello Yun,
You have come to the right place.
Those articles you read could not have been on this site though. Look around at some of the threads here on this sub-forum, your questions have been asked and answered many times.
PS
HINT:. There is no oem unlock switch in this phone(option hidden by manufacturer to block root attempt). And if build custom version higher than 8, there is no working root method.

mrmazak said:
Well hello Yun,
You have come to the right place.
Those articles you read could not have been on this site though. Look around at some of the threads here on this sub-forum, your questions have been asked and answered many times.
PS
HINT:. There is no oem unlock switch in this phone(option hidden by manufacturer to block root attempt). And if build custom version higher than 8, there is no working root method.
Click to expand...
Click to collapse
Hi mrmazak,
Thanks so much for the warm greeting.
On this forum what I found is this: R1 HD Amazon Bootloader unlock method https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104
I tried the method 1 and here is what I got as I already posted:
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>fastboot getvar all
.
.
.
(bootloader) unlocked: no
.
.
.
And I also tried method 2 and got a S_BROM_DOWNLOAD_DA_FAIL (0x7D4) error.
Then on https://forum.xda-developers.com/r1-hd/help/error-sbromdownloaddafail-0x7d4-help-t3485791 someone said
If you are on prime update 6.6 or newer then that message is because the preloader has been replaced by Blu the purposefully block sp flash tool.
Does that "prime update 6.6 or newer" also means "build custom version" as you mentioned?
The build custom version on my phone is BLU_R0010UU_V8.5_GENERIC 13-06-2017 18:25, so according to your statement looks like I won't have a chance to root it ... So sad T_T ...
Anyway, thanks very much again!

Look in Settings->About device->Custom build version and tell us what it is. Someone posted that the phones currently shipping from Amazon are coming with version 8.x which can not be rooted or flashed.

yaconsult said:
Look in Settings->About device->Custom build version and tell us what it is. Someone posted that the phones currently shipping from Amazon are coming with version 8.x which can not be rooted or flashed.
Click to expand...
Click to collapse
Hi yaconsult, it's BLU_R0010UU_V8.5_GENERIC 13-06-2017 18:25. Thanks.

Yun Wu said:
Hi yaconsult, it's BLU_R0010UU_V8.5_GENERIC 13-06-2017 18:25. Thanks.
Click to expand...
Click to collapse
Then you have the updated version that can't be rooted as SP Flash Tool has been disabled. If you didn't update it yourself after you got it then you must have gotten one of the newer versions that Amazon is reported to be shipping now.
It might still be possible to remove the ads, though. Read all the way through this thread: https://forum.xda-developers.com/r1-hd/help/remove-ads-fresh-blu-r1-hd-t3654431 But I'm not sure if this still works with the latest version or not.

yaconsult said:
Then you have the updated version that can't be rooted as SP Flash Tool has been disabled. If you didn't update it yourself after you got it then you must have gotten one of the newer versions that Amazon is reported to be shipping now.
It might still be possible to remove the ads, though. Read all the way through this thread: https://forum.xda-developers.com/r1-hd/help/remove-ads-fresh-blu-r1-hd-t3654431 But I'm not sure if this still works with the latest version or not.
Click to expand...
Click to collapse
Thanks.
Yes, I did the update some time ago
I will try the "pm hide" method and update my status later, thanks very much for your suggestion!

yaconsult said:
Then you have the updated version that can't be rooted as SP Flash Tool has been disabled. If you didn't update it yourself after you got it then you must have gotten one of the newer versions that Amazon is reported to be shipping now.
It might still be possible to remove the ads, though. Read all the way through this thread: https://forum.xda-developers.com/r1-hd/help/remove-ads-fresh-blu-r1-hd-t3654431 But I'm not sure if this still works with the latest version or not.
Click to expand...
Click to collapse
Hi yaconsult,
Unfortunately, looks like I am not able to "pm hide" an app on my BLU R1 HD running BLU_R0010UU_V8.5_GENERIC.
The reason is my phone is not shown on "adb devices".
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>adb devices
List of devices attached
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>adb shell pm list packages
error: no devices found
D:\phone\BLU-R1-HD-Bootlaoder-Unlock>
Before doing this I have already enabled USB debugging.
One thing I noticed is there are only 3 choices for USB:
- Charging only;
- MTP;
- PTP;
I am not sure whether there is an debugging choice when running version older than v8.x.
Thanks,
Yun

Well, you can't do anything until adb can see your phone, so...
Did you check the windows device manager to see if Windows has a driver for the phone installed? Or is there an exclamation mark in device manager meaning that there isn't a driver for it? Windows drivers can be a pain so I used my Linux system to reflash and root my phone.
Did you enable developer options on the phone?
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number." (Your build number may vary from ours here.)
Tap it seven (7) times.​You can find some posts about getting adb working on your phone in this thread, if you need them, even though you can't root your updated phone using that method: https://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Once you can see your phone with 'adb devices', then see mrmazak's post here: https://forum.xda-developers.com/showpost.php?p=73582720&postcount=18

yaconsult said:
Well, you can't do anything until adb can see your phone, so...
Did you check the windows device manager to see if Windows has a driver for the phone installed? Or is there an exclamation mark in device manager meaning that there isn't a driver for it? Windows drivers can be a pain so I used my Linux system to reflash and root my phone.
Did you enable developer options on the phone?
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number." (Your build number may vary from ours here.)
Tap it seven (7) times.​You can find some posts about getting adb working on your phone in this thread, if you need them, even though you can't root your updated phone using that method: https://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Once you can see your phone with 'adb devices', then see mrmazak's post here: https://forum.xda-developers.com/showpost.php?p=73582720&postcount=18
Click to expand...
Click to collapse
Thanks.
I think the driver is successfully installed. I can see my phone in the Computer, and I didn't see any exclamation in the device manger. But, OK I will try Linux.
Yes I have already enable develop options.
I read the thread you mentioned (https://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677), the problem is, as I mentioned many times, I always got a S_BROM_DOWNLOAD_DA_FAIL (0x7D4) error after my phone powered off.
I will try on Linux to see whether my phone can show up on 'adb devices'.
Thanks and let me update later.

yaconsult said:
Well, you can't do anything until adb can see your phone, so...
Did you check the windows device manager to see if Windows has a driver for the phone installed? Or is there an exclamation mark in device manager meaning that there isn't a driver for it? Windows drivers can be a pain so I used my Linux system to reflash and root my phone.
Did you enable developer options on the phone?
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number." (Your build number may vary from ours here.)
Tap it seven (7) times.​You can find some posts about getting adb working on your phone in this thread, if you need them, even though you can't root your updated phone using that method: https://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Once you can see your phone with 'adb devices', then see mrmazak's post here: https://forum.xda-developers.com/showpost.php?p=73582720&postcount=18
Click to expand...
Click to collapse
Thanks god!
Finally, my device is showing up on "adb devices" when I used another Win 7 laptop.
Probably, the reason I could not make it is because driver is not correctly installed.
Now, I have followed thread https://forum.xda-developers.com/r1-hd/help/remove-ads-fresh-blu-r1-hd-t3654431/page2 #12 and remove all amazon apps, and I feel so good!
Thanks yaconsult, mrmazak and kameleon25 very very much! You guys helped me a lot!
I wish you guys have a great long weekend!
There is still one thing left:
Does anyone knows how to remove this "Discover your next favorite book"?
I guess it is a lock-screen wallpaper, and wonder whether there is a chance to replace it or remove it.
I did some google, however have not found an answer yet.
{
"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"
}

HTC 626G cannot retreive OEM identifier token from fastboot

Hello,
I have been trying in vain for the last two days to unlock the bootloader of my wife's HTC 626G phone following the instructions on HTC's site which, as I understand, is the first prerequisite before one can install a custom ROM on it.
I have scoured the Web for all sorts of recipes, howtos, and hacks (also in this forum) but none of them seems to match my particular environment.
In fact, most instructions assume that their user have a Windows host at their hand which is no option for me, for I can only rely on a Linux host and would like to prefer usage of the ADB tools from a shell.
I am trying this on a Fedora with following Android tools' versions.
Code:
[[email protected]:~/HTC_Desire-626/log]
$ rpm -qf $(which fastboot)
android-tools-20160327git3761365735de-2.fc25.x86_64
I have only discovered ways so far, to boot the phone into one of the following modes: bootloader, recovery, or sideload (no idea, what the last one would be used for), either via adb reboot ...[\i], or by pressing Volume Down plus Power On buttons at phone.
I haven't discovered how to boot into the ominous "download" mode.
So having attached the phone, that has been booted into fastboot mode
(n.b. phone's display shows at the bottom "=> FASTBOOT mode...")
to my Fedora host's USB port, while the ADB Server is running
(started via systemd, though don't know if this is necessary, when only fastboot commands are issued)
Code:
[[email protected]:~/HTC_Desire-626/log]
$ systemctl is-active adb.service
active
[[email protected]:~/HTC_Desire-626/log]
$ systemctl show adb.service -p MainPID
MainPID=3862
the fastboot command that should be issued to retrieve the OEM token, that needs to be submitted to the HTC site in order to receive an unlock token from them, fails.
(n.b. unlike all issued adb commands in device mode, I found out that the fastboot command requires root privileges.
when issuing fastboot as !root user, I get the pesky "waiting for device" hang)
Code:
[[email protected]:~/HTC_Desire-626/log]
$ fastboot --version
fastboot version 3761365735de
[[email protected]:~/HTC_Desire-626/log]
$ fastboot devices
no permissions; see [http://developer.android.com/tools/device.html] fastboot
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot devices -l
0123456789AB fastboot usb:3-1.3
[[email protected]:~/HTC_Desire-626/log]
$ fastboot oem get_identifier_token
< waiting for any device >
^C
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot flashing get_unlock_ability
...
FAILED (remote: unknown command)
finished. total time: 0.003s
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot getvar all
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 5e000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: ce0000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:cota: 3200000
(bootloader) partition-type:cota: ext4
(bootloader) partition-size:resv: 80000
(bootloader) partition-type:resv: raw data
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: a00000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: a00000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) kernel: lk
(bootloader) product: HTC_EUROPE
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.004s
Can anyone tell me if my phone is capable at all to disclose the coveted OEM identity token, or suggest a method or hack that would work in my Windows-free setting?

I had a similar issue just today with mine. I am running Ubuntu so it may not be the same issue for you:
I am running a 64 bit fastboot (same as you it appears). I downloaded the fastboot from htcdev site (32 bit) and had to install the 32 bit libraries before it would even run. Even after getting that fastboot to run I was receiving the same error. I ended up getting this working by booting the device to Download mode and using the 32 bit fastboot.
If you get an ambiguous error that the file doesn't exist you need 32 bit libraries: ia32-libs (aka lib32z1) and 32 bit libs for c++ (lib32stdc++6); you should be able to yum those.
TLDR; Try adb reboot bootloader then using volume down to select reboot Download mode. if that doesn't work try the fastboot from htcdev site while the device is in download mode; not bootloader mode.

Cpt_Birdseye said:
Hello,
I have been trying in vain for the last two days to unlock the bootloader of my wife's HTC 626G phone following the instructions on HTC's site which, as I understand, is the first prerequisite before one can install a custom ROM on it.
I have scoured the Web for all sorts of recipes, howtos, and hacks (also in this forum) but none of them seems to match my particular environment.
In fact, most instructions assume that their user have a Windows host at their hand which is no option for me, for I can only rely on a Linux host and would like to prefer usage of the ADB tools from a shell.
I am trying this on a Fedora with following Android tools' versions.
Code:
[[email protected]:~/HTC_Desire-626/log]
$ rpm -qf $(which fastboot)
android-tools-20160327git3761365735de-2.fc25.x86_64
I have only discovered ways so far, to boot the phone into one of the following modes: bootloader, recovery, or sideload (no idea, what the last one would be used for), either via adb reboot ...[\i], or by pressing Volume Down plus Power On buttons at phone.
I haven't discovered how to boot into the ominous "download" mode.
So having attached the phone, that has been booted into fastboot mode
(n.b. phone's display shows at the bottom "=> FASTBOOT mode...")
to my Fedora host's USB port, while the ADB Server is running
(started via systemd, though don't know if this is necessary, when only fastboot commands are issued)
Code:
[[email protected]:~/HTC_Desire-626/log]
$ systemctl is-active adb.service
active
[[email protected]:~/HTC_Desire-626/log]
$ systemctl show adb.service -p MainPID
MainPID=3862
the fastboot command that should be issued to retrieve the OEM token, that needs to be submitted to the HTC site in order to receive an unlock token from them, fails.
(n.b. unlike all issued adb commands in device mode, I found out that the fastboot command requires root privileges.
when issuing fastboot as !root user, I get the pesky "waiting for device" hang)
Code:
[[email protected]:~/HTC_Desire-626/log]
$ fastboot --version
fastboot version 3761365735de
[[email protected]:~/HTC_Desire-626/log]
$ fastboot devices
no permissions; see [http://developer.android.com/tools/device.html] fastboot
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot devices -l
0123456789AB fastboot usb:3-1.3
[[email protected]:~/HTC_Desire-626/log]
$ fastboot oem get_identifier_token
< waiting for any device >
^C
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot flashing get_unlock_ability
...
FAILED (remote: unknown command)
finished. total time: 0.003s
[[email protected]:~/HTC_Desire-626/log]
$ sudo fastboot getvar all
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 5e000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: ce0000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:cota: 3200000
(bootloader) partition-type:cota: ext4
(bootloader) partition-size:resv: 80000
(bootloader) partition-type:resv: raw data
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: a00000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: a00000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) kernel: lk
(bootloader) product: HTC_EUROPE
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.004s
Can anyone tell me if my phone is capable at all to disclose the coveted OEM identity token, or suggest a method or hack that would work in my Windows-free setting?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77300835&postcount=2

i need help R1 HD

I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all

This is photo of recovery may help you to help me get it back

KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?

mrmazak said:
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?
Click to expand...
Click to collapse
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
When use flash tool I get this error
S_BROM_DOWNLOAD_DA_FAIL (0x7D4)

KARIM9377 said:
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
Click to expand...
Click to collapse
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip

mrmazak said:
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
Here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...ric_6.0_20170505-17451495815395129/update.zip
Click to expand...
Click to collapse
r0011uu is it working on r0030uu ?

KARIM9377 said:
r0011uu is it working on r0030uu ?
Click to expand...
Click to collapse
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away

still no fix
mrmazak said:
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away
Click to expand...
Click to collapse
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s

KARIM9377 said:
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s
Click to expand...
Click to collapse
dont think there is anything you can do.
Contact "Blu" customer service, maybe they will send you a repair file or let you send it in for repair. The phones have 1 year warrenty

BLU R1 HD won't turn on
KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
Hey guys, my BLU HD has stopped working and it is just stuck whit white screen blu logo, I tried hard reset from recovery mode and unlock bootloader with fastboot but nothing has changed. Can somebody help me, please?

Question Please help recover photos from boot looping Xiaomi Redmi Note 10S

Hi
I have a Xiaomi Redmi Note 10S that randomly rebooted during normal use and then got stuck in a boot loop, it loads the 'powered by android' screen then reboots on a loop to this screen. There was no notification of update or suchlike, however I am aware there has been a recent update sent out, however I don't know if it had been sent to this phone and automatically rebooted itself.
I would be eternally grateful for any advice or guidance in trying to recover photos and data, or at least being able to boot the phone to enable this in the usual manner. I have very limited knowledge of this and have read several posts here and elsewhere over last 24hrs, but would appreciate some clarification of some points below in 'questions'. Phone is 3 months old, Xiaomi can't help. they wipe it on receipt, can't find local phone shop to help.
The phone is stock as new from the factory.
Situation:
-Boot loops as above
-Can access MIUI recovery 5.0 by pressing volume and power buttons, only options are 'reboot' (just loops again), 'wipe' (not an option as need to retrieve photos) and 'connect mi assistant' (can connect by ADB sideloader in this mode)
- Can access fastboot by pressing volume and power button and fastboot devices sees it connected
Main objective:
Retrieve photos and whatsapp messages
Attempted solutions:
-reboot through recovery menu on MIUI recovery 5.0, loops still
- tried to connect to Xiaomi PC suite, phone not seen as connected (is seen through command line ADB/fastboot devices, i think perhaps the phone isn't supported by PC suite)
- I tried a suggested solution of fastboot continue when in fast boot mode, but i get the error FAILED (remote: not support on security), what does this mean?
Questions:
- As I understand it as the bootloader is locked and it is a stock ROM I cannot retrieve the data through ADB/fastboot, is this correct?
- I considered wiping the cache partition in the hope this may fix the bootloop (there is no option to do this in MIUI recovery just a full wipe) so was going to do it through fastboot but I read it deletes the hole partition I.E. not just the data within, is this the case?
Open to suggestions but from what I gather from limited research is my only options would be appear to be :
A: flash a system.img (I do not know how I obtain this or how to load it, nor do I know what version of MIUI / Android the phone was on before this fault)
B: sideload a .zip file having edited the .bat file to remove the overwrite of the user data and remove the wipe command. Will this leave the photos/app data intact? (again i do not know how i identify the right official ROM to download and whether it is recovery or fastboot)
C: load a boot.img, again same challenges as above
Thank you for any advice or help you can offer

shw2021 said:
Hi
I have a Xiaomi Redmi Note 10S that randomly rebooted during normal use and then got stuck in a boot loop, it loads the 'powered by android' screen then reboots on a loop to this screen. There was no notification of update or suchlike, however I am aware there has been a recent update sent out, however I don't know if it had been sent to this phone and automatically rebooted itself.
I would be eternally grateful for any advice or guidance in trying to recover photos and data, or at least being able to boot the phone to enable this in the usual manner. I have very limited knowledge of this and have read several posts here and elsewhere over last 24hrs, but would appreciate some clarification of some points below in 'questions'. Phone is 3 months old, Xiaomi can't help. they wipe it on receipt, can't find local phone shop to help.
The phone is stock as new from the factory.
Situation:
-Boot loops as above
-Can access MIUI recovery 5.0 by pressing volume and power buttons, only options are 'reboot' (just loops again), 'wipe' (not an option as need to retrieve photos) and 'connect mi assistant' (can connect by ADB sideloader in this mode)
- Can access fastboot by pressing volume and power button and fastboot devices sees it connected
Main objective:
Retrieve photos and whatsapp messages
Attempted solutions:
-reboot through recovery menu on MIUI recovery 5.0, loops still
- tried to connect to Xiaomi PC suite, phone not seen as connected (is seen through command line ADB/fastboot devices, i think perhaps the phone isn't supported by PC suite)
- I tried a suggested solution of fastboot continue when in fast boot mode, but i get the error FAILED (remote: not support on security), what does this mean?
Questions:
- As I understand it as the bootloader is locked and it is a stock ROM I cannot retrieve the data through ADB/fastboot, is this correct?
- I considered wiping the cache partition in the hope this may fix the bootloop (there is no option to do this in MIUI recovery just a full wipe) so was going to do it through fastboot but I read it deletes the hole partition I.E. not just the data within, is this the case?
Open to suggestions but from what I gather from limited research is my only options would be appear to be :
A: flash a system.img (I do not know how I obtain this or how to load it, nor do I know what version of MIUI / Android the phone was on before this fault)
B: sideload a .zip file having edited the .bat file to remove the overwrite of the user data and remove the wipe command. Will this leave the photos/app data intact? (again i do not know how i identify the right official ROM to download and whether it is recovery or fastboot)
Thank you for any advice or help you can offer
Click to expand...
Click to collapse
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?

mvikrant97 said:
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?
Click to expand...
Click to collapse
Thank you, no remote backups unfortunately

mvikrant97 said:
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?
Click to expand...
Click to collapse
Flashing phone without user data data partition may also help.

Below added in case anyone can interpret this to ID correct files to download, thank you
(bootloader) max-download-size: 0x8000000
(bootloader) fuse: yes
(bootloader) cpuid: fb3095cc17db56aed6aa8522f88647336c21ce04fddab3339f15
(bootloader) variant:
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: ca00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4244mV
(bootloader) partition-size:sgpt: 8000
(bootloader) partition-type:sgpt: raw data
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 1b13bf8000
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:super: 220000000
(bootloader) partition-type:super: raw data
(bootloader) partition-size:tee_b: 500000
(bootloader) partition-type:tee_b: raw data
(bootloader) partition-size:dtbo_b: 800000
(bootloader) partition-type:dtbo_b: raw data
(bootloader) partition-size:vendor_boot_b: 4000000
(bootloader) partition-type:vendor_boot_b: raw data
(bootloader) partition-size:boot_b: 4000000
(bootloader) partition-type:boot_b: raw data
(bootloader) partition-size:lk_b: 400000
(bootloader) partition-type:lk_b: raw data
(bootloader) partition-size:gz_b: 2000000
(bootloader) partition-type:gz_b: raw data
(bootloader) partition-size:cam_vpu3_b: f00000
(bootloader) partition-type:cam_vpu3_b: raw data
(bootloader) partition-size:cam_vpu2_b: f00000
(bootloader) partition-type:cam_vpu2_b: raw data
(bootloader) partition-size:cam_vpu1_b: f00000
(bootloader) partition-type:cam_vpu1_b: raw data
(bootloader) partition-size:sspm_b: 100000
(bootloader) partition-type:sspm_b: raw data
(bootloader) partition-size:scp_b: 600000
(bootloader) partition-type:scp_b: raw data
(bootloader) partition-size:audio_dsp_b: 400000
(bootloader) partition-type:audio_dsp_b: raw data
(bootloader) partition-size:spmfw_b: 100000
(bootloader) partition-type:spmfw_b: raw data
(bootloader) partition-size:md1img_b: 9600000
(bootloader) partition-type:md1img_b: raw data
(bootloader) partition-size:logo: 880000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot_para: 1a00000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:efuse: 80000
(bootloader) partition-type:efuse: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:tee_a: 500000
(bootloader) partition-type:tee_a: raw data
(bootloader) partition-size:dtbo_a: 800000
(bootloader) partition-type:dtbo_a: raw data
(bootloader) partition-size:vendor_boot_a: 4000000
(bootloader) partition-type:vendor_boot_a: raw data
(bootloader) partition-size:boot_a: 4000000
(bootloader) partition-type:boot_a: raw data
(bootloader) partition-size:lk_a: 400000
(bootloader) partition-type:lk_a: raw data
(bootloader) partition-size:gz_a: 2000000
(bootloader) partition-type:gz_a: raw data
(bootloader) partition-size:cam_vpu3_a: f00000
(bootloader) partition-type:cam_vpu3_a: raw data
(bootloader) partition-size:cam_vpu2_a: f00000
(bootloader) partition-type:cam_vpu2_a: raw data
(bootloader) partition-size:cam_vpu1_a: f00000
(bootloader) partition-type:cam_vpu1_a: raw data
(bootloader) partition-size:sspm_a: 100000
(bootloader) partition-type:sspm_a: raw data
(bootloader) partition-size:scp_a: 600000
(bootloader) partition-type:scp_a: raw data
(bootloader) partition-size:audio_dsp_a: 400000
(bootloader) partition-type:audio_dsp_a: raw data
(bootloader) partition-size:spmfw_a: 100000
(bootloader) partition-type:spmfw_a: raw data
(bootloader) partition-size:md1img_a: 9600000
(bootloader) partition-type:md1img_a: raw data
(bootloader) partition-sizetp: 3000000
(bootloader) partition-typetp: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: 800000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: 800000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-sizeersist: 315e000
(bootloader) partition-typeersist: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:md_udc: 169a000
(bootloader) partition-type:md_udc: raw data
(bootloader) partition-size:vbmeta_vendor_b: 800000
(bootloader) partition-type:vbmeta_vendor_b: raw data
(bootloader) partition-size:vbmeta_system_b: 800000
(bootloader) partition-type:vbmeta_system_b: raw data
(bootloader) partition-size:vbmeta_b: 800000
(bootloader) partition-type:vbmeta_b: raw data
(bootloader) partition-size:vbmeta_vendor_a: 800000
(bootloader) partition-type:vbmeta_vendor_a: raw data
(bootloader) partition-size:vbmeta_system_a: 800000
(bootloader) partition-type:vbmeta_system_a: raw data
(bootloader) partition-size:vbmeta_a: 800000
(bootloader) partition-type:vbmeta_a: raw data
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:rescue: 8000000
(bootloader) partition-type:rescue: raw data
(bootloader) partition-size:blk1: 800000
(bootloader) partition-type:blk1: raw data
(bootloader) partition-size:cust: 40000000
(bootloader) partition-type:cust: raw data
(bootloader) partition-size:ffu: 800000
(bootloader) partition-type:ffu: raw data
(bootloader) partition-size:gsort: 1000000
(bootloader) partition-type:gsort: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:countrycode: 200000
(bootloader) partition-type:countrycode: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-sizegpt: 8000
(bootloader) partition-typegpt: raw data
(bootloader) partition-sizereloader_b: 400000
(bootloader) partition-typereloader_b: raw data
(bootloader) partition-sizereloader_a: 400000
(bootloader) partition-typereloader_a: raw data
(bootloader) partition-sizereloader: 400000
(bootloader) partition-typereloader: raw data
(bootloader) serialno: [redacted by OP if required please advise]
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) tokenversion: 2
(bootloader) crc: 1
(bootloader) kernel: lk
(bootloader) product: rosemary
(bootloader) is-userspace: no
(bootloader) slot-retry-count:b: 1
(bootloader) slot-retry-count:a: 1
(bootloader) slot-unbootable:b: no
(bootloader) slot-unbootable:a: no
(bootloader) slot-successful:b: yes
(bootloader) slot-successful:a: yes
(bootloader) slot-count: 2
(bootloader) current-slot: a
(bootloader) has-slot:sgpt: no
(bootloader) has-slot:flashinfo: no
(bootloader) has-slot:userdata: no
(bootloader) has-slot:super: no
(bootloader) has-slot:logo: no
(bootloader) has-slot:boot_para: no
(bootloader) has-slot:nvram: no
(bootloader) has-slot:efuse: no
(bootloader) has-slotroinfo: no
(bootloader) has-slot:sec1: no
(bootloader) has-slot:tee: yes
(bootloader) has-slot:dtbo: yes
(bootloader) has-slot:vendor_boot: yes
(bootloader) has-slot:boot: yes
(bootloader) has-slot:lk: yes
(bootloader) has-slot:gz: yes
(bootloader) has-slot:cam_vpu3: yes
(bootloader) has-slot:cam_vpu2: yes
(bootloader) has-slot:cam_vpu1: yes
(bootloader) has-slot:sspm: yes
(bootloader) has-slot:scp: yes
(bootloader) has-slot:audio_dsp: yes
(bootloader) has-slot:spmfw: yes
(bootloader) has-slot:md1img: yes
(bootloader) has-slottp: no
(bootloader) has-slot:seccfg: no
(bootloader) has-slotrotect2: no
(bootloader) has-slotrotect1: no
(bootloader) has-slotersist: no
(bootloader) has-slot:metadata: no
(bootloader) has-slot:md_udc: no
(bootloader) has-slot:vbmeta_vendor: yes
(bootloader) has-slot:vbmeta_system: yes
(bootloader) has-slot:vbmeta: yes
(bootloader) has-slot:nvdata: no
(bootloader) has-slot:nvcfg: no
(bootloader) has-slot:frp: no
(bootloader) has-slot:rescue: no
(bootloader) has-slot:blk1: no
(bootloader) has-slot:cust: no
(bootloader) has-slot:ffu: no
(bootloader) has-slot:gsort: no
(bootloader) has-slot:expdb: no
(bootloader) has-slotara: no
(bootloader) has-slot:countrycode: no
(bootloader) has-slot:misc: no
(bootloader) has-slotgpt: no
(bootloader) has-slotreloader: yes
(bootloader) version-baseband: MOLY.LR13.R1.MP.V89.5.P47
(bootloader) version-bootloader: k85v1_64-879e20af-20210531104000-202108
(bootloader) version-preloader:
(bootloader) anti: 1
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.814s

@shw2021
Take note that in the moment you unlock phone's bootloader - what is required to sucessfully run most of the FASTBOOT commands and/or flash a Custom ROM - all user-data automatically get wiped.
Take note that ADB won't work on a bootlooping device because a stable USB-connection isn't given.

Try to get it to boot in safe mode.
Sometimes when boot looping they will go into safe mode automatically after a few cycles... depending on the degree of damage.
If you get into safe mode, don't reboot, grab the data then.
Try clearing system cache.
If you reflash all bets are off... in the future always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Edit, OP got me with the quickness...

blackhawk said:
Try to get it to boot in safe mode.
Sometimes when boot looping they will go into safe mode automatically after a few cycles... depending on the degree of damage.
If you get into safe mode, don't reboot, grab the data then.
Try clearing system cache.
If you reflash all bets are off... in the future always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Edit, OP got me with the quickness...
Click to expand...
Click to collapse
Thank you for quick reply, I don't know how i get it to boot in safe mode, it has been left overnight and continues looping until it beeps and turns off, I can get it to the 'fastboot' screen or the MIUI recovery screen. How can i grab the data? From what I read, as it is locked pulling data from sdcard won't work? Grateful for pointers though. How do I clear system cache please, there is no option for this in MIUI recovery menu? Indeed I am kicking myself, never had a phone do this before, I will definitely take on board the double back up point you made.
jwoegerbauer said:
@shw2021
Take note that in the moment you unlock phone's bootloader - what is required to sucessfully run most of the FASTBOOT commands and/or flash a Custom ROM - all user-data automatically get wiped.
Take note that ADB won't work on a bootlooping device because a stable USB-connection isn't given.
Click to expand...
Click to collapse
Thank you for quick reply, I wasn't intending to unlock the bootloader, again this is only what I have read, that if loading a stock ROM or .img then the bootloader does not need to be unlocked. Is it the case that I cannot boot a boot.img or flash a system.img?
I seem to get a stable ADB connection by booting phone into MIUI recovery menu and selecting 'connect miassistant', i then get ADB sideloader and phone shows on devices

This tutorial covers how to flash the Redmi notes 10S and here are the flash file links.
I would recommend you not to flash the userdata and cache partition to prevent data loss.

shw2021 said:
I seem to get a stable ADB connection by booting phone into MIUI recovery menu and selecting 'connect miassistant', i then get ADB sideloader and phone shows on devices
Click to expand...
Click to collapse
Then try to sideload phone's Stock ROM via ADB Sideload method as offered in recovery menu - but this may overwrite already existing user-data, because the /data partition, where user-data are stored, is part of Stock ROM.

.

Keep trying to boot it up, it may take. Try at at dozen times... play with it.

You can recover data from formated or lost partition via data recovery software .

HeiloWorid said:
You can recover data from formated or lost partition via data recovery software .
Click to expand...
Click to collapse
Without rooting the device it is not possible to recover that data and the partition once overwritten while flashing will wipe all data.

I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.

HeiloWorid said:
I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.
Click to expand...
Click to collapse
Do you have specifics please? Program used, method employed? thank you

jwoegerbauer said:
Then try to sideload phone's Stock ROM via ADB Sideload method as offered in recovery menu - but this may overwrite already existing user-data, because the /data partition, where user-data are stored, is part of Stock ROM.
Click to expand...
Click to collapse
From what I gather from @mvikrant97 and elsewhere, editing the flashall.bat file possibly offers the opportunity to not overwrite the user data.
However MIUI recovery menu doesn't have the option to initiate the load of an ADB sideloaded file, if i sideload the stock ROM will the phone load it upon reboot, or do you need to have an option within the recovery menu on the phone to make it load it? thank you

blackhawk said:
Keep trying to boot it up, it may take. Try at at dozen times... play with it.
Click to expand...
Click to collapse
No luck with this unfortunately, thank you for the suggestion though was definitely worth a shot

HeiloWorid said:
I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.
Click to expand...
Click to collapse
Which software did you used?

I use software from Hiren’s BootCD PE
Hard Disk Tools/Data Recovery:Lazesoft Data Recovery ,Puran Data Recovery ,Puran File Recovery ,Recuva .I've tryed with all of them and they have different percent success more than 90% recovered of all pictures.

[Solved] A7600-F: How to flash TWRP when recovery partition doesn't support flashing

Hey there,
Spoiler: Edits
- I just hit in "fastboot reboot" and the device rebootet. So the fastboot might not be broken.
- used "fastboot flash recovery twrp.img", it returns me "Partition "recovery" not support flash"
- Added a Spoiler with returns of fastboot
- Added the try "fastboot boot twrp.img"
- added the solution
Spoiler: erased because of edits
if I turn my device into the fastboot mode, it seems to stuck while loading. First my steps and the Interface that I can see.
1. Starting the device while holding Vol+ and Power
2. Selecting fastboot
3. See "FASTBOOT mode..."
First Question: Do I get any other interface, when fastboot mode is started? In general there is a different image shown.
My overall aim is to intall twrp (and lineage os). So I installed a driver set for this device and the latest adb-toolset. Starting the fastboot mode, I'll try to turn over some fastboot commands, like "fastboot oem device-status", but there is no response.
If I use "fastboot devices" my device is shown in the list. My (windows 10-)hardware manager doesnt return any devices with driver errors. But, the tab is shown as a device by tp-link.
Could someone help me to get twrp installed?
I've rooted the tablet by kingoroot. (I know about) There are no sensible dates on and I'm ok with unrooting as well as reinstalling all stock-roms before installing lineage. Just wanted to be sure, that the environment is open for all activities to get twrp running.
My question turns into "how to flash twrp, when the recovery doesn't support flashing"?
When I use "fastboot flash recovery twrp.img", it returns me "Partition 'recovery' not support flash"
Thank you for your time and help
Edit:
Spoiler: return of fastboot getvar all
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 10000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 4c800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:flex: 2800000
(bootloader) partition-type:flex: ext4
(bootloader) partition-size:resv: 80000
(bootloader) partition-type:resv: raw data
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect_s: a00000
(bootloader) partition-typerotect_s: ext4
(bootloader) partition-sizerotect_f: a00000
(bootloader) partition-typerotect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizero_info: 300000
(bootloader) partition-typero_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-sizereloader: 1400000
(bootloader) partition-typereloader: raw data
(bootloader) kernel: lk
(bootloader) product: LVP9_ROW_WIFIONLY
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.109s
If I try to temporarly boot from the twrp-image, this is happening:
"fastboot boot twrp.img" (imagine the image is called twrp)
Sending ... ok:
Booting ........ (nothing happens, neither on the tablet, nor the command line)
Edit:
Found a solution. Following this steps will help: https://forum.xda-developers.com/t/...-lenovo-a7600-f-mt6582.3895322/#post-78799763