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.
Related
First of all, let me introduce myself. My name's Rafael and this is my 1st post in this forum. I hope humbly that you can to help me with the problem that I'll show you then:
Well. To begin, the issue is this... I am working with a telephone that's not mine. Somebody sent it to me to fix it, they said me that the phone doesn't download more apps because of "full memory". When I checked it, apparently it had the internal memory partitioned incorrectly, it said it was 16gb total storage with 7 GB available, but when I was installing some apps and went back to see the memory, it showed the Available Storage Memory with a large negative number, and it wasn't letting me install more apps. Some of the features of the phone are the following (according to MTK Droid Tools):
MTK6589 <---------(Actually it's MTK6571)
Model Name: Galaxy S5
Android Version: 4.4.4 <---------(Questionable)
Model Number: SM-G900H
Base Band: G900HXXU1ANCE
Then, to see if I could make some change, I decided to install a custom ROM, apparently for MTK6589 (at that time I didn't suspect about the horrible phone's falsehood). I wanted to see if this ROM brought the partition configured correctly. I tried to carry out the installation by the CWM Recovery from SD card. It turned out that the installation did not exceed 10% and it froze there. Then I removed the battery of the phone and inserted it again. When I try to turn it back on, it stays on the screen Mediatek. And from there, it does absolutely nothing more.
I've tried to flash back the backup that I made to the phone with MTK Droid Tools, both version 5 of SP Flash Tool as version 3, but I'm still not achieving positive results, always it throws me errors errors and more errors . I've searched all over the web, compatible ROMs for this phone, but apparently there is not anything. The only way in which (at least) it begins to flash from SPFT v5, is loading a ROM MTK6571; if not, it only throws errors. However, I've already tried, but it gave me error. It appears when the yellow bar that says Download Flash reaches 3%, and then it throws the error.
The only possible solution I see is to make a ROM (from the backup I made to the phone with MTK Droid Tools before to **** it up) installable from recovery (CWM) that is the only thing that works relatively well. And I have not reached that conclusion alone, but in bilateral agreement with an expert from another forum with who I have almost a month discussing the issue.
I really need help buddies. I am desperate because I'm a bit under pressure because I have almost a month with the phone without achieving the desired results. :crying:
Greetings and thanks in advance to any of you who want to help me.
PD: Sorry for my bad English if I committed mistakes.
Post removed
Killwish said:
Download stock firmware from http://samsung-updates.com or http://sammobile.com
And flash it via odin...
Good luck
Click to expand...
Click to collapse
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Sorry for my previous post..... I didn't read carefully. It's not s5 its clone....
Another way...
zelendel said:
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Click to expand...
Click to collapse
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
06rafagar94d said:
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
Click to expand...
Click to collapse
Best advise is that you can try. Like I said we dont deal with clones at all really.
Worst thing that will happen is that it wont work and you learned a lesson about clone devices.
Long story short:
How do i get my current working android device to revive an identical soft-bricked device. More challenging than you think: there is no boot menu accessible in the devices. Which means the only other choice is to use a usb connection to a PC to perform all tasks, i.e. create a rom system image backup of the working device, then use that to restore the system onto the soft-bricked one.
So is there a way to revive the s/bricked device with a rom image of the working twin?
The long story:
After using the super-sume app, my device got softbricked. Phones of my type are uncommon and are therefore not worked on by the android hacker community as much as flagship devices are. And little is known or discovered about them. So after doing more research, i've sadly come to know that there are other users here and there, having suffered the same problem as I. But enough about that.
As far as i've read and come to understand, i would need to re-flash the firmware to bring it back from it's softbrick issue easiest/safest way.
Though am not sure how the android platform would work. With PCs, i could restore a messed up system from a cloned image. What i need to confirm is if the firmware is separate from the OS (roms i believe) the same way device drivers are separate from the windows OS on PCs.
So am not sure if flashing firmware is enough and would need to stock rom too. Or is the rom considered both firmware and OS all in one?
I mentioned "restore from a clone image backup" because I have another, exact same model of my softbricked device, that functions still properly.
So i wonder if there is a way that i could use my working device to revive the soft-bricked one. In the sense that i would need to make a system image copy of my working one, to restore onto the s/bricked one.
What the problem looks like when starting the phone:
As for the softbrick appearance, the phone boots into the LG logo screen and is frozen there. It doesn't quite look like it's boot looping since the screen Never fades to black quickly just to come right back. It's just frozen there. This recovery mode screen is the only other thing i can get to besides the frozen LG screen: https://wcrates.files.wordpress.com/2015/03/lg-g3-recover-mode.jpg
I've come to learn (but may need correction on) that Tracfone devices are deliberately handicapped in a way i've never seen before. That is, their devices have no other boot type of menu besides the Recovery Menu (found before os begins boot) that is basically a factory reset. It just deletes all user data and resets system settings so that the phone works like it would at first when right out of the box. For the s/bricked device, that screen can be accessed, though executing that just resorts to the frozen boot screen again. If there is a boot menu to backup/restore from, clear cache, install from zip and what not, then please enlighten me. Because as i've tried everything, the tracfone-devices have nothing compared to non-tracfone-devices
So in order to install an updated rom, i may need to get into a type of system boot menu from where i would be able to select the option to install a rom or update it and what not. To some degree i assume that connecting the device through USB to a computer, one may do the same rom installation action through the PC, but it's in cases like these where i would need the help of and expert's first hand experience with such things or ways.
I don't mind if you want to leave a link to some tutorial some other guy has made that may closely related to (if not exactly) to help solve this issue. But i do prefer to get into contact with someone who i can report to with how the solution process is progressing. Mostly because me being a noob at this point of my android experience, but am confident since i've done this with pc's a lot.
I'm still trying to figure out what most of the android community speaks of when it comes to methods of backing up their stock roms and what kinds of software on PC or apps on the device are needed to accomplish a worthy backup. I do realize i'd need ADB and what other LG device compatible PC software out there. Here is a link where i think firmware files can be found, but since it's all in Chinese, i'm not sure how reliable the site is/can be. It's been about a month since i contacted some of their users. At this point it seems like they're no hope:
http://mobile.gaodi.net/Firmware-669539-1-1.html
I hope that i can find success so that i can post it up to help others who are in the same situation as me, and also for the many more who may yet fall into this situation.
Any help will be greatly appreciated.
Thanks.
Device: LG l21g (aka lgl21g) Destiny (model) by TracFone
Android: 5.0.1
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.
Hello
I've just flashed my Philips Xenium v787 and installed an official ROM here mediafire.com/file/o91r1zl8nuvsy7u/Philips_V787_MT6753.zip but after flashing is successfully completed, i tried to turn on my mobile but it won't load up and i tried to charge it but no sign!!
Please help.
Caboz said:
Hello
I've just flashed my Philips Xenium v787 and installed an official ROM here mediafire.com/file/o91r1zl8nuvsy7u/Philips_V787_MT6753.zip but after flashing is successfully completed, i tried to turn on my mobile but it won't load up and i tried to charge it but no sign!!
Please help.
Click to expand...
Click to collapse
When you say official ROM, do you mean a stock ROM ripped and put on the internet, or a custom ROM used for customization? Does anything pop-up on the screen when you press the power button (i.e. battery indicator)?
CrafterJG said:
When you say official ROM, do you mean a stock ROM ripped and put on the internet, or a custom ROM used for customization? Does anything pop-up on the screen when you press the power button (i.e. battery indicator)?
Click to expand...
Click to collapse
I meant a stock ROM on the internet. Nothing shows up at all, tried to charge the phone and there's no sign, and then tried to get into the recovery mode using power off and volume up + down buttons and nothing happens at all. I'm afraid that my phone could be completely damaged :crying:
Caboz said:
I meant a stock ROM on the internet. Nothing shows up at all, tried to charge the phone and there's no sign, and then tried to get into the recovery mode using power off and volume up + down buttons and nothing happens at all. I'm afraid that my phone could be completely damaged :crying:
Click to expand...
Click to collapse
It sounds like your phone may be "bricked". This happens when you load a faulty recovery image onto your device, whether it's incompatible with your device, or a bad recovery. Don't fret, though, as this is sometimes fixable. A simple google search for how to unbrick an Android device delivers a wealth of results, but sometimes a device-specific search may be more relevant to your situation. Best of luck! :good:
- CrafterJG
CrafterJG said:
It sounds like your phone may be "bricked". This happens when you load a faulty recovery image onto your device, whether it's incompatible with your device, or a bad recovery. Don't fret, though, as this is sometimes fixable. A simple google search for how to unbrick an Android device delivers a wealth of results, but sometimes a device-specific search may be more relevant to your situation. Best of luck! :good:
- CrafterJG
Click to expand...
Click to collapse
Well i searched in Google and unfortunately it seems like my phone is hard bricked. However, I'm going to send it to a repair center and see what's going to happen but i feel like i most likely will end up needing to buy a new phone. Thanks anyways!
Caboz said:
Well i searched in Google and unfortunately it seems like my phone is hard bricked. However, I'm going to send it to a repair center and see what's going to happen but i feel like i most likely will end up needing to buy a new phone. Thanks anyways!
Click to expand...
Click to collapse
Somehow, what you flashed must not have been for your specific device. Flashing stuff that wasn't made for your specific device is the fastest way to hard-brick a device.
From what you posted in your first post, the file that you downloaded and flashed looks like it should be the correct firmware for your device. But, since you didn't download it from the official site for your device, the file that you downloaded may have been modified before it was posted at the place that you downloaded it from or maybe your downloaded file got corrupted or didn't download completely. A corrupted/incomplete file could result in a hard-brick.
Another thing that could have gone wrong is a faulty connection between your device and PC during the flashing process. Or maybe the battery died during flashing or during first boot. This can also cause a brick.
You might be able to repair the device yourself by replacing the motherboard. It could be cheaper than buying a new device or cheaper than the cost of repairs at a shop. Try finding a YouTube video that demonstrates how to disassemble your device to replace the motherboard. You will have to be certain that you are buying the correct motherboard for your specific device model number. After replacing the motherboard, you will have to make certain that you have the correct official firmware file and then flash that firmware onto the new motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Somehow, what you flashed must not have been for your specific device. Flashing stuff that wasn't made for your specific device is the fastest way to hard-brick a device.
From what you posted in your first post, the file that you downloaded and flashed looks like it should be the correct firmware for your device. But, since you didn't download it from the official site for your device, the file that you downloaded may have been modified before it was posted at the place that you downloaded it from or maybe your downloaded file got corrupted or didn't download completely. A corrupted/incomplete file could result in a hard-brick.
Another thing that could have gone wrong is a faulty connection between your device and PC during the flashing process. Or maybe the battery died during flashing or during first boot. This can also cause a brick.
You might be able to repair the device yourself by replacing the motherboard. It could be cheaper than buying a new device or cheaper than the cost of repairs at a shop. Try finding a YouTube video that demonstrates how to disassemble your device to replace the motherboard. You will have to be certain that you are buying the correct motherboard for your specific device model number. After replacing the motherboard, you will have to make certain that you have the correct official firmware file and then flash that firmware onto the new motherboard.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply.
Yesterday i went to a few local repair shops and one of technicians connected my phone to a charger where you get a light if your device is connected and working properly, then he told me that it's getting enough amps(ampere) to work well but it's probably going to need a software, unfortunately, they couldn't help me, as they don't have the required software for my device (Philips) and they advised me to visit the manufacturer's service center in order to solve this issue.
What I've noticed is that when i connect my phone to my laptop, i can still hear a sound like the one you get when you connect a USB to your laptop, so maybe it's not a hardware issue?
I've called my manufacturer's repair center and they mentioned that for any repair-related issues, it's going to take 3 working days to fix any issue (due to their policy). However, I'm afraid of having my data spied on/accessed if i left my phone over there and I'm really confused whether to buy a new one or just leave it to get fixed.
P.S To everyone who is trying to help me, i do really appreciate it