Related
please help, i can't unlocked my bootloader :'(
my rooting status : "Bootloader unlocked allowed : Yes"
but every time i flash, it makes error please help!
(bootloader) Unlock phone req
FAILED (remote: oem unlock fa
finished. total time: 0.007s
Are you sure you entered the boot loader key correctly, i. e. capital letters and no spaces?
The key has to be entered exactly like this:
Code:
fastboot.exe -i 0x0fce oem unlock 0x[I](your correct key)[/I]
Good luck!
Regards,
Chipy
Chip_88 said:
Are you sure you entered the boot loader key correctly, i. e. capital letters and no spaces?
The key has to be entered exactly like this:
Code:
fastboot.exe -i 0x0fce oem unlock 0x[I](your correct key)[/I]
Good luck!
Regards,
Chipy
Click to expand...
Click to collapse
like this one right ?
fastboot.exe -i 0x0fce oem unlock 0x9A32EFD0DDFXXXX
Click to expand...
Click to collapse
ehl.ey14 said:
like this one right ?
Click to expand...
Click to collapse
Exactly, but I think you shouldn't post your unlock key in such a public way...
Did it work?!
Chip_88 said:
Exactly, but I think you shouldn't post your unlock key in such a public way...
Did it work?!
Click to expand...
Click to collapse
(bootloader) Unlock phone req
FAILED (remote: oem unlock fa
finished. total time: 0.007s
Click to expand...
Click to collapse
same like this
Did you copied fastboot.exe to C:/ ?!
Did you start your device in fastboot mode?! Did the LED turn blue?!
Do you get any result, when you enter: fastboot.exe -i 0x0fce getvar version ?!
Chip_88 said:
Did you copied fastboot.exe to C:/ ?!
Did you start your device in fastboot mode?! Did the LED turn blue?!
Do you get any result, when you enter: fastboot.exe -i 0x0fce getvar version ?!
Click to expand...
Click to collapse
i used minimal adb 0.03 is the version? it is always detected, i installed properly the sony adb
ehl.ey14 said:
i used minimal adb 0.03 is the version? it is always detected, i installed properly the sony adb
Click to expand...
Click to collapse
If you would have mention before, that you're using minimal adb... :silly:
Then try: fastboot oem unlock *YOUR UNLOCK KEY*
Succeeded?!
Chip_88 said:
If you would have mention before, that you're using minimal adb... :silly:
Then try: fastboot oem unlock *YOUR UNLOCK KEY*
Succeeded?!
Click to expand...
Click to collapse
with space or not?
ehl.ey14 said:
with space or not?
Click to expand...
Click to collapse
Try it WITH space: fastboot oem unlock KEY
Don't forget fastboot reboot in the end. :laugh:
Chip_88 said:
Try it WITH space: fastboot oem unlock KEY
Don't forget fastboot reboot in the end. :laugh:
Click to expand...
Click to collapse
same :
<boatloader> Unlock phone requested
FAILED <remote : oem unlock 0XFFFFFFFFFFFFFFFF>
finished. total time: 0.007s
Click to expand...
Click to collapse
ehl.ey14 said:
same :
Click to expand...
Click to collapse
Very strange!
Could have some reasons:
1. Are you sure, you entered the correct 14 digits of your IMEI, when you asked for your unlock key on Sony?
Normally, the IMEI has 15 digist, but you have to leave the last one away.
Did you do so?!
2. The command fastboot oem unlock KEY has to be entered following the right folder structure.
So try the following: Open your Explorer. Go to the folder of your "minimal adb" installation.
Let's suppose you installed in on the partition E: into the folder Minimal ADB and Fastboot.
By the way: You didn't mentioned which system you're running. And it's harder then to give correct instructions.
On Vista, right click on that folder and choose "Open Command Prompt Here";
on other Windows versions it should be similar to this.
Now, the commander opens and should say something like: E:\Minimal ADB and Fastboot>.
And then write adb devices. Wait for the output.
If you get your device listed there, you did it right.
If not, you made something wrong.
If this shouldn't work again, please, be so kind to give us a detailed overview of all the steps you exactly did.
Good luck!
Try to get another unlock key from sony.
When I unlocked my bootloader I didn't use the unlock key for a week and when I finaly had time to do it I received the same error, so I went back to sony website and requested a new unlock key. It worked like a charm.
gtx_cj said:
Try to get another unlock key from sony.
When I unlocked my bootloader I didn't use the unlock key for a week and when I finaly had time to do it I received the same error, so I went back to sony website and requested a new unlock key. It worked like a charm.
Click to expand...
Click to collapse
Thanks for your answer.
It would be also the next / last step, I would suggest to her - after all the other advices weren't successful.
Chip_88 said:
Very strange!
Could have some reasons:
1. Are you sure, you entered the correct 14 digits of your IMEI, when you asked for your unlock key on Sony?
Normally, the IMEI has 15 digist, but you have to leave the last one away.
Did you do so?!
2. The command fastboot oem unlock KEY has to be entered following the right folder structure.
So try the following: Open your Explorer. Go to the folder of your "minimal adb" installation.
Let's suppose you installed in on the partition E: into the folder Minimal ADB and Fastboot.
By the way: You didn't mentioned which system you're running. And it's harder then to give correct instructions.
On Vista, right click on that folder and choose "Open Command Prompt Here";
on other Windows versions it should be similar to this.
Now, the commander opens and should say something like: E:\Minimal ADB and Fastboot>.
And then write adb devices. Wait for the output.
If you get your device listed there, you did it right.
If not, you made something wrong.
If this shouldn't work again, please, be so kind to give us a detailed overview of all the steps you exactly did.
Good luck!
Click to expand...
Click to collapse
i'll try it later
gtx_cj said:
Try to get another unlock key from sony.
When I unlocked my bootloader I didn't use the unlock key for a week and when I finaly had time to do it I received the same error, so I went back to sony website and requested a new unlock key. It worked like a charm.
Click to expand...
Click to collapse
what do you mean? i already did this, 10 time unlock keys but the same keys
Chip_88 said:
Thanks for your answer.
It would be also the next / last step, I would suggest to her - after all the other advices weren't successful.
Click to expand...
Click to collapse
</3
ehl.ey14 said:
i'll try it later
what do you mean? i already did this, 10 time unlock keys but the same keys
</3
Click to expand...
Click to collapse
'coz you didn't answer the whole day, I already thought, you unlocked your device already!
Go for it, ehl.ey14!
... and let us know, what's your result!!!
Hi there,
I must try here, and ask.... If you could help me with unlocking my bootloader.
I tried various "no boot needed" rom-s and nothing worked ! Whoever I try to ask, nobody is saying anything useful.
My t-mobile (phone is locked, only for theirs sim cards) is saying that's locked by sony, local service guy is saying something different and I don't know which side could I believe !
I would like to change that "bootloader unlock allowed:no" to yes
and after that- install ultimate hd rom. So I would ,kindly, like you to point me (what) and how should I unlock my boot loader. (I believe, there are ways and it could be done)
Big thanks and best wishes !
Željko :good:
Hi Željko!
As far as I know, the information in your device Bootloader Unlock Allowed has to be positive, i. e., saying Yes!
Otherwise you can't unlock your bootloader for free and have to choose a paid unlock.
Sorry for not having better news for you! =/
that's positive :laugh:
positive that it can be unlocked.. either way, it's going to be cheaper than new mobile phone
The best I was hoping is some homemade method, but... this is ok
another question !
When I contacted that local servicer, he said that some bootloaders can and some can't be unlocked (on lt18i), would you know why or is that true ?!
and, btw, I asked for price... he said, if unlocking is successful he's going to charge me around 20usd (just for reference)
Thanks
Chip_88 said:
'coz you didn't answer the whole day, I already thought, you unlocked your device already!
Go for it, ehl.ey14!
... and let us know, what's your result!!!
Click to expand...
Click to collapse
still locked
Bootlooping, adb not recognized, softbricked.
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.
Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.
https://developers.google.com/android/nexus/images
EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.
I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
rohanjoshi said:
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
Click to expand...
Click to collapse
Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.
Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.
Based on your initial post, it looks like you have a FLO.
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.
Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.
...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
hey did u tried doing a factory reset from the stock recovery?
varuntis1993 said:
hey did u tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
rohanjoshi said:
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
Click to expand...
Click to collapse
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
SOLVED
mdamaged said:
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
Click to expand...
Click to collapse
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
rohanjoshi said:
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
Click to expand...
Click to collapse
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
mdamaged said:
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
Click to expand...
Click to collapse
No, i understood that. I did not have the correct drivers installed and whenever I ran 'fastbook devices' nothing showed up.
I wiped all google drivers and re-installed one of the recommended packages and everything ran smoothly after that.
I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.
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!
hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked
aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you
aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools