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"
}

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?

USB run only in fastboot mode

Hi everybody,
I have a problem with my meizu m2 mini.
Charging only when it's off.
Not recognize by the PC except in fastboot mode.
I have download lot of roms but it 's not resolve my problem.
In thr engineering menu, I can active the charge icon when i play with the IF TEST in Hardware USB menu.
I have Android 5.1..1

replicator56 said:
Hi everybody,
I have a problem with my meizu m2 mini.
Charging only when it's off.
Not recognize by the PC except in fastboot mode.
I have download lot of roms but it 's not resolve my problem.
In thr engineering menu, I can active the charge icon when i play with the IF TEST in Hardware USB menu.
I have Android 5.1..1
Click to expand...
Click to collapse
What happens when you activate usb debugging in developer mode?

Hi, thanks to help me.
There is any difference that I activate or desactivate usb debbuging.
Actually, I'm running with CYANOGENMOD 12.1-20170225-UNOFFICICIAL-v0.14-meilan2
kernel: 3.10.65+ [email protected] #1
With the command lsusb on Termux:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002

replicator56 said:
Hi, thanks to help me.
There is any difference that I activate or desactivate usb debbuging.
Actually, I'm running with CYANOGENMOD 12.1-20170225-UNOFFICICIAL-v0.14-meilan2
kernel: 3.10.65+ [email protected] #1
With the command lsusb on Termux:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002
Click to expand...
Click to collapse
Usb debugging in developer mode can able to detect phone easily by pc.Try it.Next time quote me to your comment,otherwise I can't reach you.

