[Q] CM 11+ not flashing? - T-Mobile, Samsung Galaxy SIII

Hello! I'm new to the forums here. I have a T-Mobile Samsung Galaxy S 3 LTE (T999L) that i have rooted, (root 66), flashed custom recovery, ClockworkMod recovery (v6.0.4.5) and have installed CM 10.0. However when i downloaded CM 11, it wouldn't flash, I looked it up and found I needed to change the files by deleting all the Assert lines in the updater script, so I did, and compressed it, loaded it to my SD card and tried to flash it. (System wipe,wiped cache, dalvik ect...)
CWM gave me a Installation aborted. So I looked at the CWM log and it said: "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
I don't know what to do from here, so if anyone can point me at the right direction that would be great. I'm like 20% sure that it's the kernel, but like I said, I'm not that sure. I have rooted 3 devices with no problems but I have never really run into this before.

You should wipe cache partition, wipe dalvik cache, and reset data in Recovery. And then try flashing the new CM 11 ROM. Make sure it's compatible with your Phone.
If this fails then I recommend using Odin3 to flash to stock touchwiz ROM for your Samsung (getting the .md5 file or .tar ROM). Followed by wiping cache partition, wiping dalvik cache, and resetting the data in Recovery. Then flashing CM 11 in recovery by installing the CM 11 zip specifically for your phone.
Let me know the follow up.

Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...

Gravitylog said:
Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...
Click to expand...
Click to collapse
Try using different recovery. Try them all philz touch, TWRP, and Clockwork.
Sent from my SM-N900T

Gravitylog said:
Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...
Click to expand...
Click to collapse
I suggest stop using CWM (ClockworkMod recovery) simply because it's outdated. Please use TWRP. If you still have issues with the ROM then please check if you have the latest bootloader for your model to resume trying.

Related

[Q] HTC Desire HD 4.2.x ROM Process Stopped Help

Current ROM JellyTime - http://forum.xda-developers.com/showthread.php?t=1827590
Rom Manager v5.5.1.5.
Current Recovery ClockworkMod 5.0.2.0.
So I use Rom Manager to reboot into Recovery, where I wipe dalvik-cache, cache partition and data/factory reset. I then flash the zip, followed by gapps
Tried the following ROMS
http://forum.xda-developers.com/showthread.php?t=2003273
http://forum.xda-developers.com/showthread.php?t=2073992
GAPPS
http://goo.im/gapps - I used the top one CyanogenMod - 10.1.x - 4.2.1.
When booted, I get two messages, press OK and they both continue to appear
"unfortunately system ui has stopped"
"unfortunately, the process com.android.phone has stopped"
It appears as I have only just signed up, I cannot ask the Devs direct. I have searched through threads, and can see some others with same problem - no solution though. About to try a dirty flash from Jellytime.
Thanks
Dave
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
wiping
hdorius said:
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
Click to expand...
Click to collapse
I wipe dalvik-cache, cache partition and data/factory reset - is this not enough?
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
hdorius said:
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
Click to expand...
Click to collapse
Ok so, CWM "Wipe Menu" :
wipe dalvik-cache
wipe cache partition
wipe dalvik cache and cache partition
wipe battery stats
wipte data/factory reset
Try to
wipe data, cache and dalvik again
then manually (in the advanced menu if I recall correctly):
format boot
format system
<...> (everything except sdcard)
I've taken a look, and nothing relating to formatting is under Advanced.
Under Mounts and Storage Menu however, there is the following:
unmount /cache
mount /data
unmount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
mount USB storage
Yep there.
format /cache
format /data
format /system
-SmOgER said:
Yep there.
format /cache
format /data
format /system
Click to expand...
Click to collapse
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
davestar7 said:
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
Click to expand...
Click to collapse
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
yumm91 said:
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
Click to expand...
Click to collapse
I flashed just the ROM by itself, and booted up with the same two errors
davestar7 said:
I flashed just the ROM by itself, and booted up with the same two errors
Click to expand...
Click to collapse
Thats weird.. if you have already format everything except sdcard, and flash the rom only, and still got the same problem, then the cause is either from the cwm,which is quite outdated, or the rom itself.. but i doubt the rom is the culprit... try use ext4 recovery or update the latest cwm.. or maybe wait for someone who have a better solution..
Sent from my Desire HD using xda app-developers app
sashank said:
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Try to remove SD card. Just in case, as it all seems a bit mysterious.
davestar7 said:
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Click to expand...
Click to collapse
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
yumm91 said:
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the replies, sorry I was busy over the weekend.
I tried booting 4.2.x with no SD, and same error occurs.
I am not interested in trying 4EXT, CWM is a widely used custom recovery I can't see why this could be at fault? I am running the latest version, though not the "touch" version!
Can't find anyone else with this issue!
BTW - I am S-ON?
Any further help or advice on this one?
Thank you.
I would try 4ext. CWM has had some problems on thus phone in the past. Also, if you are S-ON, are you fastboot flashing the boot.img? Check the Ace Think Tank thread in the General forum for a guide on how to do that. Though usually, not doing that results in a phone that hangs at the splash screen, not one with systemui stopping...

