Database Info

[Q] Updating to kitkat

I tried updating android 4.4.2 KitKat based CM11 ROM but get stuck at the boot logo after the hole updating process, try to wipe the phone after installation multiple times, but nothing work.
I followed the next steps: http://true-android.blogspot.com.ar/2013/12/update-at-galaxy-s2-skyrocket-sgh-i727_17.html
But, in this post: http://forum.xda-developers.com/showthread.php?t=2562055&nocache=1
i read that i need CWM version 6.0.4.4, but the rom manager only update til 6.0.4.3
That would be the problem??? How can i update the cwn?
I just learn about roms, and custom android so everything its really hard to understand by my own (just new... so new that i used to had for 2 years my phone with factory OS til yesterday
Thanks in advance

Read the stickies and don't use Rom manager
Sent from my HTC One using Tapatalk

What are the stickies?
Thank you

moltis said:
What are the stickies?
Thank you
Click to expand...
Click to collapse
Stickies are posts that are generally considered extremely useful so they get "stuck" at the top of the list in the forums, so they are seen first and can resolve peoples questions without much looking. Like http://forum.xda-developers.com/showthread.php?t=1785999 . From personal experience I'd recommend using PhilZ touch recovery. It's done the trick for me so far. http://forum.xda-developers.com/showthread.php?t=2557024

Thanx Cyndar, tried with philz touch, but the same.. still loops... and cant find anything in the stickies. I think to just stay with 4.3
so... who needs google now?
Thanx again

moltis said:
Thanx Cyndar, tried with philz touch, but the same.. still loops... and cant find anything in the stickies. I think to just stay with 4.3
so... who needs google now?
Thanx again
Click to expand...
Click to collapse
imo stay with stock or whatever you got working until you read some more, youre a brick waiting to happen or a newb with questions that have been repeatedly answered.
trying reading this sticky to start |Read This b4 posting | THE MOST Common Questions Answered HERE |

moltis said:
Thanx Cyndar, tried with philz touch, but the same.. still loops... and cant find anything in the stickies. I think to just stay with 4.3
so... who needs google now?
Thanx again
Click to expand...
Click to collapse
Google now is in 4.3. Stop messing with your phone until you know what you're doing.
Sent from my HTC One using Tapatalk

moltis said:
I tried updating android 4.4.2 KitKat based CM11 ROM but get stuck at the boot logo after the hole updating process, try to wipe the phone after installation multiple times, but nothing work.
I followed the next steps: http://true-android.blogspot.com.ar/2013/12/update-at-galaxy-s2-skyrocket-sgh-i727_17.html
But, in this post: http://forum.xda-developers.com/showthread.php?t=2562055&nocache=1
i read that i need CWM version 6.0.4.4, but the rom manager only update til 6.0.4.3
That would be the problem??? How can i update the cwn?
I just learn about roms, and custom android so everything its really hard to understand by my own (just new... so new that i used to had for 2 years my phone with factory OS til yesterday
Thanks in advance
Click to expand...
Click to collapse
If you are trying the nightly ROMs, they have a known issue loading for the past few releases. Go back and find a Jan20-something nightly and give that a shot. Again...there are known boot loop issues with the nightly ROMs starting Feb1.
http://forum.cyanogenmod.com/topic/87521-problem-with-feb-1st-nightly-build/

moltis said:
I tried updating android 4.4.2 KitKat based CM11 ROM but get stuck at the boot logo after the hole updating process, try to wipe the phone after installation multiple times, but nothing work.
I followed the next steps: http://true-android.blogspot.com.ar/2013/12/update-at-galaxy-s2-skyrocket-sgh-i727_17.html
But, in this post: http://forum.xda-developers.com/showthread.php?t=2562055&nocache=1
i read that i need CWM version 6.0.4.4, but the rom manager only update til 6.0.4.3
That would be the problem??? How can i update the cwn?
I just learn about roms, and custom android so everything its really hard to understand by my own (just new... so new that i used to had for 2 years my phone with factory OS til yesterday
Thanks in advance
Click to expand...
Click to collapse
1. Download UCMC1 modem and install it
2. Go into CWM Philz thread and use Odin to install it
3. Flash your rom.
I did it with AOSB (amazing work) but had problems with PA GAPPS flashing, so i took the gapps zip from the Avatar rom and it's been working extremely nicely. As an added touch by suggestion from another user, I flashed the Uber Kernal on top of it after.
But like the others said, seriously, slow down and read the instructions rather than jumping around and accidentally screwing something up

[Q] Question about Samsung Galaxy S II Skyrocket SGH-I727

Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:

svvparakala said:
Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:
Click to expand...
Click to collapse
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.

Thanks!
SighIsAnonymous said:
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.
Click to expand...
Click to collapse
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)

svvparakala said:
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)
Click to expand...
Click to collapse
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.

Md5 Checksum?
SighIsAnonymous said:
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.
Click to expand...
Click to collapse
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:

svvparakala said:
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:
Click to expand...
Click to collapse
I usually don't check it. You did it all wrong though. There's a few ways to check the MD5, either through busybox on the phone or a app on the computer. Don't worry I thought the same thing you did when I started.:laugh: But here's a great thread with more information! http://forum.xda-developers.com/showthread.php?p=17065076 Personally though if you are sure you download the file correctly you should be good. Also most the time if something is wrong CWM Will tell you and not even let you flash it. Check that thread though it could maybe clear some things up for you.:angel:

CM11s OTA and Custom Recovery

I'm sorry for posting the same question in two different places (at the OnePlus forum and here).
It's not that I am impatient, but it's just so hard to get any straight answers over there.
Maybe someone here can help with this...
Well my device arrived yesterday and so far it is working very well.
I did the first OTA before doing anything else to the device and it went without any problem.
The only thing that really bothers me is that a couple of people wrote that they bricked their device after the OTA, when the device was unlocked and had a custom recovery installed (and was rooted, eventhough I don't think that could cause any problems).
So the question is, and I think it is a really important one...
Do CM11s OTA updates work with a custom recovery installed (twrp in my case)?
Should people flash the original, stock recovery via fastboot if they want to use the CM11s OTA update service?
And if that is the case...It is recommended, for people who do not want the stock recovery, to just go ahead and flash the the CM11 nightly (regular CM), to not receive any OTA updates?
I would really appreciate an answer to these questions.
Thanks in advance.
Ps. The problem was already mentioned at the cyanogen forum (and a couple of other places), but didn't get an answer.
http://forum.cyanogenmod.org/topic/97186-hard-bricked-oneplus-one/
Click to expand...
Click to collapse

[armitage] said:
I'm sorry for posting the same question in two different places (at the OnePlus forum and here).
It's not that I am impatient, but it's just so hard to get any straight answers over there.
Maybe someone here can help with this...
Click to expand...
Click to collapse
As far as I know, you won't be able to get OTA's with a custom recovery.
kudos

I did ota with custom recovery.Just uncheck update cm recovery in developer options
Sent from my One using XDA Premium 4 mobile app

[Q] Deleted system, only TWRP left.. what now?

Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!

Exactly which zip files are you trying to flash? What are the filenames?
Transmitted via Bacon

use a toolbox and an option to flash to stock

gfusion said:
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Click to expand...
Click to collapse
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future

Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
playya said:
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Click to expand...
Click to collapse

gfusion said:
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
Click to expand...
Click to collapse
Here's a hint. Fastboot IS how you flash a new room for the first time had you not used the tool kit you would have seen this and done it that way lol

What is the most recent version of OOS that TWRP works (well) with?

I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you

You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.

RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.

didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers

RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.

didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10

RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*

didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.

RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.

Starting to think I have a learning disability, lmao. Wish I was joking.

I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...

caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.

@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.

Thread moved to proper section

didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...