Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?
SchusterIX said:
Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?
Click to expand...
Click to collapse
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.
NickVXD said:
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.
Click to expand...
Click to collapse
Sorry about that, forgot that bit! I used odin to flash the stock rom, and even tried a .pit repartition. Kies does not see the phone. At most, it sees it but will not connect. So there are no rescue options to be had.
I thought I made progress. I was able to do the firmware reset with Keis. The phone got to the blisspop launch screen but just stayed there. I rebooted into TWRP and it still said I had 0mb of internal storage, and still had no OS installed. ADB still didn't see the phone, either. Now the phone will no longer boot to samsung, or to recovery, or TWRP. If I hold the power button the proximity sensor shines for a moment but that's it.
Same problem here, same phone but t0lte that ran many ROMs over 4 trouble-free years . Still at the pre-Kies stage, thus still can access twrp. Tried overwriting twrp with philz or CWM - Odin says PASSED but reality say no dice - twrp is still the recovery. Tried flashing stock - Odin again said PASSED, but still have twrp reporting 0MB.
Spent 1day surfing xda to ensure I have correct files and procedures.
Wonder if there has been any solution found...
When flashing a new recovery, do not check auto reboot. Flash the recovery in Odin. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery. Hopefully, this method will work.
Related
Hello!
I have a SGH-T889V Samsung Galaxy Note 2. I've had it rooted and running custom ROMs for more than 6 months, and I've never had an issue until now. I've tried flashing CM, pacman, and omnirom. All of them worked just fine (loaded ROM onto external SD, booted into recovery mode, factory reset, flashed ROM, flashed gapps, reboot phone and everything was peachy). I use Rom manager.
Yesterday, I tried flashing an update to omnirom (the 11/17 update) the same way as before. I got an error message, telling me the update failed. So I tried to reboot my phone again, but it told me that I had lost root access, and asked me if I wanted to fix that. When I picked yes, it went back to the Samsung load screen, and then the recovery screen appeared again. When I tried to "reboot phone now", it just flashed the samsung logo and then back to the recovery screen.
I tried loading the stock rom back on the eternal sd. That didn't work. Basically, when I took the external sd card out and stuck it in my computer, it told me that I had to format it to use it. It gave me exfat and ntfs as the write options. I tried it both ways, but neither of them were registering when i stuck the external sd back onto my phone and tried to mount it, so I can't flash anything from my external sd. To get my phone to register the external sd, I have to format it through rom manager / recovery screen. That works, and after that, my phone registers the SD card, but obviously I still can't flash anything off the external sd once I've formatted it on the phone.
I tried using the toolkit posted in the android development section to load the stock rom. I tried sideloading and also pushing the file to the phone. Both times, I got a messaging saying that it was waiting for USB debugging to be enabled. As far as I know, I can't do that from the recovery mode of ROM manager. So no dice there.
Essentially, I've softbricked my phone. Whenever i boot it up, it goes straight to recovery mode (and I only hold down the power button, not the typical power + home key + volume up key to bring up recovery). I can't flash the stock rom back on the phone, since my external sd does not register after i format it on my computer. When I try to plug my phone into my pc to load stuff on there directly, I can see it registers as MGH, but it does not show up in Windows Explorer to allow me to put any files on there. When I select "reboot phone now" in recovery, it shows the Samsung logo screen briefly before going back to the recovery screen.
I'm really stuck Does anyone have suggestions on what I can do. please?
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
funkstylez said:
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
Click to expand...
Click to collapse
thanks! reading up on Odin now, I'll let you know what happens after I try that.
funkstylez said:
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
Click to expand...
Click to collapse
So I have Odin up and running, I have the stock rom and it's been converted to a TAR file. However, I can't get Odin to work properly because it does not register that my phone is connected to my PC (presumably it should show up in one of the rectangles at the top of Odin once I plug my phone into my laptop via USB). Since my pc (and thus odin) does not detect my phone, I can't flash anything onto it
At this point, I have the appropriate stock roms, I have odin, and my phone still boots up to the recovery screen (with rom manager), but I can't manage to get it connected to my computer, though I have the Samsung drivers installed and working (up until i softbricked my phone).
ETA: google is my friend! Found clear instructions on using odin to flash the stock rom, and yes, it worked. Thanks!!
Google is everyone's friend and I'm glad you figured it out.
Sent from my GT-N7105 using Tapatalk 4
Hi I'm currently facing a problem. I Connected my phone ( ZE550ML or Z008) via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, I saw a post that said MOFD_UPDATE, on my phone comes up different. I tried flashing the latest 2.19.40.97/8.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
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.
So, a little background. Full stock recovery, latest Telus 4.4.2 firmware.
Phone may have suffered a drop and/or some water damage during an episode of blackout drunkenness. Yes, I know, I'm an idiot.
Worked fine for a day or two, then began randomly shutting off, seemingly at times when the phone's CPU was under stress. Keeping it in airplane mode seemed to help avoid the reboots somewhat but not completely.
This began right before I was leaving for vacation, and had no time to go replace it. Then, after successfully taking a bunch of awesome pictures while on vacation, the phone decides to go into a boot loop. Can only boot into download mode.
I've got another phone now, but would REALLY like to get the data off the phone if at all possible. I'm assuming there must be some hardware issue at this point causing the boot loop, so I'm guessing that restoring the phone to 100% original working order is probably out of the question.
Any suggestions? I'm guessing something got corrupted, but I'm wondering if maybe I can flash a new recovery or re flash the stock rom via odin and hope it boots up long enough to get the data off? Will it wipe all my data if i try to flash via Odin? Should I take it in for a JTAG? are there other options like getting someone to dump the data off the memory chip somehow?
Thanks in advance.
Since the phone will enter download mode, I suggest flashing twrp 2.87 onto the phone, boot into recovery, mount the data partition, connect the phone to a computer, and try to copy the data to the computer.
Okay, where is a reputable source to download Odin, and what version should I use?
Also, can you provide a link to the exact instructions for flashing TWRP? I looked at the info available on their website and it's not that clear...
And so once I've booted into recovery and mounted the data partition, I leave the phone on, correct? Dont do anything, just connect it to the PC, and it should show up there?
Thanks so much for your help
audit13 said:
Since the phone will enter download mode, I suggest flashing twrp 2.87 onto the phone, boot into recovery, mount the data partition, connect the phone to a computer, and try to copy the data to the computer.
Click to expand...
Click to collapse
Okay, I was able to flash TWRP successfully and boot into it.
However, when I attempt to mount the data partition, it won't let me. When I go into the log files, it says unable to mount /data, unable to mount /system, unable to mount /cache, etc......
Also says Internal Storage 0mb ....
So.... i'm guessing this is really not good
Any further suggestions??
If it can't mount the partition and the size is 0, looks like the internal memory is shot.
The only other thing you could try would be to re-flash the stock ROM without wiping anything to see if it will boot. If it fails to flash via Odin, I don't there is much you can do.
Hi,
I have Samsung Galaxy S4 Mini (serrano3gxx). I was using this ROM and CWM recovery. I really don't know how it happened. My phone shut down and when I booted it, I saw this message "Encryption Unsuccessful", so I was not able to access my storage. Then, I've searched how to fix this. I tried to backup storage in recovery and I got this error every time "Can't mount /system, /cache, /data", even while trying to mount them manually. After a few try (flashing etc.), I've become to not access ROM (also bootloader) and CWM recovery. When I tried to access them, I only got "Black screen" and nothing appeared on screen. Then, I could access "Download Mode". At this point, I've tried to flash another ROMs (including stock ROM) and recoveries via Odin. Firstly, Odin detected my phone but ADB not. Secondly, when I tried to flash something that I mentioned, Odin's log screen stuck on "Initialization" step. I've waited 1 hour only for flashing recovery... Nothing flashed and still stuck same step...
Now, actual situation is that I can't access even Download Mode! Before this, phone was shaking when I plugged it to charger or USB port and tried to power it on. Now, this is also changed, it is not shaking...
Guys, I am saying "wth is it" now. These occurred step by step:
1. Shut down and message "Encryption failed/unsuccessful".
2. Can't mount /system /cache /data.
3. Can't access both of ROM (bootloader) and recovery // Black screen
4. Can't access Download Mode.
Note that, all of required drivers installed, even Kies. By the way, Kies detected my phone but it could not complete loading to recognize.
I've found this article but I don't know if it is solution.
I guess phone's storage is corrupted.
So, my phone's storage is fried? What should I do? Thanks for helps I will get.
Try flashing the complete stock rom not just the recovery. Or find a fix and flash it!!
Maybe you should get a pit file and flash that. Reanimated a S3 mini with that.
kurtn said:
Maybe you should get a pit file and flash that. Reanimated a S3 mini with that.
Click to expand...
Click to collapse
As I wrote, I can't access/reach recovery and download mode. How can I do that if you know it? I am still searching how to fix this but it is hopeless case I guess. "getting a pit file" is ok. I found it for a few roms including stock rom. But how can I flash it? I could not find this.