Database Develop

UnBrickable SD necromancy- Totally restore your device.

Hi guys. Ralekdev, Rebellos and Myself have become quite good at hacking the extra roxor out of Samsung devices. We started with The UnBrickable Mod which now spans 15 total devices on the Samsung Galaxy S series. The UnBrickable Mod turned the Galaxy S into a development board. So we moved on to sucessfuly hacking the Qualcomm bootloaders on the Verizon Galaxy S3 and while our exploits for this device have not yet been needed, we have them ready to deploy on several devices and we've learned alot. Today we would like to present to you:
UnBrickable SD-The ultimate in Exynos Necromancy
The UnBrickable SD allows for total resurrection of an otherwise hard-bricked and dead device. It takes a device-specific SDCard, and a jumper to be placed across a tiny resistor. This triggers the device to silently boot at which point it will count to 10 and reload the device's bootloaders. This uses Samsung Official firmware unlike UnBrickable SD Mod (unreleased as of the time of this post) which allows for dual-booting of custom and official.
Why would I need this?
The processor has a small bit of ROM called IROM that tries to initialize the EMMC to load SBOOT. SBOOT then fully initializes the EMMC(Internal and soldered down MMC chip) where it pulls boot parameters, partition tables and all other information for the device to boot. if the SBOOT is damaged, the device will no longer boot and Odin/Factory modes are destroyed and the device is hard-bricked. This failed boot means the device cannot function and is locked up.
How does UnBrickable SD work?
The UnBrickable SD works because the processor is configured to attempt to load SBOOT from EMMC and then fail-over to SD, and finally UART. We've prepared an SDCard via the sdcard command in SBOOT below. By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot, check the signatures, see a valid image, and reload the SBOOT onto the EMMC thus enabling Odin.
Instructions
You will need:
The SDCard Image: http://d-h.st/KIV
The Partition Information Table(PIT file)
The Odin Firmware(Heimdall one-click coming soon) http://forum.xda-developers.com/showthread.php?t=2006138
Samsung Kies (for its drivers) http://www.samsung.com/us/kies/
Once you have the required tools, we can begin the procedure.
Create your UnBrickable SD.
Unzip the SDCard Image file from the zip.
Write it to an SDCard
Linux:
Code:
sudo dd if=GCAM-bootable-odin-from-sd-60mb-DDimg.img of=/dev/MYDEVICE
where MYDEVICE is the sdcard (usually SDB or SDC
Windows: use this tool https://launchpad.net/win32-image-writer/ . I'm not going to explain because I use Linux.
Disassemble the device
I've prepared this video which shows how to disassemble the device. You can stop after you remove the LCD. Just pull the EM shields off after that so you can access the resistor.
Insert the SDCard
If you need instructions, you should have stopped long ago
Short the EMMC Resistor
You can use a pair of tweezers or a piece of wire, really anything to conduct electricity from one side of the resistor to the other. Below you can see some needles connected by a piece of wire which I use to short this resistor.
{
"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"
}
Press the power button wait a couple of seconds and release the short
While booting, the device provides a 10 second countdown on the UART2 port. during this 10 second countdown, the EMMC needs to become enabled in order to write the bootloaders back to the device. The entire process takes 30 seconds and you will see nothing on the screen.
Flash with Odin
This procedure is the same as shown in the video below, however you will put the firmware from above in the PDA section instead of CF-AutoRoot and put the PIT from above into the PIT section
Conclusion
You have sucessfully restored your device to stock condition. Please hit the thanks button below this post.
Additional Resources
[R&D] Port SDCard Recovery to Other Exynos4412 Devices: http://forum.xda-developers.com/showthread.php?t=1986887
Would you like to see the UnBrickable SD on your Exynos4 device (GS2, GNote, Gnote2)? I need a working device and a broken device to develop and test.

So similar procedure will also work on Galaxy S3 ?

drraptor said:
So similar procedure will also work on Galaxy S3 ?
Click to expand...
Click to collapse
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.

What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...

u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?

mfsr98 said:
What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...
Click to expand...
Click to collapse
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
pratik_s said:
u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?
Click to expand...
Click to collapse
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.

AdamOutler said:
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.
Click to expand...
Click to collapse
is there any chance of getting this mod for i9003 in future?

pratik_s said:
is there any chance of getting this mod for i9003 in future?
Click to expand...
Click to collapse
I'm not working on it and I have no plans to do so.

AdamOutler said:
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.
Click to expand...
Click to collapse
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app

drraptor said:
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Nope. I need a device. read the inital post.

great
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.

Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol

terminal 7 said:
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.
Click to expand...
Click to collapse
Are you talking about UnBrickable Mod? This is a bit different. This is a temporary mod and uses SDCard instead of USB.
Guzup said:
Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol
Click to expand...
Click to collapse
follow the instructions. you need to image the card with the image file in the zip.

Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,

BABAK236 said:
Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,
Click to expand...
Click to collapse
This isn't i9020/9023, which I designed the UnBrickable Resurrector for repair. This is an undocumented procedure. This isn't NVFlash from those Tegra based devices. This isn't the i9250 and i9100 which use the OMAP specific tool. This isn't JTAG either, I have a box.
The most similar method was released for i9300 but the T-Flash method has never worked properly for myself or others. This is something which did not exist before the first post in this thread.
Keep this in your repair bookmarks for when you need it along side your Riff box. Riff takes 6 wires generally. Every one of the 16 solutions I've come up with has been 1 or less.

How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium

Guzup said:
How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Most of your questions are already answered in the OP. (commands, revive instructions etc.)
Can the sd still be used? No. There is ARM code and a boot image copied to the beginning of your SDCard. This procedure will destroy the file system metadata although, physically, all the files are still present but not accessable anymore.
@Adam
By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot
Click to expand...
Click to collapse
Is this what shorting the resistors actualy does?
We've prepared an SDCard via the sdcard command in SBOOT below
Click to expand...
Click to collapse
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?

Hi Adam
I Want Just helping You.....
So,I think you don't need
Anyway,Thanks

theq86 said:
Is this what shorting the resistors actualy does?
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?
Click to expand...
Click to collapse
Yes. Shorting the resistor disables the EMMC. The TFlash works differently.
This is different from TFlash. Using TFlash you insert a boot loader from your computer and flash it to the device with Odin. The TFlash is supposed to create a boot loader from an sboot.bin.tar.md5. It has problems and seems not to work... Like ever..

I know the first few posts said the mod will work on the s3.. but since the US versions don't have exynos, I have to ask will this work on the US versions? Including Verizon?

[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?

New oneplus 3T unbrick tutorial. (errno:258 solved)

Hi guys!
I got a really painful hard brick, i thought the device would be completely dead (msmdownloadtool always said errno: 258 while downloading system.img)
So i decided to mix two tutorials and i finally fixed it. There you have it.
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)
Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
When all of this is done, press the power button for 40 seconds and then, plug your phone while you press volume up. On control panel/devices and printers you will see your phone as Qualcomm 9008 or something like that.
Unbricktool(OP3T): https://mega.nz/#!Q1YnTTAT!gnLf6NEkS...1-vReKx7B1VVpI
run this tool as administrator and a green text will pop.
Do not use the front usb of your pc, try with the ones in the back.
Do not try the oneplus 3 unbrick tutorials, they wont work and you can kill your device since the unbrick oneplus 3 tutorials are using oneplus 3 exclusive files.

nobody?

I have the exact same problem ?

nikolajkracht said:
I have the exact same problem
Click to expand...
Click to collapse
after 1 night the device did not boot anymore and when i try to run the msmdownloadtool it always fails at the system.img step. I think i'll send it to oneplus and see if they can fix it or replace the device, ill tell them that i tried to update to android 7 and the device did not boot anymore

You should all try https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and follow it to the letter. It saved my OPT3 for sure.

gee2012 said:
You should all try https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and follow it to the letter. It saved my OPT3 for sure.
Click to expand...
Click to collapse
we are using that tutorial and the phone is still dead haha

Sonificado said:
we are using that tutorial and the phone is still dead haha
Click to expand...
Click to collapse
Try it again, maybe you made a misstake . My phone couldnt boot anymore too after an OTA update because the system partition couldn`t be read, but this tutorial saved it.

gee2012 said:
Try it again, maybe you made a misstake . My phone couldnt boot anymore too after an OTA update because the system partition couldn`t be read, but this tutorial saved it.
Click to expand...
Click to collapse
at the moment my phone does not vibrate/logo/nothing, i can only press vol+ and plug it on the computer and the let goes yellow but when i run the tool and it fails, the led turns orange

Sonificado said:
at the moment my phone does not vibrate/logo/nothing, i can only press vol+ and plug it on the computer and the let goes yellow but when i run the tool and it fails, the led turns orange
Click to expand...
Click to collapse
Are you sure the Qualcomm drivers we`re installed correctly?

gee2012 said:
Are you sure the Qualcomm drivers we`re installed correctly?
Click to expand...
Click to collapse
just tried again and it happened again
{
"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"
}

Sonificado said:
just tried again and it happened again
Click to expand...
Click to collapse
I had to try multiple times too before all went well to be honest. Try rebooting the PC and give it a few more shots, you got nothing to loose anyway.

gee2012 said:
I had to try multiple times too before all went well to be honest. Try rebooting the PC and give it a few more shots, you got nothing to loose anyway.
Click to expand...
Click to collapse
you think oneplus support will help me?

Sonificado said:
you think oneplus support will help me?
Click to expand...
Click to collapse
Think so, they offered me remote assistence to revive the phone but i fixed it myself luckily. Give them a ring or send a mail for assistence and i`am sure they`ll help you

gee2012 said:
Think so, they offered me remote assistence to revive the phone but i fixed it myself luckily. Give them a ring or send a mail for assistence and i`am sure they`ll help you
Click to expand...
Click to collapse
ill talk with them on the spanish chat tomorrow, let's see what they say.

Sonificado said:
ill talk with them on the spanish chat tomorrow, let's see what they say.
Click to expand...
Click to collapse
Oke, good luck then, i`am sure it will all be worked out.

I had the same problem with my phone, you should try to install a different version of the MSM tool and (maybe) try flashing different zips till one works. I had that error and a few other error codes after hard bricking and i finally got it to work before i called support. There's a lot of variables, sometimes you just gotta play around with it when you're hard bricked, worth a shot.

Sonificado said:
just tried again and it happened again
Click to expand...
Click to collapse
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.

manor7777 said:
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.
Click to expand...
Click to collapse
It worked on port 11 for me. Guess it differs from user to user.

gee2012 said:
It worked on port 11 for me. Guess it differs from user to user.
Click to expand...
Click to collapse
I think it depends if things on your pc are using com ports. Glad to know it worked and that I could kind of help you

manor7777 said:
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.
Click to expand...
Click to collapse
gee2012 said:
It worked on port 11 for me. Guess it differs from user to user.
Click to expand...
Click to collapse
IT WORKED!!!!!! i just changed the port to another one and the msm download tool went right to the end

[GUIDE] Unlock bootloader of Lenovo Tab 4 10 with OEM unlock "greyed out" (TB-X304F/L and other Qcom tablets)

WARNING: DO THIS AT YOUR OWN RISK !!!!
I AM NOT RESPONSIBLE IF YOU START CRYING INTO YOUR BRICKED TABLET
This guide is only for devices with "OEM Unlocking" option greyed out !!!
Others can follow the simpler procedure mentioned in the TWRP thread...
Prerequisites:
QDLoader_HS_USB_Driver (Google it and find)
Hex Editor (eg. HxD)
PC and some brain to understand....
Procedure:
Install the drivers and hex editor.
Clone this repo to PC - https://github.com/Naveen3Singh/BLUnlocker (Thanks to the dev )
Extract the firehose file from stock rom. (eg. "prog_emmc_firehose_8917_ddr.mbn" for TB-X304)
Boot into edl mode using key combo
or using adb
Code:
adb reboot edl
Check the port number in device manager and run " dump_devinfo.bat ".
Mention port number and full path to "*.mbn" file (eg. D:\where\every\it\is\prog_emmc_firehose_8917_ddr.mbn)
A file named " devinfo.img " will be dumped to the working dir. Edit it using an HEX editor as shown below.
{
"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"
}
Save the devinfo.img after editing and run " unlock.bat "
Reboot after success message.
Voila !! You have Successful unlocked the bootloader. Reboot to system by holding the power button.
EDIT (13/01/2020): After unlocking bootloader and restarting, if it asks for password, Reboot to recovery and format data...
Flash TWRP and Enjoy rooting...
PS: The same procedure can be done using QFIL tools (QPST)
Attached:
Firehose file of TB-X304F and TB-X304L (DONT USE ON OTHER DEVICES!!!)
Credits:
Thanks to the dev who wrote the code ( https://github.com/Naveen3Singh )
@hk96 (Myself)
Hit thanks if this helped....

Reserved !!!

Thank you very much! It worked perfectly!

Firehose file for X304L if anyone needs it

Hb20032003 said:
Thank you very much! It worked perfectly!
Click to expand...
Click to collapse
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!

njascgil said:
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
Click to expand...
Click to collapse
After unlocking, when u Boot into system it asks for a password, even if u didn't set one to start with (atleast in my case).
So you need Boot into recovery and wipe data.
Short answer: yes, factory reset is necessary.
Regarding file version, I hav no idea... May be u can give it a try...

Hb20032003 said:
Firehose file for X304L if anyone needs it
Click to expand...
Click to collapse
Thanks...
Let me add this to OP, so that it is easier for others.

Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.

Chhayank_Sharma said:
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Click to expand...
Click to collapse
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.

hk96 said:
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
Click to expand...
Click to collapse
ok thanks.

hk96 said:
Regarding file version, I hav no idea... May be u can give it a try...
Click to expand...
Click to collapse
I was going to try it, but it's my daughter's tablet and she didn't let me do it... She is afraid of loosing some games' progress...

Nothing work for me

Eagle-no1 said:
Nothing work for me
Click to expand...
Click to collapse
May be you would have missed something....
This seems to work for most people.

hk96 said:
May be you would have missed something....
This seems to work for most people.
Click to expand...
Click to collapse
I got to work now, I had an old bad cable in use. Thank you.

hk96 said:
PS: The same procedure can be done using QFIL tools (QPST)
Click to expand...
Click to collapse
How? I watched a video and I can load the mbn but I don't know what to put in the xml thing box. I tried doing the method steps but it says Failed to write hello response back to device Did not receive Sahara hello packet from device

Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
could you explain how you did it pleasssee

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
Haha... Everything happens gradually...
rustyrust said:
could you explain how you did it pleasssee
Click to expand...
Click to collapse
I think, the instructions are crisp and clear as possible...
Can u tell where u got stuck ??

Work! You're GENIUS

hello,
I already root some device but here I'm stuck because I don't find the port number in device manager :-( drivers installed and "lenovo tab4 10" displayed in device manager. in properties I have : port_#0002.hub_#0005
I tried use 0002 or 0005 as port number but the .bat script failed each time. do I have correct port number ?
[EDIT] I have "failed to write hello response back to device" message and my tablet is in FFBM Mode.
[EDIT] in FFBM mode, my device is recognized in device manager (but i'm not sure to find the correct port and the script don't work) and in FastBoot Mode (first menu), my device seems to be not recognized in device manager. I guess that the script must be launched in this mode but I miss a driver. I install "adb drivers" + QDLoader-HS-USB_Driver_64bit_Setup drivers. What do I miss ?

Question My mobile phone suddenly stops working and can only enter 9008 mode

Anyone can take some time to help me extract the rawprogram.xml and patch0.xml of zenfone8. I need these two files to try to repair my mobile phone. At present, the official forum has been closed. I spent four days on Google and saw that many mobile phone users have this problem, I advise friends who want to buy zenfone8 to consider carefully. Thank you. I urgently need these two documents

davinlin said:
Anyone can take some time to help me extract the rawprogram.xml and patch0.xml of zenfone8. I need these two files to try to repair my mobile phone. At present, the official forum has been closed. I spent four days on Google and saw that many mobile phone users have this problem, I advise friends who want to buy zenfone8 to consider carefully. Thank you. I urgently need these two documents
Click to expand...
Click to collapse
Where are the files located?

Sebi673 said:
Where are the files located?
Click to expand...
Click to collapse
Hello, thank you for your attention and help, but I don't know what documents to provide. Can you be more detailed? I'm a novice, please understand

{
"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"
}

Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..

Andrologic said:
Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..
Click to expand...
Click to collapse
Thank you for your reminder. Would you like to ask if it's a“ prog_ firehose_ Ddr.elf file”? In addition, I have a manually flash each partition

Andrologic said:
Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..
Click to expand...
Click to collapse
Are these two documents? If so, that's great. When I enter 9008, it always reminds me that I need rawprogram0.xml and patch0.xml files. Can you teach me how to do it and how to do it? Thank you very much!!!

Sebi673 said:
Where are the files located?
Click to expand...
Click to collapse
Dear sebi673：HI ! are these two files? Can you help me

davinlin said:
Dear sebi673：HI ! are these two files? Can you help me
Click to expand...
Click to collapse
Hi, if you're still covered by warranty, just send it in. The other option would be to flash the phone via EDL, which might not work at all. I didn't mess with that, I just sent It and they changed the motherboard within 3 days.

davinlin said:
Thank you for your reminder. Would you like to ask if it's a“ prog_ firehose_ Ddr.elf file”? In addition, I have a manually flash each partition
Click to expand...
Click to collapse
Correct. I've written a guide on this for the ASUS ROG 5 (linked below)- Follow Method 1. I'm not sure you can get access to flashing partitions without the Rawprog & patch XML's but you can try....
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com

davinlin said:
View attachment 5449999
Click to expand...
Click to collapse
There is nothing much you can do except sending to Asus service centre (most likely motherboard change).
I encountered the same issue last month and had my motherboard changed too - this is a common problem with this phone and many people are complaining.
See thread here

Sebi673 said:
Hi, if you're still covered by warranty, just send it in. The other option would be to flash the phone via EDL, which might not work at all. I didn't mess with that, I just sent It and they changed the motherboard within 3 days.
Click to expand...
Click to collapse
Hi, my mobile phone has only been used for two months and is still under warranty, but if I send it back for repair, it will generate tariff and freight, about $100, but it doesn't matter. I see many people have this problem on the Internet. I want to try to help you solve this problem, although I'm a rookie, ， I want to learn something with your help and finally solve it

Andrologic said:
Correct. I've written a guide on this for the ASUS ROG 5 (linked below)- Follow Method 1. I'm not sure you can get access to flashing partitions without the Rawprog & patch XML's but you can try....
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your reply. I will try the method you provided. If it is successful, I will come back and share the method and results with you. Thank you again

napster79 said:
There is nothing much you can do except sending to Asus service centre (most likely motherboard change).
I encountered the same issue last month and had my motherboard changed too - this is a common problem with this phone and many people are complaining.
See thread here
Click to expand...
Click to collapse
Hi，Thank you for your advice and attention. This is the first time I use ASUS mobile phone, and probably the last time. If it takes me time to solve it, it can be regarded as my counterattack to ASUS. Why can't I admit that this is their problem? I can't understand. For such a large company, I read the history of ASUS mobile phone, which seems to be a common problem