Database Develop

[Q] Need to unlock bootloader, but borked device

Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?

Few threads about this today. Seems a regular user error. Can't think of a fix right now..

rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.

boot to bootloader, fastboot oem unlock from fastboot command console on computer.

TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.

Have the same problem and try to solve it with Motorola. No luck at the moment.

lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot

simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22

rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.

TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.

rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...

Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.

I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).

You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.

beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???

simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).

I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?

efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...

You're all using the newest fastboot?

flash the factory img
edit.. nevermind, i see ive already said that

Moto g xt1064 cant do anything!! Help me please

OK so please please help me out here. I have a moto g xt1064 and I first installed twrp to flash titan prime ROM 1.0.2 beta and everything was good for about a month or two and then the phone apps started stopping and crashing especially the Google apps (unfortunately, play store has stopped)
So I restored it back to stock 4.4.4 and it was fine for along time and then the apps started crashing again. I literally can't even factory reset or even enable USB debugging. It won't let me install twrp, every time I try to install twrp with adb and fast boot it says its finished but when I go to recovery its still the stock recovery. I tried to install every single ROM and it still won't let me! I don't think its bricked because it powers on and everything. please for the love of phones help me out. Plz answer me

Is your bootloader unlocked.? You cannot flash recovery if you have locked bootloader.

I do have an unlocked bootloader.

Akwardbanana said:
I do have an unlocked bootloader.
Click to expand...
Click to collapse
Try to flash this firmware http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
Run these commands as admin. If you are downgrading it is normal first two give you a preflash verification error.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata

Ive done everything correctly but when it rebootednothing changed. I have the same apps and keeps crashing. I've also tried changing run time to Art but that didn't help

Akwardbanana said:
Ive done everything correctly but when it rebootednothing changed. I have the same apps and keeps crashing. I've also tried changing run time to Art but that didn't help
Click to expand...
Click to collapse
You can't reflash the firmware and still have the same apps, you have done something wrong

KuranKaname said:
You can't reflash the firmware and still have the same apps, you have done something wrong
Click to expand...
Click to collapse
Like I said its pretty much impossible to change something. I can't even remove the password from the phone because the next time it reboots the password reappears

Akwardbanana said:
Like I said its pretty much impossible to change something. I can't even remove the password from the phone because the next time it reboots the password reappears
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

KuranKaname said:
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
I did that a while ago a couple of times but nothing changed. I really don't know what to do :crying:

Akwardbanana said:
I did that a while ago a couple of times but nothing changed. I really don't know what to do :crying:
Click to expand...
Click to collapse
Then I think that your memory chip is gone.

Is there any way to buy a emmc chip and solder it direvtly to the motherboard?

gbb14 said:
Is there any way to buy a emmc chip and solder it direvtly to the motherboard?
Click to expand...
Click to collapse
Well, maybe from another XT1068, you can buy dead ones from amazon and other sites and if you really know what you are doing you can unsolder the broken chip and solder the new one

gbb14 said:
Is there any way to buy a emmc chip and solder it direvtly to the motherboard?
Click to expand...
Click to collapse
If you have a lot of experience soldering electronics and have the proper equipment, maybe. If not, you can forget it, not a chance.

I've seen a lot of threads about dead emmc... I think it's a hardware defect

fburgos said:
I've seen a lot of threads about dead emmc... I think it's a hardware defect
Click to expand...
Click to collapse
So its impossible to fix?

Just handed my phone to a friend of mine , which works at a GSM SERVICE,and today he will try to flash a new firmware using a service box, by COM port. Probably the flashing will take place at a low level.
I'll come back to you to tell if it worked or not.
Normally if the emmc is physically corrupted , nothing can be dine, except soldering a new emmc chip or changing the phone's motherboard which costs a lot...
Thanks

