[SOLVED]Bootmenu Confusion, oh no!!! :O - Motorola Droid RAZR

Alright, hopefully the ridiculous title helped to draw you in...
Anyways, so I was running the unofficial MIUI for my GSM Razr until the official release came out. I installed an OTA ICS and Bootmenu. I installed the hijack and the new recovery, and didn't change any settings in the app. I then booted into the new recovery. I toggled into the 2nd system and installed MIUI. Upon boot, it got stuck on the MIUI logo for 10 mins. I did a hard-reset and tried again, same thing. I then booted into the standard recovery menu and did a factory reset and rebooted. Miraculously, this time it booted up and MIUI is running perfectly now.
Okay, now I downloaded Bootmenu again, and now my MIUI is labeled as my "stock system". I'm perfectly okay with this, the only thing I'm wondering is what happened to my original stock ICS installation? I thought installing in the 2nd partition was supposed to keep my original installation clean. Now it's all confusing, I just want to make sure there's nothing lingering around.
Edit: Ugh, found out what happened. Just needed to do some more digging around. For anyone else that wants to know: "To anyone wanting to flash custom roms from droidrzr and alike you need to modify the update-script a bit to make it work correctly, failure to do this will wipe you primary system regardless that you are in the second system"

You're right. Recovery has no control of what the updater_script contents / do.

Related

Require help with flashing CM7 for Samsung Galaxy Ace

Hi,
I have the recommended clockwork mode (5.something) but when I do flash install, it just resets to my stock? I did do wipe data/factory reset as per install and then I install it afterwards, yet it just installs back to like I got the phone with google asking me about GPS and it's still got samsung apps etc.
When I install CM7 it does say installation complete in text form and the likes also.
Any help would be greatly appreciated.
Links: http://forum.xda-developers.com/showthread.php?t=1263292
shadowdogg said:
Hi,
I have the recommended clockwork mode (5.something) but when I do flash install, it just resets to my stock? I did do wipe data/factory reset as per install and then I install it afterwards, yet it just installs back to like I got the phone with google asking me about GPS and it's still got samsung apps etc.
When I install CM7 it does say installation complete in text form and the likes also.
Any help would be greatly appreciated.
Links: http://forum.xda-developers.com/showthread.php?t=1263292
Click to expand...
Click to collapse
So it looks like you're flashing a mod of CM7 for your device. After flashing CM7, and you go through all the standard set-up procedures, have you gone into your Settings > About phone and doubled checked which ROM is installed? In this menu it will list the ROM/Mod version, the kernel, etc.
Also, are you using the recommended Recovery from the ROM thread? Looks like it's v5.0.2.3...
Hi,
Yep I have got the latest on that thread. It is now blue text instead of orange from the official one. So far I have tried to mount /system /data before installing cm7 but still nothing changes.
I noticed on the 'installation' it only has [*] for installation complete.
Is that normal?
Or should be it [*] for all?, extracting system, setting permisions, flashing kernel all have just [ ]
shadowdogg said:
Hi,
I think I had to mount /system and /data but I accidently did format /system /data. That means i have to install back to stock and retry?
Edit: Forgot I had a backup
Ok, it still doesn't seem to like it?
Yeah I do have the one mentioned. Blue text update compared to official 4 one.
I noticed on the 'installation' it only has [*] for installation complete.
Is that normal?
Or should be it [*] for all?, extracting system, setting permisions, flashing kernel all have just [ ]
Click to expand...
Click to collapse
I'm having a little trouble following you.... in terms of flashing a custom ROM, you shouldn't need to mount any partitions manually. During the installation process those are taken care of automatically.
I think every file will say something slightly different when a flash is complete. I'm using 4EXT Recovery, which is based on Clockworkmod, and I believe when I flash CM7 (a nightly mod) it actually says "installation complete." But each one is a bit different so it's hard to say... but you are sure that when you boot into the phone after seemingly successfully flashing CM7 it's not CM? I only ask because the setup wizard process is very similar between lots of AOSP ROMs. Perhaps it just looks similar? It just doesn't make sense that you're flashing a ROM successfully, but then you're still on stock afterward. Especially because if you really did a factory reset first, then flashed CM and CM didn't install, there's no way your stock ROM would still be on the device. If anything, you'd have no OS...
Ditamae said:
I'm having a little trouble following you.... in terms of flashing a custom ROM, you shouldn't need to mount any partitions manually. During the installation process those are taken care of automatically.
I think every file will say something slightly different when a flash is complete. I'm using 4EXT Recovery, which is based on Clockworkmod, and I believe when I flash CM7 (a nightly mod) it actually says "installation complete." But each one is a bit different so it's hard to say... but you are sure that when you boot into the phone after seemingly successfully flashing CM7 it's not CM? I only ask because the setup wizard process is very similar between lots of AOSP ROMs. Perhaps it just looks similar? It just doesn't make sense that you're flashing a ROM successfully, but then you're still on stock afterward. Especially because if you really did a factory reset first, then flashed CM and CM didn't install, there's no way your stock ROM would still be on the device. If anything, you'd have no OS...
Click to expand...
Click to collapse
Hi apologies for misunderstanding. I shall try and explain what I meant. I presumed that [*] meant similar to a tick - wasn't sure if all of them had to go [ ] -> [*]
Well I look in the android and it is 2.3.3 and this should be 2.3.7. It also has samsung apps etc still there. All that happens is, I do it. Reboot, it shows "android" for 3 seconds - goes blank for a little while and comes back on but with samsung based one still.
shadowdogg said:
Hi apologies for misunderstanding. I shall try and explain what I meant. I presumed that [*] meant similar to a tick - wasn't sure if all of them had to go [ ] -> [*]
Well I look in the android and it is 2.3.3 and this should be 2.3.7. It also has samsung apps etc still there. All that happens is, I do it. Reboot, it shows "android" for 3 seconds - goes blank for a little while and comes back on but with samsung based one still.
Click to expand...
Click to collapse
Hmm... okay, this is very strange behavior. There are so many possibilities of things that could be responsible. Have you tried re downloading the ROM zip file? Or perhaps reflashing your Recovery image? If there is a specific thread for your device I would definitely post your issue over there. Perhaps even in the thread where you got the ROM from... who knows, maybe others with your device/Recovery version have experienced something like this.
I'm sorry I couldn't be more helpful, but without using your specific phone/Recovery/ROM I can't try to recreate the problem, and thereby help find a solution.
Yeah I would do but I need to randomly make up 10 posts to post there
shadowdogg said:
Yeah I would do but I need to randomly make up 10 posts to post there
Click to expand...
Click to collapse
Ah... to post in the development section? I see... well, perhaps you could try the Q&A for your device in the meantime. I don't believe there is a minimal post number required for that forum. Or, we could keep going back & forth here until you have 10.
Ahah! I wonder... I think I may have only flashed the 'fix' rather than the thing itself. It was only 5MB the fix which if I wasn't a complete noob I should have figured out thats rather small for a complete ROM right away
shadowdogg said:
Ahah! I wonder... I think I may have only flashed the 'fix' rather than the thing itself. It was only 5MB the fix which if I wasn't a complete noob I should have figured out thats rather small for a complete ROM right away
Click to expand...
Click to collapse
Oh yeah... ROMs can range from 70-120 MB. But never just 5 MB. Glad you figured it out.
Guess what - it works! Thanks for your help though

