Database Develop

Unbricking "Service Required Code Corrupt"

If you use "xFSTK-SoC-Driver-Setup" and "unbrick.bat" to "Unbrick your phone, and you got the "Service code corrupt" error..., This method is untested but i think it is the problem...​You need This:
Original ICS FIRMWARE that come with your phone.
xFSTK-SoC-Driver-Setup Installed (read How Install "xFSTK-SoC-Driver-Setup")
Unbrick.bat and respective folders.
Motorola Handset USB Drivers (x86 or x64).
ADB/ FASTBOOT or SDK.
Steps to revive:
Extract Unbrick.zip in "C:\atomSOC"
Go to unbrick folder. "C:\atomSOC\unbrick"
Go to your firmware folder and copy this files (dnx; ifwi)
Replace this files in "C:\atomSOC\unbrick".
Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
Run unbrick.bat in "C:\atomSOC"
How Install "xFSTK-SoC-Driver-Setup":
Run Setup
When Say "Intel Soc Is about to begin" Click OK
When Say "In Order to Complete (...) Will a device be attached (...)" Press Yes.
When Say "Step 1 (...)" Plug In your USB Cable to the pc. and click ok
When Say "Step 2 (...)" Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
¿How know if my phone go to the medfield flash method?
release the camera button, your phone will stay in a black screen with the green led.
And your pc says "New hardware recognized"
Name of hardware: MEDFIELD
Before the driver install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads:
Unbrick.bat + xFSTK-SoC-Driver-Setup Download
If it works.. please, let me know​

Nope.
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen

1994deano said:
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
Click to expand...
Click to collapse
Try again, your phone is not going to medfield flash mode correctly

I did not get the part - Go to your firmware folder and copy this files (dnx; ifwi)
How to go to firmware folder?,
I do not understand how to copy

i just re tried it and its got rid of the service required screen but now the screen is just black with the green led on

Me too samething, any sugestion?

gmpdri said:
Me too samething, any sugestion?
Click to expand...
Click to collapse
csn you boot to bootloader?? (power+vol.down)?

Nope
pangyaaaaaa said:
csn you boot to bootloader?? (power+vol.down)?
Click to expand...
Click to collapse
no that is why we are trying to use the medfield flash, as the bootloader is screwed up

1994deano said:
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
Click to expand...
Click to collapse
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...

Boss442 said:
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Click to expand...
Click to collapse
ooh nice, let us know how you get on with it

S***, REALLY GOOD NEWS.....
RDS recognizes your phone on Medfield Mode...
Someone try to flash a firmware
Flashing Firmware dont work... ¿Maybe a custom XML Work?

HELP
For that ADB / Fastboot or SDK.?
Copying pro firmware?

saiko.sensei said:
For that ADB / Fastboot or SDK.?
Copying pro firmware?
Click to expand...
Click to collapse
if i found a way for bypass the "service required" error.. maybe you need fastboot... I am working with a lenovo pad (Intel SoC) maybe can use his flash tool to work (need fastboot). But dont recognize my phone, ¿Maybe need a custom driver? i am working in that

Yes, RSD lite recognises bricked phones, but it tries to enter fastboot mode to flash anything, so we're stuck...
Good luck!

Bricked while flashing JB Radio to ICS
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.

Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.

mercurio. said:
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Click to expand...
Click to collapse
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
SharpnShiny said:
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
Is your phone bricked in this condition right now? If it is, feel free to PM me.
Click to expand...
Click to collapse
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.

Boss442 said:
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Click to expand...
Click to collapse
I found out that the tool I ment is the xFSTK-Downloader ( rghost.net/44421368 ) that was alreaddy linked here at xda by U1138 in: http://forum.xda-developers.com/showthread.php?t=2184877
And yes, i suppose the black screen only and the service required brick are the same. they probably are due to a not working combination of firmware (ifwi & dnx) and flashed OS (i suppose the fastboot, no idea how where to get the dnx file needed for flashing it). you can try different ifwi and dnx files and get different results (so far i think there are only two types, the ones for JB fw and the others for ICS).
If you flash your rom with RSD going from JB to ICS you also flash the ifwi & dnx files, but not the bootloader. Therefore you end up with a non working combination of firmware (ifwi) and OS (fastboot) => nothing starts at all.
This problem was easy to fix for me flashing the appropriate JB firmware.
Then I did the mistake of flashing the JB radio before flashing a JB rom. This lead to a situation where neither the JB (leads to service required warning) nor the ICS (black screen, green led on) firmware works anymore and I have no idea how i could change the situation.
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?

mercurio. said:
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
Click to expand...
Click to collapse
+ 1
Everything else I was try with U 1138`s help - without result

St.Noigel said:
+ 1
Everything else I was try with U 1138`s help - without result
Click to expand...
Click to collapse
I read more than 120 pages in forums, and... NOTHING!
But i'm triyng to port a "flash tool" from lenovo pad... :silly:

[GUIDE] [ROOT] root LG L90 running D41510e or higher WORKS WITH LOLLIPOP AS WELL

Yah, so as the title says, ima show you how to root ur lg l90! The only reason im doin this is because @gdjindal's guide didn't work fer me. That runs v10e or higher WITHOUT DOWNGRADING. I'm not really sure if this works on previous firmwares, but let me know if it does :good:.
Firstly, the original tutorial is here: 1x1a.com/how-to-root-a-lg-optimus-l90-d415-10e.html
Code:
WARNING
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app
failed. Please view the original guide BEFORE looking at this
abridged version! YOU are choosing to make these
modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Download the files attached.
First things first: make sure you have USB debugging enabled (can be found in dev options in settings app) Install the drivers you downloaded.
Then, you should connect your phone to your PC/laptop (must be able to run batch files) in MTP (or your PTP equivalent) If prompted for USB debugging permissions on your phone, hit allow.
Now for the actual rooting.
Open the root script zip file, and extract it wherever you like. Extract the Drivers in this zip file and run the exe within. Then, open the folder and select the LG Root Script Batch file. Now just sit back and relax.
If you get a message saying that the serial port could NOT be found, then disconnect your phone and turn it off. Then WITHOUT TURNING IT ON, hold up the volume button and push in the USB cord. This should fix the problem. Once the process completes restart your phone manually.

Worked for me on a LG L90 D514 v10e . Thank you, as no other method would work.

I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!

Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!

CaptivateKing said:
I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!
Click to expand...
Click to collapse
Your very welcome on the guide. Never really superused linux before, got it on an old computer to make it run faster after xp got discontinued. Hope you can write the shell script and send me the modified files. The best of luck! :highfive:

silentpoke said:
Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!
Click to expand...
Click to collapse
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:

Confirmed for D415 Lollipop
This method also worked to root the Lollipop update. Thank you. (I hate bloatware.) Anyone who is looking for a how and is already rooted with a custom recovery, just use Rashr or Flashify to flash the laf.img file again and use LG Flash Tool (2014 at least) to flash the D41520b_00.kdz to update to Lollipop, then use this method to root.
View attachment 3258647 View attachment 3258648

can someone help
can someone help me i did the script and im on lollipop i can acess supersu but i cant verify the root via root checker pro or use SCR pro. and my phone reboots to the tmobile logo

G33KSQUAD said:
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
1 thing edited because it couldn't find my phone
I had to manually enter in what com port my phone was on, I used lg flash tools to determine, I edited the com ports while script was running and hit save, and boom phone rooted in like 30 sec.

I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CaseyRockStar said:
I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
Click to expand...
Click to collapse
Just go to about phone, software info, then repeatedly click on build # 7 times. It should say, congrats, you're a dev now!. Then go back to the main settings page and open the dev options. Icon should be like {} symbols. Then enable usb debugging, and click yes if it asks for authorisation when run the batch!

Keep an eye on Windows driver updates
Thanks for this! Just a note to keep an eye on the Windows driver notification in the taskbar. A lot of the hangups were that you had to stop checking Windows Updates for Drivers. Once I clicked that, the downloaded drivers were installed quickly and the script moved along.

Works!
At first I started to get scared because i had to retry the manual download and it says 0% and the computer is trying to connect and for the longest time i thought i did something wrong but it seems to be working!

