Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
lorendroll said:
Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
Click to expand...
Click to collapse
you can try to use Odin, but probably you have faulty eMMC, many similiar cases around the forums about rebooting and stuck on Samsung logo.
Probably PC won't recognise your phone and there will be nothing else to do, but to give it to service
Miracles happens! Re-partitioned and fully erased nand via Odin and managed to upload the rom! Have tried 3 time before it succeed (crashed few time on system and cache image writing). Everything seems fine so far. Won't upgrade the rom from the stock 4.1.2 for a while to keep phone working. I have the insane emmc chip by the way. Hope it won't fail again.
Related
Dears,
I have galaxy nexus intl version with CM 11 , two days ago it rebooted by it self and entered a boot loop that till now couldn't get out of it, when booting it reaches the CM animation stays there for about 30 sec then it restarts.
I tried the following:
Recovery
boot into recovery, wiped cache, wiped dalvik cache, but when I was wiping the data/factory reset the device freezes and reboots, I tried to format data from recovery but I ended up the same, the devices freez, reboot and the loop, CM animation then restart and again and again and again and again.
Fastboot:
Every command to erase, lock and relock, flash stock img, flash other recoveries, everything completed successfully but as if I did nothing, nothing changes, neither the boot loader nor the recovery not even the used data, every thing there as if I did nothing, and still stuck in the loop.
ADB:
I booted into recovery , I have CWM 6.0.4, then tried to pull everything, and thankfully I succeeded, but not in pushing, every time I push a file it finishes successfully but nothing shows on the device.
I installed a new rom via sideload, and it completed successfully, so I rebooted but as if I installed nothing same loop in the same place.P.S I tried multiple roms , the result always the same.
I tried to format via adb shell command, but everytime I format the \data\media , the device freeze and reboot.
Odin
I tried to restore to stock via Odin, it failed when writing the system twice but in the third time it succeeded , and then as if I did nothing.
-------------------------------
I also tried the nexus tool kit, every command in the toolkit, I managed to run twrp recovery temporarily and tried the same as before and ended up with the same results.
I gave up , and I ran out of ideas, I wish that there is still something I can do before sending it to maintenance.
Thank you in advance.
Sounds like the emmc is fried.
bpyazel said:
Sounds like the emmc is fried.
Click to expand...
Click to collapse
So what do you thing should I do??!!
Either buy a new Emmc and replace it, have a shop do it or buy another phone.
bpyazel said:
Either buy a new Emmc and replace it, have a shop do it or buy another phone.
Click to expand...
Click to collapse
I thought, there is something that I still can do before sending it to an electronic shop.
Thank you anyway man
Hi I was wondering if someone could help me.
My dad's phone which is a S3 somehow soft bricked itself. It was on a stock rom before.
It turns on and then gets stuck on the Samsung Galaxy SIII screen.
I am able to boot into download mode as well as recovery.
I was able to flash a stock ODIN file UVUEMJC as well as the PIT file and everything went smoothly and it passed.
However, the same problem remains, it is still stuck on the Samsung Galaxy SIII screen when I boot it.
Also went into recovery and tried to wipe data, but it is unable to mount any partitions, e.g. can't mount cache, can't mount data, etc.
I was able to throw on TWRP and boot into that, and it gives me similar errors as the stock recovery. TWRP also says that my internal storage is 0 GB and I can't put any files onto the phone.
I am quite confused because if NAND was corrupted then I shouldn't I not be able to boot into recovery at all?
ADB is also working...can't push/pull anything though.
If someone could help me I would really appreciate it. Thanks.
So I flashed CWM cause I read on XDA someone said that formatting data through CWM works, now...it says there is no pit partition and there is a flash read failure whenever I try to flash a stock tar with odin w/ pit. Also tried flashing pit by itself, doesn't work.
Try installing cwm or twrp again, boot into recovery, mount sdcard0, connect to Windows machine, and try to format the partition using fat32.
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.
Hi,
A few days ago my GT-N7100 started to behave weirdly. Phone was stuck in a boot loop. I tried to open recovery but it wasn't booting into recovery mode.
I flash TWRP recovery using Odin and found that the internal storage size was showing 0 MB. So I formatted the Internal storage and then repaired it using TWRP.
Then I tried to install a custom rom in it. After the installation was successful, i wiped cache and factory reset the phone but phone was still stuck in boot loop.
I turned on my phone in recovery and found out that it /data size was 0MB. So I installed a pit file using Odin to resize it. It was successful. Then I installed a Stock rom 4.4.2. Now the phone turns on and shuts down after a few moments.
I think there is not boot loader which can boot the OS (Just my understanding).
Please help.
Thanks,
shujaathussain said:
Hi,
A few days ago my GT-N7100 started to behave weirdly. Phone was stuck in a boot loop. I tried to open recovery but it wasn't booting into recovery mode.
I flash TWRP recovery using Odin and found that the internal storage size was showing 0 MB. So I formatted the Internal storage and then repaired it using TWRP.
Then I tried to install a custom rom in it. After the installation was successful, i wiped cache and factory reset the phone but phone was still stuck in boot loop.
I turned on my phone in recovery and found out that it /data size was 0MB. So I installed a pit file using Odin to resize it. It was successful. Then I installed a Stock rom 4.4.2. Now the phone turns on and shuts down after a few moments.
I think there is not boot loader which can boot the OS (Just my understanding).
Please help.
Thanks,
Click to expand...
Click to collapse
in recovery need to mount data to show if not will show 0mb
since u already Flashed official rom can turn on phone but after few moment will shutdown by it self ?
try change the battery if helped !
good luck !
Hello,
my Samsung Galaxy S4 mini with bliss ROM stated to turn off spontaneously and sometimes it didn't start again (the Samsung logo appeared and then the phone went dead, it was impossible to enter recovery mode, download mode shut down itself immediately). After several tries, it booted normally. This happened again - and I found out it was a bad power button, which I replaced. Now it is possible to enter both recovery mode and download mode with no problems. However the main OS doesn't boot up. So I tried to do a full wipe in recovery mode and CWM recovery rebooted the phone, when it was trying to format /data partition. So I tried to flash stock firmware with ODIN. It also didn't boot up, but at least the stock recovery gave me a hint what is wrong. When I perform full wipe, I get error: "E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata"
I tried to flash the phone again, this time with a PIT file and let ODIN to reformat the partitions. However, no change. How can I fix it?
Try twrp