Hi All,
So I have a spare I9305 that is soft bricked.
As far as I can tell, the PIT is corrupted, because in recovery mode i get 'unable to mount /data'
I have scanned /dev/block/mmcblk0 for bad blocks and there are none. The phone will 'boot' but freezes at the samsung boot animation.
I have a working i9305 and I tried extracting all of the partitions from that (and the PIT) and flashing them on, as well as flashing a stock rom but nothing seems to work.
when i try and flash the PIT from my working i9305 to this one, heimdall crashes (and odin refuses to do it too)
I don't really want to send it for repairs (as I have a working i9305)... so does anyone have any ideas to help me un-brick it?
tried heimdall on linux. it crashed too... this is what I get...
{
"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"
}
this is using heimdall 1.3.1
nevermind. I was able to fix it.
The PIT was not corrupt, the userdata partition was, i was able to hack a version of darkside superwipe for the SII LTE to recreate the partitions and then re-flash the rom.
After that i restored a nandroid backup from another S3 and it worked.
Adb ftmfw
Sent from my GT-I9305 using xda premium
mick.wheelz said:
nevermind. I was able to fix it.
The PIT was not corrupt, the userdata partition was, i was able to hack a version of darkside superwipe for the SII LTE to recreate the partitions and then re-flash the rom.
After that i restored a nandroid backup from another S3 and it worked.
Click to expand...
Click to collapse
Thread closed.
Related
Hi,
I have tested CyanogenMod 7 and MAD ROM on my I5500L [Brazil], and it's works. But, I want to downgrade my phone to original version [Android 2.1].
When I flash with the pack, the phone reboot and show "Samsung" on display forever.
I have test with the zOdin for Galaxy S, but don't work .
Have solution?
Thanks a lot
I faced the same problem.. downgrading 2.1 from cyanogen !
you can flash any froyo rom before downgrade to 2.1 directly
I got success..
Your problem is that the /data partition is still formatted to EXT4, but the stock ROMs can only recognise the Samsung RFS format.
Flash this file with Odin as a One Package (no other special options): http://www.multiupload.com/OW3LQG8PZB
That will flash an empty RFS data partition to the phone, which will fix your problem.
Thanks man! It's works perfectly.
I had flashed my galaxy 5 i5500 to CyanogenMod 7.1 (aka 2.3.5) but i need to downgrade it to 2.2 or 2.1.
I had been read some guide saying that need to flash the downgrade.tar file using odin. i already done it but my phone reboot automatically and repeating the welcome page(as shown)
{
"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"
}
i though i had done the step for downgrade.tar, then i flash it again with the 2.2 firmware, but i still stuck at the odin,as picture show:
So now what can i do?can some body help?please,it's urgentT.T
Hi guys, I have a Galaxy S3 (international model) which I'm having odin problems with. I was running 4.0.4 stock ROM with cfroot isntalled and I flashed it via odin just fine. Then 4.1.1 came along so I tried flashing it via odin but it was hanging for 10 minutes on the "get PIT for mapping". So I ended up flashing 4.1.1 BTU ROM via Kies and everything went fine. This of course removed my root permissions.
So I've tried to reflash cfroot back to the phone and I'm getting the same error message. I'm also getting the error while trying to flash any stock ROM. So how do I go about fixing this?
Things I've tried so far: using odin on a PC that's never had Kies; using a win XP PC; removing my SD card; performing a factory reset; reinstalling the usb driver; redownloading cfroot. I've tried everything I can think of. Is there anything else I can try?
Or is there a way to root my S3 without odin? I'll appreciate any help. I've done a lot of searching but I haven't found anything to help.
TL: DR I get the error message "get PIT for mapping..." from odin when trying to flash anything. What do?
If I were to try flashing a XXDLJ4 .pit file along with the ROM itself, would that fix it? If so, does anybody have that .pit file?
This is what my result is each time.
{
"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"
}
Hi there people ... i got an s3 this weekend which is not booting
( stuck at Gs3 logo)
{
"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"
}
... and i am trying to fix this and i have tried lots of stuff already believe me no luck yet.
Here is my situation
it already had a cwm on it which is 5.5.0.4... i tried updating it with philz touch but it stayed the same after reboot
This is download mode
I did a backup with this cwm and it managed to do a backup of the
boot.img
recovery.img
system.ext4.tar
but when doing the data, it stuck for a little while and rebooted without doing the data backup. same thing happens when i tried to wipe data. it basically would not read the data partition.
i open the system.ext4.tar and found out the previous version of android was I9300O2UELL2(jan2013), so i tried flashing same version on top via odin and odin says NAND write start and FAIL ...
Tried several pit files for gs3 16gb but repartitioning Failed all the time...
So how to proceed with this type problem ... is it the sds people talk about.. i have not tried the mmc boot repair yet because i want to know whats the problem first
Try rescue firmware, search general forum. Otherwise the emmc chip is corrupt/damaged.
Already did that
Hi mate i already tried that option .. i tried the 4.1.2 and 4.3 firmwares but it will not pass the NAND write .. it will say fail all the time
Hi, I tried to restore to stock but still is stuck on boot logo but I can very well go to recovery and download mode,but going to recovery throws errors,one of my friend says that emmc is gone, but I still have hopes, please help me out,I m attaching pics
{
"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"
}
Please help me out asap.
Thanks in advance
The pics are too small to see, but the last post I read about this type of problem was internal memory failing.
http://forum.xda-developers.com/note-2-verizon/help/sudden-death-syndrome-t3282788
So was it a standard boot, or did you do some modding first?
Full size pic, btw I was on root66 initially but one day i was
-->trying Adam Outler Jailbreak to unlock my bootloader and my phone was --> dead,after few months I tried to wake it,it started in download mode and also went in to recovery,I immediately Odin to stock out of happiness but alas nothing happened but this.
I tried to
-->ODIN Root66 stock VRALJB 4.1.1 12/2/12- ,voila,it
-->FAILED and I switched on the phone it was stuck in boot,
-->then I ODIN Official VRALJB 4.1.1 but it
-->failed at sboot.bin
and then Finally I tried to
-->ODIN Official VRAMC3 4.1.2 5/5/1 and it
-->PASS but when I switched on nothing happened,it's stuck in this situation. Bootlooped.
Then I went to recovery to factory reset but saw this.No such file exists etc etc.
(
Please help.
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
I am thinking of trying this. Is that a good idea?
Good Idea, I would try and odin back to life as a last resort too.
Looks like the download links are all dead?
Might be able to find some files here. https://www.androidfilehost.com/?w=developers&did=77
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"
}