I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol

cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
Does it not detect it when you disconnect the USB, put phone in DL mode, and reconnect to USB? Should automatically detect the com port when you do that
Sent from my LG-D415 using XDA Free mobile app

cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.

xanscorp said:
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.
Click to expand...
Click to collapse
Thanks for the advice. I'll give that a try!
Nope... it just does not want to recognize it. As soon as I put it into download mode my computer just refuses to see it. I tried putting those com ports in manually and nothing. Maybe its a cable problem. I'll see if anything changes with a different cable.
Figured it out... it was the drivers. I thought I had the right set, but when I installed the drivers again from this post, all worked like a charm. I am now happily rooted, and thanks for all the good advice.

Successfully rooted today. It didn't detect the port automatically for me either, but following the instructions to hold volume up during boot got it there. I posted screen shots of the script and my phone. I thought the script failed because you can see where it says Special command ##, it was stuck there for several minutes and my phone showed no progress but it showed rooted in red letters. This might have been because I ran this script at a different time thinking it failed (originally from this guide http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951), but I forgot to run the supersu app once the phone rebooted.

Quick question. I ran it and it was fine up until it looked for a COM port. I manually put it in download mode, and it told me it was missing MSVCR100.dll
I downloaded it, I used one in Sys32, and I get an error when Send_Command.exe gets executed. Any help would be appreciated. This is a clean install of Win7 and I only used the attached drivers.

This work on lg g4?

[GUIDE] [ROOT] LG Optimus L90 D405, D415 T-Mobile 4.x.x - 5.x.x One Click

ONE CLICK METHOD TO ROOT LG OPTIMUS L90
In this tutorial we will use the Windows computer. This method should work on any LG official firmware (Kitkat 4.x.x / Lollipop 5.x.x). I am not responsible for any gain or loss incurred as a result of following this guide. Root your device at your own risk.
Preparation
Make sure your phone battery is charged to 70% or more
Enable USB Debugging, by open Settings > Developers Option > USB Debugging
If Developers Option is hidden, go to Settings > General > About phone > Common > Software info (tap on it for 5-8 times)
Download and Install the LG USB Driver on the PC
LG driver - MIRROR
LG driver for Verizon
Download and extract the LG One Click Root
ONE CLICK METHOD TO ROOT LG OPTIMUS L90 D415:
Connect your device with computer
Run One Click Script by double-clicking the LG Root Script.bat file
This will open a command window. Follow the instructions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait until the root process is complete.
If the SuperSU App exist on your Application Menu on your smartphone it means you’ve succesfully rooted your device.
Caution!
If the phone not recognize, try to switch between MTP and PTP options.
If you got “MSVCR100.dll is missing” error, install Visual C++ Redistributable.
Download: 32 bit / 64 bit. (If 64 bit does not work try 32 bit)
For more details, please watch following video:
Congratulations! Now your LG Optimus L90 D415 has been rooted. You can verify that your LG Optimus L90 D415 is successfully rooted or not by downloading Root Checker App on Play Store. Hopefully the tutorial of One Click Method to Root LG Optimus L90 D415 useful for you. Source: Smartphone Clinic
I DO NOT TAKE CREDIT FOR ANY PROGRAMS OR SCRIPTS IN THIS THREAD
*If previous method was unsuccessful try this new method.*
I'm not responsible for any damages that may be caused by this method.
Install Kingroot APK http://www.kingroot.net/
Open app and click root.
*Optional (Recommended)* Replace Kingroot with SuperSU (DOWN)
Download
Terminal emulator app LINK
Replace_Kingroot_With_SuperSU.zip LINK a new ver LINK.
Before starting :
Download and install Terminal emulator app
Download and unzip "Replace_Kingroot_With_SuperSU.zip" file
Steps :
Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
Open Terminal emulator and type :
su
Allow root permission
Type :
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch SuperSU or open SuperSU manually.
Update SU binary normal, then reboot.
Done!

Hello. I have a problem with respect to USB debugging. Whenever I connect the cable to the phone (L90), even with debugging turned on and installed driver in Device Manager appears as "unknown device". Thus it is impossible to root. What do you think can be done? Grateful.

