Hello everyone,
I have a Samsung P1000 GSM tablet which i purchased from Jeddah a few years ago.
Froyo started acting up and Samsung was not releasing any new firmware updates, and so i decided to root and move up to Gingerbread.
I installed 2.3.3 JPJPC and rooted and things were good.
After a while, i installed rom manager from the market, and installed the recovery for the wrong model due to ROM manager not having P1000 listed, which was a reckless move.
Since then, the TAB gets stuck on the samsung screen, and i can tell it is actually sort of trying over and over in an endless loop.
After a few reboots, it comes back, but losing all settings (home screen empty, phone book gone, SMSs gone), and it starts with the welcome wizard (language, packet data etc...).
The bootloader at that point was giving errors about not finding android_reboot and unable to load the mcc ...i'm sure you guys know them.
I read tons of threads about this, but no one actually mentioned that this problem is intermittent! And no definite solution...
Attempts:
I tried loading JPJPD (P1000JPJPD_P1000OJPJPE_P1000JXJP4_HOME.tar) via ODIN 1.7 using gt-p1000_mr_PIT and then dbdata, same thing.
I tried using P1_add_hidden.pit, same thing
I tried using GB-Stock-Safe-v5, same thing, moved again to JPJPD, same thing.
The interesting thing is even ODIN would FAIL the complete (write) then after 1 or 2 retries, it would work (same setup).
I also installed the recovery CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS, same thing.
At this stage the recovery works well, and so after each ODIN attempt I was wiping everything...
At this stage I'm trying to figure out if the P1000 is recyclable, organic, or waste!!!:crying:
Can anything be done to stabilize this TAB ?
Thank you,
Bassem
EDIT:
After posting, i entered recovery mode and found the errors i tried describing above have come back again:
"E:internal mmc : open fail
Internal MMC checksum verify failed
# MANUAL MODE#
-- Updating application...
E:failed to mount /preload (No such file or directory)
E:install_application_for_customer:can't mount /preload"
multi-CSC is ok
now when wiping /data:
"Formatting /data....
E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
I am sure this will be fixed (which happed before) if i repeat the above steps, only to break again after a few reboots.
Related
I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App
Ugh...an unfortunate response. Yes...I'm on the right forum.
I did make a CWM backup from a couple weeks ago. Not sure if that helps.
mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App
*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT
Additional Note: Settings are not saved between reboots.
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App
I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064
That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT
If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.
Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT
I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!
I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App
[This is a repost of my post over at Android Central]
Hey Everybody,
My Nexus S 4G has been unusable for a few days now and I need some help diagnosing the problem and determining if it can even be fixed.
What happened: I was running jstntp's Android 4.1.1 rom (ver 2.0). I liked the performance of version 1.2 a little better so I went back to it. Being 1.2 didn't have wifi tethering enabled I figured I'd try a 3rd party wifi tethering app just to see if it'd work (I can't remember the name of it). After install my phone rebooted itself (looking like a crash) and went into an immediate boot loop. I quickly booted to recovery and tried simply reinstalling 1.2. That failed. So I tried restoring a nandroid backup. That failed too.
What i've tried to fix it: I have tried flashing (via fastboot) stock gingerbread, stock ics, google's official stock gingerbread, google's official stock ics, sprint's official ics via odin, and a half a dozen different 3rd party roms such as some bugless beast roms that I have used in the past. The stock images all appear to flash fine with no complaints from installers. Even odin installed and displayed it's "passed" message.
Where it gets weird: In all of my recovery efforts I noticed a strange occurance happening. Everytime I would load something to the "sdcard" (whether it be by mounting in cwm or pushing through adb) it would appear in cwm while it was booted there (yet fail to install anything) and would disapear as soon as I booted out of cwm. Also, if I deleted any files while mounted (or deleted from adb shell for that matter) they would reappear after rebooting. At this point I figured the root of all of my problems is that my "sdcard" partition has a problem and needs to be fixed.
How i've tried to fix the "sdcard" partition:
- Chose to format /sdcard in cwm recovery. It said it was successful but didn't do anything at all
- Chose to format /sdcard in twrp recovery. It said "E:tw_format_rmfr: unable to locate volume for device "/dev/block/mmcblk0p3" "
- Did fastboot erase media
- Locked the device and unlocked it again agreeing to wipe all data (nothing got deleted)
- Pushed busybox over adb and ran mkfs.vfat on /dev/block/mmcblk0p3. It didn't complain and said it was successful. (still nothing deleted)
At this point I'm really at a loss. I will do anything to get this to boot. I don't care what version of Android I wind up on, I don't care that I have to lose all of the stuff on my "sdcard" (it's all backed up anyway). Just having a working phone would be great.
Thanks in advance,
- Phil -
Mount USB on Windows and just format it. Or before that you could try running chkdsk {yourdrive} /F
The chkdsk is on windows.
Hello everyone,
First let me give you some background information.
I have a P6210XXLB2 and I was on android 3.2
I have been waiting 2 years and + for an update for my tablet
Never dared to do it myself
Recently, I have tried doing so, I tried to grasp as much information as I could
However, they were no clear easy tutorial step by step on the subject
I decided to start, and rooted my phone with KangoRoot
Then, I installed CWM 6.0.2.7 through ODIN 1.85
Proceeded to a nandroid backup on my external SD.
I tried Installing PA3 following that tutorial
http://forum.xda-developers.com/showthread.php?t=2221328
Realized none of the p6210 versions were working
Followed this guy recommendation
http://www.jawalak7yatak.com/en/how...ranoid-android-3-60-on-galaxy-tab-7-plus.html
Installed the 3.60 version + 4.2.2
The phone booted up until the splash screen and then black screen
Tried different versions of p6200 and p6210 while removing the prop thing command from the p6210 one
Nothing but black screens
Decided it was enough and tried to go back to my original version
Which is on my ex SD, I had mismatches with MD5
Decided to remove the MD5 check
Now were here, I have an error while restoring /system
If I check the log, only thing that shows up is
I:Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thought it was maybe a problem with permissions, tried using fix permissions
However, its still the same error MSGs
The only solution I can come up with is from here
http://forum.xda-developers.com/showthread.php?t=2349776
I will probably do that tomorrow when I wake up If dont get any answers
http://www.ibtimes.co.uk/galaxytab-plus70-gtp6210-official-android412-xxdm3-jellybean-467821
Solved it.
I have p6210xxlb2 with android 3.2 (from Canada)
Installed the 4.1.2 MF1 from russia
Installed cwm 6.0.2.7
Bootloop, cleared cached, data, dalvik
It works now.
Hope it helps someone !
my tab plus Upgraded to 4.4.4。i think you can try it.
open nandroid.md5 .delete all text in file-save and no md5 mismatch.or u just delete file md5 and creat a new file text(blank file) with the name nandroid.md5
Edit: SOLVED
Hoping someone can roughly point me in the right direction. I'm not very savvy in flashing new ROM's, but I had success with my phone recently, so I decided to try and update my tablet and it's not going so well. It's a Samsung Galaxy Tab 10.1, model GT-P7510MA, which I believe is wifi only. I started off by following the youtube tutorial: 0eAQzxwEVjY
I did *not* make a backup, so shame on me right off the bat, but at least now I've learned this lesson.
There is no OS, but TWRP v2.2.0 is installed and I'm able to boot into it just fine. I'm able to transfer/push files via command line on my windows machine, but I did find something that seemed odd, which is that the top level directory is not named "/sdcard", instead it's just "/". When I transfer files, I have to name the the path "/" for them to show up in the top level directory. If I use "/sdcard", it looks like they upload, but I have no idea where they go. Not sure if there's any significance there, but figured I'd mention it.
The problem is that I can't seem to install any OS. I've tried Nameless 4.4.4, Clockworkmod 10.1, and AOSP 6.0. They all fail the same way, I'll type out what it says below:
--Install /aosp-6.0-p4-20151211.zip ...
Finding update package...
E:unknown volume for path [/aosp-6.0-p4-20151211.zip]
E:Can't mount '/aosp-6.0-p4-20151211.zip'
* Verifying filesystems...
* Verifying partition sizes
Error flashing zip '/aosp-6.0-p4-20151211.zip'
Another strange thing is that when I tried the aosp-6.0-p4wifi, it said that this device was a p4, which I don't think is correct, but that's why I tried the p4 version. It errors just the same. I've also tried to update TWRP, but I'm not sure you can update TWRP from within TWRP? I've tried using the file "twrp-2.8.7.-picassowifi.zip" and it errors the same as the OS'.
Edit: It's been sitting here powered on for a bit and then went to the blue teamwin screen and would flash off every five seconds or so. I figured this was maybe a screensaver? Next it powered off and on restart, all the files I've uploaded are no longer visible.
Any guidance is much appreciated.
Final edit: Kind of embarrassing...all I needed to do to find the /sdcard directory was just scroll down a little through the folders on the left (I thought it was supopsed to be the top directory). I'm pretty sure the 7510 is a wifi only version, but for some reason, none of the wifi ROM's I've tried will work. It gives an error and says my device is a p4 and not a p4wifi. Anyway, neither of the wifi/p4 Marshmallow ROM's will work, but all I had to do was wipe cache/delvic/system (I did do this several times) and factory reset (had not done this before) and install Cyanogenmod for p4 with the recommended Google Apps and all is working well.
Hey guys, I just want to share this experience. My phone is Samsung Galaxy J7 (2016). It runs Android 6.0.1 Marshmallow. Yesterday I decided to conduct a "Wipe cache partition" on my phone after installing and uninstalling lots of apps from Play Store to at least get rid of any temporary files they might have left.
I went into recovery mode and selected "Wipe cache partition" and then after it said success, I selected "Reboot system now". Then it showed "Verifying DMVerity Hash Tree..." (I don't know what that means) for at least 5 seconds and then an error text appeared. At first I was unable to take note of it because my phone rebooted immediately but I knew it was an error since the text was colored RED.
So I decided to do a wipe again and did the same procedure. This time I carefully paid attention to the error text. It only showed for maybe 1 or 2 seconds before my phone rebooted. It read "Error: Failed to mount /data (invalid argument)" or something like that. I observed my phone. Used it like I normally would and I could find no problem with it. And that is the problem now. Why would it say error when my device is fully functioning? It's very disturbing. Like some problem is lurking in the darkness waiting for it to unveil itself.
I searched the internet for problems related with "Error: Failed to mount /data (invalid argument)" and most, if not all of them, has something to do with phones stuck at boot logo.
Can you please help me? Get this worry of mine out of my mind. I have this OCD thing when it comes to personal items. Sorry for the long thread. Thank you very much and have a Happy New Year everyone.