How to recover Lenovo Legion L79031 in EDL mode (easy mode) - Lenovo Legion Duel Guides, News, & Discussion

Hello guys, today I will explain how to recover a dead phone in EDL mode
Only for international devices, do not apply this to Chinese devices
-----------------------------------------------------------------------------------
Update 12.5.538 solves the problem of the 5G network
1-Download Qualcomm Tool 9008 : install After installation restart your computer
-------------------------------------------------------------------------------------
2-Download the official ROM for the phone 12.5.538 : install
-------------------------------------------------------------------------------------
3-download tool QPST : install
-------------------------------------------------------------------------------------
4-Extract the contents of the ROM to the C disk
-------------------------------------------------------------------------------------
5-Go to the path of the tool as shown in the video
-------------------------------------------------------------------------------------
6-Press the volume down button and the volume up button together and plug the wire into the side port of the phone
-------------------------------------------------------------------------------------
7-Go to the device manager option on the computer, make sure that everything is OK and that the phone is connected to the com port 9008
--------------------------------------------------------------------------------------
8-Go to the tool as shown in the video and choose the port number in the box and apply what is mentioned in the video
--------------------------------------------------------------------------------------
9-Click on the word download and wait for the device to turn on
-------------------------------------------------------------------------------------
10-DONE
----------------------------------------------------------------------------------
educational video:::: ((((VIDEO))))

@-VEDMETA- My fellow @Oswald Boelcke already advised you to put such thread where it belongs in the "Guides" section, as it doesn't qualify for development.
I've moved the thread but this will be the last time we warn you about this.
For further information, please refer to the guidances and announcements that are stuck at the top of every forum and that I suggest to thoroughly study prior to your next posting like this one:
[INFO] Device Forum Rules (Please Read before Posting)​
Regards
DaReDeViL
XDA Moderation staff

DaReDeViL said:
@-VEDMETA- My fellow @Oswald Boelcke already advised you to put such thread where it belongs in the "Guides" section, as it doesn't qualify for development.
I've move the thread but this will be the last time we warn you about this.
For further information, please refer to the guidances and announcements that are stuck at the top of every forum and that I suggest to thoroughly study prior to your next posting like this one:​
[INFO] Device Forum Rules (Please Read before Posting)​
Regards​DaReDeViL
XDA Moderation staff​
Click to expand...
Click to collapse
I'm new to the site and I don't think I wrote the topic in the development section next time I will make sure of this, thank you

-VEDMETA- said:
... I don't think I wrote the topic in the development section ...
Click to expand...
Click to collapse
I wouldn't be here if it wasn't the case.
Anyway, thank you for your collaboration.

You can use the tool provided by Motorola (owner of Lenovo) to recover the device!
rescue-and-smart-assistant - Motorola
#hellomoto | Discover our new unlocked Android phones from motorola and stay informed about our offers and promotions.
www.motorola.com
Way simpler to use this and fail safer too

I have a question, how to deal with the Qualcomm crashdump mode?

-VEDMETA- said:
Hello guys, today I will explain how to recover a dead phone in EDL mode
Only for international devices, do not apply this to Chinese devices
-----------------------------------------------------------------------------------
Update 12.5.538 solves the problem of the 5G network
1-Download Qualcomm Tool 9008 : install After installation restart your computer
-------------------------------------------------------------------------------------
2-Download the official ROM for the phone 12.5.538 : install
-------------------------------------------------------------------------------------
3-download tool QPST : install
-------------------------------------------------------------------------------------
4-Extract the contents of the ROM to the C disk
-------------------------------------------------------------------------------------
5-Go to the path of the tool as shown in the video
-------------------------------------------------------------------------------------
6-Press the volume down button and the volume up button together and plug the wire into the side port of the phone
-------------------------------------------------------------------------------------
7-Go to the device manager option on the computer, make sure that everything is OK and that the phone is connected to the com port 9008
--------------------------------------------------------------------------------------
8-Go to the tool as shown in the video and choose the port number in the box and apply what is mentioned in the video
--------------------------------------------------------------------------------------
9-Click on the word download and wait for the device to turn on
-------------------------------------------------------------------------------------
10-DONE
----------------------------------------------------------------------------------
educational video:::: ((((VIDEO))))
Click to expand...
Click to collapse
I have a question, how to deal with the Qualcomm crashdump mode?

