SDIN5C2-8g is nand chip in our motherboard while SDIN5C2-16g is nand chip located in Xperia P.
Anyone thought about changing them?
XperianPro said:
SDIN5C2-8g is nand chip in our motherboard while SDIN5C2-16g is nand chip located in Xperia P.
Anyone thought about changing them?
Click to expand...
Click to collapse
If you could find a way to address partitioning and such, then that'd work perfectly.
Regarding the other thread about booting a kernel whilst inside the Xperia U system, could we port things suck as LK Bootloader?
I recall it was recently ported to the Xperia T.
About boot loader its completely unprotected which means it could be changed without any problems.
Also it looks there's no RAM protection or its very low.
Any low level hacking should be easy but hard because lack of sources.
XperianPro said:
About boot loader its completely unprotected which means it could be changed without any problems.
Also it looks there's no RAM protection or its very low.
Any low level hacking should be easy but hard because lack of sources.
Click to expand...
Click to collapse
Care to work together? I'm in exam period so it's hard to find the time at the moment, but two minds are better than one. Would you care to send me your current research? If any that I'm unaware of
Cheers :highfive:
Toby Benington Ingram said:
Care to work together? I'm in exam period so it's hard to find the time at the moment, but two minds are better than one. Would you care to send me your current research? If any that I'm unaware of
Cheers :highfive:
Click to expand...
Click to collapse
I will send you most things I know this evening.
XperianPro said:
I will send you most things I know this evening.
Click to expand...
Click to collapse
Thank you, I hope to see it working some day soon.
Also there is 32G one. If you succeed, it will be awesome
Sent from my LT22i using Tapatalk 2
eMMC, Sd card and usb OTG
This subject is already being discussed here http://forum.xda-developers.com/showthread.php?t=1904697 for sometime now, care to read what we have discovered and join to our "research team"?
Related
i was just reading the topics about the 0% issue, when my brain suddenly thought of an idea. a lot of people have tried to find out what's the source of this issue. but, unfortunately, all we actually know is that it happens when the phone is being downgraded from 2.3.4 to 2.3.2. there has been a countless number of logcat outputs, and whatnot, but nobody has really figured out the root of the issue.
so, what my brain thought about is - have someone with this problem actually looked at what's happening in the bootloader? not the kernel, not the ROM, not the hardware, but bootloader? maybe there's the problem?
i'm not too educated about Android bootloaders, i don't know if that can even happen, and i don't know if the bootloader is user-accessible to rummage through it to look for something, it's just what i thought about. kind of a noob idea actually
hm... i guess nobody really cares?
shadow of a soul said:
hm... i guess nobody really cares?
Click to expand...
Click to collapse
xda found no cure to your problem , try to give it back to sony to get it fixed !
only patch to fake battery gauge report.
Hardware problem.
skyboyextreme said:
xda found no cure to your problem , try to give it back to sony to get it fixed !
Click to expand...
Click to collapse
i don't have the problem, it's just an idea i thought about.
electrash said:
only patch to fake battery gauge report.
Hardware problem.
Click to expand...
Click to collapse
but don't you all think it's too weird to get a hardware problem this way?
shadow of a soul said:
but don't you all think it's too weird to get a hardware problem this way?
Click to expand...
Click to collapse
Thatswhy rooting is not offical
Sent from my MT15i using Tapatalk
Sorry to disappoint,but that "idea" of yours is thought of looong ago...
And I can't see what's weird about software damaging hardware?
If you upload bad software onto a chip and now it doesn't communicate with other hardware components the way the main software expects, that chip is pretty much dead.
problem 0% battery xperia neo (help,,,please??)
Hey Guy's
i have a big problem on My Xperia Neo MT15i prototype Version
when i downgard 2.3.4 to 2.3.2 with GingerBreak i have Now my phone in case of death because battery 0% .
I tried very hard, all means but without the usefulness
I want a solution that can bring him back to life and if at 10%, is now employed only on charge i have posted a video on Youtube if you want to see here http://www.youtube.com/watch?v=Wxpydg1LbdM
http://www.youtube.com/watch?v=smHtIzLRZEU
I wish you luck and thank you in advance
So, because of this sh*it,
my Prime is unusable. It just sits there. I wondered, if I could customize its hardware. Replace its mainboard and etc. So that I can reuse it and use the OS that I want without dealing ASUS' non-sense. Because it is unlocked it is out of warranty. And I do not want to spend 250 eur/usd (I read somewhere that they chage so much for a new mainboard) and again have the same problems.
I just wonder, if it is possible to find fitting mainboards, hdd's and/or cpu's? Probably they are all customized for the product, but may be there is a way?
thanks
eec_
eec_ said:
So, because of this sh*it,
my Prime is unusable. It just sits there. I wondered, if I could customize its hardware. Replace its mainboard and etc. So that I can reuse it and use the OS that I want without dealing ASUS' non-sense. Because it is unlocked it is out of warranty. And I do not want to spend 250 eur/usd (I read somewhere that they chage so much for a new mainboard) and again have the same problems.
I just wonder, if it is possible to find fitting mainboards, hdd's and/or cpu's? Probably they are all customized for the product, but may be there is a way?
thanks
eec_
Click to expand...
Click to collapse
You can find mainboards online but I doubt you'll be able to solder a Tegra 3 CPU.
Also, the Prime doesn't have a HDD. It has NAND flash.
no. you can only replace the motherboard with a working one
When you say "unusable" do you mean it won't turn on? It turns on but won't boot? Or just poor performance? If it's that latter then root and/or unlock and either do a custom ROM or do the stock ROM tweaks in the stock ROM performance thread. I can tell you the stock ROM tweaks work wonders. Right now I'm updating about 10 apps and surfing the net with no lag what-so-ever.
he means he didn't read the instructions and messed up the bootloader
Glebun said:
he means he didn't read the instructions and messed up the bootloader
Click to expand...
Click to collapse
I see, I didn't realize the word sh*it was a link.
Glebun said:
he means he didn't read the instructions and messed up the bootloader
Click to expand...
Click to collapse
I don't know what I missed, since I had jb bootloader already, I couldn't install NVflash and without NVflash I cannot overcome this problem.
And, I didn't understand what you meant with "working" since I wanted to replace the older mainboard with a working one. Did you mean with a board that only works for that case?
thx
I mean that your motherboard is useless. You can replace it with a working one. And only one kind oа motherboard is suitable - the exact one that you have
Glebun said:
I mean that your motherboard is useless. You can replace it with a working one. And only one kind oа motherboard is suitable - the exact one that you have
Click to expand...
Click to collapse
OK thanks
eec_ said:
OK thanks
Click to expand...
Click to collapse
hit it
Just solder in a Core i7 Extreme Edition, then solder in 16gb of RAM, solder in a 256gb msata SSD and you'll basically have yourself a new Asus Transformer Book running full Windows 8 (though you'll have to solder in Windows 8 too). One thing's for sure, you'll have some 1337 soldering skillz after all that. I'd solder in some G's too (4 to be exact) but that's just me (some people don't like the extra bill).
Ill give you Eur 100 for your device
Verstuurd van mijn Desire HD met Tapatalk
Re use the led...get a win 8 netbook and pit the hhardware inside.....bam.....magic full win8
Sent from my LG-E970 using Tapatalk 2
My Xperia P detects a USB connection fine, but doesn't detect the disconnection. For example the charging light continues to glow after unplugging. Only way to reset it is to turn it off and remove the internal battery connector.
Are there any HW experts here? I'm quite good with a soldering iron if some component is broken. It's a really annoying error.
thanks / erak
Stock firmware? What version?
ChikeD said:
Stock firmware? What version?
Click to expand...
Click to collapse
Sorry, I forgot to mention it. Because the error remains regardless of firmware. Bootloader locked and never tried custom firmware. Right now on 6.1.B.0.544
erak said:
Sorry, I forgot to mention it. Because the error remains regardless of firmware. Bootloader locked and never tried custom firmware. Right now on 6.1.B.0.544
Click to expand...
Click to collapse
Never mind custom ROMs, have you tried .54 or .75?
Could be HW problem.
ChikeD said:
have you tried .54 or .75?
Click to expand...
Click to collapse
Yes
erak said:
My Xperia P detects a USB connection fine, but doesn't detect the disconnection. For example the charging light continues to glow after unplugging. Only way to reset it is to turn it off and remove the internal battery connector.
Are there any HW experts here? I'm quite good with a soldering iron if some component is broken. It's a really annoying error.
thanks / erak
Click to expand...
Click to collapse
You did not root or anything? If you did not, send it for service
AndroidNoob69 said:
You did not root or anything?
Click to expand...
Click to collapse
Rooting doesn't cause this
AndroidNoob69 said:
send it for service
Click to expand...
Click to collapse
Out of warranty
erak said:
Rooting doesn't cause this
Out of warranty
Click to expand...
Click to collapse
I am not saying rooting caused it, just that if you root you lose your warranty unless you unroot. Since you are out of warranty, i think you need to pay as xda does not fix hardware problems
Sent from a JB Moonbreaker 3.5 device
AndroidNoob69 said:
you lose your warranty unless you unroot.
Click to expand...
Click to collapse
Precisely
AndroidNoob69 said:
Since you are out of warranty, i think you need to pay as xda does not fix hardware problems
Click to expand...
Click to collapse
XDA can of course not fix anything by itself, it's a forum. Hardware engineers lurk here also, and it was them I was asking for help. But thanks for your time
Where are you gonna get the parts
Sent from a JB Moonbreaker 3.5 device
AndroidNoob69 said:
Where are you gonna get the parts
Click to expand...
Click to collapse
The hardest part is to find the source of the error, could just be a broken trace. I thought someone might be able to point me to the correct location on the pcb.
In Europe you can buy standard components from for example farnell or elfa. If it's more product specific, ebay is an option, or a spare broken phone.
It's a hobby and I've fixed both big and small electronics, for example iPhone fpc:s. But tiny smd components can be hard, if not impossible without the correct tools.
If you don't have anything constructive to say regarding this thread I propose that you send me a pm instead. BTW, your signature is huge.
THIS TUTORIAL IS ONLY FOR HARD BRICKED DEVICES.
HARD BRICK MEANS NO FLASHMODE AND NO FASTBOOT.
IN ORDER TO PROCEED DISASSEMBLY OF YOUR DEVICE IS REQUIRED.
IF YOU HAVE WARRANTY,STOP READING THIS, GO THE SONY SERVICE AND PLAY STUPID.
AS AFTER OPENING YOUR DEVICE, YOUR WARRANTY IS 100% VOID.
I AM NOT RESPONSIBLE FOR ANY DAMAGE.
YOU'VE BEEN WARNED.
Let's get started.
1. Download tools.7z from attachments and pack for your device.
2. Install ggsetup-3.0.0.7.exe
3. Open the back cover of your device.
4. Find the test point (See attachments).
5. Disconnect a battery, connect a usb cable. LED RED will start to blink.
6. Using the paper clip connect your test point with the GND. I used the metal shield in the middle of the motherboard.
7. Open the device manager, you should see SEMC Flash Device. If no, you did something wrong.
8. Disconnect your phone from computer.
9, Repeat the step 5.
10.Run the s1tool and select S1 MSM8974 EMERGENCY for the phone type.
11. Press the flash button, and choice the APP file for your device.
12. Press testpoint ready and repeat the step 6.
13. Remove the testpoint and press READY, when program will ask you to do so.
14. If flash was successful, you may disconnect your phone from usb, connect your battery and try to boot.You may have to charge your battery.
15. Now you can flash your device normally using software.
P.S.
I was not be able to flash on windows 8 64bit, but I flashed without problems on XP.
I would like to thank:
the_laser for making the software.
myevilface from support.setool.net for finding testpoint for c69xx.
and my poor Z Ultra which I sacrificed trying to find the test point
Actually I finished him when I wanted to fix audio jack.
Was to happy that my device is fixed and damaged the screen connector
UPDATE:
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET
------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.
Maybe stupid question : Do you think with this testpoint mode there is a way of unlocking Bootlader although it is not permitted by the provider?
Sent from my C6903 using XDA Premium 4 mobile app
Mighty_X said:
Maybe stupid question : Do you think with this testpoint mode there is a way of unlocking Bootlader although it is not permitted by the provider?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is option to unlock boot, and it asks to do the testpoint trick, but I did not test it,as mine bootloader is unlocked and screen is dead now.
I really hope i never have to do this Thanks for the guide!
LordManhattan said:
I really hope i never have to do this Thanks for the guide!
Click to expand...
Click to collapse
+1
@the_laser, there are some poor souls on the Xperia Z who have the same problem by flashing a Sammy recovery to their Z which destroyed their bootloader as well...
They still seem to have some life in their mobile reporting it as a qcom device to windows (reconnecting over and over again), if I send some or one of them over to you by pm, would you be able to help them too?
This is REALLY AWESOME. :highfive:
Call me crazy, but I'm actually a bit excited to see somebody post that they totally recovered their phone to a 100% working state :victory:
And brought to us by 2 guys that aren't even "senior members" yet LOL
[NUT] said:
+1
@the_laser, there are some poor souls on the Xperia Z who have the same problem by flashing a Sammy recovery to their Z which destroyed their bootloader as well...
They still seem to have some life in their mobile reporting it as a qcom device to windows (reconnecting over and over again), if I send some or one of them over to you by pm, would you be able to help them too?
Click to expand...
Click to collapse
I'd imagine that if the the software is compatible, the only challenge is to find the test point?
zeppelinrox said:
This is REALLY AWESOME. :highfive:
Call me crazy, but I'm actually a bit excited to see somebody post that they totally recovered their phone to a 100% working state :victory:
And brought to us by 2 guys that aren't even "senior members" yet LOL
I'd imagine that if the the software is compatible, the only challenge is to find the test point?
Click to expand...
Click to collapse
Right after I brick my phone, I knew that it will be fixed without motherboard replacement.
And I was exited too, when it was recovered. Too exited. Now need a new motherboard for sure.
Perhaps you should add to the guide...
"Have a steady hand and... KEEP CALM"
zeppelinrox said:
Perhaps you should add to the guide...
"Have a steady hand and... KEEP CALM"
Click to expand...
Click to collapse
Michael J Fox is going to have a hard time.
(I'm going to hell for this one )
Sent from my C6833 using Tapatalk
LordManhattan said:
Michael J Fox is going to have a hard time.
(I'm going to hell for this one )
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
For that one, I had assumed that you were hell bound well before that post
@vovanx500 thanks for the hard work and the Guide, I hope I never need it.
blueether said:
For that one, I had assumed that you were hell bound well before that post
@vovanx500 thanks for the hard work and the Guide, I hope I never need it.
Click to expand...
Click to collapse
Hopefully there is a same guide for Z too..
Btw good job!!
I see bootloader files for XZU 6802 and 6806. Would either work for the 6833 international LTE variant ?
I am very interested in trying this - my bricked XZU is already disassembled and I would love to wake it up. And thank you for putting all of this together !
edit: just checked C6802.7z and C6806.7z and they contain an identical file - so guessing C6833 will be the same.
Woot woot!!! I love you guys! I should have checked xda before i left for work.
Guess I need to find windows XP PC as I'm running Win 8 64.
Pure Awesomeness.
Thank you for your hard work guys
Sent from my C6903 using Tapatalk
i'm so glad & thanksfull. it works for me on z1 c6903 hard bricked after update to 4.3
asphalt30000 said:
i'm so glad & thanksfull. it works for me on z1 c6903 hard bricked after update to 4.3
Click to expand...
Click to collapse
So its 100% functonal, right?
If so, you're probably the first on the planet to bring it all the way back from the grave :good:
btw did you see post 3 regarding the bootloader?
zeppelinrox said:
So its 100% functonal, right?
If so, you're probably the first on the planet to bring it all the way back from the grave :good:
btw did you see post 3 regarding the bootloader?
Click to expand...
Click to collapse
yesssss iam verry happy thank you my friends I have already made this method successfully the phone Z1 START as normally it is a really good thank you successful continuation
zeppelinrox said:
So its 100% functonal, right?
If so, you're probably the first on the planet to bring it all the way back from the grave :good:
btw did you see post 3 regarding the bootloader?
Click to expand...
Click to collapse
absolutely yes. My phone works good. Even without any flash. In 4.3 version. Thank you guys . I love you so much . All of them.
I know in my country( iran) anybody couldn't fix this problem .
yesssss iam verry happy thank you my friends I have already made this method successfully the phone Z1 START as normally it is a really good thank you successful continuation
Hi, folks.
I've got a hard bricked Asus C300. I accidentally flashed the wrong ROM. When I turn it on, I only get a power light, and none of the refresh key combos have worked.
I figure my best option to get this working again is to attempt to flash the NAND with the proper image for the device, but I cannot figure out where I would attach the BusPirate to do so, as there is no enumeration on the NAND chip.
What I can tell you is that it looks a bit like a chip on a stick of RAM... however, it has no solder 'leads' coming from it. There are 4 VERY small dots of solder on each side of the chip, though. They do not appear to be making contact with the NAND in any way. Attached is an image similar to what it looks like.
I've googled around quite a lot, but I can't seem to find any other way to get this repaired, or any documentation on flashing a Sandisk NAND. No one seems to have been stupid enough to have my issue before, which is a real shame!
If anyone has any suggestions or ideas on how to get this Chromebook up and running again, I'd be forever grateful!
You chromebook is died...
Sent from my GT-I9195 using XDA Free mobile app
AbsoZed said:
Hi, folks.
I've got a hard bricked Asus C300. I accidentally flashed the wrong ROM. When I turn it on, I only get a power light, and none of the refresh key combos have worked.
I figure my best option to get this working again is to attempt to flash the NAND with the proper image for the device, but I cannot figure out where I would attach the BusPirate to do so, as there is no enumeration on the NAND chip.
What I can tell you is that it looks a bit like a chip on a stick of RAM... however, it has no solder 'leads' coming from it. There are 4 VERY small dots of solder on each side of the chip, though. They do not appear to be making contact with the NAND in any way. Attached is an image similar to what it looks like.
I've googled around quite a lot, but I can't seem to find any other way to get this repaired, or any documentation on flashing a Sandisk NAND. No one seems to have been stupid enough to have my issue before, which is a real shame!
If anyone has any suggestions or ideas on how to get this Chromebook up and running again, I'd be forever grateful!
Click to expand...
Click to collapse
I'd suggest contacting JohnLewis by email or on his google plus. I was the one that was the original tester for the C300 BIOS builds so he may be of some help as he was going to buspirate my system if it bricked testing his stuff. Sorry to hear it turned out that way, but I can say after it was all done, it was worth the risk.
kdb424 said:
I'd suggest contacting JohnLewis by email or on his google plus. I was the one that was the original tester for the C300 BIOS builds so he may be of some help as he was going to buspirate my system if it bricked testing his stuff. Sorry to hear it turned out that way, but I can say after it was all done, it was worth the risk.
Click to expand...
Click to collapse
You were the original tester for his ASUS C300 BIOS builds?
Sent from my HTC One M9 using Tapatalk
---------- Post added at 11:31 PM ---------- Previous post was at 11:26 PM ----------
AbsoZed said:
Hi, folks.
I've got a hard bricked Asus C300. I accidentally flashed the wrong ROM. When I turn it on, I only get a power light, and none of the refresh key combos have worked.
I figure my best option to get this working again is to attempt to flash the NAND with the proper image for the device, but I cannot figure out where I would attach the BusPirate to do so, as there is no enumeration on the NAND chip.
What I can tell you is that it looks a bit like a chip on a stick of RAM... however, it has no solder 'leads' coming from it. There are 4 VERY small dots of solder on each side of the chip, though. They do not appear to be making contact with the NAND in any way. Attached is an image similar to what it looks like.
I've googled around quite a lot, but I can't seem to find any other way to get this repaired, or any documentation on flashing a Sandisk NAND. No one seems to have been stupid enough to have my issue before, which is a real shame!
If anyone has any suggestions or ideas on how to get this Chromebook up and running again, I'd be forever grateful!
Click to expand...
Click to collapse
OP, you're looking for a small-ish black square on the BOTTOM of the main board (yes it's a PITA) with 8 legs, 4 on each side
Sent from my HTC One M9 using Tapatalk
drsn0w said:
You were the original tester for his ASUS C300 BIOS builds?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=eKylYaWbb-E
That's from 2 years ago on the original build. I got a few pictures too if you want me to dig them up. It was a proud moment for me for some reason.
kdb424 said:
https://www.youtube.com/watch?v=eKylYaWbb-E
That's from 2 years ago on the original build. I got a few pictures too if you want me to dig them up. It was a proud moment for me for some reason.
Click to expand...
Click to collapse
Are we talking about the same 'book? I didn't even know it was out 2 years ago xD. My apologies, I also worked with John Lewis on the C300, wasn't aware there was work on it beforehand xD.
First of all messed with this https://github.com/drsn0w/chromebook_kernel_tools
Then with him to work on SeaBIOS, Liam Crabbe in the Google plus group.
Again, apologies, just startled me
Sent from my HTC One M9 using Tapatalk
drsn0w said:
Are we talking about the same 'book? I didn't even know it was out 2 years ago xD. My apologies, I also worked with John Lewis on the C300, wasn't aware there was work on it beforehand xD.
First of all messed with this https://github.com/drsn0w/chromebook_kernel_tools
Then with him to work on SeaBIOS, Liam Crabbe in the Google plus group.
Again, apologies, just startled me
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Nope, you are right. We aren't. They need to stop naming them so similar. You have the Asus C300, I have the Acer C300. Sorry for that. I won't be much help here.
kdb424 said:
Nope, you are right. We aren't. They need to stop naming them so similar. You have the Asus C300, I have the Acer C300. Sorry for that. I won't be much help here.
Click to expand...
Click to collapse
Oh jeez. XD well thank you for your work on Chromebooks too! Love seeing people circumventing le big Goog
Sent from my HTC One M9 using Tapatalk