Folks
Really need some help before I totally give up on my "baby" Nexus 7
- Nexus 7 2013 Wifi only
- (was running) CM12.1 Official Nightlies
Firstly
I tried to upgrade the system image using the Android 6 system image for "RazorG" as suggested
- Downloaded, started "flash-all.bat"
- erase userdata went on forever - I cant remember f I cancelled it or it timed out as I left it overnight
Bootloader (fastboot) was the only screen I could get to - there is no recovery and no system software
Fastboot commands (such as fastboot erase userdata) either takes forever or it errors "command write failed"
Secondly
Read everything similar to this problem all over the net and got loads of great ideas
- check USB ports and ADB versions (changed, checked, different computers etc etc)
- upgrade by hand i.e. individual commands rather than "flash-all", tried it but fastboot wont write
- Wugfresh NRT for "flash stock" - again errors on fastboot commands
- toggle the bootloader lock using "fastboot oem lock" (this worked) and "fastboot oem unlock" (this failed cos fastboot cant write to flash)
So now I have my N7, bootloader locked, fastboot wont write any commands or erase anything, Wug NRT doesnt do anything
Really need some experienced expert help here fellas - any ideas ?
Please let me know
The problem that started this is probably the fact that you used razorg factory image, which is the lte model while the WiFi model is razor.
As for fixing it i don't really know. As far as I know (which isn't that much), there isn't much you can do when your bootloader is locked.
Jtag service may help you but you can DIY
Order a motherboard on ebay. Cost is anywhere from 25 - 35 bucks.
Do it in 30 minutes. IFixit has a good guide.
Related
Hey all,
So I seem to have soft bricked my tablet (Nexus 7 2013 LTE). I can get into fastboot mode (but not into the recovery menu) then I am stuck on the Google logo. Does this mean the device is repairable?
Device manager on Windows shows the tablet as
- an unknown device (no drivers installed / Samsung (Wugfresh) / Google drivers)
- Android bootloader interface (Snoop05's tool)
- Android ADB Interface (PDAnet (Wugfresh)).
On all of them the driver is not correctly installed and I have the exclamation mark showing on device manager. I am unable to access the tablet via fastboot or ADB at this time.
I have tried every permutation I can think of so am turning to the hive mind for advice.
To compound matters I am in Turkey and I don't speak Turkish. I've been in an internet cafe for about 5 hours now and it's 1am (Turkish keyboards have an ı where i should be and you can imagine how many times I have mistyped). I am on a year long cycle tour and the tablet has my music, books, guidebooks and dictionaries on it so I am pretty hacked off. Especially given that I've only just arrived...
I did manage to connect via ADB yesterday but ran out of time as I was borrowing someone's computer and can't replicate the steps. Gah!
I have backups of all my data so essentially I would just like to factory reset. Any help gratefully received!
Thanks,
Don
Well, I found the right combination of drivers (Snoop05's tool then PDANet on Wugfresh) and can now see the device via fastboot so I have unlocked it. However whenever I try and flash boot / system / recovery, etc via fastboot I'm receiving an error 'remote: partition table doesn't exist'. Any ideas, people?
Probably useful to add that the problem was initially caused when I removed the SIM card whilst the unit was switched on. I received a message asking me to reboot and it has been bricked since. Also, I was runing stock unrooted.
Thanks
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Gulp! 100+ views and no replies...does no-one want to break it to me that my lovely tablet is beyond help! Is the only solution some wizardry using GParted or something? I'm already in way over my head.
I'm only bugging you all as I am running out of time in town and need to head off into the wilds. I have tonight and that's it for at least a week. It would be nice to have some company ie books and music...oh and a Turkish dictionary and translator...poor attempt to drum up sympathy I know.
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
dondelion said:
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Click to expand...
Click to collapse
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Raverbunny said:
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
Click to expand...
Click to collapse
Fastboot format still appears to require an intact partition table as I still receive an error - 'FAILED (command write failed (invalid argument))' but thank for the response.
LinearEquation said:
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this but same problem - no partition table so unable write anything to the device, thanks...
don, did you ever solve this?
I am having a similar problem but cannot unlock the device.
i have the same problem ....i just usedf flo-ebb clamours repartition and it wiped out all my partions i can only access fast boot but cant install anything as it says " no such partition "
Is your bootloader unlocked? If so, you should be able to flash the factory image in fastboot.
If not, you should be able to sideload the OTA in recovery.
Hi everyone,
It seems I was stupid enough to choose a wrong model (MediaPad M1) in TWRP Manager (downloaded from Google Play) while attempting to install TWRP recovery.
This resulted in an infinite bootloop where the "Huawei MediaPad" logo keeps appearing, the tablet restarts and again the same.
I do have access in Recovery and Bootloader mode, but all my attempts did not yield any results. Things I have tried so far:
- Download the Stock ROM from needrom.com (versions B009 and B019), extracted them and loaded the "dload" folder onto an SD card and executed recovery (by pressing both Vol UP/DOWN and starting the tablet). Even though the procedure seems to be perfoming normally, indicator reached successfully 100%, when the tablet restarts after the supposed successful recovery I am still left with the same bootloop.
My SD is a 64GB one, formatted with exFAT if this makes any difference.
- I have tried extracting UPDATE.APP using Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454) and tried to push via fastboot all necessary parts (i.e. BOOT.img, RECOVERY.img, SYSTEM.img, etc) but I get the "FAILED (remote: Command not allowed)" error message.
My bootloader was unlocked from the beginning (at least that's what showing when I enter bootleader/rescue mode with red letters - "PHONE UNLOCKED").
Any suggestions would be greatly appreciated! Thanks!
What commands are you using? It is peculiar that fastboot mode fails to flash. It may be that your bootloader is not properly unlocked even though it shows that it is.
If you have a bootloader unlock code for your device, I would suggest that you try explicitly unlocking the bootloader when in fastboot mode (it won't hurt to do this even if your bootloader is already unlocked):
Code:
fastboot oem unlock <YOUR_BOOTLOADER_UNLOCK_CODE>
Then you can verify that the bootloader is actually unlocked by issuing the following command:
Code:
fastboot oem get-bootinfo
If your bootloader is properly unlocked, then the previous command should return output similar to the following:
Code:
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.002s
At this point, let's try to restore your original BOOT partition and RECOVERY partition.
Now, gather the following partition images from your OEM firmware package:
BOOT.img
RECOVERY.img
SYSTEM.img
USERDATA.img
Only BOOT.img and RECOVERY.img should be needed to solve your issue, but we'll have SYSTEM.img and USERDATA.img ready and available here just in case our efforts fail with just boot and recovery alone.
Now erase and flash boot and recovery as follows (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot erase cache
fastboot reboot
Hopefully, at this point your bootloop issue is resolved and your ROM boots normally. If not, then read on.
Uh oh, time to flash SYSTEM.img and USERDATA.img too and see if that makes a difference. While we're at it, let's also reflash BOOT.img and RECOVERY.img. Use the following commands (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot erase system -w
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot flash userdata </path/to/oem/USERDATA.IMG>
fastboot flash system </path/to/oem/SYSTEM.IMG>
fastboot erase cache
fastboot reboot
...and hopefully now you're back up and running.
Good luck!
In case you don't have a unlock code and *already* bricked it, you can get the imei from fastboot as well. Simply send the following command from fastboot:
fastboot oem get-psid
Using the imei you can then request an unlock code from huawei on their web site.
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck. This is the log from that attempt:
===================================================================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type *#*#2846579#*#* for Qualcomm and Kirin based models, or *#*#14789632#*#* for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
===================================================================
DC - Unlocker 2 Client 1.00.1322
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI M2-803L
Model : Huawei phone in fastboot mode
Serial NR. : YVF4C15928000296
Firmware : V100R001C00B000
unlocked
Battery state: 3648mv
===================================================================
Factory reset protection Erase start
unknown error (398)
===================================================================
Since I already paid the €15 at DC Unlocker I decided to give a go using their other piece of software, DC Phoenix. This one allowed me to flash pieces of the UPDATE.app package while in fastboot mode, without complaining about locks. It seemed to be flasing normally (I tried flashing all contents of the latest UPDATE.app package) and then (as per DC’s instructions) I tried re-flashing everything using the second option (Upgrade Mode) while in Repair mode (i.e. Vol +/- pressed while powering the tablet).
No success either – Tried various combination of DC Phoenix – even only the files you suggested (BOOT & RECOVERY, BOOT & RECOVERY & USERDATA & SYSTEM).
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
manowar666 said:
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Click to expand...
Click to collapse
I did contact Huawei for an unlock code, myself - I sent emails to [email protected] and [email protected] and received a reply back from them the next day. Here is what they said:
Dear User,
Huawei Customer Service is pleased to be at your service.
Apology for any inconvenience.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website http://emui.huawei.com/en/ on your phone.
2.Log in your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than twice within 6 months.If you meet the criteria,please go to http://emui.huawei.com/en/ and click the 'download'button to login your Huawei ID other than any other third party ID to apply for the unlock code.Please contact us by mail or local service hotline as following if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, SN, IMEI/MEID and erro message in your e-mail.We also need to know that your phone is rooted, it can be out of the best working state and some of the functions may not be able to work normally. In additon, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. For the lack of testing,third party software may not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think twice.
If you have any other problems, please send your feedback to us. We will be at your service to help you to solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team
Click to expand...
Click to collapse
I didn't want to faff around with all that logging in nonsense for two weeks, and also the Huawei bootloader code site seemed to be offline (kept getting "Page not found" errors with the error page in Chinese characters and what was ostensibly an HTTP 600 error, which was why I contacted Huawei support over email), so I just ponied up about $4.25 for 4 dc-unlocker credits (4 euros) and got my bootloader unlock code from the dc-unlocker software. Neat, clean, easy and non-messy.
manowar666 said:
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
Click to expand...
Click to collapse
Yes, that does seem very odd. I would expect it to take at least some time in userspace (the "total time" field).
manowar666 said:
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck.
Click to expand...
Click to collapse
I find it very peculiar that your bootloader is unlocked but FRP is activated. I think that dc-unlocker does not give you the option to unlock the bootloader because FRP protection is still active - according to all guides, FRP must first be deactivated if you want to unlock the bootloader.
What does your phone say in the bootloader screen for the FRP? You'll find it directly under the "Phone Unlocked" text. It should say either "FRP Locked" in green or "FRP Unlock" in red.
manowar666 said:
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
Click to expand...
Click to collapse
There isn't, directly, but you can try to issue the fastboot command
Code:
fastboot oem frp-erase
although at this point I am not very hopeful that it will work.
FRP is nothing but the developer option to allow an OEM unlock of the phone - it is the option mentioned in this image in the Huawei "Unlock bootloader" guide thread.
Like I said, I find it very peculiar that FRP is enabled but the bootloader is "unlocked". Did you at any point reset the developer options or reflash the stock ROM before you soft-bricked the device? Did you pick up this phone second-hand/used or something?
I think that the root (excuse me, I couldn't resist) of all your problems is that FRP is still enabled, and this is what is causing your flash attempts to fail.
Here is the dc-unlocker guide to repair a bricked Huawei phone even if the bootloader and FRP are locked. If you follow this guide very carefully, maybe it can save you. Since you already seem to have tried "Method 1" of the guide, maybe you can try "Method 2".
Another suggestion I have is that you can contact the dc-unlocker guys for online chat support (when you see that the chat is online). They are very helpful, and since you've thrown so much money at them (be sure to mention that, just in case they don't know), they should be able to do something to help you out. Good luck, and I hope that you can get your phone back online...
I've been faced with all the same issues as the OP for the last 24 hours and thought all was lost. I had been through all the same stuff - every fastboot command and every key combination possible. I'd tried different tools and apps to get some life out of the device but no luck. I had even downloaded the ROM from beast.in.black's thread and extracted it to the SD card but it didn't do anything for me.
Worse still, the tablet was now out of juice. And as soon as I plugged it into the mains, the screen lit up and the all too familiar fastboot screen would stay on, meaning the tablet was barely charging long enough for me to try anything new with adb / fastboot or whatever.
So in trying to get the screen off and charge the tablet, while it was plugged in I held vol up / vol down / power together for 10 seconds. I was hoping this would leave the screen off (I had managed this earlier while plugged into USB) but instead it booted again. So I walked away for a minute, then came back expected to see the fastboot screen but no, it was in the middle of an EMUI software install. Huzzah! I left it to do its thing but at the end, it came up and said install failed and my only option was to press power to reboot. Sigh. So I pressed power and then got another surprise. The Huawei boot logo. The tablet was booting. A few seconds later I'm at the "Choose your regional settings & language" screen in the setup wizard. After trying everything under the sun, it turns out all I needed was the ROM on the SD card and to give the tablet the three-finger-salute while plugged into mains.
Happy days!
I found the Official M2-803L ROM!
For anyone who needs it, I've found an official download (direct from the Huawei China support site) for the M2-803L.
I've posted the ROM details here for anyone who needs this ROM.
Status update for anyone that might be interested: I was able to restore the tablet with the help of DC-Unlocker. I highly recommend them for any unlocking/restoring needs.
More specifically, I contected them via email and they were kind enough to give me credits (since I already paid them) in order to try again with Method 2 as per https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Step 2 of this method did not work for me (i.e. flashing in upgrade mode) but I was able to replace this step simply by re-flashing with DC Phoenix in fastboot mode.
After this, my IMEI was zeroed-out (that was a problem since this tablet is 4G-enabled thus I couldn't register on my provider's network) but I was also to fix that by using HCU-Client (had to purchase 8 more credits from DC-Unlocker).
All are working fine now.
Special thanks to @beast.in.black for pointing me towards the right direction!
Hey, I know that there are many threads with this issue. However none of them seem to work. My phone got stuck in a bootloop about a year ago - I just put it back in the box and threw it in a draw... - and it would be nice to fix this now.
So far I have installed the USB Drivers, ADB software and connected my phone and put it within Fastboot Mode. I can send commands to the phone successfully.
My issue is that I never enabled "OEM unlocking" whilst the phone was booted, can no longer do that due to being unable to boot it.
I have tried the following commands, none work:
fastboot flashing unlock
fastboot flash boot *image*
fastboot flash recovery *image*
fastboot format userdata
fastboot format cache
They all return the same error:
FAILED (remote: device is locked. Cannot flash images)
Click to expand...
Click to collapse
What are my options? Also, even if I manage to flash my device, will it get stuck in this bootloop again as I have read that it is possibly a hardware issue.
If it is a hardware issue, can I easily fix it or do I need tools for removing chips etc...
Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone
You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks
chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.
Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.
If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion
type fastboot devices and show me the result.
maybe you do not have correct fastboot driver
It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable
Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice
I've been trying to unlock the Bootloader for this day and seems that my Honor 9X (4 GB RAM, 128 GB Storage with one SIM and one SD Card Slot) can't get past the bootloader unlock. Since I wanted to change the ROM due to upcoming Harmony OS Update that might happen anytime. Plus, it would be easier for me if there was an official TWRP Support, but even the creators behind the project does not even offer an official build for it.
I am not an expert at coding the TWRP for my device itself, and I am not a Windows User since I changed the primary OS to Linux (to Ubuntu 20.04). Can't install HiSuite (even with wine, for some reason) and even with an unlock code, I cannot unlock the bootloader.
Here is what I tried so far:
Reboot the device into the Bootloader by using ADB (my easiest way)
Check if Fastboot recognized the device
Ran fastboot flashing unlock, fastboot oem unlock (my short unlock code), fastboot oem unlock
Restarted Fastboot multiple times using fastboot reboot-bootloader
For every command, Fastboot showed me either "invalid command" or "command not allowed". I don't know if I am doing anything wrong, but for some reason, Fastboot gives me an error if there is some command included with the words "oem" or "flash(-ing)". Tried wiping user data and cache with Fastboot and even this is a problem. Any command that might manipulate my phone won't let me perform the task that I want my phone to do.
Is my phone bootloader protected, or what is the issue that I cannot unlock it nor modify any contents?
I might address that using ADB from Recovery is not an option from me. Starting recovery (from ADB and the boot combination) and checking with ADB if the device is found. Nothing. Going into eRecovery changed only a bit, but ADB recognized my device this time. When my phone is in eRecovery, ADB finds the device, but it is unauthorized, meaning I cannot perform any tasks. If I don't get to know what this issue is causing, then I'll throw my phone out of the window.
BeChris100 said:
I've been trying to unlock the Bootloader for this day and seems that my Honor 9X (4 GB RAM, 128 GB Storage with one SIM and one SD Card Slot) can't get past the bootloader unlock. Since I wanted to change the ROM due to upcoming Harmony OS Update that might happen anytime. Plus, it would be easier for me if there was an official TWRP Support, but even the creators behind the project does not even offer an official build for it.
I am not an expert at coding the TWRP for my device itself, and I am not a Windows User since I changed the primary OS to Linux (to Ubuntu 20.04). Can't install HiSuite (even with wine, for some reason) and even with an unlock code, I cannot unlock the bootloader.
Here is what I tried so far:
Reboot the device into the Bootloader by using ADB (my easiest way)
Check if Fastboot recognized the device
Ran fastboot flashing unlock, fastboot oem unlock (my short unlock code), fastboot oem unlock
Restarted Fastboot multiple times using fastboot reboot-bootloader
For every command, Fastboot showed me either "invalid command" or "command not allowed". I don't know if I am doing anything wrong, but for some reason, Fastboot gives me an error if there is some command included with the words "oem" or "flash(-ing)". Tried wiping user data and cache with Fastboot and even this is a problem. Any command that might manipulate my phone won't let me perform the task that I want my phone to do.
Is my phone bootloader protected, or what is the issue that I cannot unlock it nor modify any contents?
I might address that using ADB from Recovery is not an option from me. Starting recovery (from ADB and the boot combination) and checking with ADB if the device is found. Nothing. Going into eRecovery changed only a bit, but ADB recognized my device this time. When my phone is in eRecovery, ADB finds the device, but it is unauthorized, meaning I cannot perform any tasks. If I don't get to know what this issue is causing, then I'll throw my phone out of the window.
Click to expand...
Click to collapse
Huawei removed oem unlock comands in emui 10