.
Sorry to bother everybody...
I just wanna know that can we flash non carrier firmware into a verizon moto z3 (xt 1929-17) as it can not be getting its boatloader unlocked?? Please help... M new here at xda ....
How is your phone now? Is it still stucked on lockscreen lockout? Is it still containing the exact version of miui? My guess is yes but I need a confirmation.
You can't access adb from lockscreen for an obvious purposes, not even MTP.
And what is the error says?
@Osmanism.91 please ask in that particular forum before you ask it elsewhere
.
You may try from recovery flash via mi flash pro. It will need a miui account and internet connection
Second approach is by erasing every lines up to something that says "fastboot erase boot". Keep those line downwards.
.
rodagola said:
you mean delete everything but "fastboot erase boot"? probably not going to do anything because that line also shown me an error before.
Click to expand...
Click to collapse
Not everything, just every checks. It will goes like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1 : Lines to be removed
If you specify every error messages you've encountered, it will help everyone.
rodagola said:
I loaded up mi flash pro before and hit the recovery button to go to that interface but the actual recovery interface within miflashpro didn't popup, do you recommend a specific miflashpro version and specific drivers? or is it because I haven't logged into a mi account yet? can it be a brand new mi account?
Also if I actually have the chance to download a recovery rom then go into this recovery miflashpro menu...I'm scared miflashpro might delete the personal data partition, at least on regular MiFlash there's a checkbox with "save user data"
Click to expand...
Click to collapse
You need to boot to recovery, of course. You're in vanilla, so I bet you still have the miui recovery. No need to be specific about miflash pro version, any version will do. It will work like an upgrade. It will require same level or more recent firmware. You can't revert your firmware this way: the server will refuse. I don't know about the account requirements, but it will be better to log in to your account there.
Figure 2 : MiFlashPro > Recovery Flash interface. My flash is rejected. IDK why. It's been rejected when I tried to upgrade from 12.0.6 to 12.5.1. Used first method to upgrade instead.There is that "Wipe user data" button, pretty self-explanatory.
.
rodagola said:
oh alright, recovery method could work as long as I dont click wipe data, however, how do I get to that screen you screenshoted? Since a Mi Account is a must, if I make an account today, you think will that let me work with that?
Click to expand...
Click to collapse
Boot to recovery, select "Connect to PC Suite", the 3rd option, control selection with volume rocker and select with power button. Depending on how is your device is connected, it will automatically detects the corresponding flash method. In this case, there will be this "Flash in recovery" button in the main interface. Just click that and select your ROM directory.
I don't know about account details, since I always use my account that have permission to get a device unlocked
rodagola said:
Hi all, I've had this issue for a while.
I have a RN8P Chinese running MIUI11.0.3 stable over Android9, however, I wanted to start customizing my experience but didn't mean to go 'too far'.. the issue is:
> I've never unlocked the bootloader on it, therefore no custom recovery available on it. But didn't mean to change this and wanted to keep stock ROM
> However, within my stock ROM, I wanted to have it as clean as possible from bloatware, so I went ahead and plugged the phone to my PC, installed adb, and started running commands with adb shell pm uninstall... I managed to uninstall quite a few useless apps but also thought uninstalling a system app called something like "yman" and another like "xman" was a good idea, oh boy it wasn't a good idea...
> Now the phone has some sort of soft brick. When it reboots and goes to the lock screen (I had it with swipe), I try to swipe up but the phone doesn't respond, and I think the yman and xman apps were responsible for this function, but are now uninstalled)
> I need a way to get my phone working normally. When going back to adb to reinstall these via commands, I get "unauthorized" when checking the phone status with 'adb devices', so no commands are accepted. I also went into the stock recovery mode and tried to run commands but it now shows "sideload" and will give error for every command, so I discarded this option
> Maybe I can run these commands through the fastboot menu somehow? However I don't know how (if even possible)
> If there's absolute no way to get this RN8P to receive the command to reinstall the same package that caused the trouble, then I think I could try flashing...
> I went and downloaded MiFlash, downloaded the corresponding same exact stable ROM on same region for fastboot, plugged my phone and checked SAVE USER DATA on the botton, in order to have the data partition intact, but MiFlash throws some errors. I read somewhere just click on the desired batch file while the phone is still plugged in and it might bypass MiFlash errors, but it didn't, then I tried redownloading drivers and from 3 different PCs, looked up why MiFlash was failing and found out perhaps deleting a few lines from the batch would fix it, but I kept getting further errors related to the next line and the errors were endless.
> Still with the flashing idea on MiFlash, I downloaded the other further Chinese fastboot ROMs, as in upgraded versions to Android10 and MIUI12 (instead of the exact versions the phone still had). But now I get same thing as before, endless errors keep coming up and the flash process won't go through.
> I really want to retain my personal data, so I was suggested to try MiFlashTool v2, however, I've heard that one has no option to save the data partition, so I haven't bothered yet, and before I move on to try, could anybody with experience tell me their experience?
> In general, would there be a way still for me to fix the phone without losing user data? Maybe there's hopes the phone can receive adb commands somehow still? I'm confident I can revive the phone very quick through adb, if only it still wanted to be adb friendly...
Thanks to any pros that might be out there and would save a junior
Click to expand...
Click to collapse
You said you have a RN8Pro Chinese.
Can you give us the full MIUI ROM filename that you're attempting to flash? We have to be sure you're flashing the correct ROM.
Also check if the MIUI ROM you downloaded isn't corrupted.
Compass.
.
rodagola said:
I downloaded "begonia_images_V11.0.3.0.QGGCNXM_20200518.0000.00_10.0_cn" which is supposed to be rn8p chinese fastboot miui11.0.3 a10. And from 2 different sources to try to make sure it wasn't corrupted. I don't know any actual way to check if the ROM is corrupted or not...
Before the soft brick, the phone had this exact same version but for a9 instead of a10. So I guess this is some sort of upgrade.
I'm now going to try downloading same thing but for the recovery version within miflashpro, just like what kekesed97 said
This could have a different output, so I'll update here
If this doesn't go successful, then I guess next step is trying SP flash tool? though I have no clue how to use that one
Click to expand...
Click to collapse
You downloaded a very old MIUI but it should work. Check the link below for a newer release. The latest fastboot for MIUI 12.0.x China is V12.0.5.0.QGGCNXM (if I didn't skip a version; the list is quite big). There's also MIUI 12.5.x China if you want the latest stable (MIUI 12.5.x Global is buggy so I'd skip MIUI 12.5.x for now).
https://xiaomifirmwareupdater.com/archive/miui/begonia/
Here is a YouTube playlist that might help you: https://www.youtube.com/playlist?list=PLLy0_Q3fJ1DLjE5Cx7uCD3yTxeTaUbiIo
Be careful when you flash so that you keep your data. If I remember well that author usually wipes data in his videos.
I don't know which package manager people with Windows are using these days, but I guess WinRar is a popular choice. WinRar should have a "test file" so you could try that to check for a corrupted download.
I can't help you with the flashing process on Windows since I don't use it. kekesed97 instructions or the YouTube playlist should work (I think the YouTube author uses different software for flashing, just so you know).
Compass.
.
rodagola said:
Hi again, I'm in MiFlashPro recovery section, and have downloaded the corresponding recovery ROM, it downloaded as zip. Now should I just browse and select it as is, or do I need to uncompress and select something else? My guess is select as is but would like to confirm. Thanks a lot for your tips so far dude.
Click to expand...
Click to collapse
No unzipping. Use it as is as it will be sent over your phone and flashing is done recovery side (put it simply, it's an ADB sideload, with restrictions)
rodagola said:
Moreover, there's an option to download an incremental zip (just the ota extra files instead of full zip) would you recommend that over full zip? would that fix the brick? My guess is not because it doesn't have all the apks on it, whereas the full one has all the apks so it can reinstall the uninstalled app that caused my brick, and probably the OTA version can't, but I'm NOT sure...
Click to expand...
Click to collapse
It only accepts recovery ROMs (2 gb ones). You are only allowed to flash greater version of your current firmware from the same ROM distribution. It's works like updating your phone when incremental update fails after all.
rodagola said:
Also, to add more detail, I was looking arond and found that MiFlash Tool could not be so friendly with phones running on Mediatek so it's more for Qualcomms... instead, SP flash tool is more meant for MediaTeks (so that makes me believe that's why my RN8P was having all sorts of errors with that "MiFlashTool"). Anyway, I'll stay away from SP flash tool aswell because I read it always wipes everything. So my only real chance now seems to be the Recovery method on MiFlashPro, but I'd love if you confirmed my inquiry mentioned above
Click to expand...
Click to collapse
Not quite correct. There are 3 different flashing methods there. Recovery mode, fastboot mode, and deep flash mode.
In recovery mode, flash is using ADB sideload-like mechanics (or it is? I have no evidence, but it works similiarly that way), while in the Mi Flash program is using fastboot method. Both methods are platform-independent, which means it will work in both MTK or SD chipsets, as long as the phone permits. As for deep flash one, it will require lower level access to hardwares, and only manufacturers are having such access. Thus, flashing method diverges. MTK is using SP Flash tools, in which the mechanics behind that can be red in the CFW Megathread (CFW is quite irrelevant today, but the boot process explanation is something else that will never went irrelevant, unless another boot sequence is introduced), as for SD chipsets will use QPST over Sahara Protocol (more info on this: just dig how to ressurect xiaomi redmi note 5 pro edl 9008 that have their arb lock triggered).
It isn't that it will wipe your phone clean that to be your concern. That can be avoided by selecting "Download Only". But that there is this method requires a special account that only service centres have (but a bypass method is known recently, just dig deeper). Consider this as your last resort. Oh yes, it will need a fastboot rom, and the scatter file is available in the ROM directory.
.
rodagola said:
Hi again, I'm now in recovery mode in MiFlashPro and have attempted browsing the files I downloaded from https://xiaomifirmwareupdater.com
The files I choose were recovery roms with "stable branch" ( I don't know if weekly branch would work better?). Well, I loaded the stable ones into the menu and xiaomi servers authenticated and checked the rom... but then it throws "Sorry, flash to this stable version is not allowed" error.
What is this... I first tried with my downloaded zip package "miui_BEGONIA_V11.0.3.0.QGGCNXM_b656ebe642_10.0"
which is 1 step forward from the version I had (I had v11.0.3 with A9 but this package should update me to A10)
got the error... then tried with a little further update with another zip I downloaded "miui_BEGONIA_V12.0.2.0.QGGCNXM_972f66522c_10.0"
Same error again after xiaomi servers check it out.
There only seems to be a few more stable ROM versions for my chinese variant AFTER these. Those are: "V12.0.3.0.QGGCNXM", "V12.0.4.0.QGGCNXM", "V12.0.5.0.QGGCNXM" and "V12.5.1.0.RGGCNXM".
Before I try with these next 4 versions, from older to newer, I'd like to ask if should I rather try with BETA versions instead of stables... (since the error I was getting says: "Sorry, flash to this stable version is not allowed")
Anyways, I have read somewhere that with an authorized account it would let me install betas and stuff no problem, however those 2 that I tried to install weren't even betas. So I'm confused.
Thanks a lot again for your help dude
Click to expand...
Click to collapse
Don't do that.
Weekly is beta and doesn't mean it's better. It's supposed to be a test version and bug hunting release to device enthusiast so xiaomi can go fix it and accumulate the bug fixes to be included in the next stable version. Weekly is always newer so moving from beta to stable is considered downgrade, which require a data wipe. Btw, is your current firmware is from stable branch?
Or perhaps is it because your account doesn't hold a permission to flash since it's never been granted bootloader unlock permission? Idk about the account part.
Well, now try to use fastboot method if recovery update method fails. Mi Flash Pro have it so you don't have to download another tool. It allows broader range of firmware version, particularly for this phone.
Download a recovery rom and unzip it. Load it to mi flash, boot your phone to fastboot, and flash it there.
Figure 3: Mi Flash main interface. Choose this option to retain dataOr modify a flash batch file as I instructed in previous post and run it through command prompt.
I never flashed anything in a locked bootloader because I always unlock my phone the moment I grab it. But one thing for sure is you are bound to the same ROM region. Never flash any other ROM from another region distribution. You have been warned.
.
.
rodagola said:
Also, reading other threads, I should quote this guy called "zqm" on xda forums. From this post: https://forum.xda-developers.com/t/is-mi-unlock-really-needed-to-unlock-bootloader.4024519/
I quote his input: "This shouldn't be a concern for now. Xiaomi isn't planning to restrict unlocking the bootloader. Another thing you should consider is that Redmi note 8 pro gets easily bricked by flashing custom twrp, magisk, etc. but it's not easily recovered as it requires xiaomi authorised account."
So he's implying you need an auth account for recovery ROMs, (I think)......
I'm reposting this for you because you said you didn't know about the account requirements, maybe this brings forward a theory. However I insist I might need to borrow an authorized account now but don't know where or how
Click to expand...
Click to collapse
No, that one thing is different. What @zaqm talking about is the one to access the low level parts of hardware i.e. deep flash via SPFT, which only the manufacturers have, perhaps xiaomi engineering team and service center team to name a few. Adb sideload and fastboot is user accessible, so it doesn't need such permission, with limited access to emmc partitions (afaik no raw readback is one of its limitation). And fastboot doesn't enforce any account security measure, so does the adb sideload. That thing is implemented via mi recovery and mi flash pro. It will send an sha check to one of xiaomi server, returning if the phone is ok to be flashed. After the check returned true, it will begin to send the zip file to phone. This procedure is non-skippable. Therefore, you can only send firmwares this way. This is not happening in custom recovery, so you can send any command. But unfortunately you have vanilla.
After a quick inspection, that is indeed ADB sideload.
It refuse adb sideload command on redmi note 5 pro with vanilla recovery, unlocked bootloader (see attachment). After the command is issued, the phone immidiately restart and boot to system. It's likely won't hurt, so I think it worth the shot.
Try this :
1. Connect your phone to phone thru pc suite mode in recovery
2. Download minimal adb and fastboot or adb platform tools. Extract it.
3. Check your device by executing this in command prompt:
Code:
adb devices
4. If your device is connected, command prompt will return this:
Code:
D:\begonia\Minimal ADB and Fastboot>adb devices
List of devices attached
3d9ac49b sideload
5. Rename your firmware to something easy (something like update.zip but I don't care) and copy it to the same directory as the adb directory
6. Execute sideload command
Apache config:
adb sideload update.zip
7. See if wonder happens
8. ...
9. Profit?!
Anyway write back if this you succeed or not.
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
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:
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
{
"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"
}
kvas said:
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
Click to expand...
Click to collapse
Pics wont appear in thread from hosting
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
I thought I came across a tutorial somewhere that allows USB debugging to be bypassed
Phalanx7621 said:
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
Click to expand...
Click to collapse
Is there an option to enable USB debugging mode in recovery or through ADB? I can't even remember if I had debugging mode enabled.... My device was shipped through Verizon in Oct 2016, so it is bootloader locked anyway... It seems to be communicating with my laptop in CMD adp sideload, but Im not 100% sure.
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Thanks for the reply!
altwu said:
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Click to expand...
Click to collapse
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
kvas said:
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
Click to expand...
Click to collapse
there are 2 methods to flash android to your phone.
flash the factory image. the factory image zip contains a script that takes care of the flashing. it's basically several fastboot commands. to prevent data from getting wiped, the script needs to be edited to remove the -w option from the last fastboot command. the instructions you've seen that mention this are ones for flashing a factory image. but your bootloader needs to be unlocked to do this. since yours isn't, this isn't an option for you.
flash the ota zip. this is done with an adb sideload command. according to google's ota page(http://developers.google.com/android/ota), "This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." unlike flashing a full factory image, no extra steps are needed to prevent data from getting wiped.
i don't think one option is better than the other. some people here prefer to flash the ota, others prefer to flash the full factory image. i've been going with the factory image route ever since nougat and i can confirm that the script edit needed to prevent a data wipe works. but for you, since your bootloader is locked, you have only one option and that's to flash an ota. the instructions for flashing an ota are on google's ota page that i gave a link to or in the guide i mentioned in my previous reply.
Yup, that explains it. I wasn't clear about the instructions of the OTA method because on the developers site for Google it both talks about sideloading and enabling usb debugging in the options menu. Since I can't access my setting because my phone is soft bricked I have to use sideloader through the ADB. What I am also not clear on is the OTA for my situation. I gathered that the OTA flash was for Pixels that wouldnt take and update in a non-soft bricked phone. At this point I have no choice but to try. I talked to someone at Google and he sat on the phone for over an hour and a half with me helping me research this method. (THANKS GOOGLE))). Although I read that after the last Pie update many peoples phones became bricked so at least it shows they care. I just hope the OTA flash is provisioned for a soft bricked device. But in this business I realize nothing is guaranteed. I just wish I could locate someone who tried this on thier device so they could give some pointers....
We can all agree, if your phone is bootloader LOCKED do not do a factory flash if attempting to retain any data. Editing the script (-W) will only work with a bootloader UNLOCKED device. Long live the Pixel
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
kvas said:
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
Click to expand...
Click to collapse
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
sb1893 said:
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
Click to expand...
Click to collapse
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
sb1893 said:
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
Click to expand...
Click to collapse
You guys make the XDA community look good.
kudos to each of you.
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
kvas said:
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
Click to expand...
Click to collapse
Bummer - that stinks. Sounds like we are close. Out of curiousity - can you post the exact/full text (or a picture if you have a camera or second device) of that screen that shows "Your data may be corrupt"...the only "corrupt" message I am familiar with is from the Bootloader unlocked warning screen. So - want to see what specific error message you are getting.
Sorry again you weren't able to recover your device.
I tried to post a all the pictures I have taken, but the hosting site wont show them. Is there a better way to show the pics?
I just attach pics using the reply screen...Like this....
sb1893 said:
I just attach pics using the reply screen...Like this....
Click to expand...
Click to collapse
Hopefully this works... Google Pixel XL flashing OTA
kvas said:
Hopefully this works... Google Pixel XL flashing OTA
Click to expand...
Click to collapse
So you power up the device and it works on booting for a little while and then immediately drops you into that recovery screen? It doesn't give you a message when the boot fails before launching recovery?
Also - that OTA file looks to be the August 2018 OTA file, not September 2018 - which is what I thought you were trying to sideload...
I did end up flashing the latest OTA.. It let both of them install. I flashed the same one on my phone, then I flashed the newest on on the list of google developers site. PPR2. 180905.006.A1. That is what is has now. I am still stumped as to why it won't work. I'm sure it needs a full factory flash, but I cant do it because its locked. So even if I wanted to recover the files I can't. Even if I could recover the files somehow without further flashing the files would be encrypted and useless. I could either wait to see if another option is available in the future, or factory reset it losing all my precious files. Extremely frustrating. Also, Why didnt google send me a notice about the September update? I never updated this month. Probably why it froze while in Hangouts
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?
DISCLAIMERS (please read !)
This thread is made for the Redmi Note 9, also known as Redmi 10X 4G.
This device's codename is Merlin.
I will not be held responsible if you brick your device.
Follow the instructions shown in this thread at your own risks.
Follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded files.
Feel free to cite parts of this thread in your own, just make sure to give credit where it's due.
Prerequisites for most manipulations
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Tutorials
Spoiler: Unlocking your bootloader (Required for all other tutorials below)
Step 1
Make sure you have a Mi Account ready.
You should've created one when first setting up your phone, with your phone number and a password.
- If you have it: Double-check you have access to it by attempting to connect on Xiaomi's official website (Login page).
- If you don't: Create one with the Create an account button below the password form (same link as above), then connect to it.
Step 2
On your PC, go to Xiaomi's unlock page and click the colored Download Mi Unlock button.
{
"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"
}
Step 3
A download should start. Wait for it to finish, move the archive to your desktop and extract its content.
Step 4
Inside the extracted folder, double click the file called miflash_unlock.exe to start Xiaomi's Unlocking program.
Step 5
Read Xiaomi's Disclaimer then agree to their terms, or stop here and leave this thread if you don't.
Step 6
Sign in to your Mi Account we talked about in Step 1.
Step 7
Let's get your phone ready for unlocking.
Go to your phone's Settings > Mi Account and make sure you're logged in.
Now Settings > About Phone and tap the "MIUI Version" box multiple times until it says You are now a developer!
And finally Settings > Additional Settings > Developer Options
Enable the following settings inside Developer Options, and click Accept when warnings pop-up:
OEM Unlocking
USB Debugging
Still in Developer Options, check your Mi Unlock status and click the Add account and device button at the bottom if present.
Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 8
Alright, all backed up? Confident? Let's get going with the final steps.
Turn off your phone.
Turn it back on into fastboot mode by holding down the Power button AND Volume Down together until it vibrates, you may then let go of the Power Button, but keep Volume Down held until you see the fastboot image on your phone.
Connect your phone to your computer with the USB Cable.
Xiaomi's Software should detect it. If not, click on the cog-wheel in the top right, click the Check button to install the driver and follow instructions, then keep going.
Click Unlock, and follow the instructions!
Now there are two possible scenarios
Either you've done all this before and can have your phone unlocked right away.
Or this is the first time and at the end of the progress it'll ask you to wait ~7days, and, well, there's no way around that, so come back in 7 days and start from Step 8 again.
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install custom ROMs/recovery!
Spoiler: Rooting (Magisk)
Step 1
Download the latest Magisk .apk on your phone.
Go to the link above, click the latest (topmost) Magisk-vXX.X.apk you see in the list to start the download, open the file and install it.
Step 2
Go to the download page for the MIUI Official Rom for your region, make sure to get the fastboot version.
OR (if you don't want/can't download 3gb of ROM)
Follow DavitidzeSh's instructions on how to gather the boot.img and vbmeta.img files and SKIP to Step 5.
OR (if you're on a custom rom)
Look into your custom rom's .zip, find the boot.img and vbmeta.img files and SKIP to Step 5.
Step 3
Take the file you downloaded above, it should be a .tgz archive.
Extract it, you'll get a .tar achive.
Extract that one again.
Step 4
You should now have a folder similar to the one below
Go inside the images folder
Step 5
Grab the the vbmeta.img file and copy it to your ADB & Fastboot (Platform Tools) folder.
Grab the boot.img file and copy it to your phone's internal storage.
(where the Android, DCIM, Download, and more are present, just drop it in there)
Here's how it should look inside your phone's storage in the end.
Step 6
On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 7
Link your phone to your PC, grab the file made by Magisk Manager.
It's located in your phone's downloads folder, called magisk_patched.img.
Copy and paste it where your ADB & Fastboot (Platform Tools) are located.
You should now have a folder structure like this:
adb.exe
fastboot.exe
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8
Alright, we're ready to root!
Turn off your phone, then get in fastboot mode.
(Power + Volume Down, like the unlocking tutorial)
Step 9
Link your phone to your PC with the USB cable if not done already.
Step 10
Shift + Right click in an empty space inside the folder we prepared in Step 7,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe devices
Click to expand...
Click to collapse
Make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
.\fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
.\fastboot.exe flash boot .\magisk_patched.img
.\fastboot.exe reboot
Click to expand...
Click to collapse
Note: Your PowerShell window will look different, I'm using a different program, don't worry
Your phone will reboot.
Open up Magisk Manager, and double check that it's installed.
You're done!
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is rooted.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Getting EdXposed
I very much discourage to EdXposed your phone unless you have a very good reason for it.
It's a pain to pass SafetyNet.
It doesn't get updated often.
It has very niche use cases for which it's actually worth it.
That said, I explain it here for people who know what they're getting into and want instructions on how to do it.
This procedure requires to be rooted with Magisk.
Step 1
Inside Magisk Manager, go to the Modules tab.
Click the search button (bottom right) and search Riru.
Install the Riru module by Rikka.
Activate it and Reboot.
Step 2
Download and install the latest EdXposed Manager, the same way you did with Magisk Manager when rooting.
Step 3
Open it up, go to the ALPHA tab and click install/update.
It'll start a file download.
Step 4
Go back to Magisk Manager, Modules tab, except this time click Install from Storage.
Point to the .zip file you just got, located in the Downloads folder of your phone.
At the end of the installation, click reboot.
Step 5
Let's double check your installation is operational.
Go to EdXposed Manager, first tab.
It should say EdXposed Framework is active.
You're done!
You should now be able to install EdXposed modules.
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is EdXposed.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Passing SafetyNet (Magisk/EdXposed)
For Magisk Rooted Phones
Enable Magisk Hide inside Magisk Manager's settings.
You may also need to use the Props module to spoof your phone as another, if you want a tutorial on that, let me know.
For EdXposed Phones
Again, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework
Reboot and enjoy! You're all set and SafetyNet should pass.
Spoiler: Installing GSI's (Non-device specific ROMs)
Step 1
Pick your poison in the Treble Forums!
My recommendations are in the Extras section of this post.
Step 2
Download the chosen ROM's A/B Arm64 version
It should be an .img.xz file
Extract it and you'll get an .img file.
You're almost ready to flash.
Make sure to backup your phone's data.
Continuing this tutorial will wipe your phone!
Step 3
Put your phone into fastboot mode.
(Power + Volume Down)
Connect it to your PC.
Step 4
Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder.
Rename it to system.img
Step 5
Shift + Right click in an empty space inside the folder,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe reboot fastboot
.\fastboot.exe --disable-verification flash vbmeta .\vbmeta.img
.\fastboot.exe flash system .\system.img
.\fastboot.exe -w
.\fastboot.exe reboot
Click to expand...
Click to collapse
Your phone will now reboot on its own.
Set it all up and enjoy!
That said, depending on how old the GSI you picked is, you MAY have issues leaving it at that.
Therefore, I highly recommend checking out the next tutorial section about Fixing GSI Issues.
Spoiler: Fixing brightness/jack on older GSI's
I have worked together with a developer to bring fixes for our device to every custom GSI rom out there.
The most recent GSI's shouldn't need the fixes listed below.
Older GSI (treble) roms have two known bugs that we can fix:
The brightness slider being misscalibrated, and therefore auto-brightness broken too.
The headphone jack not working.
You need to be rooted to do so.
Step 1 - Get yourself a Terminal Emulator, I recommend Termux
Step 2 - Type the following commands inside of it, line by line, in order:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
Click to expand...
Click to collapse
You're done! Brightness should be fine, headphones get detected, enjoy!
Spoiler: Resetting your phone
Backup all the data you might have on your phone to restore it after the manipulation!
Step 1
Download the fastboot ROM corresponding to your region here.
(The same one used to grab the boot.img and vbmeta.img when rooting)
And extract it.
Step 2
Download the latest MiFlashTool.
And extract it.
Step 3
Put your device in fastboot mode.
(Power + Vol Down, refer to the rooting tutorial for a more info)
And connect it to your computer via USB.
Step 4
Open MiFlashTool (XiaoMiFlash.exe), your device should appear in the list.
Step 5
Click the Select button in the top left,
And point to your fastboot ROM's folder
(The one containing the "AP", "BP", "BP_IN", "images" folders and a bunch of files)
Step 6
At the bottom right of the software, choose if you either want to just:
clean all
(wipe and re-install)
OR
clean all and lock
(wipe, reinstall and re-lock your bootloader)
Note: If you re-lock your bootloader but wish to unlock it again later, you won't have to wait the 7 days again.
Step 7
Finally, in the top right, click the flash button.
Now just wait a while, your phone will reboot on the stock rom and you're good to go!
Extras
Spoiler: Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not, it's easily reversable too, check the "Resetting your phone" tutorial.
Q: I rooted/EdXposed my phone and now Netflix won't even open, or doesn't work properly, what's up with that?
A: There's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Q: I tried unlocking my bootloader but, Mi Flash Unlock doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
Try another USB port.
Try another USB cable.
Install the Mi USB Drivers manually, they're included in the MiFlashUnlock folder.
Run the driver_install_64.exe, OR go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install.
In the Device Manager, check that the driver provider is Xiaomi.
If not, uninstall it and restart your computer.
RESERVED
Akitake said:
RESERVED
Click to expand...
Click to collapse
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.
Yxnq_Param said:
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.
Click to expand...
Click to collapse
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks
HemanthJabalpuri said:
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks
Click to expand...
Click to collapse
Anti-rollback is only an issue if you're trying to downgrade through the stock recovery (Vol + Up) or through MIUI's recovery (About Phone > MIUI Version > Three dots and there is an option there)
If you want to go back to MIUI 11 for some reason, you can, by flashing it through fastboot.
HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1 - Google, this isn't Merlin specific.
2 - No, you can go back directly to the latest MIUI for your device.
3 - Just start over, your device will remain in fastboot, it's actually really safe.
4 - That's a niche demand, 99% of people use Windows and, if you use something else it's on you. If you're a Linux user, you're used googling information and it's not a problem. And for mac, well, worst case scenario use someone else's pc for 10 minutes.
5 - To prevent boot-loops. If you don't flash vbmeta, it won't boot.
6 - Read disclaimers, the tutorial literally tells you to take the vbmeta from the official rom. There's no such thing as a modified vbmeta, what matters is how we flash it with fastboot, disabling verifications.
Also this is my first post, and I'll add more as time goes on. But even as it is, I think it's miles better than what people care to create for most devices on XDA. It's also pretty detailed with images and such to reassure the user.
can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?
markevan12 said:
can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?
Click to expand...
Click to collapse
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.
hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?
fachrizoyy said:
hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?
Click to expand...
Click to collapse
I will not support custom recovery's. I highly dislike them, and they're unofficial for Merlin as well.
Thx for the answer
Akitake said:
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.
Click to expand...
Click to collapse
thanks but I solved it by moving the unlock folder to C:
Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?
mirzanuman6612 said:
Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?
Click to expand...
Click to collapse
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.
Akitake said:
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.
Click to expand...
Click to collapse
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.
Akitake said:
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.
Click to expand...
Click to collapse
Alrighty, thanks for your replies.
mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Had you tried moving the unlock folder to c:/ ?
markevan12 said:
Had you tried moving the unlock folder to c:/ ?
Click to expand...
Click to collapse
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.
mirzanuman6612 said:
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.
Click to expand...
Click to collapse
Nope I didn't YET, I'm still waiting for the unlock to complete. I did tried treble roms in my other device. It just is basically have the same performance (LOSQ) but I had heating problems in my Samsung device, I expect a normal experience with this ROMs.