masterouch said:
I have a question, how to deal with the Qualcomm crashdump mode?
Click to expand...
Click to collapse
flash persist.img file. But fingerprint sensor will not work anymore because you broke your original persist files

Related

Mediatek MT65xx Successfully Unbricked

Hi guys:
After 1 day tries Mediatek MT6575 GT-S7562 was unbricked with no test point. after it was dead because of wrong ROM flashing.
Steps:
1- clean your drivers and install VCOM driver according to this video tutorial:
https://www.youtube.com/watch?v=hKYH7gkvrvY
Big thanks to : ITXtutor
2- Big thanks to : yuweng for the nice quote
with the the WARNING & you still do it...
Inspired by fellow xda member to start this thread to help out other xda member that run in to similar problem so here are the solution but it might not work for all MT65xx...
If you have already brick it by flashing wrong PRELOADER then you still have a 50/ 50 chance to revive it so keep you fingers-crossed...
For MT6573
Requirement : Your MT6573 factory ROM, SP Flash Tool
MT6573 Meta Driver - If you don't have, download it from here
First you will need to open Device Manager, switch off your phone, press & hold Menu button but don't let go, now plug-in your usb cable will activate META mode(Thanks to Master Shifu Cybermaus for his insight knowledge)...You'll notice Mediatek USB VCOM will appear at Device Manager -> Ports
Mediatek USB VCOM will stay connected until you download factory ROM then it will auto disconnect, reconnect as PRELOADER USB VCOM & continue downloading...
After factory ROM download completed, it will be auto disconnected & you'll have your phone raise from the dead !
This hidden feature will enable you to download factory ROM when you brick it by flashing wrong PRELOADER meant for other phone however for some MT6573 there is no way to access META mode except by dismantling the whole phone...
If you can't find your model factory ROM, try to hunt for similar ROM. I have had feedback from fellow xda member it actually works ! Luckily, most MT65xx ROM are very similar to each other. Try to look for similarity at build.prop -> ro.build.product for eg, typical build are bird73_gb , e1109_v73_jy1, huaqin73_gb, tinnoes73_s8030_2g, mt73_w831_a9100_yingt & etc... google search is your friend...
For MT6575/ 77
With the battery out, hold the volume up, don't let go & plug in the USB cable will activate META mode for few seconds...Typically, you need to click Download at SP Flash Tool before entering META mode or it will auto disconnected...
If all doesn't work & you don't have a local service center for your MT65xx then may be you would want to try rua1's method but its not for the ordinary user... Use google chrome for translation...
Attach is few photos that i've downloaded from that forum as it can only be viewed by members at that forum....
----------------------------------------------------------------------
Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE
it seems that MT65xx is really 'unbrickable' thanks to whitetigerdk who inform me with his how-tos
So you can raise your DEAD MT65xx back to life...
The trick is quite simple, for whitetigerdk case, he flash his GooPhone Y5 with Zopo100 factory ROM & the phone went DEAD...
He proceed to reinstall preloader driver from Zopo & was able to use FlashTool again and flash back his factory GooPhone ROM & thats how he brought back his MT6575 back to life...
Updates
i've pm'ed whitetigerdk & got a reply from him confirming that indeed his GooPhone Y5 has this META mode built-in (plug in USB while holding VOL +)
Device Manager will detect new device... Having said that, not all MT65xx device has this feature...
----------------------------------------------------------------------
Added on Dec 20, 2012 - DO NOT USE MEMORY TEST AT SPFT !
There has been confirmed cases that fellow xda member brick their MT6575/ 77 by using the MEMORY TEST function at SP Flash Tool !
When you put a check mark at NAND Flash Test or EMMC Test what it does is that it actually FORMAT it & this will brick your device !
For those who are having problem such as 3013 S_DA_SOC_CHECK_FAIL or 8038 SP FLASH TOOL ERROR for MT6575/ 77 even with testpoint, you will need SP_Flash_Tool_v3.1224.0.sn85
I have upload it to here for ease to fellow xda member, Credits to Master Shifu rua1...
----------------------------------------------------------------------
Added on Jan 06, 2013 - DO NOT JUST FLASH ANY ROM WHEN YOU BRICK YOUR DEVICE !
Well known brands like Lenovo, Zopo, ZTE & etc do provide FACTORY ROM at their webpage for download...
However, for those lesser known brand, its hard to say so you will have to hunt for it & do as the title says...
Credits to XDA Senior Member cybermaus, he has put up a simple guide on How to search for replacement rom...
----------------------------------------------------------------------
Added on Feb 11 2013 - Guide for Backing Up your device Factory ROM
This guide here is meant for you to pass to a good Samaritan that will help you unbrick your device, hopefully...
----------------------------------------------------------------------
Added on Feb 20 2013 - Mediatek Driver Auto Installer
Found a Mediatek Driver Auto Installer, download it from here... Will be useful for those having drivers issues...
Works on WinNT, WinXP, Win2003, WinVista, Win7 be it x86 or x64, just double-click Install...
But remember to turn off User Account Control Settings...
----------------------------------------------------------------------
Added on Feb 25, 2013
Operation to Support & Reward our MTK SoC Developers
Head up to here & show your support...
----------------------------------------------------------------------
Added on May 13, 2013 - Reward for a Job Well Done
It is Master Shifu rua1 that discovered MTK devices can be unbrick via testpoint & he has developed a great tool & continuously updating it, the MTK Droid Root & Tools that can backup Factory ROM out of an unknown MTK devices, get hardware information, Root it, port CWM & many many more...
Its sad to see users are taking advantage of all these free infos & tool developed by Master Shifu... Recent check with Master Shifu & he told me he only get 3 donations from xda Come on people...
Please understand the significant amount of time and effort required to understand how the MTK devices works, then developing a software, a new function, bug fixes, add new features, testing it & etc before releasing it as a free tool...
Master Shifu never demanded any payment for using his software & inline with the xda spirit to Gives Credit Where Credit is Due you should start hitting the DONATE button now...
As i have mention in this thread before, when you have unbrick your MTK devices using these infos & tool by Master Shifu, it means you don't have to fork out another USD 200+ to get a new devices...
So how about spending Master Shifu breakfast, lunch or dinner that you have manage to save $$$
Pls pls consider making a donation to the Master Shifu rua1 to support him to continue development of this free great tool...
Free software/ tool on xda = you download it, use it & it help you = Hit that DONATE button
in this thread :http://forum.xda-developers.com/showpost.php?p=32960423&postcount=1
.
3- According to yuweng thread .. use just this SP flash tool:
http://www.4shared.com/get/wz6lmzBJ/SP_Flash_Tool_v312240sn85.html
4- Use the correct Preloader from your original ROM or factory ROM>> open your scatter with this tool and just tick the preloader.
5- while your battery not inserted >> if did not work then insert battery and try again >> while USB cable not plugged in computer >>hit the download button >
6- While continue pressing on volume up key >> plug USB cable into PC and stay pressing on volume up button >> the preloader will be flashed back to phone.
maybe not from the first time...
7- unplug USB cable and remove battery . then with select all files in ROM >> and hit download button >> plug USB cable and insert battery >>
8- flash will start and your phone will be unbricked.
Confirmation in Attachment>
Greets.
Help me to unbrick My GOSCO GS310...???
My english is bad.
I have Smartphone Android 4.04 GOSCO GS310.
I already read from Flashtool and i've got ROM_0. after that i use mtkdroidtool to process rom from flashtool and i've got some files like these file :
preloader.bin
dsp_bl
boot.img
uboot.bin
expdb
nvram.bin
factory_NonModified_recovery.img
logo.bin
misc
MT6575.fat
MT6575_Android_scatter.txt
seccnfg
secro.img
__nodl_yaffs_system
The problem is...i cannot flashback all of that files, even i try to flash only preloader and dsp_bl. the message from flashtool sometimes looks similiar but sometimes different, help me guys...please...:crying:
some message : s_da_dram_not_support (3004) / S_FT_ENABLE_DRAM_FAIL (4032)
I think my file that come from "read by flashtool" error... or i have doing something wrong when i fill the read start address by the hex file or anything wrong... i have been confused about almost 2 months.
NOTE :
I already Format Whole Flash by Flashtool, it's done but problem still exist or maybe worst.
Maybe you can give me other alternatif to use other ROM or else.
thank you very much for the help guys...