[Q] CM9 ICS Rom Manager not working

Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.

Stuck at splash screen....HELP!!

Hi guys, so i decided to install the new CM10 so i already had root, i unlocked using the official tool, then installed CWM from Rom manager.
I then downloaded CM10 and GAAPS and kept them in a folder and also copied them to an sd card for safety.
I booted into CWM sucessfully, took a deep breath, then did a full wipe/factory restore, then wiped Cache, then wiped Dalvik Cache.
Then i proceeded to TRY to flash CM10.......... Firstly, CWM didn't list my external SD Card so i selected from the one i had saved on the internal storage.
It began to do the install then failed stating something about symlinks??? I retried the install and got the same thing.
I rebooted the Prime and now it's just stuck on the Eee Pad splash screen with "The Device Is Unlocked" written in the top left corner and it wont do anything else.............
I can reboot into CWM but how can i fix this and get CM10 installed??
PLEASE help!?!?!?!?!?
Thanks in advance.
Currently, no recovery can access external memory of any sort. Did you make a backup? Is it in the internal memory? Make sure you can flash back to your original settings BEFORE trying to flash something as experimental as CM10.
Please remember any Jelly Bean roms are highly experimental, and probably won't work correctly for everyone.
Read this thread for more help:
http://forum.xda-developers.com/showthread.php?t=1514088
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
Good to hear. One last advice is to use TWRP instead of CWM. CWM has issues with the prime while TWRP is more stable.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
so how many time had u gone back then tried it.... i have the same problem i tried it like 10 times but it still stuck
what step did u do
I'm stuck in the same predicament! Did you just keep trying, and it finally worked????

[Q] Cyanoboot x2?

So I've tried searching but don't see anything relating to my question. If it's there I missed it and apologize.
My situation is this: I was running stock rooted 1.40 on my NT16 for the longest time but decided I wanted to try out the latest and greatest. I am not a noob when it comes to ROMs, but I am when it comes to Cyanoboot. I flashed CM10 and cyanoboot. then using Goomanager got the latest TWRP.
I'm not a big fan of TWRP personally, so i flashed CWM 6.0.13 and have been very happy. CM10 was nice and I liked the look and feel but it just wasn't stable enough to use as a daily so I decided to go to CM9 (0.05.3). I made a backup in CWM, wiped cache, factory reset and then flashed CM9. Rebooted and it loaded up just fine. Runs like a champ. the problem is that when I boot or reboot, I have the old cyanoboot installed. If I hold the n button to go to the menu and choose to boot EMMC recovery, it goes to the newer cyanoboot where I have to hold n again, to select boot EMMC recovery.
Now, like I said, everything seems to be working fine. I went in that way and made another backup in CWM and that finished successfully but how do I make it so there is only one cyanoboot now? I did not flash the recovery that is in the CM9 thread so is that my problem? If so, I will go ahead and flash it, but I wanted to ask before doing that. I would hate to have a third cyanoboot or worse, brick/really screw it up.
Again, I did try searching for this, but didn't find anything. If there is, please point me in the right direction and I will go from there.
Thanks!
Update... Decided to go back to CM10 and try out the latest from crmhoffmann (0.05.3). Restored my CM10 backup and flashed the new over top. Reboot and now the old version of Cyanoboot is gone leaving only the new one again.
I still don't know how to remove the first (older version) but I guess I can forget about it since the newer CM10 seems to be working much better.

[GUIDE][ROM FLASHING][WALK THRU] Easy to do! All Questions Welcome!

This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.

Categories

Resources