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
Related
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
==============================
Well, got it figured out... But had to pay for it....
First of all:
{
"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"
}
You SUCK. Thanks for NOTHING
Lastly:
Thank YOU!!!
Long story short, i've solved it but have to pay for it.
Went to HUAWEI Service Center here in Portugal, and they told me that they couldn't do anything since the phone was not marketed for Europe (??????) [ASS Os]
I've discovered this service, and as with any other service online, i get suspicious for a while, asked a lot of questions and decided:
Bought a Month Pass for 50 EUD (45 Euros), and voila, in the first try unbricked the phone
Now i have the rest of the month to play with it...
Thanks for the people of FunkyHuawei for the kind attention (mostly pacience) they had with me.
I recommend it :good::good::good::good::good:
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
Do you still have access to twrp?
It could be only hope.
I had frp lock problem after unlocking bootloader. I had hit reset to default setting while inside developer options menu. That flipped the oem unlock switch.
I had to use twrp to flash back the stock boot.img and stock recovery.img then i was able to oem relock (my code).
And boot into room and reflip oem unlock toggle
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
help
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
RSGI said:
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
Click to expand...
Click to collapse
If you tried to install exposed from twrp, it should still be there
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Sudeep Duhoon said:
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Click to expand...
Click to collapse
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
mrmazak said:
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
Click to expand...
Click to collapse
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
RSGI said:
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
Click to expand...
Click to collapse
Ok, I see
Didn't know you where 2 or 3 miss- steps past a failed exposed install.
I have no idea which service to recommend.
Hi,
Hope OP got his solution.
@matt4321
Honorable mod, I guess this thread belongs to Honor 7X Q&A forum. Please relocate.
Cheers
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
can't you install image from fastboot, if so try to flash rr or aosp system.img or extract from update.app
11122314 said:
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
Click to expand...
Click to collapse
Tried that but the only response that fastboot gives me is "Command not allowed" .
I just can´t flash anything in fastboot. I think i can thought adb shell dd (at least that how i manage to screw twrp partition), but i just can´t get ADB connection.
Just got fastboot connection with HiSuite drivers...
How can i get ADB access? It just installs an USB Storage Device...
Also i can try update via fastboot but it saying that it misses android-info.txt file.... whatever that means...
If i could boot once into the ROM, i would enable "Allow OEM Unlocking" and do exactly that.... btut i junt can´t... not yet...
11122314 said:
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
Click to expand...
Click to collapse
That was my plan... but even that is screwed-up.....
Here is my Recovery Status, without the possibility to flash any img via fastboot:
recovery_ramdisk (empty or in-error)
erecovery_ramdisk ( BND-RECOVERY-NoCheck.img flashed to update into EMUI 8.0)
With the software now, whats failling me is the ****ing recovery, that flash only 5% before it shows this error : "Install update failed!"
Dont have ADB support, maybe because i dont have the "USB Debbuging" option enable...
It seems that i will spend 15 euros to unlock this &%/())(/&%$######()/=?(/%&$#
Just thought I'd post here in case you are still in need. I believe that there are two different recovery modes - one that is triggered by holding power, up vol, and down vol, and another that is triggered by holding just power and up vol. Are you sure twrp is gone? I thought I had lost twrp when in fact it was in the other recovery.
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Sudeep Duhoon said:
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Click to expand...
Click to collapse
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
RSGI said:
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
Click to expand...
Click to collapse
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
mrmazak said:
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
Click to expand...
Click to collapse
Hi
Thank you for replying.
Already tried that.... Actually the command should be:
Code:
fastboot oem frp-unlock (unlock frp key)
Bought the unlock code from an online unlock store.
Spent 10 euros. The code is correct cause i got the message that the device will reboot and do a factory reset.
Than it reboots into an error screen, cause i screwed up the "recovery_ramdisk" partition earlier and its not working now. So, no factory reset, no changing the Frp status... Still locked.
Still no flashing img files from recovery... Still got the reply oficial Command Not Allowed...
But:
I'm trying to gain adb access while on eRecovery.
Than i could try to flash the stock recovery with the code dd command. From there i would unlock the Frp with the code and the Factory Reset might be enought to fix the bootloop.
Also the bootloop it self...
I wonder if there's a way to force the boot even with FC errors....
Access to the ROM software would allow me to flash the stock recovery and then make a factory reset, by changing the OEM Unlocking status
Thanks for your reply, maybe you can give me some tips on this 2 ways that i'm exploring right now.
Or some other ways that i haven't consider yet... please....
:cyclops::cyclops:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Help Required - Soft brick - Stuck in bootloader
Dear All, Would really appreciate if you can help me with this thread..
Thanks
Regards
Tarun
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
Try to switch the slot to B and then boot
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
amusing_ankesh said:
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
Click to expand...
Click to collapse
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
same
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that ?
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot customrecovery.img
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
kristoff07 said:
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
Click to expand...
Click to collapse
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
secure boot yes? you may have vertified boot, you can try flash patched magisk boot.img to disable that
jjgvv said:
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
Click to expand...
Click to collapse
I checked the info and it gave me 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"
}
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 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?
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.