Here some questions:
Does anybody know the exact eMMc Layout of the phone? (not only partitions, but whole nand)
I found a partition overview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, nowhere is stated where i.e. PBL and SBL are. Or other low level firmware. In SGSII and Note, PBL and SBL are not mapped to any mmcblk device.
So how's it on Galaxy S3? Also, where is the download mode saved?
Just asking if wiping all mmcblk partitions would "brick" the device, or if the low level components are hidden (or even write-protected)
theq86 said:
Here some questions:
Does anybody know the exact eMMc Layout of the phone? (not only partitions, but whole nand)
I found a partition overview:
However, nowhere is stated where i.e. PBL and SBL are. Or other low level firmware. In SGSII and Note, PBL and SBL are not mapped to any mmcblk device.
So how's it on Galaxy S3? Also, where is the download mode saved?
Just asking if wiping all mmcblk partitions would "brick" the device, or if the low level components are hidden (or even write-protected)
Click to expand...
Click to collapse
Well, best bet is to ask chainfire, for help.
I have no idea, why anyone should want to delete whole parttions, without actually knowing where they are and what they're for.
I use chainfire's triangle away app, and that's that
Just ask chainfire for help, who knows, maybe he'll actually answer you!
[REF] GT-I9300 PIT and Flash Analysis [WIP]
http://forum.xda-developers.com/showthread.php?t=1742668
Related
Is there a definitive partition layout for the I777?
Here is what I have found/guessed based on the threads I've found in the forum:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Close, somewhere off in the weeds? Anyone have anything better?
There's a PIT dump somewhere in Development - or you can use Heimdall's dump-pit. You're pretty close, and you're correct about p5 and p6 - p5 is kernel, p6 is recovery (which doesn't actually do anything on nearly all Samsungs, including ours - recovery is in the kernel initramfs.)
p2 and p3 are bootloader stuff - touch them and your phone dies.
Thanks, I'll look at the PIT file, maybe I should look at the Heimdall source to see what it does with the PIT.
Not messing with the boot loaders is why I'm interested, I'm not a One-Click'er because I want to know what is going on when I change my phone.
I believe everything else you have is correct, other than that unidentified 512M partition is listed as "hidden" - I think it somehow allows the uninstallable AT&T bloatware to be reinstalled after a wipe, as it contains the uninstallable AT&T bloat apps.
Yep, kind of had to be by default. I was thinking that it probably contained the stock /data partition contents and possibly /sdcard as well but hadn't looked onto it yet.
on the ATT bloatware, I still have a gray icon for that POS featured apps
Thanks for taking the time to help!
Edit: mounted p12 on the phone, it's a ext4 fs with a single directory (app) that contains the AT&T bloatware. Guessing the e3 recovery copies from here after a format.
hello everybody.
Here is the story, a friend of mine tried to install a custom rom on its brand new galaxy s3 and messed all things up. He came to me and we installed back an original rom, but we got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for what I understand, he isn't able to make the modem work, and the camera maybe. He told me he have done "something" to the efs partition, so I thought he messed up that. But esf files are all there and it seems the phone still have a valid imei (353*********151).
We were unable to recover it so we restored everything, resetted the counter, and bring it to assistance for warranty. They told us that there is a crack in the main board and they have to change it
They also said that there is a problem with the screen and it has to be changed. But it seems fine to us!
They also told us that those operations are not covered by warranty, and we have to pay 270 euros!!
Now we are looking for an alternative solution. It sound strange to me that is a hardware problem, because it happened when my friend started to play with the OS. Any suggestion? anything we can try before changing the mainboard?
any help will be appreciated!!
this is factory mode, use search
Glebun said:
this is factory mode, use search
Click to expand...
Click to collapse
LOL
thank you!! I managed to fix it, saving 270 euros !!
XDA vs samsung assistance 3 - 0
I'm posting this here because i'm a complete noob on this forum and apparently can't post it to the actual thread without 10 points.
This is the thread i'm talking about http://forum.xda-developers.com/showthread.php?t=2500078
Anyway, after reading the whole thing i got my T100 to boot android-x86... YAY!
But i'm having problems with the graphics. The only difference i see between what i'm doing and the thread is that i have loaded the newer BIOS rev 220. I have two modes. If i boot into the bios by holding F2 on boot, this seems to lower the display resolution to 800x600. If i then boot to android i get something that looks like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On another note, if anyone from that thread finds this, i figured out how to boot to android with just one drive instead of two.
Short version is, make a second partition on your thumb drive about 300mb ext4. i used a gparted live image to shrink the existing partition and add this new ext4 partition. For me it was /dev/sde2
Next do the step you used to do on the second drive
dd if=android-x86.iso of=/dev/sde2 (be sure to use the correct partition in your case. parted -l should get you a list to guess from)
Thats it.
Thanks,
Eric
How are you going with this, any progress? I'm working on getting an all-working Ubuntu up and running.
Is the display being duplicated horizontally, but only if you boot via the BIOS boot menu?
Hi guys
Sorry of this is in the wrong place, i need to retrieve files of my s3, basically the phone is on a loop at the samsung logo, i have tried all the resets found on the forum to no success.
Is it possible to purchase a working s3 then remove the hdd from mine and transplant it into the new one?
Any help appreciated guys
Anyone?
Zu11y said:
Hi guys
Sorry of this is in the wrong place, i need to retrieve files of my s3, basically the phone is on a loop at the samsung logo, i have tried all the resets found on the forum to no success.
Is it possible to purchase a working s3 then remove the hdd from mine and transplant it into the new one?
Any help appreciated guys
Click to expand...
Click to collapse
Well I wish this was the case for you but it's not... If it was a PC it would be. But Android phones use like solid state chips called EMMC which stands for "Embedded Multi-Media Card" This chip is partitioned with the Phone's OS, Bootloader, Recovery, Internal Storage ((Where Your Documents Go)). And etc. So if you take that chip out and solder it to the other phone it would still be stuck in boot loop. You may need to consider Jtaging your device's flash memory if possible. Look up how to Jtag a hardbricked S3 and see what you can find. If that don't work than I don't know what to do to be honest. If this was helpful at all please hit the thanks button below. Wish you the best.
Here's a picture of the EMMC Chip for your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I am trying to return to stock for Miitomo/Android Pay to work on my G3-VS985 from CM13 nightlies with the last LP radios and boostack of 35B
Essentially what happens on all flashing methods is it fails to install the mtp drivers, and fails to connect regardless of OS bitness and version (Win10x64 and Win7x32 tested) and does not change the COM number on the phone's screen,
on one of the flashes it deleted the bootloader flash partition, and i re-flashed it in TWRP3, alongside all the 47A partitions except system and recovery, blaming possibly dead partitions of previous flashes, in hope to fix the flash mode
and here i am, stuck on just 47A flash mode which doesnt seem to respond enough to flash a KDZ or TOT
in the flash mode's status box it states "VUSER B60"
How likely am i to get this back up and running? and if so, how would i go about this?
THIS HAS BEEN FIXED, BAD CABLE
Glad you solved your problem! In the future, please put questions in the Q&A section. I'll notify a mod to move it.
You can also edit the title of your thread in the Advanced edit view, and put "SOLVED" in the title.
Edit: Also, are you sure your HD2 is dead? Or just resting? (Sorry, Monty Python reference)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}