I can't root lg d410 since my phone update android 5.0.2 V20c

Wanpiro said:
Hello. I have a problem with respect to USB debugging. Whenever I connect the cable to the phone (L90), even with debugging turned on and installed driver in Device Manager appears as "unknown device". Thus it is impossible to root. What do you think can be done? Grateful.
Click to expand...
Click to collapse
Are you sure you downloaded the drivers?

ductuan9603 said:
I can't root lg d410 since my phone update android 5.0.2 V20c
Click to expand...
Click to collapse
Maybe this method does not work for d410. I don't own the d410 so I can't test it.

Billybobjoe13245 said:
Are you sure you downloaded the drivers?
Click to expand...
Click to collapse
Yes. It is properly installed.

Anyone tried this for D415 can confirm it is working?

shahsmerdis said:
Anyone tried this for D415 can confirm it is working?
Click to expand...
Click to collapse
Yes this is confirmed to work on the D415. tried it on mine.

Wanpiro said:
Yes. It is properly installed.
Click to expand...
Click to collapse
Sorry I never got a notification. But try different USB cables or ports. it is most likely the problem. Worst case try different computers. Because I'm sure it works.

Billybobjoe13245 said:
Sorry I never got a notification. But try different USB cables or ports. it is most likely the problem. Worst case try different computers. Because I'm sure it works.
Click to expand...
Click to collapse
It did not work, even changing the cables and ports.

I'm stuck at pushing files. What to do?

I'm on d41520b, and used LG One Click Root 1.3. The root seemed to go succesfully, I followed all the directions (I'm pretty sure), and nothing was implied to go wrong. When I tried to download Root Checker, the progress was stuck; the bar would keep going on, but never download (after clicking install, it never shows the donwload progress). In fact trying to get anything on the Play Store would act in the same way. And after a few minutes of booting with the root, the phone would crash. Unrooting would get rid of all the problems. Any help? Has anyone else had this problem? I'm not completely familiar with rooting.

Wanpiro said:
It did not work, even changing the cables and ports.
Click to expand...
Click to collapse
Try manually going into download mode. By holding volume up while the phone is off and then plugging in the USB cable. Still holding volume up.

Billybobjoe13245 said:
Try manually going into download mode. By holding volume up while the phone is off and then plugging in the USB cable. Still holding volume up.
Click to expand...
Click to collapse
Did not work. Download mode stands at 0%

this method does NOT work for stock lollipop D410 20C and 20D. Tested by me.

Why is this not stickied?! I spend an hour reading different things and this one was the most simplest and easiest ways!
I'm now rooted on Tmobile LG D415 5.0.2 - Next step, Cyanogenmod

Well I didn't quite solve my problem with the method mentioned in the OP, but on the other hand, Kingroot worked well. Towelroot said the device wasn't supported.
5.0.2 D415

crosswire said:
this method does NOT work for stock lollipop D410 20C and 20D. Tested by me.
Click to expand...
Click to collapse
I'll be sure to change the title.

i get this msg:
Pushing files.. cannot stat 'busybox': No such file or directory
the it stay in :
Looking for LG serial port..
what im doing wrong?

What model are you using?

LOCKED bootloader / possible to flash anything?