An odd situation please help?

Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean
sean82007 said:
Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean
Click to expand...
Click to collapse
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3
So....
joeyhdownsouth said:
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3
Click to expand...
Click to collapse
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.
sean82007 said:
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.
Click to expand...
Click to collapse
I think you need to flash both of them over.
message brought to you by my GalaxyS3
Make a backup, ODIN back to stock rooted, then reflash recovery and restore
CNexus said:
Make a backup, ODIN back to stock rooted, then reflash recovery and restore
Click to expand...
Click to collapse
I was gonna tell him that, but I figured with all the issues he was having, it was better to start from scratch.
message brought to you by my GalaxyS3

Wiping data reboots phone

rom: 4.4 aokp
kernal: ktoonz
Hey guys, i need some help. i encountered a strange problem when flashing to a new rom from 4.4 AOKP. Before the problem happened, when entering recovery, it said:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
i wiped cache, reboot phone and it was gone. however, when proceeding to wipe data to flash new rom, the phone would reboot. managed to somehow fix the problem by restoring to a previous backup. backup went through but rebooted during data restore. everything was broken so went back to recovery and wiped data. this time wipe data worked, everything seemed fine so i thought. So i flashed cm11 m6, realized it was too bare for me, so i once again go back to recovery and wiped data to flash a new rom. it happened again. phone rebooted during data wipe.
im guessing i will have to odin back to stock to fix this problem. Last time i needed to use odin was at md5, so im a little rusty on some of the information about this knox thing. Using root66 version of UVUENC2 wont cause any problem for me correct? i will be able to still flash custom roms correct? odining to stock will not wipe my internal sd card correct?
Odin will not wipe any user data. But if coming from cm/aosp you will have to factory reset. (Reset from stock recovery does wipe internal sd. From cwm/twrp internal sd is preserved).
You will trip the warranty bit if you flash recovery after updating to 4.3. This only matters if your device is still under warranty or if you care about it. Otherwise Knox is removed from all root66 and custom roms.
Sent from my SGH-T999 using Tapatalk

[Q] Is my device bricked? Is there how to fix? Help me, I desperately need your help

I was trying to install android 4.4 (kitkat) on my T-Mobile Samsung Galaxy S III (SGH-T999L) and accidentally deleted the back-up I had just created. While trying to flash the new ROM, I get the "status 7" error. I also tried the "toggle signature verification", but still the same error. In the tutorial of how to make it I had followed the instruction and had, perhaps as mistake now, formatted all data on the CMW menu (cache, system, data/factory reset, dalvik cache) I had my device hacked, and previously installed Clockwork 6.0.4.5.
I am stuck on boot screen.
My flash count says 5?
I do not know if this helps address any further help, but in the mount/unmount menu I have;
cache is mount
system in not mount
data is mount
storage/sdcard1 is mount
Flash your firmware with Odin. Should take care of that.
Thanks. Working now. Seems like I installed the kernel? And it worked.
Sent from my SGH-T999 using XDA Free mobile app

Omni update to CM11 failed

I can't update my N7100 from previous Omnirom to latest CM11. I wiped my phone, installing latest CM11 zip and phone is stuck at N7100 logo and restart to recovery. When I install Omni zip everything is working fine. I'm tried TWRP and Philz recovery but no results. Please help
did you wipe /system, /cache, /data and dalvik? (full wipe).
atmos929 said:
did you wipe /system, /cache, /data and dalvik? (full wipe).
Click to expand...
Click to collapse
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
emlo16 said:
Yes of course but I think CM isn't extracting to /system because when I leave recovery it shows there's no root and asks if I want to install it.
Click to expand...
Click to collapse
Recoveries tend to do that... they do not detect superuser from any CM based ROM and offer you to install supersu after a ROM install and rebooting system.
I you do full wipes and you have tested latest Philz and TWRP recoveries... I can only suggest you to double check that the CM11 ROM is the correct one for your N7100.
It is strange that you encounter issues with CM based ROMs... these usually install without problems... I've encountered problems booting TW based ROMs, but not these. Sorry I can't be or more help. Good luck .
EDIT:: wait a second... according to your screenshot, you did a full wipe after installing the CM ROM... you are deleting your ROM that you just installed . The steps are:
1.- full wipe
2.- install ROM
3.- Install GAPPS
4.- wipe Dalvik <-- (some devs recommend this step, others don't... doesn't hurt to do it anyway)

Categories

Resources