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.
Related
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.
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
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Feb. 18th, 2016 Edit:
Well I'm happy to announce that after nearly 5 months of trying different tactics I was finally able to get my handset up and running this weekend.
The technique I used was to first flash the new official Oxygen OS following the directions from the oneplus forums. From there I was able to boot-up for the first time in months, but had no connectivity. I went to settings and saw I had no IMEI showing. Realizing this, I tried using the technique Heisenberg suggested below in this thread, but again I had no success.
Then I tried the instructions in this thread (which I had tried previously with no success) http://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793 and viola! I got my radio back. It took me several attempts to get bluetooth and wifi back working, with rebooting in between, but alas I was able to get all fully functioning again.
Then I re-rooted and reinstalled TWRP (unofficial 3.0), backed up everything (including firmware and EFS partitions), then proceeded to flash the latest CM snapshot, then eventually the latest CM-12.1 unofficial CAF Sultanxda that I'm now happily running!!!
Thanks again to everyone who posted trying to help me get my handset working again. Now I have two fully functioning OPO's and am very happy!!!
Odysseus1962 said:
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
Click to expand...
Click to collapse
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Heisenberg said:
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Odysseus1962 said:
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Click to expand...
Click to collapse
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Heisenberg said:
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Click to expand...
Click to collapse
Thanks again for responding. I'm just at my wit's end with this and out of ideas, which is why I even suggested the hypothesis in my previous post. Fortunately, I have another OPO backup, so I still have a phone, but it too is problematic. Whenever the capacitive buttons are activated I experience phantom touches of the menu button, and usually at the most inopportune time. OPO customer service is nonexistent and have insisted since I received the defective device that my problems are firmware related and refuse to investigate further. Nearly a year later and numerous updates the problem is still unresolved, which is why I took the device out of service and made it my spare.
Now with my daily driver malfunctioning I'm nearly ready to throw in the towel and give up on Oneplus altogether and get another device from a more reputable manufacturer. They've sent me several OP2 invites, that I've declined using. My horrible customer service experience with them and now two faulty devices leads me to never want to purchase their products again, no matter how affordable or feature packed they may be.
Anyhow, as previously posted, if anyone has ideas to resolve my boot loop, please chime in. TIA
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Odysseus1962 said:
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Click to expand...
Click to collapse
A corrupt EFS partition doesn't cause this to happen, the phone will still boot but will have no network because it has no baseband and no IMEI.
Still trying to resovle. I refuse to give up!
I'm still looking for help in resolving this bootloop issue. I refuse to give up as long as there is the slightest hope of getting it back up and working.
Being a longtime Linux user I know that by default there must be some type of logs generated in the boot-up process. I'm thinking that perhaps if I can extract the log(s) and post them maybe someone can point me in the right direction towards resolving this issue. I've noticed that after flashing back the stock recovery there is a section which contains several logs. Which do I need, where do they reside, how can I extract them from my device, and how should I repost (them) here so they can be properly deciphered? TIA
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Sanjiv Kumar said:
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Click to expand...
Click to collapse
I thought about this as a possible solution, but the "hard unbricking guide" only contains solutions to use with various versions of Windows. Unfortunately, I have no access to a Windows computer (at least one that someone would allow me to use for the purpose of unbricking). I run Linux on my laptop and desktop, specifically Gentoo Linux ~AMD64. I haven't run Windows on any of my machines for over a decade. For the extremely rare instances where I need to use a Windows application I run it on WINE in Linux.
If someone knows how to run the ColorOS unbricking procedure on Linux, I'd be happy to try it out.
NoobInToto said:
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Click to expand...
Click to collapse
This device was already running TWRP-2.8.6 prior to getting stuck in the bootloop. Since then I've tried every version above 2.8.4, I've tried Phil's, and CWM and both the CyanogenOS and CM recoveries. All with the same result.
Bumb to bring back up this thread, now that I've resolved my problems. Hopefully it will help someone else who may be having similar issues.
Hi Guys,
I have GT-P3100 (Samsung Galaxy Tab2), I recently flashed Mokee ROM 4.4.4 (biggest mistake). The ROM (worked for 5-6 months) keeps restarting in every 10-15 seconds. I have tried to re-flash the ROM, but nothing is happening, I have also tried to flash the other ROMs but for most of the time I am getting this error "E: Error executing updater binary in zip 'location of the ROM file'", and even any ROM successfully installs nothing happens (the old Mokee ROM starts again on reboot, I mean come on).
I have TWRP and I tried to flash a new recovery i.e. CWM through Odin, after a successful flash TWRP starts again like the Mokee ROM.
I have also tried to flash the stock ROM fro Samsung through Odin but it fails in the middle, i have tried it multiple times. I have tried to wipe my entire phone memory, but the data and the installed ROM is still there even after a successful memory wipe
My phone keeps rebooting, I can't flash the same or any other ROM. I can't wipe my data, I can't install any other custom recovery. Nothing is happening.
The installed corrupted Mokee ROM is kind of a sticky ghost i can't get rid of. I would highly appreciate if you guys can help me out here.
If have some logs, please feel free to have a look if required. Since I am a new member I am not allowed to share a link and something is stopping to paste the logs here ( detecting a web link in the logs)
Please feel free to ask me for logs, I am always reachable at [email protected]
Thanks in advance .. I love my device.
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
putr4s said:
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
Click to expand...
Click to collapse
Thanks for your help. I think now I am in deep trouble in terms of phone. My device is rooted so the service center will not help me out. Perhaps I should figure out a way to do this by my own or find someone who can do this for me.
If I can have some more information, I may be able to fix this. Your information is good I am following the lead. Please share any info your think I should know, I am sure with help I will be able to find a way.
Thanks, keep rocking.
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
bindasboy said:
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
Click to expand...
Click to collapse
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Lightracer said:
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
[email protected] said:
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
Click to expand...
Click to collapse
Maybe you could try asking for a solution in the ROM's thread.
Sent from my espresso3g using XDA Labs
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
The problem was with the eMMC of p3100 and not the ROM.
The only fix is using jtag, replace eMMC or get new motherboard.
I agree with @bindasboy. The symptoms are exactly the same as the emmc brick bug.
Sent from my espresso3g using XDA Labs
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?