Develop Bugs

[MOD] Proof of Concept: Unbrick/Debrick hard-bricked i927 ? (untested)

Some? Samsung devices support a special kind of unbricking hard-bricked* phones.
This thread tries to provide that to the i927/glide..
Who wants this?
If you have hard-bricked* your device (please see the next post about difference between hard- and soft-bricked)
there is no other reason to use this!
Current state:
Totally untested and absolutely without any warranty.
I have no idea if the image itself is good or not - neither if the whole process would work for the i927!
As I do not own a hard-bricked device and I do not want to damage mine I cannot test this by myself.
The reason creating this is because a user had requested it: click here for the origin user request
Please give me feedback if you have tested it!!!
Known issues:
who knows..
Instructions
Requirements
First of all you need a micro SD card. If you have none you cannot continue (man.. buy one!).
Then you need a PC which is able to read this SD card or an external SD card reader.
Basic
Here in short the basic steps you need to take (detailed in the next section):
Download
Extract
Flash unbrick image to SD card
Insert SD card into the Glide
boot
wait
soft-unbrick
Detailed (Linux)
Some parts taken from here
Download i927_unbrick.zip
unzip -d /tmp/unbrick i927_unbrick.zip
Insert SD card into your PC
dmesg | grep dev | tail
--> you should see something like "/dev/sdc1" or "/dev/mmcfoo1" or similar which is your SD card you inserted just before. In the next parts we refer to it as "/dev/FROM-DMESG-OUTPUT"
The next commands will make your SD card UNUSABLE until you reformat it! Ensure that you do not have any data you need on it!
sudo umount /dev/FROM-DMESG-OUTPUT (do not use any GUI clickable eject action instead)
sudo dd if=/tmp/unbrick/unbrick.img of=/dev/FROM-DMESG-OUTPUT
pull out the SD card from the PC
remove the battery, sim and any external SD card from your device
insert your unbrick SD into your phone
insert the battery and down your power button (at this point your phone might actually boot completely and you can recovery any software/data you want)
reboot into Download mode either via adb or Volume Up while powering on
Once the device is booted into bootloader remove the SD card and start ODIN or heimdall to flash a STOCK firmware or use the OneClick Soft-unbrick tool
Detailed (Windows)
Some parts taken from here
Download win32diskimager
Download i927_unbrick.zip
Extract i927_unbrick.zip and win32diskimager
Insert your SD card into your PC and wait until it gets detected
Run win32diskimager
browse for your extracted unbrick image
Select your SD in the dropdown box
The next step will make your SD card UNUSABLE until you reformat it! Ensure that you do not have any data you need on it!
Click write
pull out the SD card from the PC
remove the battery, sim and any external SD card from your device
insert your unbrick SD into your phone
insert the battery and down your power button (at this point your phone might actually boot completely and you can recovery any software/data you want)
reboot into Download mode either via adb or Volume Up while powering on
Once the device is booted into bootloader remove the SD card and start ODIN or heimdall to flash a STOCK firmware or use the OneClick Soft-unbrick tool
Download
Please go to the Download page
Background of the unbrick.img
todo
Sources
First, Second, Third
Thanks
Please report back if it has or has not worked for you!
Thanks
xdajog
.
XDA:DevDB Information
Unbrick/Debrick hard-bricked i927, Tool/Utility for the Samsung Captivate Glide
Contributors
xdajog, alvcross
Version Information
Status: Alpha
Created 2016-01-04
Last Updated 2016-01-12

FAQ
hard-bricked?
When do we speak about hard-bricked? If one or more of the following matches your situation you have hard-bricked your device
powering on leaves the device black like it is still powered off
you cannot get into the download mode anymore
soft-bricked?
When do we speak about soft-bricked? If one or more of the following matches your situation you have soft-bricked your device and you should not use the instructions made in this thread:
you can go into the download mode
you can start recovery mode
you see the samsung logo
you see the boot animation
If you have soft-bricked your device: There is an easy one available for our device (untested by me but many tell it works fine) --> http://forum.xda-developers.com/showthread.php?t=1153310

