Database Develop

[GUIDE] Unbricking SamsungGalaxyMini

credits to those who found this out in other units
---------------------------------------------------------------------------------------------------
i have found a solution for this problem
by reading other units solutions (even if it's posted everywhere, i just want to share this)
this thing will solve the:
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
and others
unbricking steps:
- remove sim card, and sdcard
- remove battery for even less than 30-20 seconds
- hold volume down, home key and power button simultaneously and put the battery, it will go directly to Download Menu
- open ODIN and DO NOT USE ONE PACKAGE, set the files, i used XXKPI with the 4 files, CSC, APBOOT, MODEM and CODE. dont use the ONE PACKAGE in this kind of flashing. i tested it but nothing happen so i used the other option.
- flash it, wait and done! back to normal.
i thought i should bring this up to the samsung center for the warranty
though i tried other options and experimenting
whew
thanks be to GOD.

Maybe post all the 4 files for all of us?
Luckily, I don't have my device bricked... yet.

yes, u should post a few of screens

sir sevenfolds. what is the difference between the onepackage and yun split package in 4 parts

ahmish said:
sir sevenfolds. what is the difference between the onepackage and yun split package in 4 parts
Click to expand...
Click to collapse
One packages contains all the needed files at a single tar or md5 file while using separate packages you use different tar for PHONE, PDA, CSC, BOOT in Odin... There is not much difference these file are also included in the one package zip file.

Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...

same thing happened to mate, luckily the Samsung guys replaced under warranty, checkout my posts they might be of some use.

chemicalrage said:
Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...
Click to expand...
Click to collapse
until now, nothing we can do for hard-brick without special tools

chemicalrage said:
Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...
Click to expand...
Click to collapse
Good for you!!hahaha
Sent from my GT-S5570 using xda premium

Phones IMEI changed without even touching it

I have this problem - my G800F changed it's IMEI to 350695200123951. When that happened I had not touched it (no root, no nothing) at evening I still was able to make calls, but later that night it showed 'not registered on network'. I have tried factory reset, reinstalling the firmware using Kies, then I used odin, tried to make EFS backup and restore, but so far I haven't had any success. So I thought that some of you brilliant minds could help me, maybe there is a way to change the IMEI in efs backup file? The only strange thing that happened to my phone couple of days before this happened is that some random number from Ukraine called me, but for obvious reasons I did not answer it nor did I call it back. So now I'm stuck using my fathers old HTC Wildfire S, I really hope that you could help me, because I want my phone back.

SOS
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)