Hello guys,
Is it possible to flash anything to the Redmi 4X Global if the bootloader is locked? Perhaps using fastboot, Mi Flash Tool or some unofficial tool I don't know about? Maybe using the device's IMEI numbers and SN? Just shooting in the dark here.
My situation:
Locked Mi account, credentials unknown. Want to reset.
Details:
A relative of mine works at a store that sells smartphones. Boss rarely bothers sending defective devices for repairs and often gives them to employees instead. A customer brought this device back because some of the pixels on the screen are dead. He said he had performed a factory reset on the phone. They gave him a new one and handed the "defective" one to my relative who noticed the Mi Account Locked thing upon booting. When I got the device yesterday, the battery was dead. I charged it a little bit and when it turned on, it went through the setup normally, I was able to use the device without issues for 30 seconds or so (!), THEN it locked me out! That makes me think that if I let the battery go down to 0 and wait before charging and turning it back on, that will give me enough time to go to developed options and turn on OEM unlock and USB debugging (which needs a SIM card I think for some reason but OK). Then I may be able to unlock it; but that requires a lot of waiting and is unlikely to work anyway.
If you have an FRP locked Samsung phone, you just flash the stock ROM through Odin and it's as good as new. But Xiaomi locks everything down so tightly, there isn't even a download mode (just reboots to system if I choose "download" on the recovery menu)!
Wondering if there's any way to bypass all this? I don't mind the risk of bricking it cause it's useless as it is. Opening the device's back and tinkering is not an obstacle either :good: In all honestly, I understand Xiaomi does this for security (although if Samsung doesn't do it, I'm not sure why Xiaomi even bothers) and it would make me feel better knowing if someone stole my locked Xiaomi phone, they wouldn't be able to use this, but at the moment it's simply frustrating. I also know that officially unlocking the bootloader often doesn't even work, gets stuck or you never get an unlock code (personal experience with broken Xiaomi unlocking system)...
Any info appreciated. Thanks in advance.

i have a bootloader locked redmi x4 and wanted to take its original firmware backup (requires edl-mode) before unlocking/rooting/tinkering the device (i always do this with all my devices), tried every possible solution (except test point) but couldn't succeed.
You can try with deep flash cable or patched fastboot if your x4 has an old firmware...
And as per my knowledge, shorting test points is the only solution for new/updated xiaomi devices to open edl-mode now, only then you can reflash it... Good luck...
if you find any other solution, please share. As currently i have to wait for 3 days before i can unlock my x4...
Sent from my ONE 3G HD using Tapatalk

So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip ?, while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first

Or just wait a couple of days when you ask for a unlocked bootloader
Whatever floats your boat

Mister Advance said:
Or just wait a couple of days when you ask for a unlocked bootloader
Whatever floats your boat
Click to expand...
Click to collapse
Hi, I don't think you actually read the post. The device I got was completely locked, not just the bootloader. There was no way to remove the Mi account. Since the device does not normally have a download mode, there was no way to flash the stock firmware in order to factory reset it. The only way that I know of now, is what I did and described above

bi11ie said:
Hi, I don't think you actually read the post. The device I got was completely locked, not just the bootloader. There was no way to remove the Mi account. Since the device does not normally have a download mode, there was no way to flash the stock firmware in order to factory reset it. The only way that I know of now, is what I did and described above
Click to expand...
Click to collapse
Whoops, sorry read it to fast i gues then yeah xD
I already found it a weird solution to unlock a bootloader
Don't mind me pls

bi11ie said:
So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip , while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first
Click to expand...
Click to collapse
Hi, you were using miui 8 or 9 when you used the test point method?

uts58 said:
Hi, you were using miui 8 or 9 when you used the test point method?
Click to expand...
Click to collapse
Oops, forgot to mention..
MIUI 8
I don't think it makes a difference though. The test points are a hardware thing.

Locked bootloader and phone bricked
Hi,
I have a locked redmi 4x device which cannot boot to system. I can only boot to fastboot or to stock recovery. Since the bootloader is locked, I cannot flash TWRP or any rom. I have tried to apply for unlock permissions from xiaomi at http://en.miui.com/unlock/
but the link is greyed out for me. (screenshot attached)
Please let me know if there is a way to unlock my bootloader without the test points method. Thanks.

Your doing correct
Go ahead

Try using the Test Point, i use that to flash my new Redmi 4X from chinese version to global version.

Did it work?

bi11ie said:
Oops, forgot to mention..
MIUI 8
I don't think it makes a difference though. The test points are a hardware thing.
Click to expand...
Click to collapse
Thank you man!