Reserved

does it actually work?
If you brick your bootloader, you wouldnt boot from SD card IMHO.
Our phone could recovery from APX mode. More info http://forum.xda-developers.com/showthread.php?t=1528256

bubor said:
does it actually work?
If you brick your bootloader, you wouldnt boot from SD card IMHO.
Our phone could recovery from APX mode. More info http://forum.xda-developers.com/showthread.php?t=1528256
Click to expand...
Click to collapse
Thats the big question. e.g the T999 will boot from the SD card even when the bootloader is blown. So as stated above I have no idea if the same process will work for this phone so I need testers who tries it actually...
The unbrick image was made the way it should work IF yes IF the i927 will boot from the SD card in case of corrupted bootloader. so without any test I cannot tell you if it would work..
.

xdajog said:
Thats the big question. e.g the T999 will boot from the SD card even when the bootloader is blown. So as stated above I have no idea if the same process will work for this phone so I need testers who tries it actually...
The unbrick image was made the way it should work IF yes IF the i927 will boot from the SD card in case of corrupted bootloader. so without any test I cannot tell you if it would work..
.
Click to expand...
Click to collapse
There is always a preloader, what loads bootloader, I think that loads sd card. Preloader does APX mode on tegra 2.
I doubt it would work, but who knows?

Flashing Guide RoundUp for the LeEco Le Pro 3

Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
To flash only the US modem to restore band 12 on any ROM:
Download: https://www.androidfilehost.com/?fid=601300970940399635
Extract the zip file and place it in your adb & fastboot folder.
From your abd & fastboot files folder (with the modem image in there too) open a command prompt and run
fastboot flash modem modem-5.8.019s.img
Then reboot your phone.
Keep this file handy because you'll need it every time you flash a ROM that doesn't have a US modem.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, flash whatever ROMs you want, and restore US modem.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.

Thank you for the good guide.

well done. Please keep it updated...

suhridkhan said:
well done. Please keep it updated...
Click to expand...
Click to collapse
lilila said:
Thank you for the good guide.
Click to expand...
Click to collapse
Thank you and you're welcome. I'll try to keep this updated as new info or procedures come up :good:

hondajohn88 said:
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, and flash whatever ROMs you want.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Click to expand...
Click to collapse
Nice one John

seffmono said:
Nice one John
Click to expand...
Click to collapse
Thank you kind sir

"...It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther..."
Did I miss the part on how to keep the Band 12 capabilities?

Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Flashing the CN-US ROM will not relock the bootloader, so you're safe there.

I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk

rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
If you install TWRP from fastboot (fastboot flash recovery twrp.img), it should replace the factory recovery.

rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Click to expand...
Click to collapse
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.

seffmono said:
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
Click to expand...
Click to collapse
i will try that.

I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?

worries said:
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
Click to expand...
Click to collapse
I hate to speak for everyone here but it's highly unlikely someone will take the time to do that. I suggest you instead do as much research as you can, and make a video for the next person like yourself that prefers it. Speaking from experience most people on XDA will recommend spending as much time reading and learning as you can, and then taking the "leap" on your own. Rooting and unlocking is not for the faint of heart, and a bit of confidence in your own abilities can go a long way! I hope this doesn't sound condescending, but just my advice. Best of luck!

I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
---------- Post added at 05:55 AM ---------- Previous post was at 05:29 AM ----------
Nevermind. Booted into recovery and formatted the system then it ran fine.
huemedia said:
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
Click to expand...
Click to collapse

It had this happen and If i remember correctly, their is a bug in the system and it wont let you past that screen regardless what. Just boot to twrp do a data backup. Format everything else except internal storage and reflash your rom

I followed this guide and flashed the US modem zip on top of stock 19s. However, my SIM is recognized and the "Mobile Networks" setting page is grayed out. However, my phone is still booting with Chinese text in the bootloader. How do I fix this?

Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3

toanau said:
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
Click to expand...
Click to collapse
I am trying the long way and it's failing (20s)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Im dumb, nevermind

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?

