Database Develop

Fastboot Unlocked?

So I decided just to see what my fastboot looked like - attached.
{
"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"
}
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.

mxgoldman said:
So I decided just to see what my fastboot looked like - attached.
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.
Click to expand...
Click to collapse
I think it says "bootloader LOCKED" in the fastboot screen. That means, you can ONLY flash motorola compiled operating systems (specifically kernels).;
If you want to try, run a fastboot unlock-bootloader command when running in fastboot. A locked bootloader will tell you something along the lines of "command not valid"

Do not flash anything on your phone. That looks to be a unlocked bootloader!
Sent from my DROID4 using Tapatalk 2

jsnweitzel said:
Do not flash anything on your phone. That looks to be a unlocked bootloader!
Click to expand...
Click to collapse
Wait, wouldn't that be a positive that would make flashing them easier?

I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Sent from my DROID4 using Tapatalk 2

mxgoldman said:
Wait, wouldn't that be a positive that would make flashing them easier?
Click to expand...
Click to collapse
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!

podspi said:
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!
Click to expand...
Click to collapse
Makes more sense.
That's my little secret.
I could probably pull whatever from it, but I'd need some help for what you'd like pulled. Haven't rooted it or anything yet.

didnt this happen with a GSM RAZR before? dont get me wrong, i'd love to unlock my bootloader! someone bring this to their attention

FYI, on Milestone XT720, Motorola left a partially working fastboot--we can "fastboot boot boot.img" to boot self-built kernels and this bypasses the signature checks. But you have to boot via USB each time, if you use "fastboot flash boot.img" fastboot will write the kernel and reboot, but the signature check will fail after reboot.
http://forum.xda-developers.com/showthread.php?t=821210
Here's one way to muck with a kernel to change uname strings:
http://forum.xda-developers.com/showthread.php?p=11975260#post11975260

jsnweitzel said:
I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Click to expand...
Click to collapse
FWIW, the "SE" is the giveaway. If it said "S", you would be in business.

Rzrbck, how so, if it could be retrieved from the phone? Maybe I'm not understanding, but if we had that bootloader is it not like the normal S model with full permissions to the phone?

what makes it an engineering model? are the physical components the same, or is it a software setting that if we changed could unlock the phone?

would it be possible via hardware to dump an SE bootloader, and flash it to a S devic? I would be willing to give this a go if its possible.

if we could get the bootloader images off that phone an unlock for the Droid 4 might be possible. Assuming, of course that both the S and the SE model use the same keys.

Tell me what I can do to help.

I wish I knew what to do, but in the mean time, here's some literature on how the lock works (it's for the milestone, but the d4 might use the same infrastructure).
The bootchain:
http://www.droid-developers.org/wiki/Booting_chain
The mbmloader: this loads the bootloader, if this is replaced with a version that doesn't check signatures, the bootloader can be permanently replaced:
http://www.droid-developers.org/wiki/Mbmloader
The mbm (bootloader) does it's own signature check of the kernel before booting it.
If either the key burned into the phone's fuse, or the key the mbmloader uses to check the mbm are the same on both devices, one or both of those partitions can be flashed with with the unlocked version. If they're both different, this is a dead end.
The only other option after this (aside from espionage)would be to crack the signature system directly by either creating an unlocked version of the bootloader and patching it in a way that it generates the same hash, or discover a new way to factorize large (2048 bit) numbers, and reverse engineer motorola's private signing key. (If you were to discover this factoring method, nearly every security company would have to retool.)
edit: careful updating your phone, an OTA can relock your phone. The more I read, it seems less likely that the bootloader is encrypted. Dumps should be made, but this is going to require someone with greater knowledge than I.

how would we go about doing this?

dewhashish said:
how would we go about doing this?
Click to expand...
Click to collapse
It seems like you load a special kernel module to unhide the bootloader partitions then simply use the dd command to make an image copy onto the sdcard.
iow, we need a dev.

well the only ones i know might be kholk, hashcode, and p3droid

This got quiet. No news on this yet?

[SOLVED]Can't unlock bootloader-fake Hong Kong HTC One version

