To get it just download the OTA and install it, unless you're rooted, in which case you'll need to install the zip from here. Keep in mind that it takes some time for the update to get on that site, so if it's still not there check back in a day or two
Got OS 13 this morning for my Swift but have issues. At the time the update installed SIM 1 was enabled but SIM 2 was disabled. (i.e.both slots had SIM cards in them but only only card one was enabled). Post update SIM 1 works in either slot but SIM 2 will not work in either slot and cannot be enabled (Swift tells me ther is no SIM in the slot). If both SIMs are physically in place neither works and the phone tells me both slots are empty. Has the update killed SIM2? (Possibly because it was disabeld when the update happened?) I have no other SIM to try populating both slots appart from the non-functioning one.
grahamu said:
Got OS 13 this morning for my Swift but have issues. At the time the update installed SIM 1 was enabled but SIM 2 was disabled. (i.e.both slots had SIM cards in them but only only card one was enabled). Post update SIM 1 works in either slot but SIM 2 will not work in either slot and cannot be enabled (Swift tells me ther is no SIM in the slot). If both SIMs are physically in place neither works and the phone tells me both slots are empty. Has the update killed SIM2? (Possibly because it was disabeld when the update happened?) I have no other SIM to try populating both slots appart from the non-functioning one.
Click to expand...
Click to collapse
Try removing the sims and battery, sometimes my Swift doesn't detect the SIMs aswell
I have the same problem, I have tried the affected sim in a spare phone and it works fine. Also I tried a new sim and both are recognised in the swift so next step factory reset and hope it sorts the problem.
brokebloke said:
I have the same problem, I have tried the affected sim in a spare phone and it works fine. Also I tried a new sim and both are recognised in the swift so next step factory reset and hope it sorts the problem.
Click to expand...
Click to collapse
Please let us know if the reset fixes the problem.
Same issue with mine after update (doesn't detect either SIM - S1 was enabled and S1 disabled before the update) - fingers crossed it'll sort itself out.
Removing and reseating the sims and battery made no difference, fwiw
Apparently a factory reset is the official fix, according to their twitter account:
https://twitter.com/Wileyfox/status/730670536108462080
I don't see many differences with the update but there is still time to see how it will hold up.
One thing I did notice right away is that I can't get the SD card to be used as adopted storage. After the format it remains as corrupted (64GB microSDHC class 10). It doesn't have any problem to be used as portable storage. I should check with one CM13 ROM if the card is the problem or it could be something a clean COS13 install will fix.
Other than that, everything works great. Now on Tap is good, there is no longer "Advanced mode" inside About phone, security update is May 1st. Some minor UI changes here and there. Overall- very good.
I can confirm that a factory reset made the SIMs get detected again.
Now just to get this phone back the way I like it! (sigh!)
Pak0St said:
I don't see many differences with the update but there is still time to see how it will hold up.
One thing I did notice right away is that I can't get the SD card to be used as adopted storage. After the format it remains as corrupted (64GB microSDHC class 10). It doesn't have any problem to be used as portable storage. I should check with one CM13 ROM if the card is the problem or it could be something a clean COS13 install will fix.
Other than that, everything works great. Now on Tap is good, there is no longer "Advanced mode" inside About phone, security update is May 1st. Some minor UI changes here and there. Overall- very good.
Click to expand...
Click to collapse
No Advanced mode! Can you still edit the positions of the onscreen nav buttons ie swap home, back etc?
rebane2001 said:
To get it just download the OTA and install it, unless you're rooted, in which case you'll need to install the zip from here. Keep in mind that it takes some time for the update to get on that site, so if it's still not there check back in a day or two
Click to expand...
Click to collapse
there are 3 images on the cyngn.com/support website.
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
cm-13.0-ZNH0EAS2NH-crackling-signed-9c92ed2cde.zip
cm-13.0-ZNH0EAS2NH-crackling-boot-debuggable-dec9fc75ff.img
which one is the correct one for a rooted swift
ts-ascii said:
there are 3 images on the cyngn.com/support website.
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
cm-13.0-ZNH0EAS2NH-crackling-signed-9c92ed2cde.zip
cm-13.0-ZNH0EAS2NH-crackling-boot-debuggable-dec9fc75ff.img
which one is the correct one for a rooted swift
Click to expand...
Click to collapse
cm-13.0-ZNH0EAS2NH-crackling-signed-9c92ed2cde.zip did it for me
leetron said:
No Advanced mode! Can you still edit the positions of the onscreen nav buttons ie swap home, back etc?
Click to expand...
Click to collapse
I bet the advanced mode features are still there, swapping navbuttons was available atleast for me
any idea how to get root back without unlocking bootloader again and installing TWRP. I don't want to loose my data thrugh the wipe
my devise is bricked
after update my device briked ..now only working fastboot only ...any one plz help . boot loader also disabled :crying:
@leetron , absolutely! They just removed the extra step there. I believe, now everything is enabled by default.
Shame you can't modify the recent button behaviour with the extra goodies yet.
(first of all sorry about my bad english) any one please help me to recover my phone ...i try some way but i lost recovery mode by pressing volume down & power button but not working .only one flash of wileyfox come and gone. switch on is not working ..same like flashing the screen & gone dark. only working cyanogen fastboot mode by pressing volume up + power button......what i do i am not a tech no guy but a fan of cynogenmod..plz help any one.......
ts-ascii said:
any idea how to get root back without unlocking bootloader again and installing TWRP. I don't want to loose my data thrugh the wipe
Click to expand...
Click to collapse
Your bootloader should still be unlocked, you just need to reinstall TWRP, which doesn't delete your data
akkuvijay said:
after update my device briked ..now only working fastboot only ...any one plz help . boot loader also disabled :crying:
Click to expand...
Click to collapse
Go to fastboot by holding down volume up and plugging in an USB cable and flash a new recovery using these steps (you need fastboot to work on your computer):
1. Download recovery.img from here
2. Open Command Prompt and type in the following:
Code:
fastboot -i 0x2970 erase recovery
3. Then type in
Code:
fastboot -i 0x2970 flash recovery recovery.img
4. Then using fastboot, boot into recovery and using USB file transfer method copy this file to your device
5. Now wipe your device and install the zip
Then your device should work again
rebane2001 said:
Your bootloader should still be unlocked, you just need to reinstall TWRP, which doesn't delete your data
Go to fastboot by holding down volume up and plugging in an USB cable and flash a new recovery using these steps (you need fastboot to work on your computer):
1. Download recovery.img from here
2. Open Command Prompt and type in the following:
Code:
fastboot -i 0x2970 erase recovery
3. Then type in
Code:
fastboot -i 0x2970 flash recovery recovery.img
4. Then using fastboot, boot into recovery and using USB file transfer method copy this file to your device
5. Now wipe your device and install the zip
Then your device should work again
Click to expand...
Click to collapse
sir thanks for replay ... there is an error like this
{
"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"
}
akkuvijay said:
sir thanks for replay ... there is an error like this
Click to expand...
Click to collapse
You need to install the google usb driver
Related
How to fully fix au Japanese HTC Butterfly 3 with Taiwan’s ROM
[ROM verified working in US on all gsm networks and Europe (other networks may place sim lock ie. Middle East, South America)]
**Read over entire guide before starting**
**I am not responsible for any damage done to your phone. (Guide is basically without flaw, but still)**
**It is recommended you leave sim card out until point you stop, turn off phone, insert, then reboot.**
Shout out to mars3712 for uploading the file images check him out and donate:
https://www.androidfilehost.com/?w=profile&uid=24052804347819348
and another shout out to moizjazz for helping me diagnose my problem that many have been experiencing (banner error due to CID and MID[this prevents HTC updates from installing and/or installing zips])
Pre-req.s htc drivers and adb 1.3 drivers
1. Enable adb debugging on phone
2. Download this file and unzip: https://drive.google.com/file/d/0BwjkdhnznIw6THQxdHFIcWUxRms/view?usp=sharing
3. add this zip with it and unzip contents into same directory https://www.androidfilehost.com/?fid=24352994023706379
4. hold shift and then right click blank space in folder and select open command window here
5. Type: adb reboot download
6. Type: fastboot oem get_identifier_token
7. Right click terminal and left click and hold from First "<" to last ">"
8. Press enter, paste into wordpad or text editor
9. Delete all <bootloader> s and space afterwards
10. Log into www.htcdev.com
11. Copy the token to http://www.htcdev.com/bootloader/unlock-instructions/page-2
12. Proceed with instructions until you get the email.
13. Download Unlock_code.bin and put it with all other files (in b3twrp)
14. Type into terminal Fastboot flash unlocktoken Unlockcode.bin
15. You will be prompted to allow unlock, with volume rocker move to yes and press power button
16. During reboot hold all three buttons and when phone shuts off let go of vol+
17. You will be in download mode again
18. Type these commands
a. Fastboot flash boot boot.img
b. Fastboot flash recovery recovery.img
c. Fastboot flash system system.img
d. Fastboot oem writecid HTC__621
e. fastboot oem writemid 0PL220000
[Good time to make twrp backup on SD card]
[You can stop here if you are content with lollipop; skip to bottom for gps fix]
f. fastboot oem lock
19. Reboot and upgrade to marshmallow without dealing with banner errors and RUU
At this point the Tiawan rom has two software malfunctions, no gps and no nfc, however, there is a patch you can flash for gps
Marshmallow update has gps fixed and nfc detected, but unusable.
-video- https://www.youtube.com/watch?v=LEAH...SD4YsS3P4WqrPA
-Straight up link- http://1drv.ms/1nKdi4e
This dude is awesome for having the gps fix, like his video.
P.S. There is now a way to root or add xposed installer to Marshmallow because twrp 3.0 for recovery has been made for this device running marshmallow
[Edit]: Now there is twrp!!!!! (see bottom!!!!)
**I have tested this method twice and confirmed that even with some updated download mode firmware, updates will always be possible**
*This method rocks!*
Also (to end this goose chase), if any of you want the zips for some reason, here are the links to the best servers:
Japan: https://www.androidfilehost.com/?fid=24052804347822774 Credit goes to - Krocko
Taiwan: https://www.androidfilehost.com/?fid=24352994023706373 Credit goes to- mars3712
Big ANNOUNCEMENT! An actual twrp recovery image has been compiled and uploaded!(In china)
Here's my reuploaded copy! (Won't take 10 minutes to download) Thanks to mrquyen1993 for sharing this update and a HUGE thanks to... I actually dont know...
https://drive.google.com/file/d/0B6qqU5WVQ2khMVRMSUhOUWY3WU0/view?usp=sharing
Phone, SMS, and data work perfectly! I had issues with sms due to damaged SIM card(weirdest thing ever).
Hello, I believe a simlock solution has been found. add attached misc.img to your b3 adb directory and open terminal and enter command fastboot flash misc misc.img in bootloader mode. If that doesn't work try it in download mode. I can't test if this is a successful fix or not because I didn't have this problem.
So when I flash this rom, I will get a completely clean rom with no bloatware, root and TWRP?
And if I have root I can use your method to be able to text again?
Twrp is still only flashable to recovery and and all gsm cell service works, but other than that you're correct. These are the stock flashable images. (You need to decompress the file)
Sent from my HTC_B830x using XDA-Developers mobile app
Works like a charm, thanks a lot!
So if I follow your steps, I can convert my Japan version to Taiwan version? Does NFC and GPS work?
Can you post a copy of your updated boot.img somehow?
NP. Srry I Just saw this now.
[deleted]
Half correct
frosticfire said:
So if I follow your steps, I can convert my Japan version to Taiwan version? Does NFC and GPS work?
Click to expand...
Click to collapse
Only gps will work and you have to follow the bottom link. Follow the instructions.txt in the zip.
Sim card problem
My phone keeps showing "SIM network subset unlock PIN" , it reboots after i entered the pin, it goes back to the same page after it reboots. Any solutions?
This only happens when there's a SIM card being inserted.
Troubleshooting
bernard090 said:
My phone keeps showing "SIM network subset unlock PIN" , it reboots after i entered the pin, it goes back to the same page after it reboots. Any solutions?
This only happens when there's a SIM card being inserted.
Click to expand...
Click to collapse
Have you tried:
-soft factory reset(in settings)
-factory reset and/or wiping cache in download mode
-factory reset and/or wiping cache in recovery
-wiping system, data, and cache in twrp prior to flashing boot, recovery, and system
-reverting to backup
-trying simlock toggle in recovery/weird mode with vol+ and power on boot
-Checking sim support/trying different sim
These are steps I would take (in the order least to most in depth[not this order])
Sounds like a problem with your sim card from your specific provider. The phone with Tiawan has an international apn-configs.xml
TWRP for B3 By BOA ai-dev
Tutorial Chinese
TWRP-Recovery Rom taiwan
TWRP-Recovery Rom Japan
Rom stock B3 HTV31 Au ver 1.11.970.0 - new
Boa rom cook pay
After updating Marshmallow , you do not need to fix gps.
Sorry, my english very bad
{
"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"
}
Bug:
1. NFC.
2. Power.
This is some awesome stuff!
mrquyen1993 said:
TWRP for B3 By BOA ai-dev
Tutorial Chinese
TWRP-Recovery Rom taiwan
TWRP-Recovery Rom Japan
Rom stock B3 HTV31 Au ver 1.11.970.0 - new
Boa rom cook pay
After updating Marshmallow , you do not need to fix gps.
Sorry, my english very bad
Bug:
1. NFC.
2. Power.
Click to expand...
Click to collapse
I'm going to test these files!
[Edit] I have now confirmed twrp works. If you can, please have the creator make a thread in android development!
@ boa19861105
http://forum.xda-developers.com/member.php?u=1580110
Sent from my HTC_B830x using XDA-Developers mobile app
Birkyjon said:
Have you tried:
-soft factory reset(in settings)
-factory reset and/or wiping cache in download mode
-factory reset and/or wiping cache in recovery
-wiping system, data, and cache in twrp prior to flashing boot, recovery, and system
-reverting to backup
-trying simlock toggle in recovery/weird mode with vol+ and power on boot
-Checking sim support/trying different sim
These are steps I would take (in the order least to most in depth[not this order])
Sounds like a problem with your sim card from your specific provider. The phone with Tiawan has an international apn-configs.xml
Click to expand...
Click to collapse
I've tried every single method you have listed but to no avail, any other suggestions?
Butterfly 3 android 6 sense 8
https://m.facebook.com/story.php?story_fbid=1083701208319409&id=241474159208789
Sent from my HTC_B830x using XDA-Developers mobile app
So... will SMS Work?
Hi, the whole reason to do this for me is to get SMS working in the UK on this phone. Will this fix it? Also will this root the phone, as the KLGadget guy on Youtube seems to think that you can flash the Taiwan Rom without Root, but I have had no luck (keeps saying SC CARD NOT MOUNTED when I try his method) thanks.
nickbarr said:
Hi, the whole reason to do this for me is to get SMS working in the UK on this phone. Will this fix it? Also will this root the phone, as the KLGadget guy on Youtube seems to think that you can flash the Taiwan Rom without Root, but I have had no luck (keeps saying SC CARD NOT MOUNTED when I try his method) thanks.
Click to expand...
Click to collapse
you should have a PC, Laptop and follow my instructions.
however I write in Vietnamese, you can use gg translate
Link
Sorry my english very bad
mrquyen1993 said:
you should have a PC, Laptop and follow my instructions.
however I write in Vietnamese, you can use gg translate
Link
Sorry my english very bad
Click to expand...
Click to collapse
Thanks, but I am not sure you have answered my questions.
Rom stock taiwan can fix sms,
I use adb to flash rom, it should not need sd
mrquyen1993 said:
Rom stock taiwan can fix sms,
I use adb to flash rom, it should not need sd
Click to expand...
Click to collapse
thanks. I will follow the original instructions.
Hi,
I've update my Mi Lite from 07 to 08 update and since this morning, my smartphone don't have provider data (Proximus - Belgium).
I've change sim card with a newone, change sim1 to sim2,...
My sim card is working in another smartphone
I just have wifi...
After April Update, my phone has bugs with data connecting.
Am I alone with these problems ?
EDIT :
after full Reset Factory : same problem
Le Dam said:
Hi,
I've update my Mi Lite from 07 to 08 update and since this morning, my smartphone don't have provider data (Proximus - Belgium).
I've change sim card with a newone, change sim1 to sim2,...
My sim card is working in another smartphone
I just have wifi...
After April Update, my phone has bugs with data connecting.
Am I alone with these problems ?
EDIT :
after full Reset Factory : same problem
Click to expand...
Click to collapse
Looks like software is buggy, I'm not surprised because Xiaomi sucks at this. Download stock rom and flash it via MiFlash (latest should be 10.0.3.0), then after you've setup your device, go to Settings -> About Phone, tap on build number a few times until you open dev. options. Then go to System settings, go to developer options and disable automatic system update, so it doesn't update itself. You can try installing the update again if you still have the problem. But I'd suggest waiting until May update, if it ever comes lol. Xiaomi done f***ed up. Good luck.
Le Dam said:
Hi,
I've update my Mi Lite from 07 to 08 update and since this morning, my smartphone don't have provider data (Proximus - Belgium).
I've change sim card with a newone, change sim1 to sim2,...
My sim card is working in another smartphone
I just have wifi...
After April Update, my phone has bugs with data connecting.
Am I alone with these problems ?
EDIT :
after full Reset Factory : same problem
Click to expand...
Click to collapse
I'm also from Belgium, on latest stock rom (april update) I also face minnor troubles on mobile network, sms is sending slow, and 4G connection drops sometimes, I'm on mobile viking network ( Orange) but it's not so bad that I can't use my phone , battery life is good,I 'm not rooted only unlocked bootloader. I 'll wait to root and flash custom rom untill android one stops with updating monthly. Did you check your apn settings?
It's just a problem of APN settings, no bugs raised in this update
Hi, thanks for you reply's...
@marstonpear
Before I read your message, I've flash some stock ROM... and neither work. Always the same problem.
@Nxkealen
I'm not @orange and I think it's not the same frequency but your problems are same mine in the beginning.
I just flashed my phone like it was when I bought it. And I never change APN.
@IlSaro
I don't think it's APN problem...
I'm not shure but APN are only for data ???
I'm not sure. Try to restore only the network settings
IlSaro said:
I'm not sure. Try to restore only the network settings
Click to expand...
Click to collapse
I already try this and flash old stock rom...
But same result
Provider network icon remains disabled :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I try any idea... thanks for your help !
Have you also tried another SIM?
Flash the modem.img from Pie (?!)
Solve: This issue
Hi,
After update April update mobile network totally gone.
How to solve:
1. unzip daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.gz
2. find modem.img from image folder.
3. take modem.img to adb folder.
4. Put my mobile device on fastboot mode.
5. On CMD type fastboot flash modem modem.img and hit enter. the fastboot reboot.
Mobile network working fine.
nowbo said:
Hi,
After update April update mobile network totally gone.
How to solve:
1. unzip daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.gz
2. find modem.img from image folder.
3. take modem.img to adb folder.
4. Put my mobile device on fastboot mode.
5. On CMD type fastboot flash modem modem.img and hit enter. the fastboot reboot.
Mobile network working fine.
Click to expand...
Click to collapse
Thank you for your help.
I just try to flash exactly you propose but the modem still not present...
Le Dam said:
Thank you for your help.
I just try to flash exactly you propose but the modem still not present...
Click to expand...
Click to collapse
Maybe it's a hardware problem,you have still warranty? Flash fastboot stock rom update to latest one, don't root ,lock bootloader and send it back, i got my device from coolblue
I use to have this problem (No imei & Sim not being detected) even when I downgraded it was still exsisting, So I found a fix :
REQUIRES THE BOOTLOADER TO BE UNLOCKED!!!
Use twrp (What I've used to fix that issue) :
1.Boot into TWRP recovery.
2.From TWRP’s main screen, select Advanced » then Terminal.
3.Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
4.Reboot device.
Or you could try it with ADB :
1.Setup ADB and Fastboot on your PC.
2.Enable Developer options & USB debugging on your Android device.
3.Connect your device to the PC and open a command window on the PC.
4.Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
4.adb reboot
Basicly it fixes the EFS that maybe got corrupted.
I do recommend to reinstall the modem by doing this :
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
And after doing that just run the "flash_all.bat" or "flash_all_lock.bat" from CMD in the folder that you have adb drivers and the official rom file.
If you don't know how to do that you could PM me I would gladly help you
Many thanks Noam (and other forum users), I'll check that this evening (in 5 hours).
I think I'll use ADB method (not TWRP on my device).
After your 2th method, do I reflash a full rom ?
If I erase all modems, how and wher can I find newone ?
Thank you
Not working...
I've make what you propose without result.
After, I've reflashed "daisy_global_images_V9.6.4.0.ODLMIFF_8.1" (only this ROM is flashable without bootloop).
But after reboot... no modem.
I let smartphone OTA update...
But after reboot... again no modem.
The SIM card is detected but smartphone never mount it.
Le Dam said:
Not working...
I've make what you propose without result.
After, I've reflashed "daisy_global_images_V9.6.4.0.ODLMIFF_8.1" (only this ROM is flashable without bootloop).
But after reboot... no modem.
I let smartphone OTA update...
But after reboot... again no modem.
The SIM card is detected but smartphone never mount it.
Click to expand...
Click to collapse
did u flash with "Mi Flash Tool"?
If you did you need to format it through fastboot and let it reinstall everything through fastboot.
If you want help I would help you with discord or whatever you want
I know the feeling that the phone doesn't work I bricked mine not so long ago and I fixed everything.
Yes, I've flash with Mi flash tool.
And the flash was ok with no error.
Do you really think it's different with fastboot ?
Can you give me the way (and eventually links for rom,...) for flash with ADB ?
I appreciate your help.
Thank you
The problem is kwnow on many forums.
This smartphone have many network problems... but I don't find THE solution for repair mine...
https://forum.xda-developers.com/mi-a2-lite/help/april-update-lost-network-edge-3g-4g-t3926141
https://forum.xda-developers.com/mi-a2-lite/help/network-problem-dont-ignore-t3895879
https://forum.xda-developers.com/mi-a2-lite/help/slot-2-sim-registering-network-t3829654
...
with these problems I think Ill never update to 9
its actually works everything well in latest 8.1
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?
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!
Thanks to VD171 for his post.
I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.
Learn more about it in this video
reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?
mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.
no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked
reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.
Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.
reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.
if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.
{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.