Related
I have flashed my galaxy S with ROM 2.3.3 XXJVK, odin finished, and rebot my phone into recovery mode where i got this error
E: failed to mount /dbdata
E: copy_dbdata_media: can't mount /dbdata
so i select just restart, and phone start.. So i don't know what this mean. Anything wrong? Cause my phone is working on this rom alright, didn't find problems
Only strange thing i find, when i tried to install doc rom it doesn't install.
I selected:
*Wipe version
*Chainfire's Kernel
*All Apps with default Samsung TW Launcher
*XXJVK Stock Theme + AOSP lockscreen + Shut Off Animation
But none of that install after in say in recovery COMPLETE..
if the phone is working fine, dont worry about it.
if it starts to cause issues, you need to flash 'dbdata' thru odin, or a firmware that contains it, such as JM8 or Darkys 9.2 resurrection.
ive had this issue a few times, leading me to boot loops. so if you experience them, you will know why.
or, a more simple solution,
CLEAN YOUR DEVICE BEFORE FLASHING.
i think it is written in every guide,
erase cache, erase internal storage, erase user data!
then flash, and there will be no problem, no error.
also, disable all lagfixes!
nonyhaha said:
or, a more simple solution,
CLEAN YOUR DEVICE BEFORE FLASHING.
i think it is written in every guide,
erase cache, erase internal storage, erase user data!
then flash, and there will be no problem, no error.
also, disable all lagfixes!
Click to expand...
Click to collapse
if any error appear i will do that and flash again.. But i don't use any lagfixes..
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hi XDA sorry to bother you but I really really really need your help because I am desperate ...
I am French but I speak a little English and I am your community for a long time!
Here I have a note 4 (N910F) and I was officially NK4. I wanted to install a custom rom but I had beug on official NK4, so I decide to make a clean reinstall before putting a custom rom!
The problem is that in order to do I put my note 4 in download mode and I opened odin then I checked auto reboot, re partition, f reset time and nand erase all. I put the PIT, BL, AP, CP and the SCC in the right boxes then I clicked on START and then restarts the mobile was stuck on the samsung logo and waited 15min .. Always blocked after 15 minutes so I extinguishes.
I tried other manipulation: I try to flash the rom 4 files with the pit but check the nand erase all but still stuck on the Samsung logo.
I try to flash the rom 4 file without the pit but still stuck on the Samsung logo.
I installed philz and restore a backup but always the same.
And I try to do a factory reset before installing the official NK4 and always the same.
I also found that when I do a factory reset I have two errors:
the first E: Error mouting / data!
the second E: Error mouting / sdcard / .android_secure!
Voila so I really need your help because no one can solve my problem: '(
Thank you in advance ..
Download new rom from sammobile, use odin and restart everything from scratch! Dont un-check or change Anything in odin, just start when you have chosen right file..!
Try To change file system of data And sdcard, like this http://forum.xda-developers.com/showthread.php?p=56956070
Maybe you can try this: http://www.phonandroid.com/forum/reinstallation-propre-du-note-4-sm-n910f-t110393.html
First I wanted to thank you for your help!
I finally managed to solve my problem!
I spent more than 7 hours on this problem to finally succeed!
I did a nand erase all with odin then directly flash the cfroot without turning it on after nand erase all. Then I was in the recovery then wipe and factory reset wipe Cache and then I restart my phone and it worked!
For without the flash cfroot it did not work!
it was really long to find this a bit weird solution!
Thank you for your help!
For future reference:
Wipe /data from stock recovery after flashing a PIT and ROM.
Flashing a PIT wipes all partitions on the phone, and Odin only flashes /system, leaving /data unformatted. Wiping /data from stock recovery fixes that.
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Orangley said:
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Click to expand...
Click to collapse
Try a full factory reset. Be careful as this will wipe your internal storage.
GDReaper said:
Try a full factory reset. Be careful as this will wipe your internal storage.
Click to expand...
Click to collapse
Thank you for your answer but I did it after flash stock rom via odin. Wiped data / factory reset , cache partition , mounted cache , system , data , wiped dalvik cache..
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
GDReaper said:
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
Click to expand...
Click to collapse
Flashing stock rom is same with factory reset i think clears everything.
I don't know. Haven't flashed stock on this device yet.
But don't most guys recommend doing a wipe before going back to stock?
I dont know i'll try that when i have free time. I did research some guys saying lollipop causing these problems. I'll try wipe before flash stock rom again , if issues keep happen i'll use lates 4.4.2 custom rom. Thank you for your answers i'll report back.
Real reset
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have the PIT file downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Thank you so much i'll try this now.
AndroidInitiate said:
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have it downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Click to expand...
Click to collapse
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Orangley said:
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Click to expand...
Click to collapse
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
AndroidInitiate said:
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
Click to expand...
Click to collapse
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Orangley said:
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Click to expand...
Click to collapse
What carrier are you using, model number of the phone, etc.
Have you backed everything up? And can you flash the custom recovery through Odin if it fails?
Try it without wiping efs first just to be safe
Look here for your device you will be able to find standalone flash able versions of twrp that should work through odin.
http://twrp.me/Devices/
Using i9500. And i did what you said and works fine thank you! Mods close thread please.
Can anyone help unbrick my i9506? It will boot to the Samsung logo but then comes up with the message: “Encryption failed. Unable to complete encryption because of interruption. Perform factory data reset …” etc. I have never encrypted the phone and this came out of the blue, though I did delete cache and dalvik cache under TWRP the day before. The phone will boot into TWRP recovery where I tried doing a factory reset and data wipe but nothing works and all I get is “Unable to mount /data, Unable to mount /cache, Unable to mount storage” in TWRP.
I tried flashing a stock rom with Odin (3.07, 3.09, 3.10, 1.85, different USB ports, official samsung cable, different computers) but that also failed, and fastboot doesn’t work either. Looks like a corrupt partition? Is there any work around to this problem, or failing that, can I flash a stock recovery so I can take this in for repair under warranty?
Did the Odin flash work? If it flashed succesfully, then flash the firmware with a .pit file and check re-partition. That should fix it.
Tired flashing numerous times with Odin but all failed. Tried with .pit file but also failed.
OK, I’m just an old noob, but after three days of searching, downloading and flashing, I am ready to give up. I found a number of references to ‘Encryption failed’ but few answers. The constant mmc_write fail in Downloading when flashing suggests, according to some, a hardware failure with the mmc chip, and Knox also gets a mention as a cause. So it looks like a hardware and Samsung issue, and the only easy fixes reported come from those who get a replacement motherboard under warranty.
But I can still boot into twrp recovery, which suggests a soft brick, and some users experiencing similar issues have revived their phones. My numerous attempts to flash stock rom, stock recovery, CWD etc with Odin failed. In trwp, data and cache will not mount, nor will data mount through adb shell. Looks like a partition issue, though all partitions appear to exist under dev/block/ and flashing the i9506 pit file in Odin does nothing. Tried to wipe data, cache, system etc and do a manual reformat of /data (userdata partition 26 in i9506) through adb but all failed. Tried superwipe (doesn’t work), and while fastboot erase then rom flashing works for some to overcome the dreaded ‘Unable to mount /data failed’, Samsung phones don’t support fastboot. Some users report success through CWD recovery, the main problem solver, and flashing older ICS roms (I’m on 5.01 but also d tried 4.4.2 and 4.3 without success). Twrp crops up as a real suspect for many users – me too - but my attempts to get rid of it and flash either stock recovery or CWD/Philz failed.
So, I’ll try to get a hardware replacement for my phone, but given I’ve tripped Knox when rooting, I don’t fancy my chances. My conclusions, apart from don’t mess with your phone, are avoid Samsung and Knox, and twrp sucks but, hey … who knows?
Follow up. Got it fixed under warranty. They replaced the PCB (motherboard). Looks like I wasted all those hours trying to get it up and running, and it was hardware after all.