gbb14 said:
Just handed my phone to a friend of mine , which works at a GSM SERVICE,and today he will try to flash a new firmware using a service box, by COM port. Probably the flashing will take place at a low level.
I'll come back to you to tell if it worked or not.
Normally if the emmc is physically corrupted , nothing can be dine, except soldering a new emmc chip or changing the phone's motherboard which costs a lot...
Thanks
Click to expand...
Click to collapse
Please let me know asap. Thanks

Akwardbanana said:
Please let me know asap. Thanks
Click to expand...
Click to collapse
we are on the same brickboat, let's hope somehow it works

so, came back from the gsm service, I'll have to wait 1 more day.
because the phone was sent to another guy .
my friend thinks that my phone is 90% done but until i will get it back i am not celebrating
of course i want to get all the details in what he has done,
brickboats won't sink !!!

so, Yesterday I got the news that i have a problem with my internal memory (surprise surprise!).
So the guys said that they will try to fix the problem, hopefully monday I will have the device back, either in the same state, broken, or fully functional. anyways, I will keep you updated

(SOLVED BY REPLACE MOTHER BORD) firmware version

hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????

try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list

gordonyoung53 said:
try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list
Click to expand...
Click to collapse
Thanks for your reply,i will try with version ale-l21v100r001c432b136a,to see if can i unbrick my phone

cristi.blidariu said:
hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????
Click to expand...
Click to collapse
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.

pilililo2 said:
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.
Click to expand...
Click to collapse
i have bootloader unlock,i have try many firmware to flash via adb,but when i type fastboot reboot only led blink red for 2 sec and then green for 10 sec,after that the phone shutdown,if i try to turn on same thing,led blink red the green,i dont have any clue what is the problem

To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.

