First post here... and all for the wrong reasons
N7000, unlocked bought in amazon.de
Working well for over a year, recent upgrade to official jelly bean (LPY rom out of germany).Successfully rooted.
All was well for 2 weeks until one day, out of the blue, the internal SDCARD vanished (started getting message of "sd card not mounted" in various applications, including file managers, etc...) although everything else still worked (including the external SD card).
When trying to debug, I issued "ADB reboot fastboot" from my laptop and all hell broke loose... Now I'm stuck at the initial "Samsung GALAXY Note GT-N7000" when I power it on.
If I power on into recovery (vol+, home , power) I get a series of messages in red including "failed to mount", "can't mount", "Can't open" /system, /cache, /data... after all the messages are displayed I get the standard Android System Recovery menu (I.e. reboot, apply update, wipe... etc).
If I power on to download (vol-, home, power) i get the normal warning about custom OS, etc... and I can load a new ROM from ODIN in this mode, with apparently no errors, but at the end the phone reboots into recovery still unable to mount /system, etc...
ADB only sees the phone in recovery. Fastboot does not see the phone.
I'm a bit at a loss. I have transferred to the phone the official jelly bean rom, and an older official ICS rom, all with the same result.
In odin, I only check the "PDA" file.
Questions:
1) Would rewriting the PIT help? Can I just find a PIT and ROM, check PIT & PDA in odin and go from there? or do I need all the other odin files (bootloader, phone, CSC)?
2) Is there a site that explains how the whole phone/roms/android system is organized? My background is computing, but I'm at a loss re the complexities of fastboot/bootloader/download/recovery, plus all the partitions that apparently android needs to operate. To me it is quite puzzling that a phone can "brick", short of loosing whatever it needs to load stuff from an external device...
3) how do you get the phone into fastboot?
4) Any other suggestions?
To compound matters, I have tried to ask samsung to fix the phone under warranty, and was rejected because the original invoice from AMAZON does not contain the IMEI. Amazon says it is not legally bound to print IMEI on invoices and that their systems are not prepared for that, so I'm stuck between a rock and a hard place
Help very myuch appreciated.
Luis
Send to Amazon They have a legal obligation to you.
sent by reversed alien technology....
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
I had a very simmeler thing. Could only boot loop load roms with same results. I used Odin to load a kernel with cwm. This allowed me to get into recovery and sort it. I'm not saying do it but it worked for me
sent by reversed alien technology....
Fixed. Had to flash PIT & PDA with Odin... used the original GB ROM and the PIT file for my phone model, and this seems to have worked. I'm now back on the latest JB.
Related
To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
I have a Verizon Galaxy tablet 7 inch the original one. I have had many custom roms on it in the past. Recently I had AOKP on it...I am not sure what build. For some reason my kids were playing with it and it would not boot up. I went into recovery and tried flashing AOKP and it would stay locked up on the boot screen. I eventually tried flashing all ICS roms with no success. I eventually ended up trying to go back to stock. I can get into download mode with and communicate with Heimdall and/or Odin. The problem is that every thing I flash goes into a boot loop. when I go into recovery I get an unable to mount error like E: unable to mount cache and one for kernel and about 6 more. I figure that there is something wrong with the file system so I have used a pit file when I flashed with no success. I am not sure if there is an issue with the file system being the wrong type or if I have to many partitions now. I know that the mount error in recovery is where the problem has to be. If someone could please point me in the right direction. I have been all over these forums.
Thanks,
Leroy
In order to determine if it is file related. Try to do a full wipe right after the Odin.
That is all 3 Wipes (Cache,Dalvik,Data)
Also check all the boxes on the right side of the Odin screen to flash the stock rom.
Well I got a little further now it boots up after 5 minutes and states encryption unsuccessful and asks to reset tablet. There is some threads on this so I will get to trying to resolve this. In fact I just realized this is how everything started off I didn't read the message and powered it down. So it must have started on its own or from the kids playing on the tablet.
Is there any way to determine if your internal memory is shot. It seems like there is a problem mounting my internal memory > emmc?
Hello fellow XDA'ers!
I have come into possession of a tablet that has the following problem:
When applying the OTA update to the SGH-i957 LTE tablet from Rogers, the previous owner plugged in the tablet into a mains power supply.
Because of this, I was told that the OTA update did not "complete." Specifically, at device reboot, the tablet was not accessing the newly updated ROM. At this point, the owner went into a bit of a panic:
- They hooked up the device to ODIN3 v1.85, with no response;
- They wiped all data & performed a factory reset;
- They wiped the cache partition;
- They formatted /cache;
- They formatted /data;
- They formatted /system
- They also made sure all settings were clear.
I tried to restore via Nandroid, but I get the following output via CWM-based Recovery (v5.5.0.4):
Code:
restoring boot image...
restoring system...
restoring data...
".android_secure.img not found. Skipping restore of /sdcard/.androidsecure."
restoring cache...
Restore complete!
Obviously, this isn't good. But wait, there's more! When I am trying to activate the option to "mount USB storage," I get the following error:
Code:
E: Unable to open ums lunfile (No such file or directory)
I opened the CWM recovery log, and like the Stanley Kubrick movie "The Shining," the log printed following 10 to 12 times:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory.
I have yet to connect the device to my computer, as I don't want to mess it up any further. The tablet is currently plugged in to a mains power supply, awaiting resurrection.
I have experience in successfully restocking & flashing my Samsung Galaxy Tab (GT-P1000) via ODIN with Overcome/CM9, so I am more than happy to troubleshoot and thoroughly document anything that is happening with the tablet.
I have searched this specific forum for threads that relate to OTA failed updates, but I have not seen a similar thread or post.
I fully promise to document this problem in this thread if other people have issues in the future relating to this problem.
Therefore, how do I bring this tablet back to its former glory of sweet LTE-goodness?
Thanks,
willing_to_cooperate
Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
It works! It came back from the dead!
Eun-Hjzjined said:
Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
Click to expand...
Click to collapse
It worked!
For anyone that may have the same problem:
1) Put SGH-i957 into download mode (turn off, then hold power and volume up-down keys):
2) When you see a warning, make sure to press the volume up key (therefore, if you're looking at the tablet screen with the power cord outlet on the left hand side, it would be the bottom rocker button, furthest away from the power button).
3) Connect to ODIN v1.85.
4) Load the firmware into the PDA slot.
5) Make sure that Re-Partition and Flash Lock are NOT checked.
6) Make sure that Auto Reboot and F. Reset Time are checked.
7) Press start.
The tablet will go through its process, and may reboot 1-2 times. It will build a cache (you will see the Android figure with a geometric ball rotating in its stomach).
After that, it should boot into your carrier's logo screen, with setup of the device.
Thanks again, Eun-Hjzjined!
willing_to_cooperate
---------------------------EDIT:
This process also removes root from the tablet. However, no hiccups when re-installing root.
Hi thanks for all your help!
I have an i957 on ATT in the US, and previously had rooted with DaG v2 Kernel, worked great.
Yesterday I used the stock i957M (Bell) Update to get on ICS. Failed on Modem (known issue mo XDA), but rebooted and works fine.
It removed the root (as yours did above) - when I tried to re-root with same kernel on ODIN, everything locked up. Had to re-do the firmware with ODIN as in your entry above - now back in action.
Question: If there was some way you re-did your root so it was compatible with your build, can you point me to it?
Did some searching around, and only found dated sources that talked to how I did original root.
Maybe you have some magic.
Sure would be nice to get SU and CWM again, rather than stock.
Nevermind - Got it working - used "Method 1" - Stock Kernel from http://forum.xda-developers.com/showthread.php?t=1401100
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
asertap said:
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
Click to expand...
Click to collapse
sd card issues are usually due to kernel, have you tried flashing a custom one to boot in recovery?
If your internal is dying, partitioning an external sd should work but since it's still not fully booting, I feel like that's not the issue. I had that happen to mine, tried many Odin and Heimdall, when finally one Heimdall worked (after like 10-15 different attempts). Shortly after my internal died though.
So I would start by flashing a kernel with Odin 1.7, see if you can boot in recovery (always took me a few attempts to get it). From there you can flash a custom ROM (I always suggest GamerzROM for the cappy but really it's personal preference). Otherwise, your 2nd option is bashing your head on Odin/Heimdall one-clicks lol
PS.: Just came across this if all else fails: http://forum.xda-developers.com/showpost.php?p=61479845&postcount=58
I have this exact same issue... Thank god I'm not alone! I wondered what that stupid "encryption failed' message was all about.
So I've done just about everything the above has done, except the problem is I continue to get a boot loop. The ODIN one-clicks all boot loop. Ive been able to install a custom kernel and CWM, and surprisingly my internal storage is still accessible, but when I try to install the CM9 that's on there it freezes at "opening update package".
So, stuck between a rock and a hard place. I can't put any other ROM's on the internal storage because I have no way of accessing it. Therefore I have to rely on a ODIN one-click. All of which boot loop or just fail outright. Is there a way to access the internal storage without fully booting android?
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Use smart swirch recovery method in help tab. The process guide you to process. Dont worry it will be ok.
Sent from my SM-N950F using Tapatalk
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
In more there is option of emergency software recovery, plug phone and it will help you.
Sent from my SM-N950F using Tapatalk
Try installing the last rom... one which is showing up in ur pc... remove any encryption if its there.... that should solve ur problem.....