Database Develop

Urgent advice needed on Razr i XT890

hi, my phone Razr i XT890 is showing the Red Moto Logo, I tried to factory reset by going into fastboot also but nothing happened, I can find many thread here about the same problem but nothing conclusive could be found in those threads, hence I sent my phone for repairs, the technician hooked it up to a computer and said that most likely it is a software issue and the phone would be ok, after waiting for an hour I was told that the emmc has died and it cannot be replaced and the only solution would be to change the motherboard, since the mother board is not avaible in the market I looked it up on aliexpress and it costs around 70$ where as a new/refurbished phones are listed for 75$, need you guys advice on whether it can be repaired or not and if yes then how. I am a regular user and not an expert like you guys so if you suggest any thing plz do it in detail. FYI its a factory unlocked phone which had jelly bean OS and I never rooted it or did any hanky panky to it. Thanks

What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.

Hazou said:
What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.
Click to expand...
Click to collapse
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.

cooljatt18 said:
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.
Click to expand...
Click to collapse
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?

Hazou said:
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?
Click to expand...
Click to collapse
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !

cooljatt18 said:
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !
Click to expand...
Click to collapse
This is most likely solvable. Try that flash methods a few post above and see what happens s

Hazou said:
This is most likely solvable. Try that flash methods a few post above and see what happens s
Click to expand...
Click to collapse
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it

cooljatt18 said:
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it
Click to expand...
Click to collapse
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !

cooljatt18 said:
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !
Click to expand...
Click to collapse
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
thanks a ton!!!

hi, guys sorry for posting so late, was super busy, any how haven't got a mechanic to flash the phone, guess I will have to do it myself, request you to answer my queries
.1) a mechanic to whom I went convinced me to believe that the problem was due to a faulty battery and he could fix it in 5 mins flat, He opened the phone did some tinkering with it, I am not sure what but the phone was in same condition ie Red logo on booting. Was very disappointed came back home and I tried to restore it through fast boot and I noticed that the Battery Current was coming as 4.1 V earlier it was 3.7 !!! I am sure that the mechanic messed it up. Now my question is will it harm the phone, battery or any other part?? Should I just leave it the way it is ie 4.1V and not try to rectify it to bring it to 3.7V.
.2) I am not able to get a mechanic who can flash the phone as suggested in previous posts, pl tell how I can do it myself, I am a newbie at this and have zero knowledge of the process, pl tell what all software are needed! And hardware if any. All I have got currently is the firmware posted in previous posts.
Thanks

(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!

99% chance I bricked my phone

Edit: problem solved someone remove this thread.. I dont know where the delete button is D
I'm pretty sure there is not much I can do anymore... I don't have an os installed because I couldn't restore it (I coulnd't restore the data..). I'm stuck in twrp and it doesn't recognize sd card. The files in my internal storage are all corrupted. Is my phone now fully bricked? Is there a way to make the phone recognize the sd card? Also I cannot move files from my pc to phone..

Fisuxcel said:
I'm pretty sure there is not much I can do anymore... I don't have an os installed because I couldn't restore it (I coulnd't restore the data..). I'm stuck in twrp and it doesn't recognize sd card. The files in my internal storage are all corrupted. Is my phone now fully bricked? Is there a way to make the phone recognize the sd card?
Click to expand...
Click to collapse
Use the flashtool to restore the system.

umm I don't think I can..
SXUsr said:
Use the flashtool to restore the system.
Click to expand...
Click to collapse
because of this...
No usb device with vid:0x0fce pid:0xb00b !
Press any key to continue . . .

Fisuxcel said:
because of this...
No usb device with vid:0x0fce pid:0xb00b !
Press any key to continue . . .
Click to expand...
Click to collapse
Try Sony EMMA.

nope, doesnt work
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.

Fisuxcel said:
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.
Click to expand...
Click to collapse
https://postimg.cc/G45ssGzW

Fisuxcel said:
https://postimg.cc/G45ssGzW
Click to expand...
Click to collapse
Can I boot to bootloader if I don't have an os?

Fisuxcel said:
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.
Click to expand...
Click to collapse
You've connected it in flash mode?

SXUsr said:
You've connected it in flash mode?
Click to expand...
Click to collapse
doesnt work, I cant let the pc access my phone if I dont have an os. And yes its in flash mode now. You know its supposed to ask for the fingeprint but I cant accept it as long as I cant access the os.

Fisuxcel said:
doesnt work, I cant let the pc access my phone if I dont have an os. And yes its in flash mode now.
Click to expand...
Click to collapse
Your problem now is getting an OS back on the phone. The screenshot you've posted shows it's not in flash mode whilst EMMA is running, so what does EMMA do when you connect it in flash mode when prompted? Restoring the phone with the Flashtool, Newflasher or EMMA shouldn't be this difficult.

