Hello everyone,
I just installed cyanogenmod 10.2 stable rom in my skyrocket. After install mobile was booted but when I gave reboot that phone not showing anything after showing samsung logo . Any idea ? Used TWRP 2.6.3.0 touch recovery for install that Rom. Please help me. Thanks in advance.
jibon57 said:
Hello everyone,
I just installed cyanogenmod 10.2 stable rom in my skyrocket. After install mobile was booted but when I gave reboot that phone not showing anything after showing samsung logo . Any idea ? Used TWRP 2.6.3.0 touch recovery for install that Rom. Please help me. Thanks in advance.
Click to expand...
Click to collapse
well try to superwipe and install again..happend to me to and it fixed it..oh and for the future use CWM with CM
Sounds like the standard recovery issue but yours should be new enough. As mentioned, do a full wipe, if that doesn't work do another and try flashing using cwm. I haven't had a single issue with 10.2 yet, good luck!
I think twrp 2.6.1.0 has worked for some people or use cwm(philz I think) and flash from there. After that switch back to twrp 2.6.3.0.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Related
Hi,
I have currently 4.5 CleanRom, and I used TWRP to install it, but I want Jellybean on my phone, can I just use TWRP to install CyanogenMod 10 with it? or do I need another installer of roms like CWM Recovery?
thanks.
yching07 said:
Hi,
I have currently 4.5 CleanRom, and I used TWRP to install it, but I want Jellybean on my phone, can I just use TWRP to install CyanogenMod 10 with it? or do I need another installer of roms like CWM Recovery?
thanks.
Click to expand...
Click to collapse
of course you can, but if you're on a newer Hboot, you will need to boot the rom through fast boot with boot.img
but of course.
dustin4vn said:
of course you can, but if you're on a newer Hboot, you will need to boot the rom through fast boot with boot.img
but of course.
Click to expand...
Click to collapse
I already have TWRP installed and I know how to access it on fastboot, the only reason I asked why is because I have seen some rooms not working properly with CWM Recovery, so I didnt know if there was any problem the other way around with roms like Cyanogen.
Thanks!
your good to go with twrp, i recommend updating to twrp 2.3.1.0
Will the CM nightlies flash normally on the old hboot?
Sent from my Nexus 7 using xda premium
they should but if you have any problems go into bootloader and run this command "fastboot erase cache"
are you using twrp 2.3.1.0?
Bootlooping CM10 on Telstra One XL
Hey guys been trying to work this out for the last 20 hours.
Now i followed the very good guides to put TWRP on the phone that worked fine tried to load cm10 latest nightly rom on kept bootlooping. so decided to give another rom ago.
used viper and it worked fine.
wanted to try and get cm10 working
So i have twrp 2.3.1
And latest cm-10-20121102-NIGHTLY-evita.zip
i wipe system, factory default cache. and the other cache.
go and install the rom all looks good, wipe caches and reboot.. than goes to the cool cm10 logo and loops there for AGES like 30 mins than i power cycled it and tried over.
with no working cm10 there i looked around and followed a guide to fastboot a new boot.img on from out of the cm10 zip.
this looked like it was going to work but still reboot and bootlooping.
can anyone help please.
AnThraXau said:
Hey guys been trying to work this out for the last 20 hours.
Now i followed the very good guides to put TWRP on the phone that worked fine tried to load cm10 latest nightly rom on kept bootlooping. so decided to give another rom ago.
used viper and it worked fine.
wanted to try and get cm10 working
So i have twrp 2.3.1
And latest cm-10-20121102-NIGHTLY-evita.zip
i wipe system, factory default cache. and the other cache.
go and install the rom all looks good, wipe caches and reboot.. than goes to the cool cm10 logo and loops there for AGES like 30 mins than i power cycled it and tried over.
with no working cm10 there i looked around and followed a guide to fastboot a new boot.img on from out of the cm10 zip.
this looked like it was going to work but still reboot and bootlooping.
can anyone help please.
Click to expand...
Click to collapse
try this.
1.) Download the 10/27 build
2.) get the boot.img from this build
3.) wipe cach/dalvik and system
4.) install 11/2 nightly
5.) flash the 10/27 boot.img
6.) reboot
This worked for me, something with the 11/2 and 11/1 boot.img was keeping it from booting.
Good luck
yching07 said:
can I just use TWRP to install CyanogenMod 10 with it? or do I need another installer of roms like CWM Recovery?
Click to expand...
Click to collapse
I would only recommend TWRP with CM10, or any other ROM.
Problems with CMW are due to the fact that it never officially supported our device, and was just a port. TWRP has no such issues.
redpoint73 said:
I would only recommend TWRP with CM10, or any other ROM.
Problems with CMW are due to the fact that it never officially supported our device, and was just a port. TWRP has no such issues.
Click to expand...
Click to collapse
Ohh okok, great thanks, I already installed the TWRP 2.3 from goomanager, lets see if I get the courage to use cm10
yching07 said:
Ohh okok, great thanks, I already installed the TWRP 2.3 from goomanager, lets see if I get the courage to use cm10
Click to expand...
Click to collapse
You don't need courage to do that. You need patience, reading and common sense.. Good luck
Sent from my HTC One XL using xda premium
I recently rooted my LG Optimus one (2.3.3) using the superoneclick method. I then installed ROM manager and flashed the custom recovery successfully. After that, when I chose to boot into recovery, the device booted into standard recovery and formatted my phone. This has been happening ever since and I am unable to boot into custom recovery and am ending up formatting my phone again and again.
Also, when I flashed the custom recovery, ROM manager flashed CWM 5.0.2.0 (LGE optimus one (Old baseband)), but I have been told that my phone has the new BB as it is running stock 2.3.3. Please help me regarding this issue.
Also, I am unaware if this the right place to post this question. could the mods please move it to the right section if I am wrong ?
Thank You
ntraturownrisk said:
I recently rooted my LG Optimus one (2.3.3) using the superoneclick method. I then installed ROM manager and flashed the custom recovery successfully. After that, when I chose to boot into recovery, the device booted into standard recovery and formatted my phone. This has been happening ever since and I am unable to boot into custom recovery and am ending up formatting my phone again and again.
Also, when I flashed the custom recovery, ROM manager flashed CWM 5.0.2.0 (LGE optimus one (Old baseband)), but I have been told that my phone has the new BB as it is running stock 2.3.3. Please help me regarding this issue.
Also, I am unaware if this the right place to post this question. could the mods please move it to the right section if I am wrong ?
Thank You
Click to expand...
Click to collapse
try this the safest method
http://forum.xda-developers.com/showthread.php?t=2003080
Thank you. I'll try this. In order to run CM 10, is it necessary for my recovery to be from CWM? or is it possible to run CM 10 with an AmonRa recovery installed ?
ntraturownrisk said:
Thank you. I'll try this. In order to run CM 10, is it necessary for my recovery to be from CWM? or is it possible to run CM 10 with an AmonRa recovery installed ?
Click to expand...
Click to collapse
yes amonra will work
Thanks mate. Worked like a charm.
ntraturownrisk said:
Thanks mate. Worked like a charm.
Click to expand...
Click to collapse
just a favour comment on the main thread also
Hi,
I currently have ClockworkMod Recovery 6.0.2.3 installed and am using ROM Manager Premium 5.5.1.5 to attempt to install CyanogenMod.
I have the correct rom downloaded for the Verizon version, but every time I try to boot into the ClockworkMod recovery, the standard Android Recovery screen comes up instead.
I have followed about 3 different tutorials, and each ended in the same result.
Any idea what could be going on?
Thanks!
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Edgehood said:
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Click to expand...
Click to collapse
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
CAKELIE said:
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Click to expand...
Click to collapse
How did it fail?
Sent from my LG spectrum (that's right) blazing fast on cm10!
I am having almost the same problem. I rooted my phone using this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT6 - ZSLO2 Fixed for bootloop
ZCLSF (no bootloop fix, proper default.prop)
http://d-h.st/users/philz_touch/?fld_id=16061#files
taken from here: http://forum.xda-developers.com/showthread.php?p=31911620#post31911620
as it matches my phone make, build, kernel's date, model, etc. The trouble is when I go to recovery mode from ROM Manager it just stops on its way showing me this green little robot and a progress bar in the middle and it could stay like this for hours without moving anywhere. I have to press my power button and then it moves on and reboots into CWM. I have tried a whole lot of different rootings methods but ROM Manager v5.5.3.7 simply refuses to work with PHILZ-CWM6-DDLSC-ODD-5.06.1-SIGND.ZIP... I am completely lost...
Could anybody suggest / advise anything please? I would highly appreciate it Many thanks in advance!
I am on Android 4.1.2 Jelly Bean, Samsung Galaxy Note GT N7000, build number is JZ054K.N7000DDLSC, baseband version is N7000DDLS6, kernel version is 3.0.31 – 906407 March 6, 2013.
I have in the last couple days attempted to flash a new ROM but have been unsuccessful to do so.Currently I'm running 4.1.2 cm10 stable, I notice when I reboot to recovery in twrp that the updates I've downloaded or ROMs I flash are not being saved at all to my sdcard
I flashed ROMs and gapps from goo.manager rebooted to twrp nothing, I even tried downloading from cm10 directly and nothing,if somebody can guide me as to maybe what I can do to fix this thanxs in advance:fingers-crossed: hello out there in xda land ...... is it twrp or my SD card??
Datstonerguy7 said:
I have in the last couple days attempted to flash a new ROM but have been unsuccessful to do so.Currently I'm running 4.1.2 cm10 stable, I notice when I reboot to recovery in twrp that the updates I've downloaded or ROMs I flash are not being saved at all to my sdcard
I flashed ROMs and gapps from goo.manager rebooted to twrp nothing, I even tried downloading from cm10 directly and nothing,if somebody can guide me as to maybe what I can do to fix this thanxs in advance:fingers-crossed: hello out there in xda land ...... is it twrp or my SD card??
Click to expand...
Click to collapse
Anyone:crying:
Hi,
i'm using the official CM 11 on my XT925 and pretty much installed every new Nightly - never had any serious Problems, not even with Bluetooth (i get no Track in the Display, but at least it works ).
Since the 01.07.2014 Nightly i can't install the Nightlys anymore, because it wants a KK/ Kernel 3.4 compatible Bootloader. First, i flashed the new TWRP 2.7.1.0. Didn't work, very strange Problem (see below). So then i tried the new CWM 6.0.4.9. Also didn't work... same error message as with CWM 6.0.4.4 (which I used until now) - "no KitKat Compatible recovery detected". So I tried philz touch recovery. Also doesn't work.
Now i'm back with the 30.06.2014 Nightly.
Now the strange part: TWRP didn't recognize any touch inputs at all, I had to hard-reboot the phone. Also Philz touch recovery didn't recognize any touch inputs. CWM 6.0.4.4 hat the "Swipe-Touch" thingy, which I used, but it seems that CWM 6.0.4.9 also doesn't recognize any touch inputs! I can't swipe.
So the big questions are: What the hell have I done wrong, that no Recovery is not recognizing any touch inputs anymore?! Flashed it with fastboot, everything looked ok, only got an "ERROR: could not get pipe properties", but it flasehd it and it worked - apart from the touch.
It wouldn't even be such a big "bother" if the new CWM could install the new CM Nightly... Am I really stuck with 30.06.?
greetings,
David
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, to install new nightlies we have to flash the KK OTA first, right?
TYG
pbosio said:
So, to install new nightlies we have to flash the KK OTA first, right?
Click to expand...
Click to collapse
Take a look HERE.
If I were you I'd wait for the official kk bootloader....if you read the previous post the method being used is risky for our model.
Sent from my RAZR HD using XDA Free mobile app