Warranty service restored the original IMEI
KVE123 said:
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)
Click to expand...
Click to collapse
Just couple of days ago got my phone back from warranty and they fixed it (thought they wouldn't since it was rooted), so I would suggest doing the same thing. At the warranty center I had to explain my problem for about 30 minutes, because they believed that phone couldn't change its IMEI. Also you could try other service centers, because some of them said that they could fix this problem for about 30-50 EUR. I believe the only thing that could help otherwise is something like the z3x box, but it would be more expensive as it costs 100+ USD.

If you download the original stock firmware you can flash the IMEI number back to the phone

:S
No solution has been under warranty , the pochaine time to think about backup your EMEI

Yes yes
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.

KVE123 said:
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.
Click to expand...
Click to collapse
A back up of your phone? I would suggest just making a new back up because it's less time consuming.

BUP
irontaco1 said:
A back up of your phone? I would suggest just making a new back up because it's less time consuming.
Click to expand...
Click to collapse
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards

KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
Nope it shouldn't. The IMEI number is installed with the firmware. So if you back it up and factory reset, it should fix it.
---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------
KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
If factory reseting doesn't work, then I suggest flashing the firmware manually.

BUP
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.

What's the model number?

Reflash
KVE123 said:
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.
Click to expand...
Click to collapse
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
Click to expand...
Click to collapse
Correction = SM-G800F

KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
Correction = SM-G800F
Click to expand...
Click to collapse
So you get an error when backing it up?

kies
irontaco1 said:
So you get an error when backing it up?
Click to expand...
Click to collapse
No, I mean downloading the firmware upgrade. It will download the new files but not install. This was long ago. Right now I get to tools to upgrade and initialise and get the message "does not support initializing" I give up!

No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.

irontaco1 said:
No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.
Click to expand...
Click to collapse
What you propose was the second thing I did. The first was doing a factory reset with the older version of the firmware (what the phone came out with). Neither steps worked. The firmware I flashed was (Build number) KOT49H.G800FXXU1AOG2. Which btw Kies indicates as the latest version.

Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.

email
[/COLOR]The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.[/QUOTE]
Kies does not work anyway
Can do (email) but not on this open forum. Use the private messages
Added edit in wrong place but, given the phone to samsung tech. Will post the outcome somewhere next week

irontaco1 said:
Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.
Click to expand...
Click to collapse
Can you help me please, i have the same probleme one week ago, without solutions, i pm you, please help me!

same problem here

Relock Bootloader H811?

I had rooted my H811 but ive had problems with my phone contacted T-Mobile and they are going to replace my phone but i had flashed the 81110n kdz i got no unlocked bootloader warning but once it updated to 20i the warning came back is there any way to relock the bootloader or pull the warning help plz

Doubt it will even matter
Sent from my LG-H811 using Tapatalk

Please help....

To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.

DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
Worked ty vm @DrakenFX

Im sorry, but I too have the dreaded keyboard problem with the LG G4 and need to send it back for repair. Mine came with unlocked bootloader, and it shows on the LG screen where it gets stuck. I have managed to get it to reboot temporarily by putting it in the fridge for like 15 mins. But how do I get to the screen above so I can remove twrp and relock the bootloader?

i tried it for my h815 and it didnt worked
FAILED (remote: unknown command)
finished. total time: 0.004s

DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
would you do a video of it.? show us?
---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------
Rich7597 said:
Worked ty vm @DrakenFX
Click to expand...
Click to collapse
or would you??
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
maikalwolf said:
Im sorry, but I too have the dreaded keyboard problem with the LG G4 and need to send it back for repair. Mine came with unlocked bootloader, and it shows on the LG screen where it gets stuck. I have managed to get it to reboot temporarily by putting it in the fridge for like 15 mins. But how do I get to the screen above so I can remove twrp and relock the bootloader?
Click to expand...
Click to collapse
so what happen to yours ??? what you did? did you fixed? relock it.? if you did relock it would you make a video of it..?

raptorddd said:
would you do a video of it.? show us?
---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------
or would you??
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
so what happen to yours ??? what you did? did you fixed? relock it.? if you did relock it would you make a video of it..?
Click to expand...
Click to collapse
So I kept trying to do the freezer trick over and over again until I noticed that it actually had to be in the freezer the 20 mins just to start!! If it did not it would not boot at all. It was not a battery problem, it just stopped unless it was cold. I took a chance on sending it in since it was warrantied still, and crossed my fingers that they would not do the freezer trick at the factory. They did not and a few days later I checked and it was in their repair qwe. Keeping my fingers crossed until I saw that the resolution was "Replace motherboard" Reason "bent motherboard". I know the bent mobo was BS. But hey what ever it took right? A few days later it was in the mail and my son has been using it perfectly well since then with that same battery and another he purchased! They did take the protective glass screen saver off for some reason. So Bonus a practically new phone and I still got some warranty left until Oct of this year!

maikalwolf said:
So I kept trying to do the freezer trick over and over again until I noticed that it actually had to be in the freezer the 20 mins just to start!! If it did not it would not boot at all. It was not a battery problem, it just stopped unless it was cold. I took a chance on sending it in since it was warrantied still, and crossed my fingers that they would not do the freezer trick at the factory. They did not and a few days later I checked and it was in their repair qwe. Keeping my fingers crossed until I saw that the resolution was "Replace motherboard" Reason "bent motherboard". I know the bent mobo was BS. But hey what ever it took right? A few days later it was in the mail and my son has been using it perfectly well since then with that same battery and another he purchased! They did take the protective glass screen saver off for some reason. So Bonus a practically new phone and I still got some warranty left until Oct of this year!
Click to expand...
Click to collapse
did you send it to LG ot TMO.?
great at least you have a working phone, thats what you paid for anyways..
did you unlocked bootloader? i wouldd like to unlock it. but same reason warranty... so i was thinking since i saw this post that it can be relocked but theres no video of it... like unlock it, then if i get bootloop. flash the modded KDZ relock it, then flash stock and send it for repairs... could it be done?

raptorddd said:
did you send it to LG ot TMO.?
great at least you have a working phone, thats what you paid for anyways..
did you unlocked bootloader? i wouldd like to unlock it. but same reason warranty... so i was thinking since i saw this post that it can be relocked but theres no video of it... like unlock it, then if i get bootloop. flash the modded KDZ relock it, then flash stock and send it for repairs... could it be done?
Click to expand...
Click to collapse
I bought it unlocked, it turned out to be one of the models with the bad motherboard. The previous owner directed me to here so I could re-lock the boot loader. I got to the window several times but it would not stay long enough for me to try re-locking it. That's why it was nice that the phone's mobo was bad enough that it just stopped booting up! I took a chance. If it had booted and they would have seen the un-locked BL they could have told me tough luck. But I have read in many forums that LG is pretty good about this issue with the bad models. So it's a roll of the dice and lucky for me either the phone did not boot up for the Tech who handled my phone, or he saw what was going on and went ahead and switched out the mobo despite seeing the first screen screaming "unlocked bootloader!"

maikalwolf said:
I bought it unlocked, it turned out to be one of the models with the bad motherboard. The previous owner directed me to here so I could re-lock the boot loader. I got to the window several times but it would not stay long enough for me to try re-locking it. That's why it was nice that the phone's mobo was bad enough that it just stopped booting up! I took a chance. If it had booted and they would have seen the un-locked BL they could have told me tough luck. But I have read in many forums that LG is pretty good about this issue with the bad models. So it's a roll of the dice and lucky for me either the phone did not boot up for the Tech who handled my phone, or he saw what was going on and went ahead and switched out the mobo despite seeing the first screen screaming "unlocked bootloader!"
Click to expand...
Click to collapse
you were lucky only a few of them have been repair after unlocked bootloader..:good:
i have heard some complaint from other users that theirs were denied. not unlocked, but he assumes they LG tought it was unlocked because he says that when you request unlock.bin you must place your imei or serial number so they have it on record....
so you planing on unlocking this ?? HAHA if you do. i would like to see someone post a video or relocking and that it works..

No I will not be unlocking it. My son has the phone and wants to keep it locked in case. Like I said he is still under warranty.

maikalwolf said:
No I will not be unlocking it. My son has the phone and wants to keep it locked in case. Like I said he is still under warranty.
Click to expand...
Click to collapse
yeah makes sense, better have it under warranty.

DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
This process will remove my all data like Images, Video, contacts etc.... or will wipe out my complete phone including OS files??

[TOOL] 6T MsmDownloadTool v4.0.59 (OOS v9.0.13)

This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.
OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
Run MsmDownloadTool V4.0 and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
Driver
Alternative driver
Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.

Wow nice. Now to test this on T-Mobile!! Let the flashing commence

Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.

im tempted to run this today on the tmobile model. how high is the risk of hard brick? will it leave me without fastboot if it doesnt work?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
apparently the flash to 9.0.5 in the other thread overwrites the modem anyway. its the criticals that dont overwrite. worst case im within my 14 days still, can alwasy return

dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445

SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.

SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
strictlyphat said:
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
Click to expand...
Click to collapse
One of three things will happen.
One, it will recognize it as the wrong device and won't flash at all.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.

hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
Click to expand...
Click to collapse
Screw it. I'm gonna do this soon. Will report back

hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Wanna find out? I'll probably test in a few, lol.

hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Cuz I'm assuming it's the same as Samsung. One hardware multiple softwares.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Dark Nightmare said:
Wanna find out? I'll probably test in a few, lol.
Click to expand...
Click to collapse
Dude I will owe you one. Ur much braver than I. If my son falls asleep I'm trying to. PLEASE LET ME KNOW. And please let me buy u a beer lmfao

strictlyphat said:
Screw it. I'm gonna do this soon. Will report back
Click to expand...
Click to collapse
Guess I'll wait on your results...

Dark Nightmare said:
Guess I'll wait on your results...
Click to expand...
Click to collapse
I'm.having doubts man. Lol. What's your input. How likely I hard brick?

strictlyphat said:
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
Click to expand...
Click to collapse
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.

Dark Nightmare said:
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Click to expand...
Click to collapse
Ah u r king. I had a backup iPhone til my daughter destroyed hers.

strictlyphat said:
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
Click to expand...
Click to collapse
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.

Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.[/QUOTE
oof that sucks. thanks again
Click to expand...
Click to collapse

Safe flashing to anyone taking the plunge!

Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
tried it for good measure, same error

iaTa said:
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.58 and OOS v9.0.5 and is compatible with the non T-mobile international models (T-mobile compatibility currently unknown).
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download the driver below and install.
Run MsmDownloadTool V4.0_factory.exe and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
MsmDownloadTool: https://androidfilehost.com/?fid=11410963190603846961
Driver: https://androidfilehost.com/?fid=24052804347798730
Shameless plug - my OP referral link for any peops that would like $20/£20/€20 discount: https://www.oneplus.com/invite#EC5BZVULJDUUO22
Click to expand...
Click to collapse
Oh my God you just saved my life brother. Thank you so much.

Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
Sad days... Appreciate the risks you've taken tho!!

Is There Any Way To Remove "Orange State Your Dev.." Message?

Hi guys I unlocked my bootloader etc and like everyone else who owns a E4 Plus I get the message "Orange state your device has been unlocked bla blah"
I was wondering is there anyway to remove/hide it? I already searched the forum and most answers were a "no".
But I just wanted to double clarify hence I started this thread.. I know the message only shows up on bootup but like everyone else I would prefer it not to be there..
any replies would be appreciated thanks.
My model is XT1771 Nicklaus
Cheers.

I flashed a bootlogo that covered it. There are several around, pick what you like.

koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks

koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
Cobrahaze said:
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks
Click to expand...
Click to collapse
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed

hetor99 said:
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed
Click to expand...
Click to collapse
Thanks for clearing that up for me.

My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.

koop1955 said:
My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.
Click to expand...
Click to collapse
I just got this phone for christmas, There are way too many versions of this phone, so confusion is going be a learning curve, what works on one version doesn't work on another.
So far that's the only downside I have found so far with this phone. Mine is the retail version, xt1775.