I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
DiskDumper said:
I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
Click to expand...
Click to collapse
Recovering the data is a lost cause at this point.
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
zelendel said:
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
Click to expand...
Click to collapse
Well yeah, but as it had a stock rom and was probably not encrypted (Android 4.3) it might be possible the recover some files (I have done things like that in the past). Maybe the /data filesystem is okay and the partition table is just broken.
But without having the data at all I can't even try to recover the files.
Related
Hi,
after 24h of searching and try and error im writing this post. If i really missed some important informations, please be gentle
long story short:
was installing new kernel and theme via some kitchen app, and ended in a boot loop. would not be a big problem, if i could access the recovery menu, but i could not. i always tried also with pulled battery for some time before.
The only accessible "door" was the download / odin mode.
But Odin could not write the stock fw i wanted to install as "recovery"
Extracted the tar and installed via heimdall. worked. Now a kind of stock fw installed. FW was: GT-I9100_DBT_I9100XWKE2_I9100XXKDJ_I9100OXXKE2
Modem: XXKDJ
Phone: XWKE2
Well... If i remember correctly, i flashed in heimdall those files:
- cache.img
- hidden.img
- zImage
- facotryfs.img
- modem.bin
im not sure at those, but i know i flashed one or more of them also.
- Sbl.bin
- boot.bin
- param.lfs
so. heimdall did flash them, heureka i thought. but wrong. things would get worse.
NOW the situation looks like that:
- Download mode not longer working. lsusb under linux didtn show any output, windows recognizes it as "unknown device"
- stock recovery console is working and shows a few leftovers from my formerly working internal flash memory (the 12gb, u know?)
- stock fw cant access the internal flash mentioned above. nor will show it. android says: no sd card inserted.
- kies wont recognize the device in normal mode
- adb works in debug enabled mode.
- superoneclick wont work.
- installing any app wont work since there is no accessible flash/sdcard
im stuck, f*cked off, p*ssed on and really really tiered.
i dont know what to do now.
maybe someone has an idea or a sugestion i didnt mention or have forgotten?
any kind of logs i could provide?
with kind regards,
alteregon
i'm assuming you tried this: http://forum.xda-developers.com/showthread.php?t=1108499
if so, i don't have another idea to rescue your device...
Thank you for your reply,
since the phone is not recognized from the pc in download mode, odin nor heimdall see it.
So recovery through download mode is no option, right now.
Two choices one USB recovery jig to se if it will get to download mode .
Second service centre .
No warranty with hacked phones so i suggest saying it stopped during a Kies update .
jje
Sooo. Yesterday i set up a clean xp install to sort out pc-side problems.
- the phone is only recognized correctly in debug-mode.
- normal mode gets error 10 and is not useable i.e. for kies.
- odin mode gets recognized as unknown device.
tomorrow i will solder me a 301k jig. But i dont exoect much from it. since it can go to download mode, but wont be recogniced from the pc.
at least the custom binary counter will be reset i hope.
for today, i will try to do everything possible via adb in debug-mode. since the sys is kind of working, i have still hope
does someone know how to flash the phone via running android?
Hi Guys!
I have a problem with my P7510.
My tab is on a bootloop
Stock recovery and download mode work
BUT
Tab is not recognized by PC or Odin
Wiping cache and factory reset don't solve this :crying:
This happened after i installed A1 Kernel on Infamous Rom 4.0.4, looking for USB charging. After installing it, no matter what, the PC wouldn't recognize the tablet (no notifications of any kind. Couldn't even find the tab on device manager. tested it on 3 computers, installing and reinstalling drivers, and the same error kept happening), it just charges it's battery. Tried several Roms and Kernels, but the problem was still there
Trying to find a solution i considered installing a stock firmware from samsung, but without USB recognition from my computer, i couldn't use ODIN3 1.85, but i stumbled upon MOBILE ODIN, so i used it to flash a stock firmware, but after a succesfull flash, the tab went into a bootloop. Tried wiping cache and factory reset,on the STOCK RECOVERY (not CWM) and the tab kept bootlooping :crying:
So, to recover my Tab, i need ODIN, but i can't use ODIN since my PC (and therefore ODIN) doesn't recognize my tablet.
So here's when i ask you ¿What can i do to recover my tablet? ¿Should i send it to a technician?
Thanks in advance
Sebastian
Some aclarations:
-I use odin as administrator on windows 7 32 bit
-i don't have Kies on the background
-I instaled and reinstalled the tab drivers
-I looked for the tablet on device manager. I didn't find it.
-The PC doesn't respond at all when i plug the Tablet (no notifications or sound),
Maybe you can try using ADB while your tab is in the Recovery mode.
I accidentally wiped my /sdcard fs and used this method to push a custom rom in the /data/media fs.
Since your Recovery mode is working, you can try to flash a new rom.
ADB Still works on Stock Recovery? (not CWM or TWRP)
ayankm said:
Maybe you can try using ADB while your tab is in the Recovery mode.
I accidentally wiped my /sdcard fs and used this method to push a custom rom in the /data/media fs.
Since your Recovery mode is working, you can try to flash a new rom.
Click to expand...
Click to collapse
My recovery is the STOCK samsung recovery, not CWM are you sure ADB still works with it?
Thanks for your reply, anyways
Hello,
a few weeks ago i flashed cwm and cyanogenmod 10.2 nightly to my L9. I wanted to use Link2SD to move some apps from internal memory, so i had to repartition the sd-card. Unfortunaly the phone would not let me remove the sd-card (seems like it is stuck because the eject-mechanism is not working). So i tried to repartition the memory with Aparted from within the phone and of course i accidentally removed the phones internal partition, instead of the sd-card partition. Now the phone won't respond to almost anything i have tried. That includes:
- turning the phone on
- booting to recovery
- s/w upgrade mode
With Lelus tool i am able to get a fastboot connection, it even looks like i am able to flash another recovery image (i have the omap drivers still installed from flashing the phone the first time). But in the end the phone itself does not respond to anything. When trying to install ics x and u boot with Lelus script it fails after complaining about a missing partition.
Do you know another way to restore internal partition(s)? Is there any hope to get the phone working again?
Thank you in advance
if all fails try this you may get lucky
http://forum.xda-developers.com/showthread.php?t=2546571
tawhid111 said:
if all fails try this you may get lucky
http://forum.xda-developers.com/showthread.php?t=2546571
Click to expand...
Click to collapse
Thanks a lot! Looks like LG Support Tool recognizes my phone now (there is no visual feedback on the phone screen in S/W Upgrade right?) But when i start to use the tool to recover from a failed upgrade, it always skips around 20-25% progress. For a moment the phone is not shown in my windows device manager and after that, it is recognized as Ti Board - Omap44xx every few seconds and then lost again, like the driver is not properly installed (is that possible after being able to get to fastboot and S/W Upgrade mode?). Any idea?
kidCurly said:
Thanks a lot! Looks like LG Support Tool recognizes my phone now (there is no visual feedback on the phone screen in S/W Upgrade right?) But when i start to use the tool to recover from a failed upgrade, it always skips around 20-25% progress. For a moment the phone is not shown in my windows device manager and after that, it is recognized as Ti Board - Omap44xx every few seconds and then lost again, like the driver is not properly installed (is that possible after being able to get to fastboot and S/W Upgrade mode?). Any idea?
Click to expand...
Click to collapse
The s/w mode from the unofficial fastboot is not going to work. I think you really messed up your phone doing that (aparted). You might be able to run a fastboot command to repartition it but I doubt it will work. Try this command select option 1 (just fastboot)
fastboot devices
fastboot oem format
You should have a look at this information as well http://www.omappedia.com/wiki/Android_Fastboot
Sent from my LGMS769 using XDA Premium 4 mobile app
my phone just LOGO,, try update offline error 4%
then i try with fastboot:
fastboot devices
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash u-boot 2.img
fastboot flash boot 3.img
fastboot flash recovery 4.img
now phone is dead,, i se on device manager omap4430 fastboot usb device only connect then disconect continuesly...
please helpp,,, #cry
This should help you fix it: http://forum.xda-developers.com/showthread.php?t=2119090
It will give you fastboot access again so you can flash the correct files.
I love omap devices, they seem to be difficult to hard brick with the exception of the high security models.
Sent from my Amazon Tate using Tapatalk
I tried to install Conceptify ROM. When I was making a partition, I had mistake, instead of typing rm 29, i typed rm 3. Then I came back to recovery and power off telephone. At first time I was able to enter recovery, but then I wasnt. Flashmode and Fastboot arent working, device dont start. On my pc its named like an unknown device or somc, Does anyone can help?:crying:
Hi bro , did have solve your problem yet?? , I've got the same situation as you the same rm 3 if only I added another number , I think that block 3 has files for flashboot that is why it isn't working anymore , I tried with xperia companion but also asked about that flashboot
The only solution is to find a workaround on how to flash the firmware through fastboot , anyone has any idea??
partition 3 is s1sbl (related to bootloader), so you can't restore your device via flashtool, pc companion or emma. it's hard bricked, sorry
it can be recovered if you have any jtag box
Cubbins said:
partition 3 is s1sbl (related to bootloader), so you can't restore your device via flashtool, pc companion or emma. it's hard bricked, sorry
it can be recovered if you have any jtag box
Click to expand...
Click to collapse
thanks for clarifying , So the jtag box used for recover the lost partitions or repartitions the whole device?
do you know any the proccess to recover with jtag?
also when I tried to fix that partition with fastboot or flash bootimg or recovery it's said that my partitions table is not exist
othmane.os said:
thanks for clarifying , So the jtag box used for recover the lost partitions or repartitions the whole device?
do you know any the proccess to recover with jtag?
also when I tried to fix that partition with fastboot or flash bootimg or recovery it's said that my partitions table is not exist
Click to expand...
Click to collapse
please join to our telegram chat then we can discuss about your problem
Any joy in getting your boot partition back. I may have gone the same route with my M4. No flashmode, no LED when connecting to USB, etc.
Links to possible JTAG solutions for this phone?
mannemerak said:
Any joy in getting your boot partition back. I may have gone the same route with my M4. No flashmode, no LED when connecting to USB, etc.
Links to possible JTAG solutions for this phone?
Click to expand...
Click to collapse
which partition have you mistakenly delete? did fastboot still work for you? if so you can flash recovery and restore your OS and somehow you could fix flashmode with usb debugging on
but if you're unlucky like me with locking the bootloader mistakenly then
there's setool box and JTAG box but the question is which one is easier for restoring boot partitions
also I saw some way of restore partitions but that was with emmc replacement
Hello,
Cause of some problems (my Hisense enter test mode when charging), I've try re-installing firmware 6.03 from qfil method.
My problem is during the transfert, I had a power failure.
I don't know why but now my Hisense is empty of partitions.
I can not reboot, it stay in edl mode.
I was wondering if it's dead or if there is a way to recreate the partition table?
I have access to it in QFIL.
Thanks
Re-flash phone's Stock ROM.
The problem is too my knowledge, no official rom exist.
I has abble to recreate a partion table with emmc from firmware 6.03 (seems to be international rom).
So with qfil I've flash boot/vendor and recovery.
The problem is that my phone stay in edl mode.
I can't reboot to install firmware 6.09 from TF mode.
Disconnecting the battery don't change.
Edit: They are warnings when I upload files from eemcdl (PblHack: Error - 1836597052). I have to remove the battery after every operation.
emmcdl -gpt don't list any partition.