fluster84 said:
Hi,
I have a locked redmi 4x device which cannot boot to system. I can only boot to fastboot or to stock recovery. Since the bootloader is locked, I cannot flash TWRP or any rom. I have tried to apply for unlock permissions from xiaomi at http://en.miui.com/unlock/
but the link is greyed out for me. (screenshot attached)
Please let me know if there is a way to unlock my bootloader without the test points method. Thanks.
Click to expand...
Click to collapse
Hi, as far as I know, there is no other way. The test points are there exactly for cases like yours and mine, where you need to restore a device to factory defaults. There's no reason not to try it. If you are careful, you won't damage the phone and it won't even show that you opened it.

Hi,
I restored santoni 8.2.8 in EDL mode but bootloader is still locked, did I miss an important step?
best regards

Sorry for pulling an old thread but I was wondering if this solution would work in Redmi Note 3SD as I am facing the same problem i.e. locked bootloader and no option to enter developer options for turning on debugging options

I have the same issue
bi11ie said:
So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip , while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first
Click to expand...
Click to collapse
Hey, so I have the same issue.. Redmi 4x boots into the boot screen all the time.. Bootloader is locked so I can't flash a ROM from Fastboot. I found a solution wherin I require to use a Deep Flash Cable so as to flash a stock ROM. I just ordered one and am planning to try that. Do you think that method would work as well? .... After reading your post I tried opeing up the phone... but one of the screws is so messep up it just isn't unscrewing!
So my question, is the Deep Flash Cable method legit ?
---------- Post added at 01:57 PM ---------- Previous post was at 01:47 PM ----------
sambau5 said:
Hey, so I have the same issue.. Redmi 4x boots into the boot screen all the time.. Bootloader is locked so I can't flash a ROM from Fastboot. I found a solution wherin I require to use a Deep Flash Cable so as to flash a stock ROM. I just ordered one and am planning to try that. Do you think that method would work as well? .... After reading your post I tried opeing up the phone... but one of the screws is so messep up it just isn't unscrewing!
So my question, is the Deep Flash Cable method legit ?
Click to expand...
Click to collapse
Alrternate method found:
#1 To enter EDL mode (also known as Download mode) :
Make a 'Deep Flash Cable' by short-circuiting the 'Green' and the 'Black' wire inside the USB cable. I would better recommend you to buy a quality thick USB cable from a local store and tell the guy to cut open the cable and solder the green and the black wire to a small switch.
Now, power off your device and yes, make sure it's powered off. (In case the device is not getting powered off, see the images below for disconnecting and reconnecting the battery connector.)
If Windows 10 or 8/8.1, press 'Shift' key while restarting your computer. Now, go to Advanced settings - Startup Settings - Reboot, and if on Windows 7, reboot your PC and press F8 key before the Windows startup icon appears.
Now, select 'Disable Driver Signature Enforcement' from the list.
Connect the cable to your phone and pressing the switch, connect the cable to your PC. Your phone should not show as charging. Being sure that it's not charging, release the switch. You should now see your device recognized as 'Qualcomm QLoader 9008' under Device Manager. Voila ! You are on EDL mode.
Link for making your own Deep Flash cable : https://www.youtube.com/watch?v=hmdrj4uX7gY
#2 To flash official MIUI ROM :
Download the fastboot ROM for your device, and download the latest Mi Flash tool from http://api.bbs.miui.com/url/MiFlash
I would recommend downloading the fastboot ROM with a separate download manager. Internet Download Manger - Recommended (https://www.internetdownloadmanager.com/download.html)
Also install 7Zip and WinRAR from https://ninite.com/
Now, first extract the fastboot ROM file with WinRAR and then re-extract it from the extract folder with 7Zip, and shorten the file names.
Having installed Mi Flash tool along with all its drivers ( I mean the popups asking for installing driver while installing Mi Flash), run it and select 'Clean all' from the bottom-right side.
Click 'Refresh' and it should show as 'COM10' or something similar. Now, click 'Flash'. And yes, that's it.
After successful flash, disconnect it from the cable and boot it up by pressing the Power key until it vibrates and turns on.
Yeah, you DID IT
*Why a download manager ? I had downloaded the file with Chrome and Firefox (without even pausing it), but even after successful flash, the phone does not boots into MIUI. It gets stuck on the MI logo. However, on using a download manager, the boot successfully completes without any hassle. I have used several download manager, but only IDM downloads the file with .tar extension which always and YES, ALWAYS results in successful flash. You can try out a different method but I would recommend you to play safe as my method is FOOLPROOF.

I have try this method before, but unfortunately it doesnt work. When i connecting those 2 pins, there are nothing changed in my device manager. No new hardware founds at all. I Have install these drivers too, no luck
---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------
meltbanana said:
Hi,
I restored santoni 8.2.8 in EDL mode but bootloader is still locked, did I miss an important step?
best regards
Click to expand...
Click to collapse
Flahing ROM didn't unlock your bootloader bro. Its just a way to migrate from somehow global rom into dev rom. UBL is kind of different things

Hello
i've bought a used phone, and the device is locked (MIUI10) with the MI account of the first owner. The bootloader is locked.
If i try to flash ROM in EDL mode, is the MI account of the first owner will be delete ??
Thanks

conduisant said:
Hello
i've bought a used phone, and the device is locked (MIUI10) with the MI account of the first owner. The bootloader is locked.
If i try to flash ROM in EDL mode, is the MI account of the first owner will be delete ??
Thanks
Click to expand...
Click to collapse
Yes, it should be.

Phone bricked after trying to update to android 6

Hello, I have the LG G4 H811 (S/W: V10d, written on back of the phone) version. After buying the phone, I tried to update to marshmallow from lollipop using LG Bridge as the automatic update wasn't coming to my phone. After the process was apparently completed my phone isn't turning on anymore. Tried power button, volume up+down+power etc. But not working. no charging sign.
When connecting the phone to pc through usb, most of the times it doesn't find anything ("unknown usb device" or something). Once in a while it finds as "Qualcomm HS-USB QDLOADER 9008" in device manager. ( P.S. It finds as "Qualcomm HS-USB QDLOADER 9008" if I remove and insert the battery for the first time)
Now I've surfed the net for a few hours and found various potential solutions. Was trying this solution first: boycracked dot com/2016/08/04/how-to-unbrick-updates-firmware-flashing-any-lg-android-devices-using-kdz-updater-tools/
(Can't copy direct link being a new member. please replace the "dot")
But the method is not working. Showing "extract file error" when i select the .kdz file and click "launch software update"
Should I try this method: androidmtk dot com/use-qualcomm-flash-image-loader-qfil
By the way, Do I need a specific .kdz file (stock firmware) for the V10d variant? If so, I haven't found it after searching for hours and was trying different .kdz files (all for H811 though). If I need the specific file please give me some link where I can find it. So far the model number(H811) isn't matching when i find a V10d version.
I'll try to use the SD card fix once I manage a card and card reader: forum dot xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
Still I would need the specifc .kdz file I guess for V10d version??
Also if possible please give me the link to a method which is apparently most successful as it seems to be a old problem.
My phone is virtually brand new and am feeling a bit helpless. Please help me by giving some effective solutions. Thanks in advance.
Update: FWIW I followed this link: forum dot gsmhosting.com/vbb/f779/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box-2211744/
I apparently succeeded in finishing the operation (didn't use jumper method. Pressed volume up+down method)
But after it showed "succeed", nothing seems to have changed. But seems like the phone is shown as "Qualcomm HS-USB QDLOADER 9008" every time I connect it to PC. Before doing this operation, I had to remove battery and insert again to show it that way. Otherwise it showed "unknown usb device"
But seeing that nothing substantial happening, i tried to follow the same process again. But this time it showed error "Unable to download flash programmer using Sahara protocol"
I don't know what's happening, but just describing the process so that it might be easier for experienced guys to understand.

Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Instructions:
1. Connect USB cable to PC.
2. Power off phone and then hold Vol. Up while connecting the USB cable to phone.
3. Your LG G4 should now be in Download Mode.
4. Start LGUP.
5. It should detect your phone. If it does, you will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. Select "Upgrade" and then use the "...." to select the .kdz for your phone.
7. Now decide if you want to do a full wipe and flash (Refurbish), or upgrade to a higher version of Android (Upgrade) and keep all of your files and settings.
8. Hit "Start" and wait for it to finish. It may restart your phone a few times. Be patient.
9. You can check the percentage under "Progress".
10. It will let you know when it's done.

Gurren Lagann said:
Why not just use LGUP to flash the Android 6.0 Marshmallow .kdz as a "Referb" and be done with it?
Get the Android 6.0 Marshmallow .kdz for your phone model here:
http://storagecow.eu/index.php?dir=Xda/LG+G4/
Look for T-Mobile H811.
Click to expand...
Click to collapse
Which H811 version should I use? As I asked do I need to use the specific version my phone had before being bricked? (I don't remember which but the default version written on the back of the phone is V10d)
Gurren Lagann said:
Get LGUP here. LGUP is better than the LG Flash Tool (IMO) and it's easier to use. Don't let the instructions deter you. It's simpler than it looks.
https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LGUP couldn't detect my phone. I can't remember if I used volume up when connecting but I've tried similar things when trying to different softwares and it wasnt working.
I've given it to a repair shop. After they removed the battery and plugged in two wires from some device to the back of the phone it did turn on but the lg logo came and showing probably error 1006. The repaired said the phone isn't coming to the 'download mode'.
Then they initally tried downloading some h811 dump file and installing it. But failed. Now they're saying they'll need to use JTAG box to fix it.

I just remember now, after buying the phone from some guy, I factory reset it. Now when I opened chrome, some att dot com website was showing as default homepage. That website started loading by default. What does it mean???
Does it mean the phone already had at&t(H810) firmware installed? But when powering on the phone it shows T-mobile logo and H811 is written on the back of the phone(after popping out the back cover) multiple places.
The repairer says the phone is refurbished( (I also think so). So two things can happen:
1. The motherboard was originally H811 but a H810 motherboad and H810 firmware were installed on the phone upon refurbishment. In that case why would it show the T-mobile logo when the phone starts?? Also it showed "H811" in Android (About Phone>>Model number)
2. The motherboard is still H811, but somehow H810 firmware was installed on the phone. Is it possible??? If it is then when I tried to do official update using LG Bridge, maybe LG Bridge thought the phone firmware is H811 and tried to install H811 firmware over a H810 one and the phone got bricked.
What do you think guys?? Any expert suggestion will be highly helpful... As I do feel like knowing which installing the proper firmware(H810 or H811) will take the phone back to life.

Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Sounds like a Frankenstein device. You can't recover it with using the wrong files. Jtag or not.
Identify the real model first (mainboard FRONT)
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.

onikett said:
So I've to install the firmware(.kdz) according to the model no. written on the motherboard, no matter what other firmware was installed when the phone was running?
Another question, when running normal, it showed "H811" as model number in "About phone" section. Is it possible that the motherboard is NOT H811 but a H811 firmware was installed on it during refurbishment?
Btw, where is the model no. written on the mainboard? Here's a link of the phone teardown: https://www.ifixit.com/Teardown/LG+G4+Teardown/42705
Please give me the link of the picture where it's showing the model no.
Click to expand...
Click to collapse
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Frankenstein is what we call a device which is refurbished in a hackish way:
https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post75817533
---> FAQ 21
So yes I can even let your device say it's an iPhone in android settings, download mode or almost anywhere. It's just code. And yes it's easy.
You can also just flash parts of another ROM if you know how and what so it does not brick or blow fuses. Dangerous when you don't understand how the g4 works internally but the refurbish ppl know what they do to fake the device enough so the average one do not see a diff.
You just have to follow that link in the above FAQ 21 and disassemble the mainboard and on the front you will see it.
Click to expand...
Click to collapse
Thanks.
1. Do I have to use the .kdz compatible with the actual model number written on the mainboard?
2. Should I use LGUP procedure mentioned in an above post (by Gurren Lagann)?
2. How to know what version of .kdz do I have to install? I heard if the installed version is a downgrade from the actual version (before the phone was bricked), it will not work.
3. If LGUP can't detect my phone due to it being totally hard bricked, what procedure should I follow to install the new .kdz?
I'm not an expert on the intricacies of Android OS. So please answer the questions elaborately.

Dont Try to Update 6.0, if dont wont bricked 9008 mode