Good evening to all.
I have spent more than 24h searching over the internet how to unlock the bootloader of my device, in order to flash twrp and enjoy a custom rom.
The problem is that my bootloader is locked, as fastboot states after oem device-info. I have tried various configs and drivers (windows 7 32 bit, windows 10, linux) with no luck.
Enable usb debugging, oem unlock are enabled. My phone is rooted with kingroot and i have removed screen locks (some suggested that it may cause the problem in other devices).
Here is the procedure i am following:
1. Proper installation of drivers and adb (both windows and linux)
2. With the device turned on --> adb devices and i get my device's output
3. adb reboot bootloader --> ok
4. fastboot devices --> ok
5. fastboot boot twrp --> fails cause of locked bootloader
6. fastboot oem unlock and similar won't do the trick.
If someone has a clue, please help. Even a link to something working will be fine, I don't want to spent your time.
Thanks in advance.
If you have got Lenovo then go to developer options and there you will see OEM Unlocking option enable it. And try the steps once again.
Thanks for your reply, but I've done that already
SOLVED!
For future reference, look for the answer in TWRP section, page 83.
I used qspt to flash another (stock) rom, then fastboot worked fine.
yianemma said:
Good evening to all.
I have spent more than 24h searching over the internet how to unlock the bootloader of my device, in order to flash twrp and enjoy a custom rom.
The problem is that my bootloader is locked, as fastboot states after oem device-info. I have tried various configs and drivers (windows 7 32 bit, windows 10, linux) with no luck.
Enable usb debugging, oem unlock are enabled. My phone is rooted with kingroot and i have removed screen locks (some suggested that it may cause the problem in other devices).
Here is the procedure i am following:
1. Proper installation of drivers and adb (both windows and linux)
2. With the device turned on --> adb devices and i get my device's output
3. adb reboot bootloader --> ok
4. fastboot devices --> ok
5. fastboot boot twrp --> fails cause of locked bootloader
6. fastboot oem unlock and similar won't do the trick.
If someone has a clue, please help. Even a link to something working will be fine, I don't want to spent your time.
Thanks in advance.
Click to expand...
Click to collapse
Okay lemmi help ya
I also have a41 device this is what i did
Download stock rom with lenovo smart assistant
Download lastest twrp and rename it
Code:
recovery.img
flash with qfil
To avoid sahara start windows with sig. enforcement disabled and login as admin.?
Sent from my Lenovo Vibe K5 using XDA Labs
electric.droid said:
Okay lemmi help ya
I also have a41 device this is what i did
Download stock rom with lenovo smart assistant
Download lastest twrp and rename it
Code:
recovery.img[CODE/]
flash with qfil
To avoid sahara start windows with sig. enforcement disabled and login as admin.
Sent from my Lenovo Vibe K5 using XDA Labs[/QUOTE]
Man, i have the same problem!
The only thing different is my cell phone model, is a A6020l36.... that help, is it works for me?
Where do i can find that qfil?
regards!
Click to expand...
Click to collapse
ccofre said:
Man, i have the same problem!
The only thing different is my cell phone model, is a A6020l36.... that help, is it works for me?
Where do i can find that qfil?
regards!
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/k5-plus/how-to/noob-guide-flash-lenovo-devices-to-stock-t3442086
Download drivers and qfil from there.
My device is a SD415 soc. Files from firmware you supposed to download from lenovo smart assistant should work. Dont want to scare you but, DO THIS AT YOUR OWN RISK as i dont own this device. Good luck 'n' have a nice day
Sent from my A6020a41 using XDA Labs
electric.droid said:
Here https://forum.xda-developers.com/k5-plus/how-to/noob-guide-flash-lenovo-devices-to-stock-t3442086
Download drivers and qfil from there.
My device is a SD415 soc. Files from firmware you supposed to download from lenovo smart assistant should work. Dont want to scare you but, DO THIS AT YOUR OWN RISK as i dont own this device. Good luck 'n' have a nice day
Sent from my A6020a41 using XDA Labs
Click to expand...
Click to collapse
Ok, thanks a lot!... i will post how it was in here.
EDIT: Ok man, i made it. With the post you told me and using this i was able to use a Stock rom, and with that i was able to run TWRP (with no bootloader unlock), flash Lineage and Gapps, and change my recovery too.
Thanks for the help!, I hope this could help anyone with this problem too.
ccofre said:
Ok, thanks a lot!... i will post how it was in here.
EDIT: Ok man, i made it. With the post you told me and using this i was able to use a Stock rom, and with that i was able to run TWRP (with no bootloader unlock), flash Lineage and Gapps, and change my recovery too.
Thanks for the help!, I hope this could help anyone with this problem too.
Click to expand...
Click to collapse
Well done. You can hit thanks btw
Sent from my A6020a41 using XDA Labs
My k5 a6020a41 has a 616 soc, it seems that there are two versions of this phone. Currently reverted mine to stock, since I had issues with the custom ROMs I have tried. Maybe this info is useful to developers.
yianemma said:
My k5 a6020a41 has a 616 soc, it seems that there are two versions of this phone. Currently reverted mine to stock, since I had issues with the custom ROMs I have tried. Maybe this info is useful to developers.
Click to expand...
Click to collapse
My k5 is the A6020l36, has a Snapdragon 616 too. I think your k5 is very supported... what was wrong with custom roms?. I been testing Lineage 14.1 and AOKP, both are Ok, but with the Lineage i have better results.
I wanted to point out that maybe there are two variants for a6020a41. Both aokp and nougat worked fine, apart some "stopped working" errors from time to time. Stock ROM just seems easier to me, same battery life as custom roms, so why not?
electric.droid said:
Okay lemmi help ya
I also have a41 device this is what i did
Download stock rom with lenovo smart assistant
Download lastest twrp and rename it
Code:
recovery.img
flash with qfil
To avoid sahara start windows with sig. enforcement disabled and login as admin.
Sent from my Lenovo Vibe K5 using XDA Labs
Click to expand...
Click to collapse
Hello,
Can you please give me exact guide on how you did this ?
I also have a41 version of K5 and suprise, suprise unable to unlock bootloader in any sort of way.
I would be greatful if you would help me with my issue as well.
I'm aware that you might refer to me to check that thread you shared and I have already done so but I can not really find thing to satisfy my craving.
Thank you.
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
yianemma said:
I wanted to point out that maybe there are two variants for a6020a41. Both aokp and nougat worked fine, apart some "stopped working" errors from time to time. Stock ROM just seems easier to me, same battery life as custom roms, so why not?
Click to expand...
Click to collapse
Hello there,
I am looking for help on how to flash or re-flash my stock rom on a41 K5 version. I was also unable to unlock bootloader using any sort of way and that was not working... so and you refered TWRP section p.83 I would like to ask for a link if possible.
Thank you.
yianemma said:
Good evening to all.
I have spent more than 24h searching over the internet how to unlock the bootloader of my device, in order to flash twrp and enjoy a custom rom.
The problem is that my bootloader is locked, as fastboot states after oem device-info. I have tried various configs and drivers (windows 7 32 bit, windows 10, linux) with no luck.
Enable usb debugging, oem unlock are enabled. My phone is rooted with kingroot and i have removed screen locks (some suggested that it may cause the problem in other devices).
Here is the procedure i am following:
1. Proper installation of drivers and adb (both windows and linux)
2. With the device turned on --> adb devices and i get my device's output
3. adb reboot bootloader --> ok
4. fastboot devices --> ok
5. fastboot boot twrp --> fails cause of locked bootloader
6. fastboot oem unlock and similar won't do the trick.
If someone has a clue, please help. Even a link to something working will be fine, I don't want to spent your time.
Thanks in advance.
Click to expand...
Click to collapse
Same here
Related
HELP Please !
My htc explorer initially got stuck at the htc logo at boot and won't go any further.
I searched for solutions on xda and tried to install Cyanogenmod 10.2 on it. Now the device gets stuck at cyanogenmod boot animation (was going on until half -an-hour ! )
Next i searched some more, caught TWRP recovery on a glance. Tried installing it, but my Laptop ( Win8.1 x64 ) doesnt recognize the device whatsover, even after installing the adb drivers and HTC SYNC. !
Now i finally installed FLYROM v4 refined, and the phone is stuck at htc 'quietly brilliant' logo . !
PLEASE get me out of this misery ! I want my little buddy back in action
Please .. Anybody ?
Nobody to help ?
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Thanks, but no luck
pjohn23 said:
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Click to expand...
Click to collapse
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
DrSakethReddy said:
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
Click to expand...
Click to collapse
dont you have flashtools?
More INFO needed.
pjohn23 said:
dont you have flashtools?
Click to expand...
Click to collapse
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
DrSakethReddy said:
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
Click to expand...
Click to collapse
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Thank you very much, for your reply
I hit thanks button too
I'll get back to you soon as i perform the steps you've stated in a Win 7 PC.
sadly NO
pjohn23 said:
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
Click to expand...
Click to collapse
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
pjohn23 said:
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
Click to expand...
Click to collapse
Hey ! C'mon. Don't say u didn't help !
Providing a light to this thread for others to answer it too was the read deal you made !
Thanks again, bro
AWESOME !
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
Great ! I love getting things done easier with tools !
I'll give this a shot too, and then if this doesn't work, i'll head for the recovery.img flashing .
Thanks
Unsuccessful ! (error)
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Alas ! Error again
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
I've done the adb command method and failed, now i've even performed updating it with RUU, but i have this result :
ERROR 155: unkown error
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and update your phone.
DrSakethReddy said:
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Click to expand...
Click to collapse
I'm so sorry! I left out something in that command! It's:
fastboot flash boot boot.img
Sorry, poor proofreading skills.
As far as the 155 error, I think you also might need to do this in bootloader / fastboot mode (if the previous command doesn't get you going with the rom you are already on - it should):
fastboot oem lock
Then re-run RUU.
Sorry guys, for a very late reply.
I tried all the methods you said, with the new command too, but alas ! The device didn't get a life.
I'm gonna use it as a very costly paperweight now !
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
Any news about to root the iRulu V3?
Boris The Spider said:
Any news about to root the iRulu V3?
Click to expand...
Click to collapse
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
volcomyae23 said:
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
Click to expand...
Click to collapse
i am also interested in rooting this phone, i have the firmware if anyone can make a custom recovery in order to root it.
i have tried every rooting tool without success.
I'm also looking for a root method for the v3.
It's an inexpensive, neat, non bloatware phone which is really underrated and unappreciated by the rooting community. I also have the firmware and I'm willing to donate the cost of the phone to whomever can post a successful root method?
I have heard that framaroot 1.9.1 would root this phone.
I found this solution in China web site.
Sent from my Nexus 5 using xda premium
Please,somebody can give me the firmware link?
Thx
I'm not sure which serial number it is...
N.Ákos said:
Please,somebody can give me the firmware link?
Thx
Click to expand...
Click to collapse
Right from irulu.
https://www.irulu.com/download/lists.html
Can anyone help verify the serial for the V3 2gb/16gb?
I can't find the firmware on Irulu's website
Hi
I believe that this is firmware:x1067wf1601073e.
Confirm if this is correct.
When searching for this use PC or desktop mode.
Sent from my Nexus 5 using xda premium
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
marsian0 said:
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
Click to expand...
Click to collapse
how did you flash it (using what)?
In the zip are the instructions, and the tools required (qpst or some). My device no longer works, cause i flashed by mistake another firmware from another device, it boots but the touch is totally messed up.
Sent from my Nexus 6 using Tapatalk
I downloaded the above V3 high configuration and all the tools and instructions are there in the zip file. Here is the problem though with rooting the device. The device needs to have the bootloader unlocked prior to rooting and if you check your device you'll find that the bootloader is locked on it. I've tried all the oem unlock options and none of it works because it appears that irulu has the fastboot commands turn off for the most part on our device. What we need to do now is to figure out how to edit the bootloader files, ie aboot.c specifically, to allow for bootloader unlocking, then after we do that and flash that bootloader to the device we'll be able to install a custom recovery and root it probably pretty easily. Anyways, if anyone that knows a little bit more about how to edit those files and stuff would like to get involved in this I can confirm that the above link to the V3 firmware is legit and contains the correct files and firmware.
Actually I take that back. I was able to unlock the bootloader with the command 'fastboot oem forceunlock' followed by fastboot oem unlock-go just to be sure and then I checked with fastboot oem device-info and it then stated that the bootloader was indeed unlocked. So that's good news, now we just need to figure out a way to root and install a custom recovery.
I'm pretty satisfied with the V3 2GB phone the way it is coming out of the box.
The only reason I wish to root the device is to get rid of that stupid and annoying bootup music file .
The file on the irulu site is for the 1GB V3 version phone.
I can see that that the link supplied in the past post is for the V3 2GB US LTE device ?
Is that correct?
Thank You
Going to take 2 days to download the V3 High Configuration firmware.
Anyone have a better link so far irulu has not assisted.
Thanks.
http://forum.xda-developers.com/showthread.php?p=32965365
How to compile twrp.
Sent from my Nexus 6 using xda premium
Ended up downloading the 1.6GB file using my cell phone using T-mobile.
Centurylink fiber has some kind of blocks against Chinese file sharing .
Finally!
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
BigDizawg2015 said:
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
Click to expand...
Click to collapse
Thank You for sharing your skills.
Hi guys I need your help.
I just got my Redmi Note 3 Pro 32GB. It was on official China ROM from what I know. I tried to unlock the bootloader without permission using this guide http://en.miui.com/thread-235865-1-1.html but when I flashed the ROM using MiFlash I got an error. I later restarted the phone and then all of a sudden my WLAN, Bluetooth and SIM would not work at all. So I tried again and now I get this error saying (Reached end of file... Receiving Hello Packets).
I can't flash a ROM from MiSuite through recovery as it always says it fails.
I'm at a loss here stressing out for days trying to get this to work and install CM13 on it. Was really excited but now this phone kind of pisses me off everytime I look at it. If I could fix the problems and flash CM13, this would be a great phone. Guess after this I'll probably not purchase another Xiaomi, nightmare to unlock and stuff.
All your help is appreciated. Thanks!
Try use Miflash too to wipe it with latest beta or stable rom.
Kevinwith4y said:
Hi guys I need your help.
I just got my Redmi Note 3 Pro 32GB. It was on official China ROM from what I know. I tried to unlock the bootloader without permission using this guide http://en.miui.com/thread-235865-1-1.html but when I flashed the ROM using MiFlash I got an error. I later restarted the phone and then all of a sudden my WLAN, Bluetooth and SIM would not work at all. So I tried again and now I get this error saying (Reached end of file... Receiving Hello Packets).
I can't flash a ROM from MiSuite through recovery as it always says it fails.
I'm at a loss here stressing out for days trying to get this to work and install CM13 on it. Was really excited but now this phone kind of pisses me off everytime I look at it. If I could fix the problems and flash CM13, this would be a great phone. Guess after this I'll probably not purchase another Xiaomi, nightmare to unlock and stuff.
All your help is appreciated. Thanks!
Click to expand...
Click to collapse
Unlock your bootloader, then open your phone in fastboot mode. miflash works in fastboot mode too. Flash your phone. If the wifi problem is still present, then flash a radio package. PM me i will send the link if the problem is still present.
Archit9169 said:
Unlock your bootloader, then open your phone in fastboot mode. miflash works in fastboot mode too. Flash your phone. If the wifi problem is still present, then flash a radio package. PM me i will send the link if the problem is still present.
Click to expand...
Click to collapse
Okay I'll try to unlock officially cause I can't for any reason do it unofficially cause of that Hello Packet error. Waiting for the code
Flashed new global Beta and unlocked just fine.
Archit9169 said:
Unlock your bootloader, then open your phone in fastboot mode. miflash works in fastboot mode too. Flash your phone. If the wifi problem is still present, then flash a radio package. PM me i will send the link if the problem is still present.
Click to expand...
Click to collapse
Well applied for official unlock and when trying to unlock it couldn't verify the device cause I have to MiAccount on my redmi note 3. I can't log in to one on my device because I want get any network on it. So I guess I'm screwed here huh.
Kevinwith4y said:
Well applied for official unlock and when trying to unlock it couldn't verify the device cause I have to MiAccount on my redmi note 3. I can't log in to one on my device because I want get any network on it. So I guess I'm screwed here huh.
Click to expand...
Click to collapse
Download the latest miflash. Try to flash a fastboot rom via edl mode. Ise 64 bit os. Make sure driver signature is disabled. Once you have properly flashed the rom, open miunlocl and then proceed normally.
When i revert back to miui from cm13, i encountered network and wifi problem. I unlocked bootloader via unlocktool and it unlocked like a charm.
Archit9169 said:
Download the latest miflash. Try to flash a fastboot rom via edl mode. Ise 64 bit os. Make sure driver signature is disabled. Once you have properly flashed the rom, open miunlocl and then proceed normally.
When i revert back to miui from cm13, i encountered network and wifi problem. I unlocked bootloader via unlocktool and it unlocked like a charm.
Click to expand...
Click to collapse
Just tried that again. Whenever I use miflash I get error receiving hello packet. On miflash beta I get cannot read COM port.
I've disabled the driver signatures.
Qualcomm drivers and phone drivers are all installed correctly. Just nothing is working
Kevinwith4y said:
Just tried that again. Whenever I use miflash I get error receiving hello packet. On miflash beta I get cannot read COM port.
I've disabled the driver signatures.
Qualcomm drivers and phone drivers are all installed correctly. Just nothing is working
Click to expand...
Click to collapse
Try using windows 7. It has higher success rate. Also try to download some other version of fastboot rom. Maybe the rom has problems. As for your network and wifi related problem, it can be fixed by flashing a different nonhlos.bin file
Archit9169 said:
Try using windows 7. It has higher success rate. Also try to download some other version of fastboot rom. Maybe the rom has problems. As for your network and wifi related problem, it can be fixed by flashing a different nonhlos.bin file
Click to expand...
Click to collapse
How do I flash that file? Do I need to be unlocked first?
Kevinwith4y said:
How do I flash that file? Do I need to be unlocked first?
Click to expand...
Click to collapse
Unfortunately, yes you have to unlock first. Keep trying the edl mode. I am sure its either software problem or windows problem.
Archit9169 said:
Unfortunately, yes you have to unlock first. Keep trying the edl mode. I am sure its either software problem or windows problem.
Click to expand...
Click to collapse
Alright. Currently trying will tell you how it goes.
Archit9169 said:
Unfortunately, yes you have to unlock first. Keep trying the edl mode. I am sure its either software problem or windows problem.
Click to expand...
Click to collapse
Not going well man. Still same problems no matter the ROM. If I try the same method on fastboot they tell me the bootloader is locked. I don't have access to another PC so I can't really try out. Looks like I'm all out of options and this phone is pretty much a brick. Maybe I'll buy another one and try again but... goddamn
Kevinwith4y said:
Not going well man. Still same problems no matter the ROM. If I try the same method on fastboot they tell me the bootloader is locked. I don't have access to another PC so I can't really try out. Looks like I'm all out of options and this phone is pretty much a brick. Maybe I'll buy another one and try again but... goddamn
Click to expand...
Click to collapse
As long as you phone does not have any hardware fault and can boot in either edl mode or fastnoot mode, then it can be repaired. Keep patience. Better yet take it to xiaomi service centre, they'll do it for you. But as far as i know, edl mode can help you properly flash. Keep patiece buddy
Archit9169 said:
As long as you phone does not have any hardware fault and can boot in either edl mode or fastnoot mode, then it can be repaired. Keep patience. Better yet take it to xiaomi service centre, they'll do it for you. But as far as i know, edl mode can help you properly flash. Keep patiece buddy
Click to expand...
Click to collapse
Maybe I'll try again tomorrow or take it to a repair centre or something. Thanks a lot for the help man! Really appreciate it
Kevinwith4y said:
Maybe I'll try again tomorrow or take it to a repair centre or something. Thanks a lot for the help man! Really appreciate it
Click to expand...
Click to collapse
Where do you live?
Archit9169 said:
Where do you live?
Click to expand...
Click to collapse
Singapore man
Kevinwith4y said:
Singapore man
Click to expand...
Click to collapse
Alright. I know that there are service centre there so take you mobile there and theyll repair it. I dont know about the cost, sadly, however it wont be much.
Kevinwith4y said:
Maybe I'll try again tomorrow or take it to a repair centre or something. Thanks a lot for the help man! Really appreciate it
Click to expand...
Click to collapse
Which windows version you are using.and can you boot into edl mode
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Which windows version you are using.and can you boot into edl mode
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Windows 10 64bit and yes I can