Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
rail205 said:
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
Click to expand...
Click to collapse
I got the same thing on my Samsung Galaxy s3.
Related
I'm not positive where this should be posted it can be moved as needed but i am beyond lost right now. I have looked through hundreds of pages of forums for help and cant fix my phone yet.
I have a good amount of experience with android, adb, rooting, etcs and usually have been able to solve my problems. I was running CM7.0.3 on my droid incredible fine for months without problems and then out of no where i went to turn it on and it got stuck at the splash screen. I was away from my computer on vacation so i started trying to figure it out on my own. I could still access CWM via Hboot but when i loaded CWM it couldnt mount /data and /cache. Last time i had a problem similar to this i just flashed a RUU through Hboot and rerooted my phone afterwards so i thought this might work. I flashed it and phone booted up and i thought it was fixed.
This is where things started getting confusing. The internal storage in my phone has completely disappeared and theirs only 149MB available under phone memory which is suppose to be at 748MB. I tried to run unrevoked so i could reroot, get CWM back, and try to figure out what happened but it cant run because the internal storage it missing.
I have been reading for hours and trying to figure what to do next but i have no clue. i really need some help anything would be appreciated.
UPDATE: After more work on my phone i tried reflashing the RUU and then doing a factory data reset through hBoot and couldnt complete it because internal storage having problems mounting. im trying to get a logcat right now to post showing what it is. i believe it is the /dev/block/mmcblk0p1, CACHE:recovery/log, and poart of the mtdblock
Have you tried a brand new flash of CM7? Do a Full Wipe, Format System and anything else you deem necessary to format and flash CM7 from your SD. Then you can begin to work from there, because at least you'll have a working phone.
I'm a little confused as to why you would immediately run the RUU after getting a Bootloop instead of Restoring a Nand or Wiping Cache or Data?
I could get it to boot into clockwork but /data couldnt mount. i could not do a wipe or flash from inside CWM. i tried to do a fresh install but it wouldnt let me. I couldnt restore a NAND for the same reason. Now because of the RUU i dont have CWM anymore or root access. unrevoked wont work to reroot because in the internal storage is all messed up.
Was running a Rotted stock Rom which is flashed with CWM. All was fine until i tried to install Google official 4.2.1 update. That messed up something and now i cant get it to boot. I wiped everything in CWM but nothing. Also been trying to connect it to PC to transfer a new ROM but i dont know why the mount sdcard option is not working.
1) you were not on a 100% stock rom, so dont ever take a OTA
2) the mount sdcard will never work on this phone as there is no sdcard
3) do yourself a favor and follow this (it even has a section on how to root your phone): http://forum.xda-developers.com/showthread.php?t=1626895
Restore
Try this it has always worked for me and I have bricked my phone many, many times. I find this to be so much easier than all the other ways out there, but that's just me.
http://forum.xda-developers.com/showthread.php?t=1426207
Thanks for the help. I turned it back to stock and all good now.
Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!
Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?
Format /system under Mounts and Storage in CWM and reflash ROM and GApps?
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good
Hello Everybody
I hope you can help me with my first Androidproblem.
I installed rootprivileg on my Tab by flashing Custom-Rom with Odin etc.
Everything was working fine after that. Super-SU was working and i was root and was able to change CPU-Settings and everything else. Now my problem. Since i am a Technerd and always want to learn more, i wanted to restore the system to default to have a clean device. I made a backup with Kies which worked fine (Windows 10). Then i went to the Settings menu on my tab and choose the reset option. Than the screen went black. Since then Android is only booting into CWM-Mode and the Tablet is not recognized anymore by Kies when i connect it via USB-Cable. It is recognized as a USB-Device by Windows but i cant restore the backup on the tablet.
When i press the powerbutton the tab always reboots in CWM-Recovery v. 6.0.4.8.
What can i do to solve the problem? Thank you very much for your help.
I really need it.
Naturestone said:
Hello Everybody
I hope you can help me with my first Androidproblem.
I installed rootprivileg on my Tab by flashing Custom-Rom with Odin etc.
Everything was working fine after that. Super-SU was working and i was root and was able to change CPU-Settings and everything else. Now my problem. Since i am a Technerd and always want to learn more, i wanted to restore the system to default to have a clean device. I made a backup with Kies which worked fine (Windows 10). Then i went to the Settings menu on my tab and choose the reset option. Than the screen went black. Since then Android is only booting into CWM-Mode and the Tablet is not recognized anymore by Kies when i connect it via USB-Cable. It is recognized as a USB-Device by Windows but i cant restore the backup on the tablet.
When i press the powerbutton the tab always reboots in CWM-Recovery v. 6.0.4.8.
What can i do to solve the problem? Thank you very much for your help.
I really need it.
Click to expand...
Click to collapse
Read the last post of the CWM thread.
Sent from my SM-G920V using Tapatalk
Could you please sent me a link to the CWM-Thread, so that i know with thread you mean? That would be very friendly.
I think i got the idea for solving the problem, but after reading for 8 hours on xda i feel like i am blind. So many different roms....so many ways to handle it. I am confused.
I would like to install the Una T111-Rom which also seems to work with the T110 Tab. But there is a big problem: Since i dont have access to my sd-card anymore i cant copy the rom in the backup-folder on the sd. I could take the sd-card out of the tab if i would find the adapter to the bigger format SD-Card, then i could put the card in my notebook and copy the file in the right directory. Maybe it would work then and i have a nice safe googlefree Tab.
Thank you very much for your kindness
Maybe using Adb is an option?:fingers-crossed::
I hope i have a solution now. I will try to install the Criskelo-Rom (although i am not a big fan of the dark colors in there) with Odin. I hope it works....because its starting to get intense....for a newbie like me.
Hello everybody
After having a constant bootloop in the CWM-Recovery i now managed to flash TWRP v.2.7.0.1 and it works. At least i boot into TWRP instead of CWM now. Its the TWRP-Version of SELinux and i cant access the kernels content, it says. What would be the next step? I can access my data on the (wiped) sd and main partition now but i still dont have the possibility to install the rom i would like (Criskelo or Stock NE4lite for T110) because i cant get it on the sdcard. I would really like to get back in the Androidbootup of my Tab...
Please help me out. I really need your experience with this. It took me 24 hours and a lot of reading, downloading etc to get to this point.
Thank you very much.
Very beautiful TWRP-Interface bye the way. Very impressive.
It says: Kernel does not have support for reading SELinux contents.
Hello guys
Keeping you up to date. I am smarter now...
I flashed the device with this custom-rom: T110UEUANE4. I transferred this file to my sdcard using ADB and then installed the Rom. Worked perfect.
Great Tutorial: https://www.youtube.com/watch?v=VTGIAzofZCM
After rebooting i was hoping it would boot into Android, but it didnt. It booted into the TWRP and the screen flickered.
So i flashed again with this one: Philz Touch Advanced CWM recovery
Here i had the problem that ADB didnt work, so i flashed back the TWRP 2.7.0.1
I would like to know why i cant boot into Android after i installed the Custom-Rom for T110.
Any help and suggestions are deeply appreciated cause i am learning fast but i am still learning.
Bye the way: Now i understand how you can get addicted to flashing. But it would be nice to be able to boot in the system again...
Many thanks for your help.
Naturestone said:
Hello guys
Keeping you up to date. I am smarter now...
I flashed the device with this custom-rom: T110UEUANE4. I transferred this file to my sdcard using ADB and then installed the Rom. Worked perfect.
Great Tutorial: https://www.youtube.com/watch?v=VTGIAzofZCM
After rebooting i was hoping it would boot into Android, but it didnt. It booted into the TWRP and the screen flickered.
So i flashed again with this one: Philz Touch Advanced CWM recovery
Here i had the problem that ADB didnt work, so i flashed back the TWRP 2.7.0.1
I would like to know why i cant boot into Android after i installed the Custom-Rom for T110.
Any help and suggestions are deeply appreciated cause i am learning fast but i am still learning.
Bye the way: Now i understand how you can get addicted to flashing. But it would be nice to be able to boot in the system again...
Many thanks for your help.
Click to expand...
Click to collapse
You need to install stock recovery. Then reboot. The first reboot will boot into recovery, then you should be able to boot into rom.
Sent from my SM-T310 using Tapatalk
Hello Everybody
I flashed my Tab successfully now with the custom-rom from mknrls. Many thanks for your work and your passion.:good:
Also i want to thank gr8nole for the keyword: Stock Recovery. Thanks for your files and your help.
The Tab is running well, except for the issue with the contacts - which is not such a big deal cause i use my Nokia N9 as a phone...not only as a phone... After flashing, it took me several days to "recover" myself from the loss of sleep.
I flashed the Tab 4 days ago.
My next Custom-Androidrom will probably be on my beloved N9.:good:
Maybe i will try to install UNA-OS on my Tab...i think i am becoming flash-addicted.
Sent from my SM-T310 using Tapatalk[/QUOTE]