After a lot of troubles I finally determined that my HTC One is actually a fake Hong Kong custom version with different hardware but amazingly similar look. If your HTC One:
- doesn't have Sense preinstalled,
- lack proper identification,
- came with BeatsAudio headphones,
- is made of plastic,
- has Chinese factory mode,
- different barebone bootloader
- and anything else which doesn't look right in regard to HTC One
There's even post on Engadget.
It's probably fake...
After I found that I have different bootloader then usual one I tried to unlock it but when I come to 'fastboot oem get_identifier_token' step cmd just outputs tree dots so I left it for a while but nothing happens after that. It's same for every other oem command. Device is recognized by fastboot and every command that I try works like it should, 'fastboot reboot' reboots device, 'fastboot reboot-bootloader' boots to bootloader, 'fastboot -w' clears userdata and cache so it doesn't seem that adb and drivers aren't set properly.
{
"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"
}
This is how my fastboot menu looks like(picture below);nothing like one on picture above:
Is there anything I can do to unlock my HTC One?

BUMP

Where did you get this one?

I got it second hand but I checked via IMEI and H/P on HTC site and they say it's valid device from England.
Sent from my iPad using Tapatalk HD

BUMP

Jon2555 said:
After I found that I have different bootloader then usual one I tried to unlock it but when I come to 'fastboot oem get_identifier_token' step cmd just outputs tree dots so I left it for a while but nothing happens after that. It's same for every other oem command. Device is recognized by fastboot and every command that I try works like it should, 'fastboot reboot' reboots device, 'fastboot reboot-bootloader' boots to bootloader, 'fastboot -w' clears userdata and cache so it doesn't seem that adb and drivers aren't set properly.
This is how my fastboot menu looks like(picture below);nothing like one on picture above-background is black and words are in white(I'll upload picture as soon as I make one):
Code:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
[UART Boot]
Is there anything I can do to unlock my HTC One?
Click to expand...
Click to collapse
Have you tried the Revone S-Off method, I know it's still in early stages, but it worked great for me.
No need for the OEM token method if you use it.
I know it took a few tries but just keep at it and you shoul get there

Thanks for answer, I already tried that but I keep getting same error all over time which other users don't get(as far as I saw)

Jon2555 said:
Thanks for answer, I already tried that but I keep getting same error all over time which other users don't get(as far as I saw)
Click to expand...
Click to collapse
I kept on getting errors even following the instructions to the T. it took me about 2 and a half hours of trying-rebooting and trying again.
But which errros are you recieving?

I always get error code 1

try this unlock toolkit by hasoon2000 .. worked for me ..
http://forum.xda-developers.com/showthread.php?t=2183942

Thanks, tried that too but didn't help.

The only other thing I could suggest is to go back to stock with an RUU and try it all again bro
Sent from my HTC One using xda app-developers app

Yea...I gave a try to that too but I can't figure out CID and other needed ID, getvar in fastboot display nothing related to CID and as I said in main post I can't execute oem commands for flashing. Anything else...

From you've said it's either a custom HBOOT or it's a fake...
Sent from my Nexus 4 using xda premium

If I flash other HBOOT and something go wrong, can I fix things? You can't access fastboot without it and stock recovery is pretty useless.

Jon2555 said:
If I flash other HBOOT and something go wrong, can I fix things? You can't access fastboot without it and stock recovery is pretty useless.
Click to expand...
Click to collapse
Take a photo of the current HBOOT and post it up - we'll go from there

EddyOS said:
Take a photo of the current HBOOT and post it up - we'll go from there
Click to expand...
Click to collapse
Here's the photo of bootloader(it's really bad quality, can't make good one with my One X's camera, letters are too small, I hope it'll help):
I described boot menu in first post.

Jon2555 said:
Here's the photo of bootloader(it's really bad quality, can't make good one with my One X's camera, letters are too small, I hope it'll help):
I described boot menu in first post.
Click to expand...
Click to collapse
Photo doesn't work...

Is this one OK:

Jon2555 said:
Is this one OK:
Click to expand...
Click to collapse
Nope, dead link. just attach it to your post on here

[Q] Stuck On White HTC Boot Screen PLEASE HELP!!!

When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.

plotgee said:
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
Click to expand...
Click to collapse
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
{
"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"
}
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).

projectisaac said:
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
Click to expand...
Click to collapse
I have the vivid , and yes it says *** locked ***
I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..
Thanks, I hope this works.

Fingers crossed here. Let me know what happens.
Sent from my Vivid 4G using xda app-developers app

Alright! So apparently this solution worked (got a PM from OP)!

Tmobile 5.1 update questions

