hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
Did you try using fastboot to erase system, data, cache, and osh partitions?
Sent from my MB860 using xda app-developers app
edit
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
hm, can anyone tell me, why i cant get internal storage to mount from clockworkmod? is this a common problem?
i dont understand what went wrong for me, when i followed the same steps that many others did.
epinter said:
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
Click to expand...
Click to collapse
Your phone is not a paperweight, just not boot the operating system
You did a backup with CWM? restore a backup as Emerson says
You can borrow a sd card copy there CM7 and install from the sdcard
You can also use RDS to install a stock rom
Never install a rom without having an one that you know works 100%
AND ALWAYS READ ALL FAULTS AND SOLUTIONS BEFORE INSTALLING A CUSTOM ROM
ok guys, i went and bought an sd card, clockworkmod mouted it fine, i found and copied over to the sd card android 2.34 for atrix, it flashed fine and my phone is back up.
can you gentleman tell me, whats a good solid rom to flash? cyanogen mod 9 obviously didnt work for me. id like to get started setting up the phone, so i need a good rom to begin with.
thanks to everyone in advance
Go with montouri's version of cm7.2 ,mrom-Olympus you can find it in the developer section. Its my daily driver. Its the most stable and has the best battery life out of all the roms that I've tried
motoxrcr1 thanks for the recommendation, running m-rom now and it runs smooth.
the first time i tried to install it, it hung at the boot logo, then i got to thinking maybe i better try updating clockworkmod, turned out that clockworkmod 4.0X that was installed by the 1-click rooter, is rather old, so i found and updated to 5.XX. tried re-flashing m-rom again, and it worked fine that time.
older clockworkmod, that's probably what caused my original problem with cyanogenmod 9..
does mrom support overclocking? not that i guess i need it, but just to know for future reference
thanks!
the trouble i caused myself, was all due to flashing the rom from an older version of clockworkmod.. after updating to a newer version 5.xx, it flashed fine
delete
Related
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.
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????
Hi everyone,
So, I think ive damaged my internal memory...But let me give u some info first.
UK SGS3 i9300 on vodafone. I rooted it a while ago and have had several roms. I know the basics of android hacking since I've hacked several as well as my previous 2 contract phones. I was on paranoidandroid 2.22 or w.e. version it was, however I wanted to go back to a sammy rom, and decided to clear my internal sdcard n ext sdcard (more or less - leave my music folder on there foe example) at the same time. I only mention this because my lead has been a little touchy recently and during the process it disconnected a fair few times till i got the cable sat right. I didnt have easy ums or anything - it was mtp. I completed this and loaded my rom onto the extsdcard.
I then went into the cwm touch recovery 6.xx or w.e. selected factory reset, wipe cache n dalvik, then installed it. It just got stuck at the boot logo for a while, then kept boot looping. I then tried wiping a few times, and a couple of different roms, and during this time I noticed that when I click wipe data it rebooted recovery. I then downloads the appropriate stock firmware to flash via odin. I flashed it and it was still stuck on the boot logo. I then realized I couldnt get into recovery, so I flash cf-root via odin, I got the 5.xxx recovery that comes with it. I tried to wipe all again, and it just didnt seem to work, I was stuck in a bootloop. I then posted this:
http://forum.xda-developers.com/showthread.php?t=1948255
So yeah with adb, I got it to boot, but i had the wrong size internal memory capacity. Then tonight I flashed twrp (a recovery if u dont know) (latest version) via goomanager and then selected in goo manager ti reboot recovery. Now my phone just goes from the sgs3 logo to the twrp logo and back, even if I boot normally, it does that, and same for trying to boot recovery. I can still get into download mode, but thats it.
I have since tried flashing the stock firmware again to no avail, I'm going to flashing cf root to get recovery... but we'll see what happens...
so what can i do?!?!
Have you tried flashing complete stock firmware through Odin? Then start from there?
You say internal memory is wrong? Might have to flash .pit aswell with re-partition?
Carl.Brand.87 said:
Have you tried flashing complete stock firmware through Odin? Then start from there?
You say internal memory is wrong? Might have to flash .pit aswell with re-partition?
Click to expand...
Click to collapse
yes I have, several times, if u read it all... Where can i get teh CORRECT pit file? I've tried one, but it didnt help.
I've just flashed cf root (after a pass on stock firmware) and its booted the ultima rom again... and still got 12.1gb internal... so my phone boots again, but the internal is still wrong! help!
You know that some of the 16gb is taken for the system files right? My phone only reports like 11.6gb in total to use.
Android reserves about 4gb that's why you only have 12gb free there is no problem there.
mattyyey said:
yes I have, several times, if u read it all... Where can i get teh CORRECT pit file? I've tried one, but it didnt help.
I've just flashed cf root (after a pass on stock firmware) and its booted the ultima rom again... and still got 12.1gb internal... so my phone boots again, but the internal is still wrong! help!
Click to expand...
Click to collapse
That's normal, the 12.1GB is COMPLETELY normal.
Other memory is reserved by the system.
This is usual and it should work that way, stop messing with it.
32GB models should have about 25GB~.
idiot here
Skander1998 said:
That's normal, the 12.1GB is COMPLETELY normal.
Other memory is reserved by the system.
This is usual and it should work that way, stop messing with it.
32GB models should have about 25GB~.
Click to expand...
Click to collapse
oooookk, TT used to show 16gb tho.... i remember i like the fact it read 16gb sd & 16gb extsd. nvm, im just wrong. thanks. I'll use it as it for now, still not 100% convinced but ya know... never had this sort of trouble with my HTC's :/
I'd just like to thank fellow-idiot for this thread, had similar situation (semibricked device, flashed something I should not have been flashing), and now my Internal is 11.3, and I seem to remember it was 14.7, just like my external - but I may be wrong. Changing ROMs, formating Internal, changing recoveries (now on Teamwin Recovery) doesn't seem to change a thing about it. Oh well, not that I'm gonna need it, just wondering where it went (never said hallo either... no manners, today's internal memories..)
11.3 is what it should be
So I got an HTC Hero. I rooted, flashed custom ROMS, had much fun, but trouble started when I wanted to try out BEASTsense. Prepaired SDCard with EXT, flashed, all went fine. Like the fool I am, I removed the sdcard while ROM was working, so all apps disappeared. In order to fix that I rebooted. And then it started:
- Phone bootloops (not even reaching bootscreen) when the sdcard is in (yes, I tried another sdcard, yes, they had no EXT partition).
- Phone boots just right when sdcard is not in, and when I install it it doesn't detect it.
- RUU'd to stock, same problem
- HEROIMG'd to stock, same problem.
I would say it's hardware, but the bootloader/HBOOT reads and installs the HEROIMG from SD just fine. Help. Please.
(sorry for my relatively poor English)
EDIT: Before using RUU or HEROIMG, I tried booting into recovery and wiping everything, but the recovery itself wouldn't recognise my SD, so I could not flash another ROM or use my precious NANDroid backups. Just so you know
help!
Got the same issue, hero keeps rebooting, cant reach any menu, think i got it bricket.
Anyone has any idee, tryed hard reset.
With or without sdcard, same story
Try to wipe sd-ext in recovery... (it will delete your apps)
thanks
pirlouit2 said:
Try to wipe sd-ext in recovery... (it will delete your apps)
Click to expand...
Click to collapse
Got mine working now, now i got a strange batterydrain when i start the market or the internet browser. couple of minutes and the battery is out of order...
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.