Develop Bugs

[Q] No Recovery Mode at All?

I've skimmed through other's issues here, and I don't see anything like my exact issue.
This is an SM-T210R WiFi only
At one time I had a custom ROM and Recovery - all worked fine. But I ran into the problem where I let the battery drain to the point where it wouldn't charge anymore (not sure if this has anything to do with anything - just being thorough). I simply haven't used the tablet in a while.
I trickle charged and I'm passed that problem.
I can charge and power up the tablet, and I can get into the Odin Mode to flash the tablet - but I can't get into recovery, nor can I boot up. No logo, nothing. Just a black (backlit) screen.
I've flashed the stock ROM/Recovery from January 2014, and tried flashing stock ROM/Recovery from September 2014. Still no joy - I can power up to a black screen, or I can go into Odin Mode. No Recovery, No Boot.
I'm stuck - I've done all I can think of, and spent about six hours flashing different Recoveries, Roms, and stock Firmware. I'm out of ideas and open to suggestions.

Lonely Raven said:
I've skimmed through other's issues here, and I don't see anything like my exact issue.
This is an SM-T210R WiFi only
At one time I had a custom ROM and Recovery - all worked fine. But I ran into the problem where I let the battery drain to the point where it wouldn't charge anymore (not sure if this has anything to do with anything - just being thorough). I simply haven't used the tablet in a while.
I trickle charged and I'm passed that problem.
I can charge and power up the tablet, and I can get into the Odin Mode to flash the tablet - but I can't get into recovery, nor can I boot up. No logo, nothing. Just a black (backlit) screen.
I've flashed the stock ROM/Recovery from January 2014, and tried flashing stock ROM/Recovery from September 2014. Still no joy - I can power up to a black screen, or I can go into Odin Mode. No Recovery, No Boot.
I'm stuck - I've done all I can think of, and spent about six hours flashing different Recoveries, Roms, and stock Firmware. I'm out of ideas and open to suggestions.
Click to expand...
Click to collapse
Strange! Did you tried installing latest firmware? Make a video of device being flashed and upload it to some place so we can see
Try flashing the same firmware twice and if it dont reply, we will find a solution, don't worry
Sent from my SM-T211 using XDA Free mobile app

sscsps said:
Strange! Did you tried installing latest firmware? Make a video of device being flashed and upload it to some place so we can see
Try flashing the same firmware twice and if it dont reply, we will find a solution, don't worry
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
So I happened to be out of town at a tech conference, and there were a couple other guys there with the same tablet and several roms - together we tried the latest firmware, and some of their roms. We wound up stuck in exactly the same position. It looks like the ROM/Firmware/Recovery loads just fine, but then when we power cycle the device, we have no boot, no recovery mode, and only the download mode is available.
I could try to do a video, but after having every other very well experienced Android guys look at it, we're all baffled - the Odin software shows the firmware loaded fine, it says PASS, but then nothing. . The only thing we can figure is something is corrupted. Maybe my partitions are gone? (I have no idea what the symptoms of that would be). Maybe the onboard memory is corrupted? I'm just out of ideas. Without the Recovery mode, I'm flat out stuck.

LR,
try packing your intended boot.img and recovery.img individually for odin flash,
first odin flash recovery , i would suggest twrp for the wipe data function.
while cwm seems to have the same function, i have had better success with twrp on that point.
if recovery takes go directly to adb, do not pass go, do not collect $200 :silly:
in adb push boot.img to sdcard and switch to adb shell #
then cat /proc/partition , mount, and maybe run parted just to see output from print all
if everything looks square then dd write your boot.img.
then power off and plug in charger and see if battery screen shows up.
if good then choose a know reliable recovery flashable rom.zip or swap to your preferred recovery.zip
for rom backup-restoration.
m
in black screen boot you should connect to see if adb is doable.

moonbutt74 said:
LR,
try packing your intended boot.img and recovery.img individually for odin flash,
first odin flash recovery , i would suggest twrp for the wipe data function.
while cwm seems to have the same function, i have had better success with twrp on that point.
if recovery takes go directly to adb, do not pass go, do not collect $200 :silly:
in adb push boot.img to sdcard and switch to adb shell #
then cat /proc/partition , mount, and maybe run parted just to see output from print all
if everything looks square then dd write your boot.img.
then power off and plug in charger and see if battery screen shows up.
if good then choose a know reliable recovery flashable rom.zip or swap to your preferred recovery.zip
for rom backup-restoration.
m
in black screen boot you should connect to see if adb is doable.
Click to expand...
Click to collapse
Moon, you lost me a little bit. I think I've done what you suggested.
I have tried to load several recovery img using odin, and none of them work. If I could get any recovery to work at all, then I think I'd be fine figuring it out for myself from there. Both flashing both stock Firmware, or TWRP or CWM leaves me right back where I'm at - no battery icon, no recovery mode, no boot. Just the Download option. I even tried various version of Odin to see if maybe an older version would work - no joy.
What is ADB? that's where you lost me. Reading what I just wrote here, I think I'm understanding most of what you're suggesting, I just want to make sure I'm not missing anything that might get me out of this. It's really like the device simply won't run any Recovery at all. I'll grab all my files and do a couple screen shots and post here. Maybe you can suggest specific versions/files for me to try?
Thanks again for everyone's suggestions! Hopefully I get this going...I hate to just toss it out. I really can't afford a replacement.

