Database Info

Bricked A110 - Calling for help

Hi Guys,
Calling for help,
Post flashing new ROM, android device has got bricked (no offence to ROM, I’m sure it’s just my ignorance that has caused it).
Device isn’t responding, tried flashing SP tool, installed drive devices no luck what so ever, in fact SP tool doesn’t detect the device. As an alternate downloaded volcano & Miracle app just to realise that he does require hardware, which i don’t own.
Now before banging my head to the near wall , can somebody please advise if there is anything else i should give it as a try?
Any thoughts/suggestion would be appreciated. It has been 2 frustrating days since trying to jig with the device in bricked condition.
Thanks in advance
:fingers-crossed:
Cheers,

stalingard said:
Hi Guys,
Calling for help,
Post flashing new ROM, android device has got bricked (no offence to ROM, I’m sure it’s just my ignorance that has caused it).
Device isn’t responding, tried flashing SP tool, installed drive devices no luck what so ever, in fact SP tool doesn’t detect the device. As an alternate downloaded volcano & Miracle app just to realise that he does require hardware, which i don’t own.
Now before banging my head to the near wall , can somebody please advise if there is anything else i should give it as a try?
Any thoughts/suggestion would be appreciated. It has been 2 frustrating days since trying to jig with the device in bricked condition.
Thanks in advance
:fingers-crossed:
Cheers,
Click to expand...
Click to collapse
hi Bro go to my thread, I got the same problem 2 yrs back n successfully got my phone back, u can search for chaitu.swaroop, there u can get the solution to get your phone back

