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?
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
[/CENTER]
Credits:
- TWRP Team
Device: Lenovo Tab3 7 Tablet - TB3-730X
Do not flash this on TB3-730F. The F model has different chipset and this recovery will softbrick it.
@sun_dream reported that 730F is working. So you can probably flash it, but be prepared with OFW, in case something goes wrong.
Instructions:
IMPORTANT: read all instructions at least once, before starting.
Note: If you're are a newbie, you can read more detailed instructions by honzazkrumlova here
- Download from link below.
- Enable "USB debugging" from developer options.
- Enable "OEM Unlocking" from developer options.
- Reboot device in Fastboot Mode (Bootloader mode), either with "adb reboot bootloader" or with VolDown+Power, to enter Recovery mode and then select "Reboot into bootloader"
- Unlock the bootloader with "fastboot flashing unlock" or "fastboot oem unlock" and follow the instructions on the tablet. (WARNING: This will erase all your data - Factory Reset)
- Once unlocked, you can use "fastboot boot TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img" to start TWRP.
- When TWRP ask to modify system partition, answer "NO". Otherwise you will soft-brick your device and you will have to flash the original firmware and start from the beginning.
- If you want root - flash SuperSU, or as the user @Kellicros reported, you can flash Magisk 11.1.
- If you want XPosed, get it here.
- If you want to permanently flash the recovery, use "fastboot flash recovery TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img".
- If you use it on any other Lenovo Tab3 7 device, please post the model.
- Thanks is always welcome.
Downloads:
TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.zip (well tested, consider it stable)
TWRP_3.1.1_Lenovo_TB3-730X_Android-6.0_recovery.zip
Unbrick your device:
Follow this thread
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
beldy said:
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
Click to expand...
Click to collapse
Hi.
When TWRP is started for the first time, it asks to modify the system partition.
I answered NO, NEVER. I saw some posts about other MTK devices and other people seems to have problems like yours when TWRP modify the system partition.
Is this your case?
If yes, then you need to download the original firmware and flash it on the device. After that you need to flash the recovery again.
I've downloaded the original firmware from Russian forum (this post: http://4pda.ru/forum/index.php?showtopic=731493&st=20#entry52434543). Here is direct link: https://cloud.mail.ru/public/Fjd9/u7e8mUbhq )
This is the last TB3-730X firmware. Do not try 710 firmwares, they should not work and it is probably dangerous to flash it. I dont know for 730F, this one could work, but anyway, download the the 730X firmware from the link above.
I guess you will need the SPFlash Tool to flash the firmware.
Hope this helps.
Thank you for the link ...
so probably it is my case that TWRP modify the system partition ... try this firmware and send the result ..
Thanks again for your help, I appreciate it.
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
DonKapselo said:
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
Click to expand...
Click to collapse
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
beldy said:
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
Click to expand...
Click to collapse
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
0xAF said:
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
Click to expand...
Click to collapse
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
DonKapselo said:
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
Click to expand...
Click to collapse
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
Error 0×7D4
Message: BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL
Meaning: SP Flash tool encountered an error writing to the phone
Solution
* Try using a different USB cord, PC port and PC
* Use the latest version of SP flash tool
* Ensure the battery is well charged and the phone's USB port isn't faulty
Click to expand...
Click to collapse
But I guess it's not very helpful.
0xAF said:
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
But I guess it's not very helpful.
Click to expand...
Click to collapse
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
DonKapselo said:
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
Click to expand...
Click to collapse
The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.
Thanks for info Any link to step by step how to replace kernet, what data change?
DonKapselo said:
Thanks for info Any link to step by step how to replace kernet, what data change?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.
Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/
The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.
Many thanks!
0xAF said:
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
Click to expand...
Click to collapse
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
beldy said:
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
Click to expand...
Click to collapse
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
0xAF said:
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
Click to expand...
Click to collapse
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
beldy said:
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Click to expand...
Click to collapse
You should try to flash the dump with "fastboot flash system <file>"
Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
ayadmanhal said:
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
Click to expand...
Click to collapse
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
mrmazak said:
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
Click to expand...
Click to collapse
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
{
"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"
}
ayadmanhal said:
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
Click to expand...
Click to collapse
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
crayonicle said:
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
Click to expand...
Click to collapse
i did everything but nothing changed
ihave installed all IMGs
nothing happened and my phone still empty !
i trying to flash [OpenKirin's RROS ] room
it says succes but when im reboot still rebooting into recovery mode {twrp} 3.1.1.0
and my storage still empty
idk what i have to do
im think we have nothing to do !?
dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
i think we loose our devices <\3
crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
ayadmanhal said:
i think we loose our devices <\3
Click to expand...
Click to collapse
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
dutyyaknow said:
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
Click to expand...
Click to collapse
we cant go to huawei center bcz the phone unlocked and rooted
so the phone has no Guarantee and they will see the boot when says the device is not trusted <\3
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
dutyyaknow said:
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
Click to expand...
Click to collapse
my device only auto booting for twrp nothing more
up
no help :\
ayadmanhal said:
no help :\
Click to expand...
Click to collapse
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
RSGI said:
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
Click to expand...
Click to collapse
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
dutyyaknow said:
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
Click to expand...
Click to collapse
Have you re-flash with Huawei Multi Tool, but first you must have file update.zip and extract update.app from http://pro-teammt.ru/firmware-database/?firmware_model=BND&firmware_page=0
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
ayadmanhal said:
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
Click to expand...
Click to collapse
you on Nougat? have try to upgrade to Oreo from this thread,
https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
there's maybe can fix your system file
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
...
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
mrmazak said:
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Click to expand...
Click to collapse
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
mrmazak said:
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
Click to expand...
Click to collapse
Yes, I think this is what happened with the MiFlash. My device was probably Willow. I sent it back to repair but I don't know yet if they will be willing to fix it.
douteiful said:
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
.
Click to expand...
Click to collapse
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
mrmazak said:
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Click to expand...
Click to collapse
Thanks, but I'm pretty sure I entered the command correctly and it was among the lines of "FAILED (status read failed (Too many links))". I have searched for the error but nobody seems to know the cause.
LoadOP2 said:
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
Click to expand...
Click to collapse
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
douteiful said:
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
Click to expand...
Click to collapse
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
I don't know if they changed it of it's because I had already unlocked a bootloader before (my previous Redmi Note 5) but it only asked to wait for 168 hours (7 days).
{
"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"
}
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
-You don't reboot to recovery after flashing twrp, it wont stick if you don't reboot it
-No problem for wiping system as ive done full wipe before, it will delete your os (needed for converting to cusrom)
-Tried to copy files into sdcard through twrp is not stable in my experience as i couldnt do it as well (not responding), i turned off device as well but it boot back to recovery quickly by it's own (im using latest twrp official), i dont force myself using adb anymore and just use external sdcard, copied rom directly with sdcard reader, install rom and got bootloop (back to recovery automatically, i format data and boot properly)
-You don't have system so turning off and try booting would be worst decision and because your twrp not stick, you can't go back neither
-Too many links is because adb commands is wrong
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
i think you dont need to wait anymore, im unlocking my redmi just a few minutes, maybe because new added verification at latest miui unlock
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
lol no.. it's 168 hours usually if you do everything correctly
you should rebout to twrp after flashing it , also you didn't flash vbmeta (i don't know what it does,but mine was fixed once i flash it)
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
On step 5, you can still boot into recovery, the button is Vol up+power, but you press voldown+power(as you mentioned) will bring you to fastboot and get into System is destroyed screen. System is destroyed screen is normal. You just need to flash VBMETA. Your biggest mistakes and caresless is you dont do your research thoroughly. Risk is yours.
Make an habit to place your file to sdcard and always flash DMVERITY after anything you have done inside TWRP. DMVERITY is a must. In your case, vbmeta itself disable that force encryption and if you flash this, youll be able to enter fastboot mode.
Too many links means you dont enter the command correctly.
On steps 7 eventually will bring your phone back. I guess you got the indian version of RN8 where many people experiencing and posted on telegrams about this issues that they are unable to flash miui stock roms when that System is destroyed screen happen and end up bricking the phone. The only way and safest way to prevent this is, to flash VBMETA if you got the System is destroyed screen. Do not ever flash miui roms using miflash until you flashed that VBMETA. Then you are good to go flashing any roms using miflash
Update, something weird happened. I just got a message from the service center telling me that the phone had no issues, and they even showed me a video of it working (same IMEI). Which is weird because I'm pretty sure I hard bricked it. My guess is that they unbricked it and didn't tell me for some reason. Either way they didn't charge me any money so I'm happy. I'll get my device back next week and I'll check the things that you told me, particularly the model (ginkgo/willow).
Got my phone today. It's working. I don't know how they fixed it, and it's also unlocked. Just for the record, the Xiaomi ADB tool identifies it as a ginkgo, and the model number is M1908C3JH which is apparently ginkgo as well. If so, why did this all happen then?
Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.
Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.
Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st
nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.
I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.
Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"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"
}
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms
First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.
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.