[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks

Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
UPDATE 17-10-21: Jio pushed a firmware update which is locking boot loader. If your device is not updated yet it is advised to re-flash your firmware with patched image given below which basically disables auto updates. If you're already locked out, currently there's no easy fix for that.
If you haven't used your device from a long time or you're still on lower or equal version than below it is advised not to use JioFi with SIM, flash this firmware first if you want to test SIM unlock.
Guide
Make sure you're on same or lower firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_patched_system.zip​
JMR541_unlocked_patched_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
fastboot erase recoveryfs
fastboot flash recoveryfs "D:\system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
.
Q. I 'accidentally' flashed my recovery and boot partition
A. Well accidentally I've backed up recovery and boot download from below
1. JMR540_boot_recovery.rar
2. JMR541_boot_recovery.rar
.
Q. FAILED: (remote: Image is locked) issue while erasing/flashing image
A. Jio recently pushed an firmware update which re-locks simlock and bootloader which basically means you can't flash unsigned/custom firmware. Currently there is no fix.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
What about JioFi 2, 4, 5, 6?
Reverse Engineering takes lot of time and coffee. Until I get physical access to device I won't be able to unlock it. I'm constantly searching them on OLX as soon as I get hands on I'll surely try to RE and unlock it. I'll update the same here if there is no update here at the time of your reading then I haven't got the device yet so please don't spam for update hope you understand that I don't get anything by doing these things, I do it for liberation of locked hardware to meet it's real destiny and of course for the people. I also have a day job so no I cannot guide or teach you, hope you understand why.
For Devs:
JMR_540_FLASH_DUMP.rar
​

Reserved

successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.

sksinha said:
successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.
Click to expand...
Click to collapse
Can you show us dashboard screenshot. This will help other users to verify

abhimortal6 said:
Can you show us dashboard screenshot. This will help other users to verify
Click to expand...
Click to collapse
...

Nice, enjoy!

abhimortal6 said:
Nice, enjoy!
Click to expand...
Click to collapse
bro is unlocking more 4g bands or manual selection of bands can be done ?

sksinha said:
bro is unlocking more 4g bands or manual selection of bands can be done ?
Click to expand...
Click to collapse
Totally possible even 3G but it can't be done through WebUI it'll requires shell access.

Totally working! thanks a ton a bro <3

srbhsngwn said:
Totally working! thanks a ton a bro <3
Click to expand...
Click to collapse
{
"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"
}

Great

..

myapky said:
JMR540 ERROR
Click to expand...
Click to collapse
you haven't properly specified the address of system.img Please give the complete path

srbhsngwn said:
you haven't properly specified the address of system.img Please give the complete path
Click to expand...
Click to collapse
Fixed issue.

myapky said:
there is a issue with JMR540, however I have successfully flashed JMR541 file on friends JioFi 3.
There is definitely a issue with JMR540 system.img file. request @abhimortal6 to check the file and reupload.
I have added a device info details for JMR540
Click to expand...
Click to collapse
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.

abhimortal6 said:
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.
View attachment 5326935
Click to expand...
Click to collapse
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?

myapky said:
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?
Click to expand...
Click to collapse
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"

abhimortal6 said:
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"
Click to expand...
Click to collapse
nand was dead...due to all day work on JioFi, now all good thanks for help.

abhimortal6 said:
Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
Guide
Make sure you're on same firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
If not please use the device for sometime it'll autoupdate.
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_system.zip​
JMR541_unlocked_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition (Skip for JMR 540 )
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
Bash:
fastboot flash recoveryfs "system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
​
Click to expand...
Click to collapse
Hi, i just read ur article on unlocking jiofi 3 and that looked amazing.But i have a jiofi JMR815 and have been looking for help to unlock it from a couple of years.But till date only your post looks promising and i ask yourhelp in helping me unlock my JioFi JMR815.Kindly consider helping me.Also i created an account in XDA just to ask your help
View attachment 5327245
View attachment 5327247
View attachment 5327249
View attachment 5327251

This is completely genius! I am now able to use Airtel sim on my JioFi! Thanks!