adarshm4you said:
Usb debugging in developer mode can able to detect phone easily by pc.Try it.Next time quote me to your comment,otherwise I can't reach you.
Click to expand...
Click to collapse
Hi adarshm4you,
I said that my pc can able to detect phone ONLY by fastboot,
but not by adb (even if I activate USB Debugging in developper mode), it don't charge neither.
I can see briefly my pc detecting phone (name M2) during a normal boot (3 secondes at the starting when the head of my CyanogenMod12 appear((just after meizu logo dosappear)

replicator56 said:
Hi adarshm4you,
I said that my pc can able to detect phone ONLY by fastboot,
but not by adb (even if I activate USB Debugging in developper mode), it don't charge neither.
I can see briefly my pc detecting phone (name M2) during a normal boot (3 secondes at the starting when the head of my CyanogenMod12 appear((just after meizu logo dosappear)
Click to expand...
Click to collapse
Ok.What about connecting to other pc's?

adarshm4you said:
Ok.What about connecting to other pc's?
Click to expand...
Click to collapse
Hi, It 's the same thing when I connect on my desktop.
Actually, I use my laptop under debian and I can recognized an other smartphone.
idem with windows.
PS: Because I played too much with fastboot, I have erase all partitions and I have locked the bootloader. :crying:
fastboot run again! but I can only flash the boot but I the phone reboot all the time.
With the others commands like for example "fastboot flash secro secro.img"(or preloader,recovery....) : I have "failed.....not allowed"
In fact, now I'm brick with fastboot but with commands not allowed.:crying:
I can copied (at the hand ) the result for the command fastboot getvar all, if it's can help you to help me. :highfive:

replicator56 said:
Hi, It 's the same thing when I connect on my desktop.
Actually, I use my laptop under debian and I can recognized an other smartphone.
idem with windows.
PS: Because I played too much with fastboot, I have erase all partitions and I have locked the bootloader. :crying:
fastboot run again! but I can only flash the boot but I the phone reboot all the time.
With the others commands like for example "fastboot flash secro secro.img"(or preloader,recovery....) : I have "failed.....not allowed"
In fact, now I'm brick with fastboot but with commands not allowed.:crying:
I can copied (at the hand ) the result for the command fastboot getvar all, if it's can help you to help me. :highfive:
Click to expand...
Click to collapse
the result of 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: 60000000
(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:custom: 20000000
(bootloader) partition-type:custom: ext4
(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: 3000000
(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: no
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: GINR6735_65C_L1
(bootloader) version: 0.5
all: Done!!

You should try enabled USB debugging and installing its drivers on your PC. Or you might have an update which you haven't installed on your Meizu 2 Mini. Check in Settings > System updates.

Adilharoon said:
You should try enabled USB debugging and installing its drivers on your PC. Or you might have an update which you haven't installed on your Meizu 2 Mini. Check in Settings > System updates.
Click to expand...
Click to collapse
Thanks but I can't boot the Meizu 2 Mini to enabled USB debugging or go on menu.

What do you see first of all?
replicator56 said:
Thanks but I can't boot the Meizu 2 Mini to enabled USB debugging or go on menu.
Click to expand...
Click to collapse
What do you see first of all? Can you perform factory or wipe out data from recovery mode?

Hi, I can't access to recovery mode, only fastboot.

replicator56 said:
Hi, I can't access to recovery mode, only fastboot.
Click to expand...
Click to collapse
Did you tried anything custom or root?

[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

Question Root?

Is there anyone who has any boot.img or knows the correct procedure to root this thing?

kouzelnik3 said:
Is there anyone who has any boot.img or knows the correct procedure to root this thing?
Click to expand...
Click to collapse
I would install Magisk by following the official installation instructions. Let me know if you have any questions after reading through them.

ethical_haquer said:
I would install Magisk by following the official installation instructions. Let me know if you have any questions after reading through them.
Click to expand...
Click to collapse
Yeah, that's what I know, but I don't have that boot img or something, yet.

kouzelnik3 said:
Yeah, that's what I know, but I don't have that boot img or something, yet.
Click to expand...
Click to collapse
If you can dd the right partition from the tablet, you can have the boot image:
From adb shell, launch the comand "lsblk". You will get a list of partition currently on the tablet. The boot partition should be indicated one way or another.
From adb shell, "dd if=/dev/[insert-boot-partition-name] of=/storage/emulated/0/boot.img"
Tranfert the saved boot.img to your computer.

w1nst0n sm1th said:
If you can dd the right partition from the tablet, you can have the boot image:
From adb shell, launch the comand "lsblk". You will get a list of partition currently on the tablet. The boot partition should be indicated one way or another.
From adb shell, "dd if=/dev/[insert-boot-partition-name] of=/storage/emulated/0/boot.img"
Tranfert the saved boot.img to your computer.
Click to expand...
Click to collapse
Well, by this command I cannot see any boot.img partition, only few others, which is weird.
Also according to the "dd" command, it didn't work (screenshots) because of Permission denied.

Error message

kouzelnik3 said:
Well, by this command I cannot see any boot.img partition, only few others, which is weird.
Also according to the "dd" command, it didn't work (screenshots) because of Permission denied.
Click to expand...
Click to collapse
There is an error in your command:
It's "lsblk", not "ls -blk"
See here for a linux version:
lsblk
You may need to set developer options on the device before being able to run such a command :
Develloper Options
And here an explanation of the dd command:
dd
If you're not sure about dd (you should be very cautious with that command), post a picture of the result of the lsblk command and I will tell you the exact command for dd.
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).

w1nst0n sm1th said:
There is an error in your command:
It's "lsblk", not "ls -blk"
See here for a linux version:
lsblk
You may need to set developer options on the device before being able to run such a command :
Develloper Options
And here an explanation of the dd command:
dd
If you're not sure about dd (you should be very cautious with that command), post a picture of the result of the lsblk command and I will tell you the exact command for dd.
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
Click to expand...
Click to collapse
I have set up the Developer options before, but when I use "lsblk" command, it says "/system/bin/sh: lsblk: inaccessible or not found" which is why I used "ls -lbk". Do you know what be an issue here?
I got same results even with my rooted OnePlus 10 Pro.

Well. Apparently, lsblk is not included.
You will have to wait for an update to be available on the telegram channel, unpack the update to extract the boot.img (init_boot.img).
See :
https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-a-10.4571171/

w1nst0n sm1th said:
Well. Apparently, lsblk is not included.
You will have to wait for an update to be available on the telegram channel, unpack the update to extract the boot.img (init_boot.img).
See :
https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-a-10.4571171/
Click to expand...
Click to collapse
I thought that. By the way, which telegram channel has those files?

w1nst0n sm1th said:
...
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
Click to expand...
Click to collapse
Too bad it's not the variant with more RAM & storage. I'm also very intrigued but know very little apart from couple YouTube videos.

While we try to gain root. Can we get instructions on how to unlock the bootloader so I don't have to have my storage wiped again when we do get root

I assume it is basic proces as on any other OP device. OEM unlock, fastboot mode and other fastboot flashing unlock, then yes. Someone can try.

Fastboot oem unlock does not work , Fastboot flashing unlock threw an error but said it was successful but did not wipe data. Manually wipped data and got stuck in a boot loop. Windows will not detect it in recovery mode and I can not get it back into bootloader mode.

XxBigBuckxX said:
Fastboot oem unlock does not work , Fastboot flashing unlock threw an error but said it was successful but did not wipe data. Manually wipped data and got stuck in a boot loop. Windows will not detect it in recovery mode and I can not get it back into bootloader mode.
Click to expand...
Click to collapse
Did you turn on OEM Unlock in developer options? And as you are stuck in bootloop without bootloader mode, I think the only option is service center.

kouzelnik3 said:
Did you turn on OEM Unlock in developer options? And as you are stuck in bootloop without bootloader mode, I think the only option is service center.
Click to expand...
Click to collapse
Yes I turned it on before unlocking bootloader, I paniced after it started to bootloop and relocked the bootloader after manually trying to wipe data which could be why I cant get into bootloader. I reached out to support hoping for a remote fix like the oneplus 10T but nothing. I could only get my pc to detect it in edl mode. I'm mailing it in today they didn't have any troubleshooting steps just going to RMA it.

XxBigBuckxX said:
Yes I turned it on before unlocking bootloader, I paniced after it started to bootloop and relocked the bootloader after manually trying to wipe data which could be why I cant get into bootloader. I reached out to support hoping for a remote fix like the oneplus 10T but nothing. I could only get my pc to detect it in edl mode. I'm mailing it in today they didn't have any troubleshooting steps just going to RMA it.
Click to expand...
Click to collapse
Well, trying to relock it was definitely the wrong move. RMA will solve it anyway.

I got my replacement today and it happened again. The only thing I had done was enable oem unlock. The only commands I ran
Code:
PS C:\Users\nate> adb devices
List of devices attached
49YLUKXKQSMBKB6T device
PS C:\Users\nate> adb reboot bootloader
PS C:\Users\nate> fastboot help
usage: fastboot [OPTION...] COMMAND...
flashing:
update ZIP Flash all partitions from an update.zip package.
flashall Flash all partitions from $ANDROID_PRODUCT_OUT.
On A/B devices, flashed slot is set as active.
Secondary images may be flashed to inactive slot.
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
basics:
devices [-l] List devices in bootloader (-l: with device paths).
getvar NAME Display given bootloader variable.
reboot [bootloader] Reboot device.
locking/unlocking:
flashing lock|unlock Lock/unlock partitions for flashing
flashing lock_critical|unlock_critical
Lock/unlock 'critical' bootloader partitions.
flashing get_unlock_ability
Check whether unlocking is allowed (1) or not(0).
advanced:
erase PARTITION Erase a flash partition.
format[:FS_TYPE[:SIZE]] PARTITION
Format a flash partition.
set_active SLOT Set the active slot.
oem [COMMAND...] Execute OEM-specific command.
gsi wipe|disable Wipe or disable a GSI installation (fastbootd only).
wipe-super [SUPER_EMPTY] Wipe the super partition. This will reset it to
contain an empty set of default dynamic partitions.
create-logical-partition NAME SIZE
Create a logical partition with the given name and
size, in the super partition.
delete-logical-partition NAME
Delete a logical partition with the given name.
resize-logical-partition NAME SIZE
Change the size of the named logical partition.
snapshot-update cancel On devices that support snapshot-based updates, cancel
an in-progress update. This may make the device
unbootable until it is reflashed.
snapshot-update merge On devices that support snapshot-based updates, finish
an in-progress update if it is in the "merging"
phase.
fetch PARTITION OUT_FILE Fetch a partition image from the device.
boot image:
boot KERNEL [RAMDISK [SECOND]]
Download and boot kernel from RAM.
flash:raw PARTITION KERNEL [RAMDISK [SECOND]]
Create boot image and flash it.
--dtb DTB Specify path to DTB for boot image header version 2.
--cmdline CMDLINE Override kernel command line.
--base ADDRESS Set kernel base address (default: 0x10000000).
--kernel-offset Set kernel offset (default: 0x00008000).
--ramdisk-offset Set ramdisk offset (default: 0x01000000).
--tags-offset Set tags offset (default: 0x00000100).
--dtb-offset Set dtb offset (default: 0x01100000).
--page-size BYTES Set flash page size (default: 2048).
--header-version VERSION Set boot image header version.
--os-version MAJOR[.MINOR[.PATCH]]
Set boot image OS version (default: 0.0.0).
--os-patch-level YYYY-MM-DD
Set boot image OS security patch level.
Android Things:
stage IN_FILE Sends given file to stage for the next command.
get_staged OUT_FILE Writes data staged by the last command to a file.
options:
-w Wipe userdata.
-s SERIAL Specify a USB device.
-s tcp|udp:HOST[:PORT] Specify a network device.
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
--force Force a flash operation that may be unsafe.
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-secondary Don't flash secondary slots in flashall/update.
--skip-reboot Don't reboot device after flashing.
--disable-verity Sets disable-verity when flashing vbmeta.
--disable-verification Sets disable-verification when flashing vbmeta.
--fs-options=OPTION[,OPTION]
Enable filesystem features. OPTION supports casefold, projid, compress
--unbuffered Don't buffer input or output.
--verbose, -v Verbose output.
--version Display version.
--help, -h Show this message.
PS C:\Users\nate> fastboot flashing get_unlock_ability
(bootloader) unlock_ability is true
OKAY [ 0.003s]
Finished. Total time: 0.004s
PS C:\Users\nate> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Finished. Total time: 15.144s
PS C:\Users\nate> fastboot getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical:preloader_raw_b:no
(bootloader) is-logical:preloader_raw_a:no
(bootloader) is-logical:pi_img_a:no
(bootloader) is-logical:scp_a:no
(bootloader) is-logical:vcp_a:no
(bootloader) is-logical:dpm_b:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:audio_dsp_a:no
(bootloader) is-logical:efuse:no
(bootloader) is-logical:connsys_wifi_a:no
(bootloader) is-logical:ocdt:no
(bootloader) is-logical:spmfw_b:no
(bootloader) is-logical:logo_b:no
(bootloader) is-logical:logo_a:no
(bootloader) is-logical:splash_odm:no
(bootloader) is-logical:sspm_b:no
(bootloader) is-logical:nvcfg:no
(bootloader) is-logical:connsys_bt_b:no
(bootloader) is-logical:vbmeta_b:no
(bootloader) is-logical:audio_dsp_b:no
(bootloader) is-logical:gpueb_b:no
(bootloader) is-logical:boot_para:no
(bootloader) is-logical:dtbo_b:no
(bootloader) is-logical:proinfo:no
(bootloader) is-logical:mvpu_algo_b:no
(bootloader) is-logical:nvdata:no
(bootloader) is-logical:protect2:no
(bootloader) is-logical:connsys_wifi_b:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:lk_b:no
(bootloader) is-logical:tee_b:no
(bootloader) is-logical:otp:no
(bootloader) is-logical:sdb:no
(bootloader) is-logical:gz_a:no
(bootloader) is-logical:gpueb_a:no
(bootloader) is-logical:dram_para:no
(bootloader) is-logical:cdt_engineering_a:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:mcupm_a:no
(bootloader) is-logical:oplus_custom:no
(bootloader) is-logical:sda:no
(bootloader) is-logical:vcp_b:no
(bootloader) is-logical:init_boot_b:no
(bootloader) is-logical:init_boot_a:no
(bootloader) is-logical:flashinfo:no
(bootloader) is-logical:frp:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical:dtbo_a:no
(bootloader) is-logical:protect1:no
(bootloader) is-logical:sspm_a:no
(bootloader) is-logical:oplusreserve3:no
(bootloader) is-logical:lk_a:no
(bootloader) is-logical:persist:no
(bootloader) is-logical:oplusreserve6:no
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:scp_b:no
(bootloader) is-logical:expdb:no
(bootloader) is-logical:param:no
(bootloader) is-logical:mvpu_algo_a:no
(bootloader) is-logical:pi_img_b:no
(bootloader) is-logical:oplusreserve1:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:dpm_a:no
(bootloader) is-logical:mcupm_b:no
(bootloader) is-logical:ccu_a:no
(bootloader) is-logical:seccfg:no
(bootloader) is-logical:vbmeta_vendor_b:no
(bootloader) is-logical:apusys_b:no
(bootloader) is-logical:para:no
(bootloader) is-logical:gz_b:no
(bootloader) is-logical:nvram:no
(bootloader) is-logical:cdt_engineering_b:no
(bootloader) is-logical:apusys_a:no
(bootloader) is-logical:vbmeta_system_b:no
(bootloader) is-logical:oplusreserve5:no
(bootloader) is-logical:spmfw_a:no
(bootloader) is-logical:ccu_b:no
(bootloader) is-logical:sdc:no
(bootloader) is-logical:tee_a:no
(bootloader) is-logical:connsys_bt_a:no
(bootloader) is-logical:sec1:no
(bootloader) is-logical:oplusreserve2:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:vbmeta_system_a:no
(bootloader) is-logical:super:no
(bootloader) is-logical:vbmeta_a:no
(bootloader) is-logical:vbmeta_vendor_a:no
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logical:product_a:yes
(bootloader) is-logical:product_b:yes
(bootloader) is-logical:my_product_a:yes
(bootloader) is-logical:my_product_b:yes
(bootloader) is-logical:odm_a:yes
(bootloader) is-logical:odm_b:yes
(bootloader) is-logical:my_engineering_a:yes
(bootloader) is-logical:my_engineering_b:yes
(bootloader) is-logical:vendor_dlkm_a:yes
(bootloader) is-logical:vendor_dlkm_b:yes
(bootloader) is-logical:odm_dlkm_a:yes
(bootloader) is-logical:odm_dlkm_b:yes
(bootloader) is-logical:my_stock_a:yes
(bootloader) is-logical:my_stock_b:yes
(bootloader) is-logical:my_heytap_a:yes
(bootloader) is-logical:my_heytap_b:yes
(bootloader) is-logical:my_carrier_a:yes
(bootloader) is-logical:my_carrier_b:yes
(bootloader) is-logical:my_region_a:yes
(bootloader) is-logical:my_region_b:yes
(bootloader) is-logical:my_company_a:yes
(bootloader) is-logical:my_company_b:yes
(bootloader) is-logical:my_preload_a:yes
(bootloader) is-logical:my_preload_b:yes
(bootloader) is-logical:my_bigball_a:yes
(bootloader) is-logical:my_bigball_b:yes
(bootloader) is-logical:my_manifest_a:yes
(bootloader) is-logical:my_manifest_b:yes
(bootloader) battery-voltage:3
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:preloader_raw_b:0x3FF000
(bootloader) partition-size:preloader_raw_a:0x3FF000
(bootloader) partition-size:pi_img_a:0x100000
(bootloader) partition-size:scp_a:0x600000
(bootloader) partition-size:vcp_a:0x600000
(bootloader) partition-size:dpm_b:0x400000
(bootloader) partition-size:misc:0x80000
(bootloader) partition-size:audio_dsp_a:0xC00000
(bootloader) partition-size:efuse:0x80000
(bootloader) partition-size:connsys_wifi_a:0x800000
(bootloader) partition-size:ocdt:0x800000
(bootloader) partition-size:spmfw_b:0x100000
(bootloader) partition-size:logo_b:0x2000000
(bootloader) partition-size:logo_a:0x2000000
(bootloader) partition-size:splash_odm:0x2580000
(bootloader) partition-size:sspm_b:0x100000
(bootloader) partition-size:nvcfg:0x2000000
(bootloader) partition-size:connsys_bt_b:0x800000
(bootloader) partition-size:vbmeta_b:0x800000
(bootloader) partition-size:audio_dsp_b:0xC00000
(bootloader) partition-size:gpueb_b:0x100000
(bootloader) partition-size:boot_para:0x100000
(bootloader) partition-size:dtbo_b:0x800000
(bootloader) partition-size:proinfo:0x300000
(bootloader) partition-size:mvpu_algo_b:0x4000000
(bootloader) partition-size:nvdata:0x4000000
(bootloader) partition-size:protect2:0x800000
(bootloader) partition-size:connsys_wifi_b:0x800000
(bootloader) partition-size:userdata:0x19DB7F8000
(bootloader) partition-size:lk_b:0x500000
(bootloader) partition-size:tee_b:0x500000
(bootloader) partition-size:otp:0x2B00000
(bootloader) partition-size:gz_a:0x2000000
(bootloader) partition-size:gpueb_a:0x100000
(bootloader) partition-size:dram_para:0x1900000
(bootloader) partition-size:cdt_engineering_a:0xC80000
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-size:mcupm_a:0x100000
(bootloader) partition-size:oplus_custom:0x100000
(bootloader) partition-size:vcp_b:0x600000
(bootloader) partition-size:init_boot_b:0x800000
(bootloader) partition-size:init_boot_a:0x800000
(bootloader) partition-size:flashinfo:0x1000000
(bootloader) partition-size:frp:0x100000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size:dtbo_a:0x800000
(bootloader) partition-size:protect1:0x800000
(bootloader) partition-size:sspm_a:0x100000
(bootloader) partition-size:oplusreserve3:0x4000000
(bootloader) partition-size:lk_a:0x500000
(bootloader) partition-size:oplusreserve6:0x4000000
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-size:scp_b:0x600000
(bootloader) partition-size:expdb:0x8000000
(bootloader) partition-size:param:0x100000
(bootloader) partition-size:mvpu_algo_a:0x4000000
(bootloader) partition-size:pi_img_b:0x100000
(bootloader) partition-size:oplusreserve1:0x800000
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:dpm_a:0x400000
(bootloader) partition-size:mcupm_b:0x100000
(bootloader) partition-size:ccu_a:0x400000
(bootloader) partition-size:seccfg:0x800000
(bootloader) partition-size:vbmeta_vendor_b:0x800000
(bootloader) partition-size:apusys_b:0x400000
(bootloader) partition-size:para:0x80000
(bootloader) partition-size:gz_b:0x2000000
(bootloader) partition-size:nvram:0x4000000
(bootloader) partition-size:cdt_engineering_b:0xC80000
(bootloader) partition-size:apusys_a:0x400000
(bootloader) partition-size:vbmeta_system_b:0x800000
(bootloader) partition-size:oplusreserve5:0x2000000
(bootloader) partition-size:spmfw_a:0x100000
(bootloader) partition-size:ccu_b:0x400000
(bootloader) partition-size:tee_a:0x500000
(bootloader) partition-size:connsys_bt_a:0x800000
(bootloader) partition-size:sec1:0x200000
(bootloader) partition-size:metadata:0x2000000
(bootloader) partition-size:vbmeta_system_a:0x800000
(bootloader) partition-size:vbmeta_a:0x800000
(bootloader) partition-size:vbmeta_vendor_a:0x800000
(bootloader) partition-size:system_a:0x2E961000
(bootloader) partition-size:system_b:0x0
(bootloader) partition-size:system_ext_a:0x3D2E6000
(bootloader) partition-size:system_ext_b:0x0
(bootloader) partition-size:vendor_a:0x421DF000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-size:product_a:0x1CA000
(bootloader) partition-size:product_b:0x0
(bootloader) partition-size:my_product_a:0x13813000
(bootloader) partition-size:my_product_b:0x0
(bootloader) partition-size:odm_a:0x46C6C000
(bootloader) partition-size:odm_b:0x0
(bootloader) partition-size:my_engineering_a:0x52000
(bootloader) partition-size:my_engineering_b:0x0
(bootloader) partition-size:vendor_dlkm_a:0x3589000
(bootloader) partition-size:vendor_dlkm_b:0x0
(bootloader) partition-size:odm_dlkm_a:0x55000
(bootloader) partition-size:odm_dlkm_b:0x0
(bootloader) partition-size:my_stock_a:0x1EAA9000
(bootloader) partition-size:my_stock_b:0x0
(bootloader) partition-size:my_heytap_a:0x2CAE2000
(bootloader) partition-size:my_heytap_b:0x0
(bootloader) partition-size:my_carrier_a:0x52000
(bootloader) partition-size:my_carrier_b:0x0
(bootloader) partition-size:my_region_a:0x376000
(bootloader) partition-size:my_region_b:0x0
(bootloader) partition-size:my_company_a:0x52000
(bootloader) partition-size:my_company_b:0x0
(bootloader) partition-size:my_preload_a:0x253000
(bootloader) partition-size:my_preload_b:0x0
(bootloader) partition-size:my_bigball_a:0x2BF47000
(bootloader) partition-size:my_bigball_b:0x0
(bootloader) partition-size:my_manifest_a:0x58000
(bootloader) partition-size:my_manifest_b:0x0
(bootloader) version-vndk:31
(bootloader) has-slot:preloader_raw:yes
(bootloader) has-slot:pi_img:yes
(bootloader) has-slot:scp:yes
(bootloader) has-slot:vcp:yes
(bootloader) has-slot:dpm:yes
(bootloader) has-slot:misc:no
(bootloader) has-slot:audio_dsp:yes
(bootloader) has-slot:efuse:no
(bootloader) has-slot:connsys_wifi:yes
(bootloader) has-slot:ocdt:no
(bootloader) has-slot:spmfw:yes
(bootloader) has-slot:logo:yes
(bootloader) has-slot:splash_odm:no
(bootloader) has-slot:sspm:yes
(bootloader) has-slot:nvcfg:no
(bootloader) has-slot:connsys_bt:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:gpueb:yes
(bootloader) has-slot:boot_para:no
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:proinfo:no
(bootloader) has-slot:mvpu_algo:yes
(bootloader) has-slot:nvdata:no
(bootloader) has-slot:protect2:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:lk:yes
(bootloader) has-slot:tee:yes
(bootloader) has-slot:otp:no
(bootloader) has-slot:sdb:no
(bootloader) has-slot:gz:yes
(bootloader) has-slot:dram_para:no
(bootloader) has-slot:cdt_engineering:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:mcupm:yes
(bootloader) has-slot:oplus_custom:no
(bootloader) has-slot:sda:no
(bootloader) has-slot:init_boot:yes
(bootloader) has-slot:flashinfo:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot:protect1:no
(bootloader) has-slot:oplusreserve3:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:oplusreserve6:no
(bootloader) has-slot:expdb:no
(bootloader) has-slot:param:no
(bootloader) has-slot:oplusreserve1:no
(bootloader) has-slot:ccu:yes
(bootloader) has-slot:seccfg:no
(bootloader) has-slot:vbmeta_vendor:yes
(bootloader) has-slot:apusys:yes
(bootloader) has-slot:para:no
(bootloader) has-slot:nvram:no
(bootloader) has-slot:vbmeta_system:yes
(bootloader) has-slot:oplusreserve5:no
(bootloader) has-slot:sdc:no
(bootloader) has-slot:sec1:no
(bootloader) has-slot:oplusreserve2:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:product:yes
(bootloader) has-slot:my_product:yes
(bootloader) has-slot:odm:yes
(bootloader) has-slot:my_engineering:yes
(bootloader) has-slot:vendor_dlkm:yes
(bootloader) has-slot:odm_dlkm:yes
(bootloader) has-slot:my_stock:yes
(bootloader) has-slot:my_heytap:yes
(bootloader) has-slot:my_carrier:yes
(bootloader) has-slot:my_region:yes
(bootloader) has-slot:my_company:yes
(bootloader) has-slot:my_preload:yes
(bootloader) has-slot:my_bigball:yes
(bootloader) has-slot:my_manifest:yes
(bootloader) security-patch-level:2023-03-05
(bootloader) vendor-fingerprint:oplus/ossi/ossi:12/SP1A.210812.016/1679153745760:user/release-keys
(bootloader) hw-revision:0
(bootloader) current-slot:a
(bootloader) serialno:49YLUKXKQSMBKB6T
(bootloader) product:ossi
(bootloader) version-os:12
(bootloader) first-api-level:31
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:oplus/ossi/ossi:12/SP1A.210812.016/1679153745760:user/release-keys
(bootloader) version-bootloader:unknown
(bootloader) unlocked:no
all:
Finished. Total time: 1.938s
PS C:\Users\nate> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001s
Ater that reboot just right back into the bootloop

Right after that? You basically just rebooted to bootloader, fastboot and then back to the system, but instead of booting, bootloop again? That's even more weird.

kouzelnik3 said:
Right after that? You basically just rebooted to bootloader, fastboot and then back to the system, but instead of booting, bootloop again? That's even more weird.
Click to expand...
Click to collapse
Yeah , I am pretty confused. Service center is not able to help me again yet (Only provide refund which is not what I want) because the previous service request is still open stuck on the device inspection stage. I am just trying to figure out stuff on my own at the moment untill that gets resolved.
I was able to figure a few more things out but not familiar with MTK as I am edl but I went down that path. I was able to get into preloader mode and also downloader mode. I switched over to linux and used mtkclient and it was detecing the device but giving watchdog errors.