chaitu.swaroop said:
hi Bro go to my thread, I got the same problem 2 yrs back n successfully got my phone back, u can search for chaitu.swaroop, there u can get the solution to get your phone back
Click to expand...
Click to collapse
Yaar, you have 13 post of which none for brick.I suppose your are referring to this thread (http://forum.xda-developers.com/showthread.php?t=2376667) which is for soft brick. Hard brick implies your phone cant be turned on.
If im wrong than i would request you to share the thread which are referring to.
thanks in advance.

stalingard said:
Hi Guys,
Calling for help,
Post flashing new ROM, android device has got bricked (no offence to ROM, I’m sure it’s just my ignorance that has caused it).
Device isn’t responding, tried flashing SP tool, installed drive devices no luck what so ever, in fact SP tool doesn’t detect the device. As an alternate downloaded volcano & Miracle app just to realise that he does require hardware, which i don’t own.
Now before banging my head to the near wall , can somebody please advise if there is anything else i should give it as a try?
Any thoughts/suggestion would be appreciated. It has been 2 frustrating days since trying to jig with the device in bricked condition.
Thanks in advance
:fingers-crossed:
Cheers,
Click to expand...
Click to collapse
if sp flash tool doesnt detect device then manually install vcom driver as explained below

LG Stylo 2(K540)- At this point I'm begging for help!

I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!

send to lg said stop working no luck with tihs hard brick

Source code to rom¿?
I ran into basically the same situation as you. I'm currently downloading Android open source project on to a fresh install Ubuntu 16.04. I am currently in the middle of running sync.
I'm curious if there is anybody out there who would be willing to give a few pointers, on compiling the ROM from LG open source code. They told me I had to use it in the readme.txt.

Im a noob with fair knowledge of modding and stylo not stylo 2. There's no way to say for sure if this will work but on lg mm on h631 u need to unlock dev option in settings 1st. Make sure to check off oem unlock and usb debugging. Connect to pc and you will get a popup or 2, one will ask to allow pc to connect to phone, the second is to allow usb debugging. After you allow both, open cmd in your adb fastboot folder. Type " adb reboot bootloader." should reboot the phone to bootloader/fastboot mode. Then you type " fastboot oem unlock." you will see sending.. Once sending is done type " fastboot reboot." when the phone restart you should see bootloader unlocked on splash screen. Then i rooted with kingroot. Then use rashr to flash twrp. Then used twrp to flash supersu to get rid of kingroot.. My h631 now in business and i just started working on a port for lg ux 5.0. This is the guild i use for a better idea http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916. You might need lgflashtool and kdz to unbrick..

NO NEED to beg.
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis

Hello Sir, I ran into same problem trying to root. If you can, can you please send me a link so that i can use my phone again. Thank You it will be greatly appreciated

can some one help me. i cannot use adb to unbrick

Please send me the link
facorbin said:
I don't know very much but I know $$$ talks and since no one save the few who suggested contacting lg wants to help, Ill try. At the moment I am efforting a solution via the Chinese. I expect to have a working copy in the next 48hrs. when I do, we can arrange for you to get access to the mega.nz cloud and get urs.
say a prayer......
Francis
Click to expand...
Click to collapse
Hi, can you please send me the link? I need it bad thx

if you cant boot into dlmode then your hard bricked, so find a way to get back to dl mode/recovery

BIN File
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware

estebangtz said:
Hello, I have a Stylo 2 K540 from cricket, it is having issues with the Wi-Fi, it will not connect to either Wi-Fi or bluetooth, MAC address was set at 02:00:00:00:00 or something like that, I opened the phone and it has humidity sensor active, cleaned the affected area but it seems like it was useless, eventhough I was pretty sure that was not the main problem. I looked for some troubleshooting options and found non of use, firmware is sold for $30 online so it is not an option since I am not certain loading firmware will be of any help. I tried repairing MAC address via Octoplus using other addresses but was useless as well.
I have little to no experience with software on phones, but I like to read and learn. I decided to connect the phone to the computer and "Read full flash" on Octopus, I have created the Bin file, I have a perfectly working phone as well, I was wondering if there is any way to get the KDZ file from the Bin file doing some sort of conversion, or if I could do some sort of fix or workaround with this bin file, I can share it if anybody needs it or if it can be of any use to get the firmware
Click to expand...
Click to collapse
cna you possible sned me it I might be able too

no longer have the bin file
HERPDERP202 said:
cna you possible sned me it I might be able too
Click to expand...
Click to collapse
I am sad to say my computer stopped working and just got it back today, all my information was lost so I no longer have the bin file

bsimpson1858 said:
I'm new to the XDA Forums and even forums in general so if I speak out of place or anything like that I apologize ahead of time. So anyway, where do I start? I'll try to give you the short version. So I bought an LG Stylo 2(model: LG K540) through Cricket the day they came out. It was $170 phone. On the second day of using my new phone I got the bright idea that I'd try and root it BY MYSELF. I knew better but for some reason I had this false burst of confidence & thought I had everything under control. Well, thanks to Kingroot that burst of confidence didn't last long and there I was with a 2 day old phone BRICKED. Reason I never posted on the forums is because I've got a buddy who , in my eyes, knows everything there is to know about Android and thats who I'd normally go to when I wanted to root a phone so he's who I immediately turned to but even he couldn't figure it out. He couldn't help me unless we had the stock firmware or someone with the exact same phone and according to him we could some how use a backup of that phone to fix mine. Cricket just wanted to sell me another phone even though I was standing there with a 2 day old phone and LG just wants me to send the phone in to them, which I have no desire to do. I've searched all over the internet trying to locate the firmware because even I can fix the phone if I had that but nothing. Had hoped by now LG would have released the firmware but at this point who knows when that'll happen. I'd even pay for it at this point. Anyway, just thought I'd give the forum a shot on the off chance someone might be able to help me or point me in the right direction. Oh and if you were wondering what the phone does now, when I turn it on the LG logo appears like it should but then right as it appears you see a message in red lettering that says: BOOT VERIFICATION FAIL!!- CAUSE: MISMATCH_SIG_LEN And it just loops this over & over until you pull the battery out. Please someone help me!
Click to expand...
Click to collapse
you can go into download mode by pressing volume up key and inserting usb cable .press the volume up until you see download mode a firmware readed by z3x box is available on clamgsm forum you can flash it with z3x box crack .

Hard Bricked S4 I545PPVRUAOH7

Hello! So I am new to all this havent done anything similar in over 7 years. Things are much more complicated now. Unfortunately during my trials I hard bricked my s4 I545PPVRUAOH7. I bought this phone this year so it never had jellybean. Going thru hardbrick tutorials I understand I need a scatter.txt. Unfortunately, I cannot seem to make this file from a number of stock i545 roms. MTK android tools simply wont read the md5 file and I dont understand at all. Needless to say now that I am aware of this I will create the scatter.txt whenever possible in the future. I have the correct VCOM drivers installed. I have been stuck for days and would really appreciate a helpful push in the right direction to get MTK android tools 2.5.3 to work... Or if someone could just send me a scatter.txt file from this phones original firmware I would owe you forever. Also am I able to just flash a different but compatible scatter with SP Flashtools? There is a huge data base of scatters but remain cautious in testing anything without confirmation, as there is nothing for my specific phone.
Thank you for your time.

Bump
Sent from my XT1528 using XDA Free mobile app

Thoughts about soft and hard brick ?!

HI there.
i read this :
Soft Brick
Soft brick is the state of android device due to some software problems like bootloops or device freezing at some point during boot. This may occur if some software problem occurred in the device mainly during OS upgrade or flashing something such as a custom ROM, camera mod or app in your custom recovery mode. A soft-bricked device is only half-dead. Because of this, your device is not booting anymore or is constantly crashing but can be recognised by a computer.
When your phone is soft brick, don't be panic. You can revive your Android device as long as it is only soft-bricked. The basic solution for this issue is flashing a clean and working version of Android to your device. While, during this process, you may need to restore a backup, flash a custom ROM or stock images to your device.
Hard Brick
Hard brick is the state of android device that occurs when your device is unbootable without a bootloop. A hard Brick device generally show little to no signs of life. If this happens, you had better to buy a new device since your device is showing you a black or grey screen at this point.
A phone get hard-bricked due to trying install ROM not made for the device or use ROM Manager incorrectly. Hard brick is more difficult to resolve and you may require an expert to give you professional advice. However you can recover from hard brick by using JTAG or send your Phone to JTAG service center to get it fixed, which means you no longer need to buy a new one.
Click to expand...
Click to collapse
Is it true that even hard bricked device can be high percent recoverable?
I own service and want to know the things good and be normally good. If i have to i will take loan to buy nessesary stuff to be successful.
Is that with JTAG true for tablets too? I have buyd from AliExpress Phone Box 2017 version but still havent used it.
If i have to be more specific. Have one client`s tablet here. It is recognised by Windows as MTK something and gone after seconds from device manager then recognised again and that...
history : it was virused and install OS to it was really needed. I shot in the dark and install it some OS for these parameters:
mt6582 1G+16G and flashed it successfull with SP Flash Tool but now the device does not boot and is half recogniseable in Device Manager. I did that because the device/'beauty' chinese tablet/ has no ID on the back side of it.
I hope this time someone to tell something good and usefull.
Thanks

diretouch said:
HI there.
i read this :
Is it true that even hard bricked device can be high percent recoverable?
I own service and want to know the things good and be normally good. If i have to i will take loan to buy nessesary stuff to be successful.
Is that with JTAG true for tablets too? I have buyd from AliExpress Phone Box 2017 version but still havent used it.
If i have to be more specific. Have one client`s tablet here. It is recognised by Windows as MTK something and gone after seconds from device manager then recognised again and that...
history : it was virused and install OS to it was really needed. I shot in the dark and install it some OS for these parameters:
mt6582 1G+16G and flashed it successfull with SP Flash Tool but now the device does not boot and is half recogniseable in Device Manager. I did that because the device/'beauty' chinese tablet/ has no ID on the back side of it.
I hope this time someone to tell something good and usefull.
Thanks
Click to expand...
Click to collapse
Yes, it is "possible" to recover hard bricked devices with a JTAG but there are no guarantees it will work and no way to guarantee each customer that there device will be fixed.
As for the MTK device you are trying to repair, you can't just flash a firmware from another mt6582 device, there is quite a bit more involved than just the same CPU. Firmware from another device must be ported to work with the other hardware on the device.
You need to identify more about the device than just it's CPU if you want to find a firmware that will work without modifications.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Can you help me identify the device ? Please...
https://drive.google.com/drive/folders/0Bxome1ZSCRIaSW5fNTZrY3NsU2s?usp=sharing

diretouch said:
Can you help me identify the device ? Please...
https://drive.google.com/drive/folders/0Bxome1ZSCRIaSW5fNTZrY3NsU2s?usp=sharing
Click to expand...
Click to collapse
If that's the device after you flashed it, it seems to be booting fine. Is it having issues where some features and functions aren't working correctly?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Unfortunately this is the device before flash.
It`s labeled as pc703 in the seller site/bulgarian not China/
The back cover of the device is
https://drive.google.com/file/d/0Bxome1ZSCRIaOGpIWjcxaGg5ek0/view?usp=sharing

diretouch said:
Unfortunately this is the device before flash.
It`s labeled as pc703 in the seller site/bulgarian not China/
The back cover of the device is
https://drive.google.com/file/d/0Bxome1ZSCRIaOGpIWjcxaGg5ek0/view?usp=sharing
Click to expand...
Click to collapse
Can you give me a link to the seller site?
Usually these cheap off branded Chinese tablets are almost impossible to identify properly because the hardware varies so much even among separate devices with the same model number. It is like this because there is no actual "manufacturer", these devices are pieced together with cheap discounted components that were bought in bulk and they use whatever they can get to work, even if it involves using completely different components. This makes it virtually impossible to say exactly which firmware you need.
When a device is bricked and the device is one of these cheap devices that can't be identified properly and has no available stock firmware or stock source code and has no support from the manufacturer, typically, the only solution is to just try different firmwares and hope one works or piece together your own firmware with pieces of others that might compatible.
You'd have to have a lot of time and android development skills to make your own firmware.
You've got a difficult road ahead, I'd suggest they replace the device because the cost of repair will be more than the device costs.
When you flashed the device with SP Flashtool, did you happen to pull anything important from the device or did you by chance make a backup of some sort before you flashed it?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Man usually understand his mistakes after he did it.
Maybe I will never take again unknown tablet for service. The problem is that the customers are waiting and I am tired of buy customers devices either second hand or new.
The site should be 4sales.BG
That said the woman.
The 'cool' is that I find there version not with 1g+16g
Good night.

In simple words, Soft brick is messing a little with your Android from which you can recover easily.
Hard Brick is like screwing up your device completely, yes, you can recover, but it needs lots of technical process.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
In simple words, Soft brick is messing a little with your Android from which you can recover easily.
Hard Brick is like screwing up your device completely, yes, you can recover, but it needs lots of technical process.

Technical or not that`s not bad. Just want to have the nessesary tools if they are not too expensive. I just wont desolder very very small smd resistances and transistors
If someone can help in my chinese tablet case i will be a little more not unhappy.

Firmware encountered a problem.......

Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.

elboobio said:
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
Click to expand...
Click to collapse
flash a custom recovery, and install this, https://builds.unlegacy-android.org/aosp-4.4/espresso/ua_espresso-4.4.4-20171105172717.zip

Thanks for the reply. I have attempted to flash a recovery, however every one I've tried fails and tells me 'NAND write failed'. I tried the TWRP recovery and philztouch. You don't have a link to a recovery you think might work? I'm pretty sure I've been using recoveries that should work, but you never know.