After long time research I have found a way how to restore hard bricked Meizu Pro 5.
It should work on phones:
1. With lost recovery and locked bootloader (fastboot) My case.
2. With lost bootloader
3. With lost recovery and bootloader
First case was tested by me with international version phone, but as restore procedure is very low level it should work and for other two cases and probably Chinese phones.
Unbrick procedure was done using 32bits. Windows 7 Professional Version 6.1 (Build 7601: Service pack 1) with installed all updates. 32 bit OS was used because I found only 32 bits. Drivers, not for the phone, but for Samsung Exynos7420. As you know this phone is based on 7420 chip.
Windows 10 won’t work.
The puzzle was solved after rethinking of information from these forum posts:
1. https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865
2. https://forum.xda-developers.com/meizu-pro-5/help/to-unlock-hardbricked-meizu-pro-5-t3566173
thanks these guys for showing me path.
The trick is to put phone in Exynos7420 mode and flash unlocked bootloader. Unlocked boot loader I took from link provided in this tread: https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-unlock-bootloader-meizu-pro-5-t3303127
First step.
Then I extracted unlocked bootloader as u-boot.bin.signed and the other three files:
1. fwbl1
2. el3.bin.signed
3. bl2.bin.signed
I took from multiUpgrade 4.8.5.rar archive, you could find them in it if you dig enough into subfolders. Extract from unlocked bootloader file I din’t succeed .
Steps:
1. Prepare 32 bit windows machine. (it could be even a virtual machine, I have done it using parallels desktop, but it is possible and with other virtualisation software, like vmware or of course bare metal)
2. Extract provided archive into somewhere It contains all necessary drivers, tools and files.
3. Install Drivers ~\Files\USB_Download_Tool_32bit\Disk1\Setup.exe
4. Install Microsoft Visual C++ 2012 ~\Files\vcredist_x86.exe
5. Copy ~\Files\USB_Download_Tool_32bit\WinDNWApi.dll and ~\Files\USB_Download_Tool_32bit\WinDNWApi.lib in in: c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
6. Rename c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\WinDNWApi.dat, just add something at the end, I renamed into to WinDNWApi.dat_
7. Run ~\Files\USB_Download_Tool_32bit\Multidownloader.exe and select file ~\Files\Bootloader\MeizuPro5.cfg
8. Boot into Exynos7420 mode Press and hold Vol + and Vol - and press one time power button, keep pressing both Vol buttons. Do not release them.
9. OS should detect device and install drivers, then in the Multidownloader.exe application window you should see connected device.
10. Select device and press start, wait until phone reboots into fastboot mode with unlocked bootloader. Now you can release both Vol buttons. Congratulations, now you have device in fastboot mode with unlocked bootloader.
11. Install Samsung drivers from ~\Files\Samsung Drivers\ using windows device manage and have disk method selecting right drivers file in ~\Files\Samsung drivers\android_winusb.inf. Now you have device in fastboot mode and accessible from fastboot.
12. RUN cmd and go to ~\Files\Rest\ then execute: “fastboot.exe devices”, it should return connected device.
13. Now we can flash TWRP recovery execute: “fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img”
14. Now flash bootloader execute: “fastboot flash bootloader bootloader"
What to do with unlocked bootloader and custom recovery I guess you know .
Because my phone was with corrupted partition TWRP couldn't flash images, so I made few more steps, but for most of the cases should be enough previous.
And of course, if you going to flash stock rom, don't forget to delete these 1) bootloader, 2) ldfw, 3) recovery.img files from update.zip, oversize you be forced to start everything from beginning.
Resources: https://megaupload.nz/Ae6fTegfb7/Files_7z
thank you very much you are my hero or the one of all, you could do it !!!!!!!!!!!!!!!
To solve this puzzle took me few month. Does it helped?
egmantas said:
To solve this puzzle took me few month. Does it helped?
Click to expand...
Click to collapse
you helped me a lot
you must edit the last line: "fastboot flash recovery bootloader bootloader" to "fastboot flash bootloader bootloader"
Guys,
How to get into Exynos mode? I know it is Vol+ and Vol- and one timer Power, but what is the starting point? Should the device be in fastboot mode, switched off or what? And how will I know that I am already in Exynos mode?
In theory I had some founded device on Multidownloader, but device did not reboot after installing bootloader. Of course bootloader is still locked.
pawelec415 said:
Guys,
How to get into Exynos mode? I know it is Vol+ and Vol- and one timer Power, but what is the starting point? Should the device be in fastboot mode, switched off or what? And how will I know that I am already in Exynos mode?
In theory I had some founded device on Multidownloader, but device did not reboot after installing bootloader. Of course bootloader is still locked.
Click to expand...
Click to collapse
To get to Exynos mode you could from every step, it is no necessary to be in fastboot or switched off, but from fastboot probably its more noticeable.
Steps:
To be sure you are in Exynos mode do these steps.
1. Run windows device manager
2. Vol+ and Vol- and one timer Power (I am holding power until I see new device in windows device manager, then continuing to hold only Vol+ and Vol-)
3. If drivers installed correctly in windows device manager com/LPT section you should see Exynos device, check its com port number.
4. Run Multidownloader and if its com port is the same as exynos device in windows device manager you will know what it is the same device.
5. Don't forget step 6 from tutorial, because WinDNWApi.dat contains map, which is not good, so simply rename file.
Everything I have done on fresh installed windows 7 32 bit. machine hosted in parallels desktop. But you could do it with bare metal.
I made everything just as you wrote. Still nothing...
Would you help me in PM?
@egmantas WOW, I was with the same situation,locked bootloader and no recovery .I do as you written and it work perfectly .
The only thing I do different is to install windows 7 32 bit on virtual machine using vmware software and it work as you said .I do it because I have windows 10 and I can not install windows 7 on this computer .
Thank you so much .
or965 said:
@egmantas WOW, I was with the same situation,locked bootloader and no recovery .I do as you written and it work perfectly .
The only thing I do different is to install windows 7 32 bit on virtual machine using vmware software and it work as you said .I do it because I have windows 10 and I can not install windows 7 on this computer .
Thank you so much .
Click to expand...
Click to collapse
I have done the same, but with parallels desktop
It works man! You are the best!
Thank you very much. :good:
With your CFG file as template, I was able to recover my Samsung SM-R760:
https://forum.xda-developers.com/showpost.php?p=78641965&postcount=700
:good:
Best Regards
great thanks!!
it works!!!
but i must mention, you need Windows 7 32 bit installation, what is capable to install windows updates (i had "tiny" or "lite" version of win 7 ultimate, and it was not capable to process this method.) so i did clean install of Windows 7 Professional.
Success!
egmantas said:
After long time research I have found a way how to restore hard bricked Meizu Pro 5.
It should work on phones:
1. With lost recovery and locked bootloader (fastboot) My case.
2. With lost bootloader
3. With lost recovery and bootloader
First case was tested by me with international version phone, but as restore procedure is very low level it should work and for other two cases and probably Chinese phones.
Unbrick procedure was done using 32bits. Windows 7 Professional Version 6.1 (Build 7601: Service pack 1) with installed all updates. 32 bit OS was used because I found only 32 bits. Drivers, not for the phone, but for Samsung Exynos7420. As you know this phone is based on 7420 chip.
Windows 10 won’t work.
The puzzle was solved after rethinking of information from these forum posts:
1. https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865
2. https://forum.xda-developers.com/meizu-pro-5/help/to-unlock-hardbricked-meizu-pro-5-t3566173
thanks these guys for showing me path.
The trick is to put phone in Exynos7420 mode and flash unlocked bootloader. Unlocked boot loader I took from link provided in this tread: https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-unlock-bootloader-meizu-pro-5-t3303127
First step.
Then I extracted unlocked bootloader as u-boot.bin.signed and the other three files:
1. fwbl1
2. el3.bin.signed
3. bl2.bin.signed
I took from multiUpgrade 4.8.5.rar archive, you could find them in it if you dig enough into subfolders. Extract from unlocked bootloader file I din’t succeed .
Steps:
1. Prepare 32 bit windows machine. (it could be even a virtual machine, I have done it using parallels desktop, but it is possible and with other virtualisation software, like vmware or of course bare metal)
2. Extract provided archive into somewhere It contains all necessary drivers, tools and files.
3. Install Drivers ~\Files\USB_Download_Tool_32bit\Disk1\Setup.exe
4. Install Microsoft Visual C++ 2012 ~\Files\vcredist_x86.exe
5. Copy ~\Files\USB_Download_Tool_32bit\WinDNWApi.dll and ~\Files\USB_Download_Tool_32bit\WinDNWApi.lib in in: c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
6. Rename c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\WinDNWApi.dat, just add something at the end, I renamed into to WinDNWApi.dat_
7. Run ~\Files\USB_Download_Tool_32bit\Multidownloader.exe and select file ~\Files\Bootloader\MeizuPro5.cfg
8. Boot into Exynos7420 mode Press and hold Vol + and Vol - and press one time power button, keep pressing both Vol buttons. Do not release them.
9. OS should detect device and install drivers, then in the Multidownloader.exe application window you should see connected device.
10. Select device and press start, wait until phone reboots into fastboot mode with unlocked bootloader. Now you can release both Vol buttons. Congratulations, now you have device in fastboot mode with unlocked bootloader.
11. Install Samsung drivers from ~\Files\Samsung Drivers\ using windows device manage and have disk method selecting right drivers file in ~\Files\Samsung drivers\android_winusb.inf. Now you have device in fastboot mode and accessible from fastboot.
12. RUN cmd and go to ~\Files\Rest\ then execute: “fastboot.exe devices”, it should return connected device.
13. Now we can flash TWRP recovery execute: “fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img”
14. Now flash bootloader execute: “fastboot flash bootloader bootloader"
What to do with unlocked bootloader and custom recovery I guess you know .
Because my phone was with corrupted partition TWRP couldn't flash images, so I made few more steps, but for most of the cases should be enough previous.
And of course, if you going to flash stock rom, don't forget to delete these 1) bootloader, 2) ldfw, 3) recovery.img files from update.zip, oversize you be forced to start everything from beginning.
Resources: https://megaupload.nz/Ae6fTegfb7/Files_7z
Click to expand...
Click to collapse
This worked very well, thank you for this guide.
I used VMWare Workstation Pro with Windows 7; VM Virtual Box did not work well.
Could someone just re-upload https://megaupload.nz/Ae6fTegfb7/Files_7z ?
Thanks
I have the same problem. Link to the files does not work
It says doesn't work on windows 10, what about Ubuntu 18? Thanks
New link to same file:
http://www.mediafire.com/file/7bi0di2pdjxkh9f/Files.7z/file
If someone knows more reliable file hosting site, not temporary, please share, I will this file to it.
Hi, no it does't work on any Ubuntu or linux versions as drivers are for windows. Of course you can use virtualization software in Ubuntu and install windows, then connect you phone to this virtual machine.
Someone with this problem did it.
Bandanaman said:
It says doesn't work on windows 10, what about Ubuntu 18? Thanks
Click to expand...
Click to collapse
Meizu pro 5 Ubuntu Touch
Guys I'm new to all this stuff and feel a bit in over my head! Is there anyone I can send my phone to (one of u guys maybe?) Who could do this for a fee?
I had a locked bootloader and broken recovery, аfter a failed installation of the last firmware with a missing serial number on my PRO 5.
I recently tried this method with different versions of windows and different PCs.
And always got the same error in Multidownloader.
The phone reboots into fastboot and there is still a locked bootloader.
It was possible to solve the problem only in the service center, using the MRT Dongle.
Are there any suggestions of what the problem might be? (for future generations)
Related
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
The summary of what happened is as follows.
I have the HDX 7 and it auto updated to 13.3.2.3.2, so I modified the build.prop to spoof it as being 13.3.0.9
I had done this successfully before (OTA update was NOT stopped by hdxposed) so I was feeling super confident
Here's where I made my mistake though
I forgot to reset my permissions
So, once I rebooted, it obviously didn't work.
In a panic, I tried to factory reset. I should have guessed it wouldn't touch /system .
Now, I personally can't think of any way I could possibly fix this device, but maybe someone here has some wizard magic I could use, I've honestly all but given up hope.
I can still see the low battery icon if it's low and I try to boot it, and I can still get into Amazon's extremely limited bootloader (your kindle could not boot, reboot, factory reset) but other than that I don't think I can do much with it.
Please, if anyone has any suggestions... ;-;
Pretty sure there's not a fix based on all the other threads where people have done the same thing.
Reboot into fastboot and try to flash amazon's stock firmware.
Demonoid111 said:
Reboot into fastboot and try to flash amazon's stock firmware.
Click to expand...
Click to collapse
Would this work?
amazon/gp/product/B0099E59SG (sorry, can't submit URL due to being a new user)
If I can actually boot into fastboot and have it work properly, I would be able to flash a .bin to it? I'm sorry for being so ignorant about the subject.
You may be able to flash a .bin if you can get into fastboot mode, but from what I understand, there is no hardware button combo that will get you into fastboot mode unless you have an unlocked bootloader. If you have any sort of adb when it tries to boot, then adb reboot-bootloader may put you in the right place, but if not, then I'm not sure there is much to be done.
I would check out this thread to get some more info on the state of fastboot.
http://forum.xda-developers.com/showthread.php?t=2799793
good luck!
Hmm, unless I can get some confirmation on that fastboot cable, I don't think I have much hope it seems ._.
The only current way to access fastboot mode is via adb, correct?
Tumbtack said:
Hmm, unless I can get some confirmation on that fastboot cable, I don't think I have much hope it seems ._.
The only current way to access fastboot mode is via adb, correct?
Click to expand...
Click to collapse
Hi! You can use the Wugfresh's nexus 7 tool, it will let you go into fastboot but as far as I know you cant flash .bin may be I'm wrong but you can try...
http://forum.xda-developers.com/showthread.php?t=2389107
SiulGM said:
Hi! You can use the Wugfresh's nexus 7 tool, it will let you go into fastboot but as far as I know you cant flash .bin may be I'm wrong but you can try...
http://forum.xda-developers.com/showthread.php?t=2389107
Click to expand...
Click to collapse
Does this actually do anything special or is it just an adb/fastboot GUI? Because I'm currently in Linux and installing windows is a /huge/ pain and I'm sure messing with it in WINE would just make things worse... Though if it does actually do something special I would be more than willing to do it for that.
Still looking for some type of answer.
Even if I did somehow access fastboot mode, would it even help me?
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
aaronkatrini said:
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
Click to expand...
Click to collapse
Will definitely try tomorrow, only difference being I'll be in arch rather than ubuntu, though that shouldn't be a big enough difference to pose a problem. I'll keep you updated with how it goes. Thanks!
Return?
Why don't you just try to give the device back? I'm pretty certain other people have done it.
I don't think
aaronkatrini said:
Try this (if you haven't already):
1. Setup a Linux environment (Ubuntu 13.04 - is being used on the tutorial) - you can install it on a USB stick and then boot the PC from the USB without making any changes.
2. Install the Android SDK (that you can have adb and fastboot installed) - (follow this guide: http://forum.xda-developers.com/showthread.php?t=2302780 )
3. Boot the tablet while pressing all the HW buttons (VOL+ , VOL - , POWER Button) - I've read somewhere from @Hashcode that the original firmware has code to boot into fastboot while pressing all the buttons without the need of a "special" fastboot cable.
4. Check the fastboot commands and see if recognizes it.
Click to expand...
Click to collapse
That it really matters if you get it to recognize it or not the device will not accept through fast boot unless it is unlocked from what I understand. What good is fastboot if we don't have any fastboot files in any public way at least anyway that I know. The fastboot commands will work from what I have read but you cannot flash any bin files or any system files. Until it is unlocked and Hashcode says once unlocked everything flashes fine .
Besides he should be working with this thread it has fixed several people with the same problem http://forum.xda-developers.com/showthread.php?t=2588608 not specifically just OP but there is very in-depth discussion throughout the thread with useful information
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
Hi all,
I'm not an expert with flashing ROMs/recovery and stuff, but I think I know the basics. So, if I was missing something, please forgive me in advance
I'm trying to install TWRP on my Oukitel K6000 Pro, but can't do it for some reason. The things I tried:
1. Rooting my phone w/ kingroot to install flashify. Kingroot failed to root my phone.
2. Via linux machine, using fastboot command. Fastboot failed installing the recovery (USB debugning was turn on. OEM unlocking was turn on, but I wasn't sure I even needed it). Error message I got: "FAILED (remote: download for partition 'recovery' is not allowed"
3. Using windows 7 and windows 10 machines to install it via SP-flash-tool (USB debuging and OEM unlocking was turned on). The SP-flash-tool did not recognized my phone.
4. Using SP-flash-tool with FWUL live-CD. It did not recognize my phone.
5. Using SP-flash-tool with linux machine. It did not recognize my phone.
As for #3 above, I was trying to install MTK drivers before performing the flash process. I think I got it right (for the win10 machine, I rebooted to a mode without signature check as required), but I'm not sure though.
If anyone can step in and help with that - I would much appreciate it.
Thanks in advance,
Tamir
you need the right drivers and the right adb tool.
Download adb tools of android sdk, google it.
Then download the oukitel drivers-> Driver_Auto_Installer_v5.1453.03, search for those., install them.
Try again, good luck.
Rooting and unlocking your phone will format your phone, beware of losing everything on it.
Btw, never use kingroot. Use latest SP Flashtool Version 1728,
Guide:
Download Magisk V16 or SuperSu to your micro sd on your phone.
--(Download your desired firmware, if you want to upgrade as well. (if you want, not needed, since you only want to root or install twrp)--
Download SPFlashTool compatible TWRP from a site that i can't mention here.
Turn off your phone.
Open Splflashtool, select the Android Scatter file that was downloaded with your twrp.
A little bit under that, select Download Only, and NOT firmware ugprade etc.
Now click Download, connect your turned off phone to your pc.
You should hear a windows sound, look at the tool and DO NOT Disconnect your phone. until a popup with Success and a green Symbol appears.
be patient and let it run. (shouldn't actually take longer than 3-5seconds)
After it is done, press simultaneously the Power and Volume+ Keys until a really small menu on the left side screen appears.
Now you can navigate with the Volume+ Key, from the top to the bottom, in an endless loop.
With the Volume- Key you can select on of the three options:
Recovery <-this is what we want, select it!
Fastboot (not really needed for us)
Normal (normal Reboot - Start of the phone)
You will now see the bootlogo, then the twrp menu will show up.
Now you can Flash Magisk or SuperSu for Root. Wipe Dalvik and cache, Reboot, Enjoy.
Generic Disclaimer: By doing any of the process listed below you accept complete responsibility over any of your actions, I will not be responsible if you end up causing hard brick, data loss or any kind of loss to your personal property.
Hii XDA fellows,
So I have seen many people asking for noob friendly guide to restore original oxygen os firmware or basically unbrick device. There are several thread on this already but trust me I have tried them all and in my case I had to use my own brain. So I have compiled a noob friendly guide which I,myself have used to unbrick my device.
small warning this will wipe all of your data.
Firstly I wants to thank Some_Random_Username for bringing up MSM Unbrick tool for OnePlus Nord. His guide to unrick nord is also fairly good enough but in my case I was stuck in bootloop after installing a rom. My phone was not even booting to Qualcomm EDL Mode so that I can use MSM Tool.
Lets start with pre-requisites:
You must have unlocked bootloader.
Original Oneplus Type - C cable.
Windows PC.
ADB debugging turned on your phone.
Firstly Switch off your device, which I think most of you have already have as the device is bricked but in case your phone is stuck in bootloop or recovery or bootloader menu itself then try holding down voume up button and power button together hold them down till you get heptic feedback and screen goes off. Let it be cool down for about a minute.
Now Setup your PC:
Download MSM tool to from this guide : Click here
Setup adb environment in your PC if you havent already setup follow this guide
Download Qualcomm EDL drivers from here: Click here
Now download Unofficial TWRP recovery by Mauronofrio from here
On your PC right click on start menu icon and start Windows Powershell(Admin) and type this command bcdedit /set testsigning on This will turn off driver signature verifications on windows you will be required to restart your pc now after you restart your pc will boot into test mode and you'll see a watermark stating the same in bottom left of your desktop. Worry not we will undo this after we have finished restoring.
install Qualcomm EDL drivers by running the setup listed above.
Unzip MSMTool there you will see a file named MsmDownloadTool V4.0.exe run it, it'll take some time but after you see a pop up asking for user type user name and password, Select other as user type and leave other stuffs blank as it is and click next.
In the next window, In the target button select O2 while using global tool or India while using indian tool or EU when using european tool.
Now you have to boot into Qualcomm Emergency Download Mode
You can do this in several diffrent ways but one I am listing here is recommended :
Boot into fastboot/bootloader mode by pressing and holding Volume up, Volume down and power button together when you see a Menu pop up on your screen you can let go all the fingers at once.
Now connect your phone to your PC and go to that folder where TWRP recovery is located. Hold Shift button and Right click inside that folder you'll see an option "Open powershell window here click on it. In the powershell window type
fastboot devices and press enter your device will be listed as fastboot devices in powershell window. Now type
fastboot boot twrp1.img press enter
your device will boot up in TWRP recovery in twrp recovery go to reboot section and select Edl, This will boot your phone Edl mode your screen will go off as soon as it happens in the MSM tool window you'll see a device listed as com3/com5/com7.
Click on start button the restoration process will begin. Wait for about 400 secs and your device will automatically boot up.
Voila you've successfully unbricked your phone.
If you want to exit from Driver test mode on your pc simply start a powershell window with admin rights and type
bcdedit /set testsigning off
and restart your PC.
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thanks!
peppanzer said:
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thank
Click to expand...
Click to collapse
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
IamAlok said:
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
Click to expand...
Click to collapse
the thing is that i cant flash other roms, my phone dosn't gets recognized in fastboot, recovery and edl, so with the aex recovery installed i have no chance to change the rom without a pc, reached out to the dev but seems i'm the only person with the proplem, but thanks for helping.