SXUsr said:
Your problem now is getting an OS back on the phone. The screenshot you've posted shows it's not in flash mode whilst EMMA is running, so what does EMMA do when you connect it in flash mode when prompted? Restoring the phone with the Flashtool, Newflasher or EMMA shouldn't be this difficult.
Click to expand...
Click to collapse
Umm.. I think I'm in the starting point again..
your device software can't be checked for corruption please lock the bootloader. Stuck in bootloop. I tried to install firmware through EMMA (didnt get any errors so I thought it had installed the firmware). Tried newflasher
got this error:
ERROR: Error CreateFile! failed with error code 5 as follows:
Access is denied.
I when I broke my phone I accidentally flashed wrong firmware, this. Thanks for helping me!

Fisuxcel said:
I when I broke my phone I accidentally flashed wrong firmware, this. Thanks for helping me!
Click to expand...
Click to collapse
Try flashing a XZ1C boot.img with fastboot and try EMMA again.

still not working...
SXUsr said:
Try flashing a XZ1C boot.img with fastboot and try EMMA again.
Click to expand...
Click to collapse
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems but when I boot up it bootloops probably because there is no os installed) I was able to flash lineage os (that I had previously installed) but when I tried to set up it all apps crashed and it rebooted.. also I have one back up of the stock rom but twrp would give me some error 255...

Fisuxcel said:
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems.
Click to expand...
Click to collapse
What does it do??? Again, it shouldn't be this hard. The phone clearly isn't bricked so user error is at play here.

Fisuxcel said:
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems but when I boot up it bootloops probably because there is no os installed) I was able to flash lineage os (that I had previously installed) but when I tried to set up it all apps crashed and it rebooted.. also I have one back up of the stock rom but twrp would give me some error 255...
Click to expand...
Click to collapse
If you're able to flash Lineage why can't you use Flash Tool to wipe the device, flash stock firmware and start over? The device is not bricked.

How to update
betacrypt said:
If you're able to flash Lineage why can't you use Flash Tool to wipe the device, flash stock firmware and start over? The device is not bricked.
Click to expand...
Click to collapse
Now that I have stock rom how do I update it to pie? Last time I flashed lineage os the camera broke.. I would like to run lineage os with working camera...

Fisuxcel said:
Now that I have stock rom how do I update it to pie? Last time I flashed lineage os the camera broke.. I would like to run lineage os with working camera...
Click to expand...
Click to collapse
If you're on the latest stock rom, you're already running Pie. Make sure you're on the latest.
The camera works well on Lineage 16 so you shouldn't be having issues. I would flash the latest stock firmware in Flash Tool. Then flash TWRP , and in TWRP flash the latest version of LOS 16. I'm running it currently and don't have any issues.

lol where is the delete button DD
nevermind

Help to Flash 'preloader.bin' via MTK-Client-command line

need to flash this last file via MTK-Client to try the restoration of a bricked device.
tried to flash it via SP Flash tool with no success, device not recognized (a complete mess!!!!)
I restored via command line all ROM .images, Vendor and Firmware files download from Original Custom ROM MT6768 (xiaomi mi note 9)
all exept 1, 'preloader.bin', this because mtk-client returned an error for a 'no specific partition location for that file'
currently, device is still dead and give no sign, but inside has been flashed quite all, is it possible that 'preloader.bin' can fix all and revive the device ???!!!
help is really appreciate, thanks anyway

Did you try flashing the full stock rom in EDL mode? Try this guide : https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/

Thanks very much, your help was precious, a thousend million billion thanks !!!!
you revived the device back again ... I can see the light back again after flat days
but from the state of coma now it is on the post surgery state !
It is in a non-stop boot-loop, and when it reach recovery it show up a 'NV data is corrupted'
I re-flash 3 time, with the command in SP Flash Tool 'Format whole flash' but none of this worked
thanks really anyway for your support, really kind !!!!!!!

thtechnician said:
Did you try flashing the full stock rom in EDL mode? Try this guide : https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
Click to expand...
Click to collapse
@thtechnican
I just love you right now, Man,
completely straight way.
Thank you. Be healthy, Have beautiful women, and that you never run out of anything you need.
@matteo555
It is in a non-stop boot-loop, and when it reach recovery it show up a 'NV data is corrupted' I re-flash 3 time, with the command in SP Flash Tool 'Format whole flash' but none of this worked thanks really anyway for your support, really kind !!!!!!!
Click to expand...
Click to collapse
Master, you did what I did - you reset all memory completely and -thanks to The Dude- restored the ability to run it. You probably lost the imei and other serious information, są flash stock rom and look for a thread about recreating the missing information - nvram.img etc. It's a miracle that I boot mine without disassembling, because I would throw it out the window. In my case it was Nokia 3.1 and thought I could create my own a/b rom instead of using lineage os 16 in gsi treble mode.
It was supposed to be few moments, but I lost 4 evenings and propably should buy another garbage to owner . Fortunately, I don't have to.