Data recovery from Samsung I9300i with broken display and no debugging mode on

Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
miborion said:
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
Click to expand...
Click to collapse
Have tried today, 3 different phones (some Sam I9300, Sam A3), but still same issue, devices not shown in devices command although I had enabled developer mode.
Should I check somethings regarding the PC? the port if is opened or not?
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Salman Al-Badgail said:
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Click to expand...
Click to collapse
Hello Salman,
The reason why I opened this post is that I need something which is not specific to my mobile model, in my case Sam. i9300i, but something which is useful for any other user as well, especially ones in my situation (broken display, with no debugging mode activated).
What I was trying to find in this section of the forum and trust me, by now I have read everything it was to read on this topic, was a custom build rom, which could have that debugging mode activated, as without it I (or somebody else in this predicament) cannot extract the needed data via ADB.
Therefore if somebody has any idea or knowledge about a such image, please do share.
Regards,
maybe you could try to enable the adb before you flash the stock rom by editing the build.prop file.
or you simply could try with this http://forum.xda-developers.com/tools/general/tool-gstreamer-emergency-toolbox-t3289951
good luck bro

Unbrick Oppo R5 /R5s

Unbrick Oppo R5
Since oppo forums support is minimal and a lot of Oppo R5/ R5s owners are facing difficulties flashing new rom and since Oppo is unbrickable here are a guide as posted to oppo forum members by the member Ricky.
I had clear instructions not to post this tool anywhere BUT THEY DON’T SUPPORT ANY DEVICE and I have to break my promise as they broke any kind of support.
This community (XDA) is to help all members
The tool works with windows 10 and not only with windows 7 as they mention in their instructions
Packages you have to download first
1- Firmware ColorOS https://www.partage-facile.com/LM6Y85FF7Z/r8106ex_11_a.16_150806.tar.bz2.html
File Name: R8106EX_11_A.16_150806.tar.bz2
Size: 1.4GB
MD5: F85ED63BA637B559976D9BFF0AED0187
2- Instructions:
https://drive.google.com/file/d/0B3AWkNVCRSNVZGNRUE1rQW5YOFk/view?sid=
3- Driver : http://en.oppo.com/downloads/firmware/driverForFind5.rar
Mirror for driver http://www109.zippyshare.com/v/MEMiPlOv/file.html
Attention
a-Unbrick tool will wipe all data on your device including photos and music etc, if do you want to reserve your data please make o back up on your PC
b- After unbrick the first time power up take around 5-15 minutes
c- The most important things are to install the driver. For windows 10 you must enable unsigned signature verification through windows advanced settings (google it) prior driver installation.
d- In order to shut phone completely hold the power button for 8 -10 secs
How to use the tool
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
amadoro said:
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
Click to expand...
Click to collapse
For R5 use 14016.
mermigas said:
For R5 use 14016.
Click to expand...
Click to collapse
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
amadoro said:
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
Click to expand...
Click to collapse
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
mermigas said:
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
Click to expand...
Click to collapse
Thank you so much. it worked. Not my Oppo r5 is back alive.
Where is the download?
Is it normal that when I hit the download link there appear aliexpress??
I thought I had bricked my R5 but while trying to follow this guide it wasn't showing up in the "Ports" section of the Device Manager. I found that my phone still had fastboot, so I used it to install latest TWRP and then the repair rom. And now my phone is finally back to working condition! I hadn't modified in any way my phone and one day it got stuck at the logo. Anyway, thanks for the guide Mermigas!
anyone mirror pls
mega
[email protected] said:
anyone mirror pls
Click to expand...
Click to collapse
[dead link]
If it asks for a key leave it blank
Kushracer said:
https://mega.nz/#F!q8YFEJyB
If it asks for a key leave it blank
Click to expand...
Click to collapse
No asking for decryption key
mirror
Uploading here: R5S Unbrick Tools
Please help
After i have done all those instructions: my phone was completely dead(no more display and can't use any buttons).
Please what should i do for revive that.
Link Broken
cpuld you re-load the link of Color Os firmware please?
Its not valid now =(
Number for R5S?
Hi, I tried the 14061 for my OPPO R5S. Unfortunately it did not work. Now the phone is not starting.. help? Should I use another number?

Is my NOKIA TA-1032 really dead?

On April,2018, I have updated my NOKIA 3 to Android 8.0.0 from Android 7.0. In between I didn't got any 7.1.1 update. Few days ago, I found a 7.1.1 ROM for NOKIA 3 & I downloaded it & tried to install the update from SD card in Recovery mode. My NOKIA 3 aborted the update & I tried the same for 3 times. After this, everything blew away leaving the Recovery mode & I was only able to go to the Fastboot mode. When I used to power it up, it directly used to go to the Recovery menu showing (alps/NE1_00W_FIH/NE1 7.1.1/NMF260/00WW_2_15A user/release_keys Use volume up/down & power key).
I tried OST LA with NE1-215H-0-00WW-B02.nb0 & NE1-215H-0-00WW-B02.nb0 files but OST LA handed me with a pop-up message showing some problems with JIT(Just In Time) Debugging. I continued, but OST LA got stucked on "loading system images" or "rebooting bootloader". I continued this for 3-4 days bit this didn't worked for me.
Then I decided to flash my Mediatek device with Smart Phone Flash Tool & flashed it with a ROM found on internet named "Nokia_TA1032_MT6737M_12042017_7.0" & after flashing it started only vibrating each 3-4 seconds when I tried to switch it up & when charger is connected. while connected with computer, Device manager showed that Mediatek Preloader is working but there was no light, no display in my NOKIA 3. It was only a black screen with vibration each 3-4 seconds. this also didn't worked for me.
I unpacked the nb0 file NE1-215H-0-00WW-B02.nb0. There was a ik_service.zip , which I couldn't unzip as it is secured with a password. Whithout ik_service, I went to flash it with SP Flash Tool. I tried to flash it unticking the Preloader, but SP Flash Tool was unable to flash it without the Preloader, so I flashed it ticking the Preloader. The flashing process was successful, & completed upto 100%. After that, my NOKIA 3 is completely dead. There is no viblation also. Connecting to the computer only shows mtk usb port is working, but not the preloader. And now I am unable to flash it again.
I think, the Preloader is deleted parmanently. Computer makes sound on connecting the NOKIA 3 and Device manager shows only Mediatek usb port is working. Is there any way to get it back? Can I flash it with the Preloader again? Or is it impossible to flash a device without Preloader? Is my NOKIA 3 completely Hard Bricked?
Saurav Dev said:
On April,2018, I have updated my NOKIA 3 to Android 8.0.0.........
Click to expand...
Click to collapse
I don't have this device but, I believe that the following thread should be helpful for what you are looking for that's specific to your device. Don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3719357
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore 64.
Ibuprophen said:
I don't have this device but, I believe that the following thread should be helpful for what you are looking for that's specific to your device. Don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3719357
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore 64.
Click to expand...
Click to collapse
Thank you very much Sir.

MDZ-22-AB Mi Box S Bricked

Hi , trying to recover the above and looking for any img file of Android 9 for this box to recover it .I believe it shipped with pie out of the box so the method using oreo img is not working . Box is dead no picture just read light and in constant worlcup mode no need to short it connects to usb burn tool immediately . Can find lots of update zips but not useful as not responding to bootcards made . Any ideas would be great but i think the only way is to get hold of a pie image .
Kind regards
jimenis said:
Hi , trying to recover the above and looking for any img file of Android 9 for this box to recover it .I believe it shipped with pie out of the box so the method using oreo img is not working . Box is dead no picture just read light and in constant worlcup mode no need to short it connects to usb burn tool immediately . Can find lots of update zips but not useful as not responding to bootcards made . Any ideas would be great but i think the only way is to get hold of a pie image .
Kind regards
Click to expand...
Click to collapse
hello
check this thread
[Update] unbricked my mi box s mdz-22-ab
[Update] Solved the issue 1. Go to this link 4pda . ru/forum/index.php?showtopic=399304&st=600#Spoil-55136455-3 (Of course without spaces) Or just search on google for "4pda forum" then in the forum search for mdz 22 ab 2. You will find a tread...
forum.xda-developers.com

Categories

Resources