CloudyG2 2.2 on JB Bootloader? - General Topics

This is a general bootloader question, CloudyG2 is irrelevant. (Bad title choice by me)
I bought my LGG2 D802 last year, rooted it as soon as I got it and installed TWRP and CyanogenMod 10 Stable which put me onto the KitKat firmware, but I do believe I was on the JellyBean firmware before hand since when I go into custom recovery I have to push the power button 3 times. I've heard that you can determine your bootloader by how you access custom recovery,
is this correct?
A few months later I am now on the CloudyG2 2.2 Rom and loving it but have some concerns about my bootloader still being
at JellyBean.
My question is: Will leaving my Bootloader as JB effect my experience with my fully functioning CloudyG2 2.2 Rom running
with 4.4.2? and how will this effect my devices stability? (as I might contemplate changing kernel in the future).
It's just a curiosity question as I'm not very confident when it comes to Bootloader versions since every ROM I flash just seems to work, "seems" being the key word.
Thank you to anyone who takes the time to respond to my thread.

Related

[Q] 4.3.3 Update Issues (Firmware, Software, Stock Recovery, etc.)

Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
The phone with the red triangle is what you are supposed to see. When you see that, you need to hit Vol-Up + Vol-Down and Power and it will take you into recovery. With that, you should be able to do the OTA to 4.4.3. I'm not sure if you need to flash the 4.4.2 firmware first or not. You can give it a try. If it fails then go ahead and flash back to the 4.4.2 firmware from Tigerstown's thread and try it again.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
SCrosler has posted a stock rooted 4.4.3 ROM. If you flash that you will all up to date (or you could flash Viper 2.4 or NuSense 2.0) essentially flashing any 4.4.3 ROM will get you where you want to be.
Here is the link to the stock, rooted ROM: http://forum.xda-developers.com/ver...m-stock-rooted-vzw-ota-2-21-605-2-wp-t2874699. With your updated firmware and that ROM you will be stock, and up to date on 4.4.3
@BladeRunner & @jsaxon2, thank you very much for your replies and the help. Looks like this was covered to some degree, and has answered my questions.
Going to try dirty-flashing the ODEX rom. I want to flash Viper pretty badly, but don't want to have to wipe everything right now. When Android L comes out, that will be fully worth starting from scratch. I have just enough patience to wait.
Will confirm shortly that everything has worked.
FYI, dirty flash of the ODEX (just wiped cache/dalvik, left data alone) worked perfectly. Software is now reading 4.4.3. Thanks to @scrosler for the stock ROM!

Why upgrade to 4.4.4?

I'm currently on rooted 4.4 (19.5.3), and I'm debating whether to flash to 4.4.4 or wait till Android L is released. I'm still on locked bootloader and I'm not in a hurry to unlock it via Sunshine if I'm staying with 4.4. Sunshine is great BTW, unlocked the wife's Moto X with it. But even with her phone, I kept it on 4.4.2 to stay on the older bootloader because the way I understand it, once you upgrade to 4.4.4, you will not be able to downgrade to anything lower. So, my logic is, keep it on 4.4, locked, until the landscape is clear unless there are real compelling reasons to unlock and upgrade now. So that is the question, are there any advantages to upgrading other than security and other small improvements? I've flashed the 4.4.4 radios and it didn't improve my reception at all, if anything, it made it worse! It switches to 3G at the house a lot where it used to stay at 4G but I don't care since I'm on wifi. The only thing I really want is the KK dialer which 4.4.4 does not have. I've also switched to the AOSP email apks which I love. Other little interface changes were applied with GravityBox and other Xposed modules. I'm pretty happy where the phone is, what are you guys' thoughts?
Here is the change log you should weight against; https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/100660
I know the bluetooth issue was enough for me to upgrade, finally fixed that issue. Not sure but don't you have to upgrade to this version before upgrading to the next version, if it is L or not?
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Johnny Wong said:
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Click to expand...
Click to collapse
Well if you unlock your guaranteed root regardless of any updates
IMHO, I would just hang off updating to 4.4.4. Here's why:
1. If you change your mind, you can unlock the bootloader and that is rarely a negative thing.
2. You can root your phone and flash custom recoveries. Having root permissions gives you unbelievable control and customization. Custom recoveries will definitely save you some unnecessary grief in case you make a mistake. It's very hard to brick your phone with a good recovery like TWRP or CWM.
3. You can flash Android L based ROMS which I'm sure will be coming out soon. ASOP, AOKP and stock unbloated ROMS give your phone a brand new life and a bit more battery life.
You can just unlock your phone's BL and stay in 4.4, just like now...
Johnny Wong said:
Thanks for that link. What was the Bluetooth issue in your case? I've Bluetooth'd to my cars just fine. I don't know if 4.4.4 is an prerequisite for Android L, but I've read that it has a new boot loader that can't be downgraded. So if I felt like trying a JB ROM capable of overclocking, I'm out of luck. Not that I would go that route, I really like KK. Just wished it was closer to stock like the Moto X. Which as Topsnake pointed out is a good reason to unlock boot loader to flash his ROM. LOL. I think the bottom line is, I want to wait so I don't close off doors like the guys that upgraded to 4.4.4 before Sunshine came out did.
Click to expand...
Click to collapse
Yes you are correct, once you move to 4.4.4 you cannot go back due to the new boot-loader not being backwards compatible. My Bluetooth issues were with any Bluetooth device it would constantly blip randomly via my car or anything connected via Bluetooth. Moto pushes out the updates to devices in order (i.e. you have to go from 4.2 to 4.4 to 4.4.4 to L), but if you obtain the update files manually you may be able to skip 4.4.4 and go straight to the next one (if that even is L or not), but that is a big maybe.

