My My Touch 4G in turn hangs on the splash screen. By all signs eMMC M4G2DE problems. Program are not able to restore. It is possible to use the programmer RIFF to try to recover eMMC or a new program SEM04G. To do this, really need a full dump
You need bootloader, misc and radio partitions, and the knowledge of their physical offsets in eMMC. These are already available somewhere in the forum, try searching for the thread, you might be better off then waiting for someone to help.
Once you're booted into bootloader - you can just reflash any ROM.
I assume that you're capable of removing and soldering eMMC chip, and you have external programmer for it.
Thank you. I found several references to upload. But the files were all deleted. I have a programmer RIFF and the ability to connect via JTAG interface.
I have a myTouch 4G, can I be of assistance? Just post a link on how to do a system dump, and I'll upload it.
how can i help? would like to know that theres a true solution for a faulty eMMC
this is making me weary of crackflashing again damn
As my friend has a programmer RIFF box
Available operations:
- Recovery,
- Restore the boot
- Restore IMEI, CID and ModelID,
- Unlock.
restores the boot, but then load the firmware from the gold card has failed. Error: Can not access the user / date. I want to try to recover eMMC, this requires a full dump. If you did not receive, If you do not happen, then buy a new eMMС
i hv the same problem
did u repaired u phone i m also searching for dump file.
its size is 12 gb waiting to get download..
is ur phone live nw is it working or in dead condition please replay..
nilesh.wankhede said:
did u repaired u phone i m also searching for dump file.
its size is 12 gb waiting to get download..
is ur phone live nw is it working or in dead condition please replay..
Click to expand...
Click to collapse
Let me ask you a question, how do you you propose to fix a dead eMMC chip using software? Unless your problem is data corruption (e.g. corrupted bootloader), what good is the riff box going to do you? Like Jack_R1 said, you are going to need to solder a new eMMC to the board.
Related
So .. my nexus s has that problem with the internal 16gigs of memory .. the samsung service in my area says its broken and in order to repair it they have to change the motherboard .. but my warranty is broken because i was using cyanogen mod instead of the original samsung rom .. so my question is .. is there any way i can flash back to original rom in order for the warranty to cover my repair ???
Delete..........
the poit is i cant load anything inside the phones memory !!! i cant use cwm ! is there an alternative way ? to flash using pc .. something like nokia's phoenix ???
yes, there's fastboot. use it to reflash recovery. should this not work, have a look around here for an unbrick-guide.
and should your memory really be broken, meaning non-accessible at all, go back to that service point and tell them to shove it. unless they can prove to you that cm9 bricked it, the guarantee is still valid. unlocking your bootloader doesn't mean broken hardware isn't covered anymore.
but my guess is that you'll succeed with fastboot already.
PS:
don't ask. the guides are all there. use search. use google. it's not a big secret how to use fastboot or how to unbrick.
Well it seems that my internal SD is damaged or G Moto conclude that after trying many tutorials in order to recover and none work, despite installing stock rom, gpe, recovery, etc (all without error and apparently good) but it seems that so do not write install on the phone because no change, in fact I have tried to not think of brick and even that allows, there will be some way to fix this? even for hardware?
Or if there is any way to format the internal sd using adb, just as is done by a custom recovery
Note: this because it allows me to install a custom recovery
Your eMMC is fine, keep looking for solution or buy a new phone and don't fid with it anymore.
liveroy said:
Your eMMC is fine, keep looking for solution or buy a new phone and don't fid with it anymore.
Click to expand...
Click to collapse
I imagine that as the problem is not your answer so ...
Hopefully you never find yourself in a situation where you've tried almost everything and nothing works
angelgzg said:
I imagine that as the problem is not your answer so ...
Hopefully you never find yourself in a situation where you've tried almost everything and nothing works
Click to expand...
Click to collapse
It may not sound like it, but I'm actually trying to help you.
Anyway, let's hope the things work out in the [email protected]
liveroy said:
It may not sound like it, but I'm actually trying to help you.
Anyway, let's hope the things work out in the [email protected]
Click to expand...
Click to collapse
If you note, thanks
angelgzg said:
Well it seems that my internal SD is damaged or G Moto conclude that after trying many tutorials in order to recover and none work, despite installing stock rom, gpe, recovery, etc (all without error and apparently good) but it seems that so do not write install on the phone because no change, in fact I have tried to not think of brick and even that allows, there will be some way to fix this? even for hardware?
Or if there is any way to format the internal sd using adb, just as is done by a custom recovery
Note: this because it allows me to install a custom recovery
Click to expand...
Click to collapse
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
debaj said:
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
Click to expand...
Click to collapse
Well it seems to be almost the same, and I give my phone as lost
debaj said:
I had a similar issue, and I have bad news. If your warranty is still valid flash the original recovery back and try to ask for a replacement. I ended up with buying a broken Verizon branded Moto G as donor and replacing my logic board, of course the cellular network does not work but at least I can use my device for development. My problem was that the eMMC chip got some bad blocks (similar to bad sectors in HDDs) and it prevented the cache partition from mounting and some of other partitions became read only, for instance I could not update the recovery or install a new ROM while I could read the system files, while I was able to push files to the /data partition.
There is a tool called badblocks which can map these blocks and thus fix the eMMC theoretically (it generates a mapping file which can be used later by fdisk) but unfortunately this tool was left out from the Moto G's base system and I don't know if there is any ARM compatible version of it.
I asked around in GSM repair shops if there is any way to replace the eMMC chip with another one of the same model but all of them replied that they don't have the proper machinery to do such fine work and unfortunately there is no official Motorola service in Hungary so they couldn't even get a replacement logic board.
Funny thing that all the write operations were successful in fastboot, but later I found out that on most devices the eMMC controller is so primitive that it barely contains any error handling at all. It will only report trivial errors with a perfectly working eMMC chip, if the eMMc is broken and it cannot produce valid error messages the controller just assumes that everything was OK.
Click to expand...
Click to collapse
I'm having the very very same issue with an XT1032 Moto G. "Read-only" eMMC. At least I know I won't have to look for a service center in Budapest since there is none.
I buy S3 phones from craigslist seller(s) with broken screens in order to repair/resell (and to play around too), and once some sneaky ass sold me a phone where he swapped t-mobile motherboard to a blacklisted AT&T one. So IMEI on the phone said one thing, but actual IMEI on motherboard was a different one. Since the screen was broken, I couldn't run it and detect that he's taking me for a ride
Here's what I'm looking to do: I have a USB jid device (looks similar to this: http://www.ebay.com/itm/1pc-Downloa...063?pt=LH_DefaultDomain_0&hash=item2a224c448f), and I can force device into download mode, whether screen is functional or not. I can use heimdal to dump PIT, which is not very useful as far as figuring out IMEI. Now I am looking into a method to dump efs partition, so that I could write a script, which gets IMEI for me. I can't find any way to dump anything but PIT using heimdal. I know ODIN has some functionality to do that, but I got no idea how to activate it.
Anyone can suggest a solution?..
galets said:
I buy S3 phones from craigslist seller(s) with broken screens in order to repair/resell (and to play around too), and once some sneaky ass sold me a phone where he swapped t-mobile motherboard to a blacklisted AT&T one. So IMEI on the phone said one thing, but actual IMEI on motherboard was a different one. Since the screen was broken, I couldn't run it and detect that he's taking me for a ride
Here's what I'm looking to do: I have a USB jid device (looks similar to this: http://www.ebay.com/itm/1pc-Downloa...063?pt=LH_DefaultDomain_0&hash=item2a224c448f), and I can force device into download mode, whether screen is functional or not. I can use heimdal to dump PIT, which is not very useful as far as figuring out IMEI. Now I am looking into a method to dump efs partition, so that I could write a script, which gets IMEI for me. I can't find any way to dump anything but PIT using heimdal. I know ODIN has some functionality to do that, but I got no idea how to activate it.
Anyone can suggest a solution?..
Click to expand...
Click to collapse
I would flash a recovery with adb enabled, assuming adb is unusable in the main system, and use dd.
miked63017 said:
I would flash a recovery with adb enabled, assuming adb is unusable in the main system, and use dd.
Click to expand...
Click to collapse
it's probably easier to come with an screen then and just run device... Besides, phone is most likely bootlocked, and I will just brick it
Hello I have a gt-p5113 that has the encryption error and I don't think usb debugging was turned on yes I know this is a old device I still like it due to its size of screen, I've tried Odin a stock room, recovery, pit files Odin says they complete but nothing changes on my tablet. I've tried adb in Ubuntu and won't show up in adb devices but will in lsusb I was wondering if there is a way to fix this or is it pretty much a brick, thanks in advance for your help
sounds like a broken emmc, find one who can update the firmware via isp or replace the emmc
Thank you for your response just wondering what Isp is? Humm wouldn't replacing the Emmc be expensive, I'm just think maybe to junk the tablet
Just wondering if you think this would possibly work
http://forum.gsmhosting.com/vbb/f672/samsung-galaxy-tab-2-gt-p5113-emmc-support-first-world-1917766/
rabidelmo said:
Just wondering if you think this would possibly work
http://forum.gsmhosting.com/vbb/f672/samsung-galaxy-tab-2-gt-p5113-emmc-support-first-world-1917766/
Click to expand...
Click to collapse
Try it If it works, you may make some people happy
About emmc replacement: about 50 Euro should be a fair price if someone adds a good emmc (good emmc ~15 Euro; 1.5 - 2 hours working time).
About Updating the emmc software: sometimes only works for a short time and isn't a final solution.
The one i know who's replacing emmc is from austria if it's interesting for you.
My problem is I'm from Canada so I would prefer something more local or do they ship the part and I install it?
I was following a guide on unlocking the bootloader and rooting my v450 device, this was using QFIL to load the abl_a and abl_b files but made a mistake and accidentally loaded the file to the MPT partition on the device. I made a backup of the abl_a partition but not of any other partitions.
Now the device gets stuck on the LG V50 boot screen and I can't get it to boot into any mode other than EFL.
One way I feel might work is by obtaining a backup of the MPT file, if this is correct does anyone know where I can find this,
Does anyone know whether this is something I can fix or if the phone is dead, any help is appreciated.
Thanks.
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
Thank you man, this is reassuring to hear, I'm going to look for a QFIL dump now, will update this post if I find any success.
T
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
doublespicc said:
T
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
Click to expand...
Click to collapse
Glad I could help!
Tell me, in the dump that is uploaded there are files rawprogram0.xml, rawprogram1.xml, etc. How to flash them?