I've read most if not all the threads about the 5.1 update but I'm still a little confused. what is the best, least trouble causing method to update to 5.1? Should I start from scratch and flash the official and then unlock bootloader and root? Can I just flash the bootloader and radio and one of the stock 5.1 roms currently available?
From what I understand, and please correct me if I'm wrong, the current 5.1 aosp roms don't work entirely well and need a fix, and none of the aosp work with the new radio on Tmo?

I believe you can flash bootloader and radio. Then flash one of the stock 5.1 roms. That's what I did, and I'm doing just fine.

So as long as I use a stock rom like what scrosler posted I'm fine? How about going back to a 5.0.2 rom?

Im on Tmobile, i was on Chroma 5.0.2 thursday and flashed the bootloader/radio for 5.1. since then i have not been able to receive calls. Today i flashed Stephan's stock 5.1 v1.2.1 which had some fixes for the speaker and such, but the calls still cannot be received. I also reflashed the bootloader/radio to no avail. I have checked my apn's too. has anyone found a fix yet? I would rather not fastboot back to the previous radio and 5.0.2 Roms (little nervous about the bricked device people were having).

TBarb169 said:
Im on Tmobile, i was on Chroma 5.0.2 thursday and flashed the bootloader/radio for 5.1. since then i have not been able to receive calls. Today i flashed Stephan's stock 5.1 v1.2.1 which had some fixes for the speaker and such, but the calls still cannot be received. I also reflashed the bootloader/radio to no avail. I have checked my apn's too. has anyone found a fix yet? I would rather not fastboot back to the previous radio and 5.0.2 Roms (little nervous about the bricked device people were having).
Click to expand...
Click to collapse
it happening to most of us with tmobile http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380/page22
anyways, what i did to fix it was to reflash the older radio.

simms22 said:
it happening to most of us with tmobile http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380/page22
anyways, what i did to fix it was to reflash the older radio.
Click to expand...
Click to collapse
hi Simms22, question:
I have got adb & fastboot set up on my computer. I have downloaded the radio.img for 5.0.1 and placed it in the folder where adb is loaded. i have booted my phone into fastboot flash mode, but when i enter the command "fastboot flash radio radio.img" (i renamed the file radio.img) i keep getting an error: cannot load 'radio.img'. any clues as to what i may be doing wrong?

TBarb169 said:
hi Simms22, question:
I have got adb & fastboot set up on my computer. I have downloaded the radio.img for 5.0.1 and placed it in the folder where adb is loaded. i have booted my phone into fastboot flash mode, but when i enter the command "fastboot flash radio radio.img" (i renamed the file radio.img) i keep getting an error: cannot load 'radio.img'. any clues as to what i may be doing wrong?
Click to expand...
Click to collapse
did you run a fastboot devices first, to make sure fastboot sees your device?

simms22 said:
did you run a fastboot devices first, to make sure fastboot sees your device?
Click to expand...
Click to collapse
yes, it recognizes it for adb & fastboot

So basically if you have tmo you shouldn't touch the new radio?

kingston73 said:
So basically if you have tmo you shouldn't touch the new radio?
Click to expand...
Click to collapse
i wouldn't until they get it squared away.

kingston73 said:
So basically if you have tmo you shouldn't touch the new radio?
Click to expand...
Click to collapse
right. i tried the radio from the verizon firmware and the same issue.
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
TBarb169 said:
yes, it recognizes it for adb & fastboot
Click to expand...
Click to collapse
if you are in your bootloader, and flashing while youre in the bootloader then it should work. check your spelling!

simms22 said:
if you are in your bootloader, and flashing while youre in the bootloader then it should work. check your spelling!
Click to expand...
Click to collapse
so, when i hold power + volume down, i get the android guy on its back. do i select a specific screen?
spelling is not the issue, as i have tried it multiple times

TBarb169 said:
so, when i hold power + volume down, i get the android guy on its back. do i select a specific screen?
spelling is not the issue, as i have tried it multiple times
Click to expand...
Click to collapse
thats where you want to be to run fastboot, dont select where to go. sray there

My reception has been wonderful with T-Mobile on 5.1. I've been in two different states and all over WA and have had zero issues aside from when they had network hiccups nationwide on Friday and that only affected my receiving texts for a few hours.

HTC just slated T-Mobile HTC m9 5.1 release for 7/20
{
"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"
}

Le S3 x626 bricked issue

Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"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"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL

You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom

damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .

it was necessary to use a mirror. for example, in the bathroom

after brick and ressurect what write in (telephone settings) model?

Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop

Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?

take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.

Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.