pilililo2 said:
To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.
Click to expand...
Click to collapse
here what i use
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot(i have try all version based on single sim and dual sim,the same error,when is try to boot the led indicator blink red then green and is shutdown,if i try to turn on same error led indicator blink red then green,the only option that i have is just to putt the phone in fastboot/rescue mod,so i don't know what is the problem )

Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.

pilililo2 said:
Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.
Click to expand...
Click to collapse
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????

I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry

pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
k,thanks for your reply

pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
cristi.blidariu said:
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????
Click to expand...
Click to collapse
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img

Lordbannakaffalatta said:
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img
Click to expand...
Click to collapse
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance

cristi.blidariu said:
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance
Click to expand...
Click to collapse
it goes the same way.
as i told you try installing twrp first wipe everything and then flash it but do it in the order i gave you.
first boot.img
second recovery.img
third cust.img
fourth system.img
this problem occured before. (cant find the thread anymore) but it should work.
and the way is see it you have nothing to lose at this point so

I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/

pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app

pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
cristi.blidariu said:
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones

Lordbannakaffalatta said:
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones
Click to expand...
Click to collapse
i run command fastboot oem get-bootinfo and show bootloader unlock

Samsung Galaxy Tab S2 T819 - MDM MODE

Hello everyone,
Recently a friend bought a tablet (SM-T819) which was in some sort of retail mode or I don't know what.
It had "Maas360" security app and it was quite locked up.
So, I didn't know what else to do since I couldn't get into settings any way, so I tried flashing TWRP without enabling OEM unlocking and USB debugging, and then I got a download mode screen saying "MDM MODE, CAN'T DOWNLOAD" and a boot loop at Samsung Logo.
I tried flashing all possible combination of stuff, custom recovery, stock AP, Smart Switch initialized recovery, but whatever I do, I can't flash it, because every time flashing starts the message mentioned above appears and flashing fails.
I tried "adb sideload" and "factory data reset", but I get blocked at MDM screen.
After all, I tried "NAND erase all", hoping it will wipe the whole device, but still just bricked.
I thought that this may be solved by flashing a PIT, security, bootloader or something, but I cannot manage to find any online.
Any ideas?
Similar problems?

Jovan Riparazioni said:
Hello everyone,
Recently a friend bought a tablet (SM-T819) which was in some sort of retail mode or I don't know what.
It had "Maas360" security app and it was quite locked up.
So, I didn't know what else to do since I couldn't get into settings any way, so I tried flashing TWRP without enabling OEM unlocking and USB debugging, and then I got a download mode screen saying "MDM MODE, CAN'T DOWNLOAD" and a boot loop at Samsung Logo.
I tried flashing all possible combination of stuff, custom recovery, stock AP, Smart Switch initialized recovery, but whatever I do, I can't flash it, because every time flashing starts the message mentioned above appears and flashing fails.
I tried "adb sideload" and "factory data reset", but I get blocked at MDM screen.
After all, I tried "NAND erase all", hoping it will wipe the whole device, but still just bricked.
I thought that this may be solved by flashing a PIT, security, bootloader or something, but I cannot manage to find any online.
Any ideas?
Similar problems?
Click to expand...
Click to collapse
I'm confused, if you can't download anything using download mode, how can you have possibly caused a boot loop?
Or do you mean you can use download mode, but it just doesnt boot?
Does ODIN complete the flash or not?

ashyx said:
I'm confused, if you can't download anything using download mode, how can you have possibly caused a boot loop?
Or do you mean you can use download mode, but it just doesnt boot?
Does ODIN complete the flash or not?
Click to expand...
Click to collapse
Odin doesn't complete the flash. I think erasing NAND caused the bootloop, but I am not sure.

Jovan Riparazioni said:
Odin doesn't complete the flash. I think erasing NAND caused the bootloop, but I am not sure.
Click to expand...
Click to collapse
If you used NAND erase all then it has wiped the internal storage, possibly wiping the system partition too.

ashyx said:
If you used NAND erase all then it has wiped the internal storage, possibly wiping the system partition too.
Click to expand...
Click to collapse
Whatever it was, do you have an idea where could this restriction be written? Don't just tell me jtag is the last resort

Jovan Riparazioni said:
Whatever it was, do you have an idea where could this restriction be written? Don't just tell me jtag is the last resort
Click to expand...
Click to collapse
Have you tried reflashing the stock Firmware?

ashyx said:
Have you tried reflashing the stock Firmware?
Click to expand...
Click to collapse
Of course, I used files which I got from Smart Switch by entering IMEI and SN, extracted from AppData.
I am advanced user, even working as a technician, but this one surely gave me trouble.
I even tried Octoplus Samsung, but the closest supported model is some variation of T819 (not sure which letter was at the end).
I tried some stuff, but not helping really. Friend who owns this box told me I should go "Factory Unlock", that it would unlock absolutely any type of lock, but it's not supported for this device, neither I think it can do anything since the system is not starting.
Device was bought cheap if I understand well and is in perfect condition, so there is nothing except the motherboard to be replaced, but since it's a friend's device, I don't wanna make him spend money on it.

Hello
Did anyone manage to solve it? Please share if any working solutions.

Technogeeks said:
Did anyone manage to solve it? Please share if any working solutions.
Click to expand...
Click to collapse
Do you have the same device, or something else?

Hello
Jovan Riparazioni said:
Do you have the same device, or something else?
Click to expand...
Click to collapse
Yes I have the same device, please tell me you have a solution

Nope, just hoped you own an older device. These features is little kernel are implemented from Android 6 I think. If you could downgrade the BL, you wouldn't have a problem. Does anyone know how to disassemble the sboot.bin back to "readable" code? I don't program, but I sure could take a look and waste my time

any more on this? have samsung SM-T819 with "MDM mode cant download" message when trying to do full factory reset with odin ,kies. any solution? thanks!

Nothing mate, try JTAG, or eventually flashing a debrick.img (if can be found) through USB with testpoint wiring.

Jovan Riparazioni said:
Nothing mate, try JTAG, or eventually flashing a debrick.img (if can be found) through USB with testpoint wiring.
Click to expand...
Click to collapse
Hmm seems really complicated I think .pit comes should have fixed the issue let me research a bit well try to contact you then

Jovan Riparazioni said:
Nothing mate, try JTAG, or eventually flashing a debrick.img (if can be found) through USB with testpoint wiring.
Click to expand...
Click to collapse
I'll see if I can get hold of the eng boot or the combo firmware. This may at least flash.
The other thing to try is to flash using Heimdall for Linux to flash the firmware.
Heimdall doesn't have the restrictions ODIN has.

ashyx said:
I'll see if I can get hold of the eng boot or the combo firmware. This may at least flash.
The other thing to try is to flash using Heimdall for Linux to flash the firmware.
Heimdall doesn't have the restrictions ODIN has.
Click to expand...
Click to collapse
If you mean HOME.tar by combo firmware, then you're losing time. I tried. The point is that certain partitions are locked for recovery and ODIN mode. I tried flashing file by file from tar's and md5's with Octoplus Samsung, as well as with Chimera Tool, but at the end, only sboot.bin can be flashed. But since that's the bootloader file which is instructed to check from (I think) data partition for restriction parameters by MDM, someone who knows how to edit them could (I suppose) easily remove that line of code.

Jovan Riparazioni said:
If you mean HOME.tar by combo firmware, then you're losing time. I tried. The point is that certain partitions are locked for recovery and ODIN mode. I tried flashing file by file from tar's and md5's with Octoplus Samsung, as well as with Chimera Tool, but at the end, only sboot.bin can be flashed. But since that's the bootloader file which is instructed to check from (I think) data partition for restriction parameters by MDM, someone who knows how to edit them could (I suppose) easily remove that line of code.
Click to expand...
Click to collapse
No, I mean the engineering firmware?

To be honest, now I don't even know what you mean. I thought maybe it can be put into QFIL mode, and then flash it, if that is what you mean?

Jovan Riparazioni said:
To be honest, now I don't even know what you mean. I thought maybe it can be put into QFIL mode, and then flash it, if that is what you mean?
Click to expand...
Click to collapse
Hi
Did you managed to solve the MDM MODE problem?? I have the same problem with phone......
Please let me know
Thanks

No, unfortunatelly
snsmosko said:
Hi
Did you managed to solve the MDM MODE problem?? I have the same problem with phone......
Please let me know
Thanks
Click to expand...
Click to collapse
This specific unit is driving me nuts... Anyways, I already read about this type of thing and all the possibilities.
Tried so far:
1) ADB enable-can't flash nothing except aboot.mbn (tried million times flashing file by file, recompiling .tar, Chimera mobile utility, Octoplus Samsung box, all the different firmwares... Not allowed, MDM!
2) Factory reset, ADB sideload-blocked by MDM!
3) Factory binary (combination)-only aboot.mbn passes
3) Tried "NAND erase all" with Odin-nothing changes
4) Re partitioned with all .pit
5) Tried flashing in kernel panic mode (unknown download mode, caused by aboot.mbn from factory binary)-fail
So, these are the options:
1) Modifying aboot??
-I need someone who can reverse engineer, or at least give me directions how to decompile the file to a readable code.
2) eMMC flash
-needs disassembly, needs files, impossible to find...
3) QFIL flash (deep flash)
-Need files for the model (almost impossible, could work with files from different unit with the same chip, or can be created from official FW files (need patch0.xml, firehose...))
-Not sure if it's possible to boot it into "qdloader 9008" mode without disassembly (test point method), it's very complicated to perform, and the chance to have it as good as new later is very little.
4) T-flash -very unknown Odin function, couldn't find much about it.
Requires a class 10 microSD card, I suppose the size of the eMMC (32GB in this case)
I'm not quite sure how it works, I do not have an SD card to give it a try, but if understood, you can put it in the device, check the option, select pit and it will flash the FW to an SD instead of eMMC, then we can work around the MDM security when we gain access to system.
Please, if anyone reads, knows or has something on this, write it!
Also, if anyone else has MDM issue, report!

So I tried to unlock via EDL...

...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)

So neither of the two USB ports in the phone seem to work for you in bootloader mode?

dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?

I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.

dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.

WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?

dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.

What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.

HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!

WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.

HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.