ahh, okay no worries.
adb is android debug bridge, search xda for setting up adb for windows.
as you're running odin it means you already have samsung usb drivers installed so you can skip that step.
basically the idea is that with adb you can run shell commands directly on your device from your pc when
connected via usb cable. NOTE-the tab 3 7 t210 DOES require usage of the cable it came with.
the explanation is a little hairy just trust me on this. i'm the poor-man's goto guy with my friends and family for
this kind of stuff.
now, once you have adb established on your pc, [if you have access to a linux machine life will be a lot easier]
power on your tab normally which in your case is black screen, connect to pc using the aforementioned cable
give things a second or two then run adb as per the proper instructions which you must find.
your first command concerning will be
adb devices
if the return/output shows no device number and tag listed then disconnect and switch to odin mode.
for this test you will only be odin-flashing a boot.img for your device sm-t210[r].
if you require assistance in obtaining that image or after researching how to package that image for odin, then let me know.
Do Not use kies.... at all.... at least not for now.
m

moonbutt74 said:
ahh, okay no worries.
adb is android debug bridge, search xda for setting up adb for windows.
as you're running odin it means you already have samsung usb drivers installed so you can skip that step.
basically the idea is that with adb you can run shell commands directly on your device from your pc when
connected via usb cable. NOTE-the tab 3 7 t210 DOES require usage of the cable it came with.
the explanation is a little hairy just trust me on this. i'm the poor-man's goto guy with my friends and family for
this kind of stuff.
now, once you have adb established on your pc, [if you have access to a linux machine life will be a lot easier]
power on your tab normally which in your case is black screen, connect to pc using the aforementioned cable
give things a second or two then run adb as per the proper instructions which you must find.
your first command concerning will be
adb devices
if the return/output shows no device number and tag listed then disconnect and switch to odin mode.
for this test you will only be odin-flashing a boot.img for your device sm-t210[r].
if you require assistance in obtaining that image or after researching how to package that image for odin, then let me know.
Do Not use kies.... at all.... at least not for now.
m
Click to expand...
Click to collapse
OK, I've read a few ADB articles, and I just can't get ADB to see the T210R. Only Odin can see the device, and only when it's in download mode (obviously).
I can send an MD5 or a full Firmware to the devices, but nothing happens, still black screen.
Any further suggestions?

Lonely Raven said:
OK, I've read a few ADB articles, and I just can't get ADB to see the T210R. Only Odin can see the device, and only when it's in download mode (obviously).
I can send an MD5 or a full Firmware to the devices, but nothing happens, still black screen.
Any further suggestions?
Click to expand...
Click to collapse
okay , stick to a holding pattern for now. i have to do some research which you can also help with.
what we need to find out is how to create an odin-flashable image that can be written to mmcblk0.
at the moment my t210r is out of reach as it is 1:34 am and rummaging through the house for it will wake
everyone. search out xda for the above information, i will do the same.
m

Thanks Moon, I need to be up for work in 5 hours, so I'll give it a short search, and I need to crash.