[Q] supersu and simcardchanger.apk survived after lolipop flash?

Hello, someting really weird (for me) happened on my nexus 5. I was running stock 4.4.4 rooted with elementalx kernel, and i decided to return to stock and flash android lolipop. (I used this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)
I firstly flashed 4.4.4 stock just to be sure there wont be any complication with the kernel change.
after that, i flashed lollipop according to the guide above.
after i locked the bootloader and opened the phone i saw something strange, an icon in the app drawer named ''SuperSU installer'' . it was a system app and i couldnt even uninstall it, but i could only disable it.
Also, in the past, i had used the ''simcardchanger.apk'' (http://forum.xda-developers.com/galaxy-s3/themes-apps/app-sim-changer-change-registered-sim-t2106490), to put my phone number in the ''about'' section of my phone because it was marked as ''unknown''. my phone number was still there after the flash of the new ROM (!)
How could these 2 survive the flash of 2 ROMS?
Is there anything i can do to return my phone to complete stock without even ''simcardchanger'' marking my phone number in the about section of the settings??
[PS: i am now running lollipop stock, unrooted and locked bootloader.]
i would appreciate if any of you is bored enough to solve this question. Thank you.

4.3 1535 - vrucml1 - Custom ROM

Hi Experts,
I'm trying to load a custom ROM.
I did the useless hting of OTA update of the 4.3
I did this ROM Changing thing long back and I even once bricked my Phone.
I have to go to a local store and get it fixed.
SO I don't want to do that mistake once again.
I have Alliance ROM, and my chances are a lot limited, if my Booklooader is Locked or something.
Can anyone please let me know if anyone found out a way to unlock the bootloader, or we don't have any options other than to go for the 3-4 ROMS that are available??
Thanks a lot for Your help.
qzmpal said:
Hi Experts,
I'm trying to load a custom ROM.
I did the useless hting of OTA update of the 4.3
I did this ROM Changing thing long back and I even once bricked my Phone.
I have to go to a local store and get it fixed.
SO I don't want to do that mistake once again.
I have Alliance ROM, and my chances are a lot limited, if my Booklooader is Locked or something.
Can anyone please let me know if anyone found out a way to unlock the bootloader, or we don't have any options other than to go for the 3-4 ROMS that are available??
Thanks a lot for Your help.
Click to expand...
Click to collapse
Bootloader is not unlocked if you are on the official 4.3 OTA or higher. And most likely no one will ever find a way to unlock it. You are restricted to using one of the safestrap compatible ROMs.
I realized that the 4.3 Bootloader cannot be unlocked.
But when I'm trying to load a ROM, basic things are not working.
My basic doubt is, if anyone upgrades to 4.3, will the most basic 2 features in the phone,
1. making calls and
2. Wifi,
Will they work or not?
I'm confused here.
But my experience with Alliance ROM is the worst.
Worst Support, Very few users, useless ROM, FULL OF COMPLICATIONS.
qzmpal said:
I realized that the 4.3 Bootloader cannot be unlocked.
But when I'm trying to load a ROM, basic things are not working.
My basic doubt is, if anyone upgrades to 4.3, will the most basic 2 features in the phone,
1. making calls and
2. Wifi,
Will they work or not?
I'm confused here.
But my experience with Alliance ROM is the worst.
Worst Support, Very few users, useless ROM, FULL OF COMPLICATIONS.
Click to expand...
Click to collapse
The dev provided 2 years of support from preorder to early/mid 2014. There aren't many Verizon S3 users left, it is a 2+ year old phone and Samsung has made this phone increasingly more difficult to mod as time passed. Those of us that are able to help, basically help blindly because we don't have locked bootloaders on our phones. Your anger should be directed at Samsung not us.
Now, with any VRUCML1 rom installed using Safestrap you have two options:
1) Flash the VRUCML1 rom, choose stock VRUCML1 kernel, then flash the VRUCML1 kernel modules to enable wifi. VRUCML1 kernel modules are in the Safestrap thread. Failing to flash the kernel modules will leave you with no working wifi.
OR
2) Flash the VRUCML1 rom in Safestrap and choose Safestrap kernel. Then boot into the rom and see if wifi works without flashing kernel modules.
If you took the VRUCNC1 4.3 OTA, you need to do a lot more work because none of the above will enable wifi for you at all. Lastly to answer your question, yes Samsung crippled this phone to the point that users will have no working wifi if they do not flash the kernel modules for their respective OTA BEFORE booting into the rom.

Migrating from one M8 to another - sanity check

Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings

Categories

Resources