Greetings to all of you. I hope you be very patient with my poor english (I write and speak spanish) and this long post (please, read all of this) and please help me with this question, my first question here.
I am a XDA user a time ago, 2 years or least; I have flashed the kernel or the ROM of a lot of Android devices (+10, tablets and phones) using your knowledge posted on this wonderful community and I talk about this to prove that I'm not a totally noob and I never had a problem like this before; sadly, this happens with my own phone: SGH-T959V.
The charging port stopped working as data transfer port and just worked as charging port, this occurred just 2 months ago; but it was not relevant for me because I did not use the function in a long time, I used to charge my phone when it requires energy and nothing else. But I read about a CyanogenMod update (unofficial) for my phone and decided try it. Then I download it, install it via CWM and it worked successfully; I had a beauty JB 4.2 running on my 3 years old phone. I noted that there was a trouble with the RAM size, the new CM ROM just recognizes 346 MB of the RAM and the last ROM (CM 9) could recognize the 512 MB. I looked for a post here which talked about my problem and I found it, they suggest to install another kernel and I proceeded to do it. It was the 3 am or close, I was tired and here comes the first big mistake: I download and install a wrong kernel, a kernel for the T959, not the T959V. I cannot remember the name of the wrong kernel (because I deleted it from my PC) but since I installed it, the phone is always on recovery mode and the title of menu is: “Devil touch recovery v6.0.1.9”.
I tried to install the last kernel which worked fine (hefe-kernel-v0.8.1) and I always get the following messages: (as with any other kernel or ROM)
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)
I formatted the SD card, put the kernel there and tried again to install it, but I have no success. I fixed permissions, tried to wipe data, wipe cache, but the same messages appeared. I look for a solution on some threads here and read about the cache format, they talk about ext3 and ext4 but I cannot find the way to reformat the phone with a kernel which has the right format to then, finally, install the right kernel for the phone. Well, at this point, I thought about all the mess up and then I conclude: Why the hell I don’t just recover the phone via download mode and Odin? If you remember, the charging port just worked for charging, not for data transfer or any other usb function; yep, I got it on that dawn: I was screwed.
Next morning, I carried the phone to the technical service (here in Cali, Colombia. It is not from Samsung) looking for a new charging port, the technician told me that he had the right repairing part; he said that was the same of the SGS3 (IFC700). I returned the next day for my phone and I found a major disaster: the “technician” did not apply properly the heat gun and all the electric conducting lines (the 7) were pasted at the pins of the old and damaged port.
I searched for another technician and thanks God could find one that gave me hope, although somewhat unreal, for my bad luck. He suggested me that if we could detect the origin of the electric conducting lines on the mainboard (unit U701, specifically) we could make a bridge between them and the pins of the new charging port; the problem is that I surf and surf through all internet and found only this pdf: On bit ly :/1dS7M61 (I cannot post links yet.)
But here, they do not give information about the PCB and the specific connections for pins, so, here comes my first question:
Do you know the specific origin of the seven electric conducting lines of the charging port? And, if you do, do you know if possible make a bridge with them?
In case this does not work, do you know how to recover the phone to the original kernel and ROM (as Odin does) but without using the usb cable, just the SD card?
I will stay watchful. Thank you for your time, your patience and your help.
Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.
TwitchyEye said:
Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.
Click to expand...
Click to collapse
Thanks for the fast answer! I will show this to the techinician and I hope that he can repair it; although I really think it is almost impossible, the lines are all deeply ripped, just the third and fifth line survived the attack.
Again, I want to answer just one more time about fixing the problem of installing kernels or ROMs via recovery mode (please read again the first post): "E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)"
Do you know how to fix this? Or install a stock kernel without those problems?
Thank you!
PD: I will post the answer of the technician to this.
Yeah the kernel you flashed screwed up your phone and the only way to recover is through heimdall or Odin which you'll need usb for.
Thank you again for your attention. Unfortunately the technician could not find the download mode pin, so it's official: my phone is a paperweight. I thank you again for your help and interest, have a good weekend.
First of all, fo ur problem, I believe that the only way u can save ur phone is using heimdall to flash another mtd kernel (if u can luckily boot into download mode) but sad that ur usb port was doom (correct me if I am wrong).
In addition, why on new kernel the phone just shows 384MB of RAM? Just fyi, new aries kernels changed the way counting RAM as they don't count the reserved RAM that the init system took but just the remain. As if u look into the kernel, there is somewhere says that RAM = total subtract reserved (in a specific calculation not words). That's why u saw 384MB even in fact we have 512MB. N why it is 384 but not 400 or 450, idk lol. So if anyone is curious bout this can have this rep as an answer as well
Sent from my SGH-T959V using Tapatalk 2
You don't need the download pin if you can get into download mode by holding the volume buttons. If you need a usb jig to get into download mode then you're out of luck. Otherwise your phone will function normally except when you put it in a dock or try to use otg which as far as I know we don't have support for anyway.
Related
After I got my skyrocket, many of my friends and family also decided on the skyrocket Well, now it's up to me to make sure they're all in working order.
So one of my family members left her skyrocket in a bag of water for a while while she was at the beach, and it was completely unresponsive. I fully disassembled it (not my first time), dried out the majority of the water, then left the phone in rice for a few days. The good news is, the phone boots up and seems to work. The battery still works and it charges over USB.
The bad news is, the cellular radio does not work, IMEI comes up as unknown, bluetooth mac is "unavailable", front facing camera is also unresponsive. Really bad news: data/adb over usb does not register at all. A few more days in rice haven't helped.
The phone is completely stock. My first thought was that flashing a new radio might reset the cellular somehow, but not having cwm/odin makes that impossible. I can't seem to get the phone into download mode either because of the USB problem.
One thing that DOES work is the stock recovery. I can tell it to flash the official ATT ICS build, which contains a radio!
However when I try flashing it says.. "E: Short write of /tmp/sideload/package.zip (No space left on device) Installation aborted". Other zips "failed to verify whole-file signature"
Any ideas? My next step will be buying a used skyrocket with a cracked screen, and transplanting the working screen from this unit...
Tom
First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.
T.J. Bender said:
First off, please use the Q&A section for, you know, questions and answers. Don't create a new thread; I'm going to ask the mods to move this one instead.
Second, your issue is that the hardware radio is dead. The stock ROM only has a software radio included. To put it a different way, the stock ROM includes programming that tells the cell radio what to do. It can't fix the cell radio if it's broken, though. Unfortunately, based on the amount of damage you've got there, I'd say your phone is pretty much toast.
If you're completely stock, try to warranty it out. Just be up front with Sammy about what happened (because, in this instance, they will figure it out if you make up a story or play dumb), and the worst thing they can say is no. You might get a sympathetic rep who'll help you out. If they won't take it, you've already got your backup plan in the working SR.
Click to expand...
Click to collapse
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom
dutchthomas said:
Meant to post this in Q&A, woops. Too many xda tabs open trying to figure this out. Sorry about that
I do know the difference between the hardware/software radios... My thought was that while the phone was turned on and submerged, the software radio could have become corrupt... A long shot perhaps
I'll try contacting samsung, but somehow I doubt they'll cover it. Sidenote, do you really think they have a more sophisticated way to check for water damage than the internal water-damage indicator sticker?
The question still stands though, if anyone is interested. Even without a cell radio, I'd like to be able to root it for other purposes
Thanks for the advice
Tom
Click to expand...
Click to collapse
Yeah, based on the amount of things going wrong, it's hardware. If the software radio was corrupt, it would be because the internal storage had been corrupted, and your phone likely would not boot.
And yes, they can find water damage beyond the sticker. They can see corrosion plain as day when they open it up and look at the internals.
You can root it without USB working. Is your wifi working? If so, download GooManager off the market, then follow the instructions in the TWRP thread to get TWRP on your phone. Download a custom ROM to your PC, then transfer it to your external SD using an adapter/card reader so you can place it on the card directly (instead of going through the USB port). Use TWRP to flash the pre-rooted ROM onto your phone and viola. Unless there's a pre-rooted stock out there (and I don't think there is for SR), a custom ROM is the only way I can think of to do it.
Be advised, though, that because of the amount of damage done to your phone's internals, there's a better-than-normal chance that something won't work and you'll brick. I'm not responsible for your decisions or for the brick if that happens.
Long story short, just get a replacement SR.
Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.
hechoen said:
Same thing happened to my girls Atrix. She gave it a nice bath in Green Tea. After shutting it down and pulling it apart I gave it the rice treatment for 48 hours. Booted but returned a radio error. Her USB port was working so I was able to root it and install a few custom ROMs on it. No change. So I would bet you actually fried the chip. Call Sammi and get a quote to cover the repair which will be a new mobo. They pay shipping both ways and are usually pretty cheap.
Click to expand...
Click to collapse
Heh, this is my mother's phone actually. First she ripped the screen ribbon cable on a nokia E75. Then she smashed her Atrix's screen, tried to fix it herself with a new screen, and managed to rip part of a ribbon cable... so it no longer has a working touch digitizer. Now she left her skyrocket in a bag of water. The girlfriend managed to crack her skyrocket's screen, which I replaced... I've also had to fix 2x nokia N95's, an N97, and a bunch of water damaged dumb phones over the years...
FWIW, the skyrocket seems to have the best repairability / internal layout of any of the phones I've messed with
The cracked screen skyrockets on ebay seem to be going for more than I thought, so I'll be giving sammy a call for sure
Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730
OK, will do. Thanks!
try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
HELLO,
i would like to try to replace the nand chip of my bricked tv box with a new chip
this because the original chip has been damaged shortening two pins trying to put the device in mask rom mode
my device is t-r42 based on rk3188
the price of the nand flash is about $4,
i can found it on some chinese online store
i hope that replacing the nand, my device will go to mask rom mode, enabling me to do the firmware loading through pc (rkbatchtool)
i know that this mode has been designed specifically to load the firmware the first time,
so i hope my device will go to this mode the first time i power on it after replacing it
any suggestion?
any hint?
i know this must be done with :microscopic` attention
thanks!!
Vicolodo said:
HELLO,
i would like to try to replace the nand chip of my bricked tv box with a new chip
this because the original chip has been damaged shortening two pins trying to put the device in mask rom mode
my device is t-r42 based on rk3188
the price of the nand flash is about $4,
i can found it on some chinese online store
i hope that replacing the nand, my device will go to mask rom mode, enabling me to do the firmware loading through pc (rkbatchtool)
i know that this mode has been designed specifically to load the firmware the first time,
so i hope my device will go to this mode the first time i power on it after replacing it
any suggestion?
any hint?
i know this must be done with :microscopic` attention
thanks!!
Click to expand...
Click to collapse
your going to have to find someone with a hot air rework station to unmount and or remount a new chip. the thing of it is, the pcb has to have perfect traces,,, 0 damage. even if that is met, unmounting and remounting a new chip in a perfect world takes a lot of skill and experience. will it get you into mask rom mode,,, I would guess yes. far as I understand it, thats a hardware thing not a os thing (os=firmware). Unless its something you just want to tinker with just to see if you can do it I wouldnt bother. Thats just me. I have crashed units over and over and got into mask rom mode doing the pin short, purposely trying different firmwares to see if they would work. I am not sure if mask rom mode will happen with out the pin short on a blank chip. maybe thats another question.
if you find someone local that does rework on surface chips, best bet would be ask them. Also a better answer here at least for me would be a close up picture of the chip you speak of, it would probly tell a thousand words. I have done rework, not in the past 5 years but I have. it takes a extremely steady hand and a good feel for when the solder is fluid. Theres tricks to it, do it wrong and theres no fixing the torn traces. Maybe craiglist would point you to someone who does this sort of work in your area. Possibly a local flat screen tv repair center may be able to direct you to someone local also, they are packed with sm chips.
Just some thoughts
stinkster said:
your going to have to find someone with a hot air rework station to unmount and or remount a new chip. the thing of it is, the pcb has to have perfect traces,,, 0 damage. even if that is met, unmounting and remounting a new chip in a perfect world takes a lot of skill and experience. will it get you into mask rom mode,,, I would guess yes. far as I understand it, thats a hardware thing not a os thing (os=firmware). Unless its something you just want to tinker with just to see if you can do it I wouldnt bother. Thats just me. I have crashed units over and over and got into mask rom mode doing the pin short, purposely trying different firmwares to see if they would work. I am not sure if mask rom mode will happen with out the pin short on a blank chip. maybe thats another question.
if you find someone local that does rework on surface chips, best bet would be ask them. Also a better answer here at least for me would be a close up picture of the chip you speak of, it would probly tell a thousand words. I have done rework, not in the past 5 years but I have. it takes a extremely steady hand and a good feel for when the solder is fluid. Theres tricks to it, do it wrong and theres no fixing the torn traces. Maybe craiglist would point you to someone who does this sort of work in your area. Possibly a local flat screen tv repair center may be able to direct you to someone local also, they are packed with sm chips.
Just some thoughts
Click to expand...
Click to collapse
thank you very much,
i will let you know!!
Vicolodo said:
thank you very much,
i will let you know!!
Click to expand...
Click to collapse
A quick alternative for establishing that it is only a faulty NAND is to try booting Linux from an SD card. If that works, then you could look around for someone who has created running Android from SD card for your device and you could at least still use your device in the interim.
HI
My wife's phone (i9300 galaxy S3) has gone wrong and it went off without battery.
I found a new battery, but it lasted only one day. I thus decided to take it for repair,
as I think that this is the charge connector that is broken, but actually, the tech told me that it was probably the motherboard,
as when it used a tool to plug it to the direct charge ports on the side, the phone only bootlooped.
Thing is:
My wife's phone wasn't using cloud or external SD,
it was not rooted.
I tried some android toolkits to connect it, but odin or adb don't detect it, so I have no chance to try and put some new kernel on it.
It has no recovery mode, and when in download mode (1st screen), it actually doesn't last long before it reboots anyway.
Choosing some option will also make it reboot.
So I think it is failed beyond software repair.
But if you have suggestion for this (the tech was at a small street stall and I don't expect him to be high level, no offense, but he seemed to only perform two repairs, screen and charge flex boards, so not much more able than me if he can't go beyond this), feel free?
So my second question is :
Does anyone know how to retrieve the internal storage of the phone without breaking it, and reinstall it in a working way on a new motherboard?
Or alternatively, on an emmc reader such as those used for raspberry cards and so on? (I don't want to put some link, I don't want my message to be filtered)
The photos on this chip are priceless for us, and I would even pay professional to retrieve these (I would prefer not having to, because money doesn't exactly come cheap to me, but I guess I won't be able to make it alone.
So if you know some repair service in Europe that would be able to perform such task, I would be grateful for your sharing of such knowledge.
I saw an alternative in malaysia, but it feels a little too far for being able to do something in case of problem.
Thanks for your attention and time.
UPDATE 24.11.20
I have recovered my HU by reading the whole night on this forum and TO THE AMAZING work of several people here.. especially GREAT GREAT thanks to marchnz and to scorillo_ro I build myself the USB cable and followed all the instructions I could find. With some moments of headache .. finally I flashed a new ROM and it booted up!!!
I have to go down on my knees to you guys for the super AMAZING work you have done. Wihtout you I woulld be now 180€ poorer. (new HU).
___________________________
When booting I get this errors...
I got a MTCE_LM PX5 unit (8Core A53 CPU 2GB RAM)
It is always very difficult to enter Recovery so I tried several times but it doesnt work. Either I just didnt mage it right or the recovery is broken.
In the pictures you can see 2 different messages. I have the feeling the long message version is when it normally tries to boot into the OS but fails.
The short message looks like when I managed to get into recovery reboot but it fails too.
Or its the same message .. it just blinks up for 10ms or something and dissapears and then blinks back after 5 secods ... I had to take like 20 photos to catch it. So maybe its the same actually.
Anyone has a clue what I can do from now on?
Great to hear another success story.
It took alot of effort to develop the method, for which was made possible by a member posting the schematic diagram to the forums for the benefit of all. Your post helps other too, so thanks!
Thanks again for the endless hours you put into developing the esiest method possible (for this SOM).
I am REALLY pissed at the Chinese somehow. They develop great stuff sometimes but fail to think over the edge. It is so easy to destroy your OS by small or stupid mistakes. And then there is no OTG to easily reflash the rom. I mean the hardware supports it. They could (and luckily and finally some new models support OTG on at least one USB port right away). But why was this not implemented right from the first designs for the headunits is puzzling me.
I would love to help anyone who needs help. But I have the PX5 HCT V4 SOM so you people wrote exactly how to do it for this specific SOM... I am not sure I can add anything of what wasnt said already.
I just had 2 main issues. The USB cable was found but not recognized at first.
So what I figured out was that you should not use more than 2 resistors to make the voltage division (thats what I did first) and I just had 2.8V on the division. I did it fast and not clean, means. No really good soldering connections.
Then I rebuild the whole thing used a good cable just 2 resistors (2kOhm and 3.3kOhm) and I soldered everything as clean and as compact as possible with least distanced to each part. So it gave me 3.1V on the division.
This was recognized immediately. Ahh.. and it helps too if you can use some contact spray for electronic parts. Because the pins sometimes do not sit well inside the SOM board.
Then the flashing of the ROM didnt want to work. It gave me an error on downloading the firmware.
Solution was to simply erease the flash memory.
But everyone who goes to your thread and reads at least the first 20 pages gets rather the clue on the minor issues. But its actually all written in there... just need to read it