Lonely Raven said:
Thanks Moon, I need to be up for work in 5 hours, so I'll give it a short search, and I need to crash.
Click to expand...
Click to collapse
Verdict, you have corrupted/overwritten your bootloader and parameter block - most likely....maybe...
Bummer - what versions of unbrick approach via external sdcard require adb functionality.
So- you would be better served to shell out the bucks for a qualified service to repair it.
If not an option- you are pretty much boned so trying the following is a maybe win maybe not situation.
in the a.m. i will pull data from mmcblk0 on my tab from the beginning up to param if my setup is what i think it is.
i'll pack it for odin flashing and post it. at which point you can choose for yourself wether or not you want to try it.
if yes you will flash it in the normal odin way, make sure repartition is NOT checked.
you will boot to odin-mode connect your device, wait for it to pick-up, select pda, navigate to the image, select it and flash.
if successful you wil have boot splash back, meaning you partition table should be reading correctly.
you will then reboot you device to odin-mode and reconnect to perform your recovery flash at which point again if successful
you wil either restore rom back-up or flash a rom.zip and swear to never use odin again. [don't do it !!! :crying: ]
anyway i will have the image posted tomorrow.
m

moonbutt74 said:
Verdict, you have corrupted/overwritten your bootloader and parameter block - most likely....maybe...
Bummer - what versions of unbrick approach via external sdcard require adb functionality.
So- you would be better served to shell out the bucks for a qualified service to repair it.
If not an option- you are pretty much boned so trying the following is a maybe win maybe not situation.
in the a.m. i will pull data from mmcblk0 on my tab from the beginning up to param if my setup is what i think it is.
i'll pack it for odin flashing and post it. at which point you can choose for yourself wether or not you want to try it.
if yes you will flash it in the normal odin way, make sure repartition is NOT checked.
you will boot to odin-mode connect your device, wait for it to pick-up, select pda, navigate to the image, select it and flash.
if successful you wil have boot splash back, meaning you partition table should be reading correctly.
you will then reboot you device to odin-mode and reconnect to perform your recovery flash at which point again if successful
you wil either restore rom back-up or flash a rom.zip and swear to never use odin again. [don't do it !!! :crying: ]
anyway i will have the image posted tomorrow.
m
Click to expand...
Click to collapse
I understand - thanks for the last ditch effort - I look forward to giving it a try.

Lonely Raven said:
I understand - thanks for the last ditch effort - I look forward to giving it a try.
Click to expand...
Click to collapse
okay , as a matter of course, i ask one more time for you to consider a repair service.
being said, try this first - see attachment.
extract .zip and you will have the following named file smt210r_mmcblk0.tar . this is the file you will flash
it may work, it may not.
i used the following command on my sm-t210r to pull from mmcblk0
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=1024 count=32245
i used the following command to pack it for odin
Code:
tar -H ustar -c mmcblk0.img > mmcblk0.img.tar
md5sum -t mmcblk0.img.tar >> mmcblk0.img.tar
so if it works it will write the following to the following
Code:
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"]1 4194kB 5243kB 1049kB MRD
2 5243kB 6291kB 1049kB MRD_BK
3 6291kB 10.5MB 4194kB BOTA0
4 10.5MB 14.7MB 4194kB SBL2
5 14.7MB 18.9MB 4194kB SBL
6 18.9MB 31.5MB 12.6MB ext4 EFS[/COLOR]
if this fails you will either be in no better shape than before or you will be completely bricked.
again, consider other options. if this does/doesn't work please let me know.
m

moonbutt74 said:
okay , as a matter of course, i ask one more time for you to consider a repair service.
being said, try this first - see attachment.
extract .zip and you will have the following named file smt210r_mmcblk0.tar . this is the file you will flash
it may work, it may not.
i used the following command on my sm-t210r to pull from mmcblk0
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=1024 count=32245
i used the following command to pack it for odin
Code:
tar -H ustar -c mmcblk0.img > mmcblk0.img.tar
md5sum -t mmcblk0.img.tar >> mmcblk0.img.tar
so if it works it will write the following to the following
Code:
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"]1 4194kB 5243kB 1049kB MRD
2 5243kB 6291kB 1049kB MRD_BK
3 6291kB 10.5MB 4194kB BOTA0
4 10.5MB 14.7MB 4194kB SBL2
5 14.7MB 18.9MB 4194kB SBL
6 18.9MB 31.5MB 12.6MB ext4 EFS[/COLOR]
if this fails you will either be in no better shape than before or you will be completely bricked.
again, consider other options. if this does/doesn't work please let me know.
m
Click to expand...
Click to collapse
Does all this look right? It's been sitting here like this for 10 minutes with no change - I think that means it's a no-go.
Assuming I'm doing this right, and it's not working...any recommendations on who I can send this to in order to get unbricked?
Again, thanks for your help!
{
"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"
}

Lonely Raven said:
Does all this look right? It's been sitting here like this for 10 minutes with no change - I think that means it's a no-go.
Assuming I'm doing this right, and it's not working...any recommendations on who I can send this to in order to get unbricked?
Again, thanks for your help!
Click to expand...
Click to collapse
hmm, yeah it looks like it's just hanging. are you using the correct version of odin ?

I don't know, what is the correct version? This is just 3.07 I downloaded from one of the articles. I also tried what I *think* is the stock cable. I can run it again with some other cables, just to be sure.

Lonely Raven said:
I don't know, what is the correct version? This is just 3.07 I downloaded from one of the articles. I also tried what I *think* is the stock cable. I can run it again with some other cables, just to be sure.
Click to expand...
Click to collapse
okay,
try this version , same as 307 just something odd about your screen shot http://d-h.st/4VU
i have another approach but i have to find the thread on how to stitch it together again.
look for a service in your area, i don't use any as i fix my own stuff.
you do need the cable that came whith your tab.
m
@Lonely Raven okay heres is my second approach - see attached, unzip as before then flash

[FIX] Blank Screen On Boot (format sys_boot)

BLACK SCREEN ON BOOT ISSUE FIX​
First of all Big thanks to my dear friend Ano11 for the bootloader image ​
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
UPDATE
You guys have asked me for the Backup procedure and i promissed to repost it but I did not have time to post so i'm very very sorry for being late!!
How to back up the bootloader partition
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard

xWaLeEdOoOx said:
Hello guys!
since we all do mistakes, i alongside alot of people have formatted /sys_boot partition on our dear RM-980.
that partition is actually the bootloader and without it the phone bricks.
the signs of that brick is black and no screen lights but a vibration that indecates "PLEASE HELP ME!!"
connecting it to windows will cause seeing a drive that windows can't detect and it will ask to format it which is the worst IDEA EVER!! and fastboot will never detect the phone.
if plugged in to Linux you'll get full control over all phone partitions including internal SD, system, boot, bootloader etc.
its easy to flash images from linux side using gparted or "disks in ubuntu which i use" but also fastboot can't be used.
all we need is an mmcblk0p3 dump to save all dead NOKIA X lives!!
it can be easily done on ADB on any computer if you are willing to help follow the following easy steps:
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
now compress that in a zip and donate it here with your phone CODE (you can find it in the back of your phone)
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
How to flash mmcblk0p3.img on linux pro? Thanks.

nguyentuyen said:
How to flash mmcblk0p3.img on linux pro? Thanks.
Click to expand...
Click to collapse
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.

xWaLeEdOoOx said:
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.
Click to expand...
Click to collapse
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks

nguyentuyen said:
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks
Click to expand...
Click to collapse
i'm still not sure about NOKIA X+ for where the bootloader is located in the mmc but thank you

xWaLeEdOoOx said:
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
I uploaded my boot partition in this thread: http://forum.xda-developers.com/showthread.php?t=2784522&page=2

GUYS ITS NOW FIXED and i've updated the TOPIC for the instructions!!! GOOD LUCK

my nokia x is no vibrate no boot no logo no blank screen no charging now is it porsib
xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX​
First of all Big thanks to my dear friend Ano11 for the bootloader image ​
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
Click to expand...
Click to collapse
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair

javidalana said:
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair
Click to expand...
Click to collapse
what did you do 1st of all?? and you need to charge your phone, keep it in charger "not pc" over night and then check if it vibrates

Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......

Kunal111 said:
Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......
Click to expand...
Click to collapse
In case you do not see any partitions, In that case you have not only formatted ("emptied") this partition but removed all partitions, I assume. So you have to make a new partition (or even all partitions) prior to restoring the mmcblk0p3.img disk image. I have no experience with doing this on a phone (don't know how critical the location and order of partitions is), but I guess a partition listing of a working Nokia X will help you further. Later today when I am at home I hope I can post the partition listing for you.

Help me
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .

Kunal111 said:
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .
Click to expand...
Click to collapse
It might help if you describe exactly what you are doing...
Is your device recognized as Qualcomm something at all?
In order to get it recognized on my Windows computer as Qualcomm device, I have to boot into bootloader mode, i.e.:
BootLoader Mode:
1. Turn off your device
2. Remove wires and battery
3. Hold on Volume + Key while you connect USB
4. Device should be detected as Qualcomm CDMA Technologies MSM
(copied from http://forum.xda-developers.com/showthread.php?t=2667572
So a different procedure as what the OP mentioned.
You so might try that on Ubuntu as well...

5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced

Kunal111 said:
5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced
Click to expand...
Click to collapse
Second attempt: Is your device recognized as a Qualcomm device? Do you see it in the device list on the left?

help
Yes , but how can i flast that img file on 52mb partion

Kunal111 said:
Yes , but how can i flast that img file on 52mb partion
Click to expand...
Click to collapse
And do you see the 52 MB partition on the right? What happens if you select it and rightclick on it, do you see the option "Restore partition from image" or something similar?
It helps if you post in detail what your problem is, otherwise we end up in many question-answer posts... Like we are doing now...

xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX​
First of all Big thanks to my dear friend Ano11 for the bootloader image ​
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Click to expand...
Click to collapse
Hi there,
First of all: thanks for the acknowledgements
This morning my son came to me complaining that his Nokia X was not working anymore.
I checked it and: no recovery mode, no bootloader access. Black screen, no Nokia logo, no vibration (!).
I thought: would I need this thread and my own bootloader image now?? That would be a coincidence!
Connecting the phone to the pc using USB still resulted in "Qualcomm device detected", but nothing more.
Then I noticed that the battery felt a bit loose inside the phone, also I noticed a crack in the plastic cover of the phone.
A closer look to the battery connector of the phone showed that two of them were really bent!
So I opened the casing to have a better access to the connector (really very easy using a torx T5 screw driver), nowhere these terrible plastic clips to break off when you open the device like in other phone brands...
Using my reading glasses and a magnifying glass I bent the clips back -> the phone was revived.
I guess my son must have dropped the phone real hard which resulted in bending these clips...
So people, the take home message is: also check the battery connectors closely when you experience similar problems.

Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.

vishalbiswas said:
Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.
Click to expand...
Click to collapse
Take a look at the second post, you can find the procedure in the quotes from the orginal posting of the OP (the OP removed it later from his post).
 @op / @ xWaLeEdOoOx : maybe good to add this the procedure to your post again.
You may need to check if the partition name is the same for the XL version, e.g. by looking at the TWRP log files.

Made a Huge Mistake: Formated and Cannot Restart the Phone! Help!!

I didn't know when I was formating my phone in CWS recovery mode. But when I tried to restart the phone, is showed me blank screen and even there is no vibration of starting.
I am really mad at this, how to get back to start my phone?

if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/

pyumredkar said:
if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/
Click to expand...
Click to collapse
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.

Love Psyche said:
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.
Click to expand...
Click to collapse
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617

pyumredkar said:
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
Click to expand...
Click to collapse
Is it worked for when there is NO vibration along with blank screen?
And if so, please upload bootloader for RM-1053 model (X+).

I would suggest you that you must flash nokia x bootloader partition for right now until ur device starts. because when you flash nokia x+ rom with care suite your appropriate bootloader img will be flashed correctly from nokia care suite

In the guide you provided:http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617, at 4th point of "How to fix", it said your phone should be vibrated.
But my phone cannot vibrate. Have you got my point? It has NO VIBRATION, not just only blank screen.

it is the last option for repairing ur device, anotherly it seems hardbricked and Microsoft stopped developing repairing spare parts of the device. so no any other hope.

Do you mean, I have no solution for this issue?

maybe

I still have hope and waiting for help about the issue.

I thought I would have a solution, but nobody showed me a solution. Maybe there is no solution!

At first check, if battery is properly inserted (maybe some pins are bent?), then recharge battery.
Next try again with this tutorial: http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
You can download latest Nokia X bootloader from http://cellomania.com/ffu/ (type your CODE from sticker inside device and download RM980_1.2.4.1_boot.img file)
If it won't work, run terminal (in Ubuntu), connect phone again, wait some seconds, type
Code:
dmesg >> ~/dmesg.log
and send dmesg.log file (use file manager to find it) to any pastebin-like service, so we'll be able to check, if Ubuntu can detect the phone.

Super-SD -->> HTC 526 VZW <<-- Boot + Run Android on SD-Card {Pre-Rooted}

Super-SD The bootable Android SD-Card
This is a SD card that has been created using the Dragonboard 410 Boot Tools. LINK IS FOR REFERENCE TO THE TOOLS AND METHOD USED
https://git.linaro.org/landing-team...mmit/ecdf098b42ed9e561b8249bcbf6f883e8151a3bc
Very easy to make and use this sd card. Even for beginners. !! :fingers-crossed:​
Benifits
Boots the android system completely from the sd card.
Both the Userdata and System are run on the card allowing the storage size to be increased both for system and userdata.
Runs a rooted system without Unlocking the Bootloader or making any modifications to the internal phone memory.
Changes you make will be applied to the SD - Card so by removing the SD Card and rebooting the phone will be in the original condition.
WILL NOT VOID YOUR WARRANTY !!!!!!!!!! :highfive: :good: :silly:
No Chance of Bricking the device.
The sd card can be mounted and changes applied to it using linux.
This removes any restrictions that would be present when attempting the same changes to the devices internal memory.
You can use this as a daily runner as well as using this to test anything.
Including Porting of roms.
The best thing is if anything ever went wrong during a test the phone will be undamaged.
Simply removing the sd card puts you back to factory state.
I could go on and on and on because there are so many benefits and uses for this.
KEY Features.
PRE-Rooted : When booting from the sd-card Super SU is already installed so Root is available.
Download Mode : Boots into Download Mode with Full S-OFF and Unlocked Status <-- ONLY WITH BOOT FROM the SD-Card.
Write-Protections :With the s-off Status SD-Card you can mount /system RW and flash partitions like FRP and MISC. Note that some partitions are Still Write Protected ( PG1FS) (Board_Info) (SEC).
FTM Mode : By holding volume up and the power key to boot the device will boot to FTM mode. If you can mount the last partition of the sd card as /mnt/media/ext_sd you should be able to use the device info tool to gain S-off and Boot Loader Unlock.
**********************************************************************************************************************************************************************************
NOTE -->> You can not unlock the boot-loader using this Card.​UNLOCKING THE BOOT LOADER IS AN OPTION NOT A REQUIREMENT, CARD WORKS WITH A LOCKED BOOT LOADERTo Unlock Boot Loader See Here -->> https://forum.xda-developers.com/desire-526/general/verizon-htc-desire-526-boot-loader-root-t3587118​**********************************************************************************************************************************************************************************
BOOT TWRP RECOVERY FROM SD-CARD WITH FisH ( Bootloader - Locked - is OK )
https://forum.xda-developers.com/an...locked-fish-hack-to-boot-want-device-t3578373
Say thanks to @steadfasterX for developing FisH.
I ported FisH for the Desire 526.
IMPORTANT INFORMATION FOR BOOTING / USING FISH
DO NOT FLASH ANY MODIFIED BOOT IMAGE OR RECOVERY IMAGE UNLESS YOU UNLOCKED YOUR BOOTLOADER FIRST
( WILL CAUSE A SOFT BRICK IF THE BOOT LOADER IS LOCKED )
INSTRUCTIONS TO MAKE SD-CARD AND USE FISH ARE BELOW​
PLEASE HIT THE THANKS BUTTON

What sd card to use ??
SD - CARD SELECTION / PURCHASING GUIDE​
STEP #1 GET THE BEST SD CARD YOU CAN
Since we are booting and running Android with the SD - Card a fast card is required. The card pictured is rated at
Please make sure that the SD Card you use has V30 or V60 or V90 on it. (See the pic below.)
Transfer speeds of up to 95 MB/s
Class 10, UHS speed class 3 (U3) and video speed class 30 (V30) ratings
{
"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"
}
The fastest cards on the market​WITH A CARD LIKE THIS YOUR DEVICE WILL RUN LIKE THE WIND ( THIS CARD HAS READ WRITE SPEEDS = TO THE INTERNAL EMMC )
https://www.amazon.com/Lexar-Profes...3212586&sr=8-13&keywords=UHS+ii+micro+sd+card
High-speed performance - leverages UHS-II technology (U3) for a read transfer speed up to 1800x (270MB/s)
Please note that I have not tested cards greater than 32GB. Anything greater than 32GB may need extra work to make operational.
Ultimately I plan to run a 128GB card with the capability of booting and running linux on The Phone. :victory:

How to make the card
Flashing the Image file to the SD-Card​
STEP #1 Download and install Win32DiskImager
Program info -->> https://wiki.ubuntu.com/Win32DiskImager
Program Download -->> https://sourceforge.net/projects/win32diskimager/
STEP #2 Download the SD-Card Image and unzip the file
http://www.mediafire.com/file/c2h48ksguo2m8ja/HTC-526-Boot.zip
A) Put the SD Card in your computer. USB or standard Card Reader is Fine.
B) Open Win32DiskImager (SEE Screen shot below for Use)
C) Click on write and select YES at the warning. The SD Card will be made
THE BURN PROCESS AFTER COMPLETED
AFTER YOU HAVE USED DISK IMAGER TO MAKE THE CARD IF YOU RE-INSERT THE CARD IN WINDOWS IT WILL TELL YOU YOU NEED TO FORMAT IT. DO NOT FORMAT IT. WINDOWS CAN NOT READ THIS DISK PROPERLY. LINUX / UBUNTU CAN PROPERLY MOUNT / READ THE DISK.
POWER OFF PHONE :
INSERT SD-CARD INTO PHONE :
POWER ON PHONE:
ENJOY RUNNING ANDROID ON THE SD

Booting FisH to run TWRP
How to BOOT FisH and run TWRP with a LOCKED Boot Loader​
After you have made the sd-card and it boots properly into system you will also be able to use FisH.
Follow these steps to boot into TWRP.
This is a special modified build of TWRP.
Please give thanks to @steadfasterX for developing FisH.
https://forum.xda-developers.com/an...locked-fish-hack-to-boot-want-device-t3578373
FOLLOW THESE STEPS EXACTLY - DO NOT DO ANYTHING DIFFERENT​
Step #1 : Power the device off completely and UNPLUG the USB if the phone was connected
Step #2 : Press power button to turn on like normal [SDCARD MUST BE IN THE DEVICE]
Step #3 : Get used to the boot sequence.
When the device is booting up from the sd card you should have noticed some minor differences.
There is a musical chime that you do not have unless the sd card is booting.
There is a phone vibration at almost the same time as the chime.
There is a phone vibration several seconds after the chime.
The RED VERIZON logo NEVER appears.
After you are familiar with how the device boots you are ready to boot FisH.
Step #4 : As soon as you hear the musical chime and the phone vibrates
Press and hold in the VOLUME UP key until the phone vibrates again.
Step #5 : DON'T RUSH THE FISH OR it WILL SWIM AWAY
You have to be very patient here.
WHEN FISH IS BOOTING THE SCREEN WILL GO OFF AND HITTING BUTTONS WONT DO ANYTHING.
(YOUR PHONE IS NOT BRICKED )
A lot of things are going on behind the scenes, the sd-card boots a little slower to begin with initially.
We are killing everything that is running on the phone and re-setting the processor to Hi-Jack the Boot.
The processes are restarted and the TWRP ramdisk is getting loaded from the SD Card into RAM.
I'm pretty sure this is all going on wile only running 1 thread of the processor. ( ALL THIS IS VERY SLOW )
Step #5 : After the screen goes black !!
DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes​ DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes​ DO NOT TOUCH a SINGLE BUTTON or PLUG THE PHONE IN for 5 Minutes​
Wait for 5 minutes. Longer is ok but do not touch anything for 5 minuets. This = 300 seconds.
If you get impatient don't worry, no damage will be done to the phone, :good: but there is a good chance that all of the processes may not initialize so some things could end up not working until you re-boot.
After the 5 minutes wait is over press the power button to turn on the screen. A quick short push.
You will be greeted by the TWRP Recovery.
If you want to use adb shell.
Once you are in TWRP go to Advanced and then Mounts.
Check the box next to system to mount the system partition.
Now adb shell and commands will work. You will have BusyBox commands available as well as all normal shell commands.
But what ???? Why is my shell not starting as root ???
When we boot into fish we are not booting in recovery mode. We are booting into Normal /System Boot Mode.
( THE DEVICE REALIZES THIS and starts shell as normal user. )
To get root access in TWRP.
Open the TWRP File Explorer.
In the root directory there is folder SuperSU.
Copy the file SU and paste it into /system/bin
Using the file explorer go to folder /system/bin
Change the permission of file SU to 777.
Now if you start adb shell.
Type
su
There is your root access. I will patch this in a future release.
Congratulations,
Your $35.00 chepo device can now do a hell of a lot more now than some of the High End Expensive ones.
TO RETURN TO NORMAL MODE JUST REBOOT LIKE NORMAL
OTHER THAN NOTED TWRP OPERATION IS AS USUAL
Do not FLASH a modified BOOT or RECOVERY if your Boot Loader is LOCKED
Unlock the BOOT Loader if you want to run TWRP through normal recovery or if you want to run a custom Boot.img
TWRP ONLY AFTER YOU HAVE UNLOCKED THE BOOT LOADER
Install TWRP by normal method.
Boot into download mode first then issue command.
Code:
fastboot flash recovery TWRP.img
http://www.mediafire.com/file/g3h14psl1m40wmi/TWRP.img <-- This one is patched so Touch Screen WORKS.

Very nice @BigCountry907 ! Your work is really appreciated and I'm glad to see this here
Just wondering which FIsH version do you use now? I have released a recent new one a while ago which should improve speed in many ways.. hopefully for your approach as well.
.

steadfasterX said:
Very nice @BigCountry907 ! Your work is really appreciated and I'm glad to see this here
Just wondering which FIsH version do you use now? I have released a recent new one a while ago which should improve speed in many ways.. hopefully for your approach as well.
.
Click to expand...
Click to collapse
@steadfasterX
I'm running the original release of FisH.
FisH will boot up faster than 5 min at times. But it depends on the SD Card Speed and other things.
During my test what i found was if I got in a hurry and didn't give enough time occasionally some things would not fully initialize.
Giving enough time for everything to initialize, always worked.
Thanks again for your work @steadfasterX .
Since you have released an updated version I will try it out.
This is one of the many benefits of the booting SD card.
All I have to do is pull the card out of the device and pop it in the computer running linux to have direct access to any of the partitions in my file explorer.

does this image just work for this type of model ? or how would you make it work for a galaxy J ?

Possible Port to Other Devices
Tonyg27 said:
does this image just work for this type of model ? or how would you make it work for a galaxy J ?
Click to expand...
Click to collapse
@Tonyg27
This is an interesting question ? There is some testing going on with other devices.
This image is good for the desire 526 ( FULL BOOT TO SYSTEM )
The image created for the 526 boot loader unlock will not produce a system boot but it will work in multiple devices to unlock the boot loader. This has been tested on a desire 526 desire 626s and a desire 530.
Confirmed working !
So heres the catch. All 3 of those / 526 626s and 530 are all msm8909 chipsets.
And they are all HTC.
@nailyk
Has reported to see minor differences in a Super-Soft Brick on a sony Xperia. -->> Bricked with no Signs of Life
There are many other reports of individuals running bricked devices simply by using a similar sd card method.
The common denominator is that they are all MSM -->> Qualcomm Chip Sets.
Depending on how the manufacturer compiled your aboot... Little Kernel
The Qualcomm chipset supports this by default provided the vendor like HTC or Sony or LG has not turned it off.
Now if you can run unsigned " Patched or Compiled " Aboot == Little Kernel then you can do this.
Normally or by default Q-comm has Little Kernel built so that if the device internal emmc dies hen it will boot the external sd card provided that the proper GPT and Partition Images exsist on the SD Card.
I believe this is a QComm alternative for the partition.xml and firehose.
Hard to say.
I am currently testing this with a couple lg devices.
I am positive that the same method to create the sd card could be used to create cards for other devices.
It will take porting and some work.
I will post a Universal tutorial in the dev section soon.

BigCountry907 said:
@Tonyg27
This is an interesting question ? There is some testing going on with other devices.
This image is good for the desire 526 ( FULL BOOT TO SYSTEM )
The image created for the 526 boot loader unlock will not produce a system boot but it will work in multiple devices to unlock the boot loader. This has been tested on a desire 526 desire 626s and a desire 530.
Confirmed working !
So heres the catch. All 3 of those / 526 626s and 530 are all msm8909 chipsets.
And they are all HTC.
@nailyk
Has reported to see minor differences in a Super-Soft Brick on a sony Xperia. -->> Bricked with no Signs of Life
There are many other reports of individuals running bricked devices simply by using a similar sd card method.
The common denominator is that they are all MSM -->> Qualcomm Chip Sets.
Depending on how the manufacturer compiled your aboot... Little Kernel
The Qualcomm chipset supports this by default provided the vendor like HTC or Sony or LG has not turned it off.
Now if you can run unsigned " Patched or Compiled " Aboot == Little Kernel then you can do this.
Normally or by default Q-comm has Little Kernel built so that if the device internal emmc dies hen it will boot the external sd card provided that the proper GPT and Partition Images exsist on the SD Card.
I believe this is a QComm alternative for the partition.xml and firehose.
Hard to say.
I am currently testing this with a couple lg devices.
I am positive that the same method to create the sd card could be used to create cards for other devices.
It will take porting and some work.
I will post a Universal tutorial in the dev section soon.
Click to expand...
Click to collapse
Many thanks.
I think the sdcard trick could work on Sony's too. I scheduled to work on this this weekend.
I will first try hammerhead (nexus 5) aboot and all partitions (except LCD panels and some other things device wont care to boot) they are the same device (same soc, same usb, same memory chip, etc...) so I have a bit of hope.
Then I will try your patched aboot + s1. If am able to build that aboot, maybe I should be able to customize it to fit Sony's cr*p requirements.
Making this Sony compatible will be pleasant for a lot of people
Anyway thanks a lot for the trick and keep up the good work :good:

I did all as the instructions said and my phone boot and after the htc logo it goes black and just sits there blank

agree with previous poster, doesn't work. Followed instructions exactly and phone just goes to blank screen after HTC logo on boot.

the boot zip is for the desire 626

@BigCountry907
I followed your directions to the tee, the phone boots up fine, however, I do not have wifi at all it's completely greyed out. Is there any way to fix it so I can use wifi?

Unsupported sandisk sd card
When I put the sd card into my HTC Desire 530 (verizon post-paid android 7.0), and turn it on, I immediately get the notification "unsupported sandisk sd card, this device doesn't support this sandisk sd card"

What if we don't have a top volume rocker?
My phone only has a decrease volume button that's functional.

Im having similar issues with the Wi-Fi network and the cellular data network being greyed out. Ive been trying all kinds of things for couple days. Nothing seems to work. Thanks for your help!

Can I get a new link to bootable image please?
Pretty much what the title said. LOL I have been searching for a good link for the bootable desire 526 image but they all seem to be dead on every thread. Can someone please provide me with a new link for this file?
**** working now! Thanks a lot!

Can i use it for my s8 active (g892u)?. My device has Snapdragon 835 (msm8998). It has locked bootloader and can not unlock. But it had rooted.

Installing Custom ROM on Cubot KingKong Mini

UPDATE 2021
The original post was for the first King Kong Mini, for instructions for the King Kong Mini 2 go to page 9 in this thread:
https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303
======================
The Cubot King Kong Mini was released in Q4 2019. It is one of the smallest Android phones on the market with a 4" screen. Like many cheap Mediatek devices, one cannot be sure of how "safe" or "secure" these devices are, so the security/privacy conscious may want to consider installing a custom ROM. Here are the instructions for installing Android AOSP on the Cubot King Kong Mini. Note: I am not responsible for any bricked devices.
Download the Stock Rom from here and SP Flash Tool just in case you need to reinstall Stock. Download a system image, note you need to use an A/B arm32 image with 64 bindings. For example AOSP 9 is here.
This process probably can be done with SP Flash Tool but I wasn't able to manage it due to the disable-verification flag required.
Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:
Code:
sudo fastboot flashing unlock
Note this will erase all data. Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you do not do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Unzip the .xz image file you wish to use and type:
Code:
fastboot flash system SYSTEM.img
where SYSTEM is the name of whatever image downloaded.
Root
For root install magisk manager and you have to patch the recovery to get root (not just boot as flashing boot alone doesn't give you root). So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:
Code:
fastboot flash boot magisk_patched_boot.img
fastboot flash recovery magisk_patched_recovery.img
You can read more about magisk from recovery here.
To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution.
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
What doesn't work
Battery usage doesn't work, this can probably be fixed following this guide. If I get time I will attempt this.
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
The battery life is definitely worse using AOSP GSI than stock, maybe that vendor overlay would help with that though.
I hope that helps others.

TWRP+Encryption Disabling+Magisk Root
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.

well well, finally and serranoltexx successor?
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]

moctir said:
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
Click to expand...
Click to collapse
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/

robrazil said:
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/
Click to expand...
Click to collapse
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!

Tom Mix said:
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
Click to expand...
Click to collapse
I did it to replacement my old Samsung J1 ace, very similar of S4 Mini, and I'm not regretful for that.
---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------
moctir said:
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
Click to expand...
Click to collapse
I understood but the point is if the TWRP source is confiable. I asked the official TWRP Team about the unofficials TWRP on websites in my last post, and they answer: "Hello, we do not run that site, so I cannot confirm the validity of their images."
So, I wonder how safe the unofficial TWRP images are.

moctir said:
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
Click to expand...
Click to collapse
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:

robrazil said:
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:
Click to expand...
Click to collapse
Yes, indeed there were three times I thought I had totally bricked and each time I was so annoyed with myself! The key is to not charge it much until you are happy with the ROM you put on.
The amount of drivers I tried to use for different OS' when I got that "unknown USB device" on Windows and Linux didn't detect it was all a waste of time!

Well... the battery image appeared again and I uploaded firmware again. I installed the Magisk in the boot recovery, because this only way to install the Magisk on devices that are using system-as-root, but the Magisk disable my 2 SIM cards. When I boot without Magisk, all back to normal.
I serched for any solution for that but I didn't find.
So, my conclusion is that the Magisk not works to Cubot King Kong Mini. How can I stay with a phone with no SIM card?
I give up.

For me I can only get root when I patched Magisk to Recovery and then boot to Recovery and it doesn't see my SIM card but I have root, so I reboot every time I need root which is a bit annoying...

It is very complicated everytime when need "root", to have power off and on the mobile in recovery boot mode. Besides that, run out of SIM card working is not an option.
I will try to get support of this issue with Magisk Team.
Thank you for share your experience.

Ce3apyc said:
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.
Click to expand...
Click to collapse
Hello,
Does anybody can confirm, that this is working with the new firmware?

I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?

Ce3apyc said:
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
Click to expand...
Click to collapse
I'm using treble AOSP Android 9 so not the latest firmware. I thought disabling the verification when installing that would be enough but maybe I do need to do those other steps. I can see the /system directory through TWRP so that's probably because that's the one I flashed, but I can't see the internal storage otherwise.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
{
"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"
}

robrazil said:
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
Click to expand...
Click to collapse
Thanks, I'll check it out!

Anyone else having problems with sensors on this phone? Rotating and compass do not work for me. That's what you get for buying a cheap Chinese phone, I guess.
EDIT: Downgrading firmware back to CUBOT_KINGKONG_MINI_9101C_V06_20191121 seems to fix some problems, rotation works, but compass is still buggy.

Never tried compass but haven't had any problems with rotation.

Tried to install root on a friends kkm but I can't get it working in the os. Is there any chance to get it working there? I am only able to get root access in twrp. Maybe an gsi with root is that possible?