Hello,
I don't get Clockwork Recovery to run on my 64gb tablet (ROW, thanks to realyst2k: http://forum.xda-developers.com/showthread.php?t=1471106 )
I did everything like explained and tried it several times. But after rebooting, the tablet freezes during "Booting recovery kernel image". With the power button I can boot into android normally and restore the factory recovery.
Did CWR work for anybody on a 64gb tablet? I did not find any post saying so.
Has anybody an idea what the problem may be?
(Sorry to post this as a new topic, I'm not allowed to write in the developement forum.)
CWM install worked flawlessly for me and is still running great. Wish I could help more.
I think I figured out what the problem is: my tablet is a WE build, not ROW. Is there a chance to get CWR for WE tablets?
lump1988 said:
I think I figured out what the problem is: my tablet is a WE build, not ROW. Is there a chance to get CWR for WE tablets?
Click to expand...
Click to collapse
The US version also works with WE
Thank you very much, now it works
Excellent news!
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
destructo322 said:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
Click to expand...
Click to collapse
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Mac of York said:
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Click to expand...
Click to collapse
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
destructo322 said:
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
Click to expand...
Click to collapse
You can flash the kernel separately and it'll be fine.
Sent from my Nexus 7 using Tapatalk HD
Hi,
I've quite a problem with setting up ubuntu on MultiROM. I've got the required kernel installed. The roms are installing properly. Just when I want to boot it, there shows the google icon twice and then goes back to MultiRom. I tried to install ubuntu desktop (newest) and ubuntu touch, always with the same result.... Any idea how to solve this?
I believe that's rather MultiROM problem because I have the same problem with BodhiLinux... Can previous using linuxonandroid affect MultiROM?
Are you sure you are using the correct kernel and flashed Ubuntu through the correct modified recovery?
I'm not sure, what was wrong... I installed everything twice again (first time it didn't work) and ubuntu installed and booting (still not working correctly, but that is always something ) Anyway, thank you for your answer without it I wouldn't have motivation to do it the second time.
Lol you're welcome
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?
Hey
I am a problem with my S4, GT9505
I use the latest CWM 6.0.3.6.
I use the CM nightlies since 10.1 and I used 10.2 since 3 weeks, today I just flashed to the latest nightly 2013-09-13
The phone does sporadically not boot completely. Sometimes it hangs at the Samsung logo screen, sometimes it restarts while booting. This happens every 2nd or 3rd booting time.
Is this a problem of CM?
Thanks
any ideas?
I just read here, that it is a known issue
http://forum.xda-developers.com/showpost.php?p=45658424&postcount=2955
but is there a fix?
does anyone know if there is a fix for this bug?
I installed the nighlies 09/25
but my phone still does not boot up every 2nd time
MasterBrush said:
I installed the nighlies 09/25
but my phone still does not boot up every 2nd time
Click to expand...
Click to collapse
Correct, it's a recovery thing, not Rom/kernel related.
Pfeffernuss said:
Correct, it's a recovery thing, not Rom/kernel related.
Click to expand...
Click to collapse
Ok so is this a bug from CWM 6.0.3.6.?
I now updated to CWM 6.0.4.4.
MasterBrush said:
Ok so is this a bug from CWM 6.0.3.6.?
I now updated to CWM 6.0.4.4.
Click to expand...
Click to collapse
So, the problem is gone?
same problem with CWM 6.0.4.4.
MasterBrush said:
same problem with CWM 6.0.4.4.
Click to expand...
Click to collapse
Yup, same here... Randomly you're just staring at a black Samsung screen and nothing further happens