When do I flash a mod in the flashing process? After the ROM, obviously... Do I need to boot the phone up at all before flashing a mod?
Thanks for the patience when you answer. I looked but didn't see my question asked before... I know it's a noob question.
Sent from my SCH-I535
Hmm, I always prefer to flash them separately. When I used to flash mods, I would flash the rom, boot to make sure it runs ok (aka no crazy force closes), then flash the mod. I'm sure that you can flash both at once but I rarely did on my last phone.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Hmm, I always prefer to flash them separately. When I used to flash mods, I would flash the rom, boot to make sure it runs ok (aka no crazy force closes), then flash the mod. I'm sure that you can flash both at once but I rarely did on my last phone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This right here. It honestly is hit or miss though. Sometimes I would have zero issues flashing the rom , kernel, and mod all at once back to back. Other times u would be in hell doing that. I have honestly noticed best performance flashing the ROM clean (complete wipe) the. Rebooting... once the ROM settles I go back to recovery and wipe cache and dalvik flash the kernel. Reboot and once that settles, I do the same thing as the kernel. Recovery, wipe cache and dalvik, flash mod and fix permissions. Then boot and done. May seem redundant but it works best for me and I get zero issues
Sent from my SCH-I535 using Tapatalk 2
I flash rom, kernel, restore data if wanted, flash mods, flash themes all at once with TWRP with no problems. Never have fixed permissions. If have to fix permissions you flashed something that UID didn't match. Usually happens when flashing over data.
I've only had problems when I flash ROM then MOD before booting up once.
Thanks so much!
Sent from my SCH-I535
Related
I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app
did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.
My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3
i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.
droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!
Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
You only need to flash boot.img separately if you are on hboot 1.14 or higher. Otherwise, it will just flash in TWRP automatically when you flash the ROM.
Don't know about your other questions.
That's "tons" of questions??? That's just 2!
CalamitySir said:
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
superchilpil said:
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Then how do I downgrade the hboot?
Another question is that when I tried to flash 4.1.1 ROMs when coming from 4.1.2 Roms, it stuck in the boot logo.
Sent from my One X using xda premium
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
InflatedTitan said:
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok now the question is, do i flash the boot.img first then flash the rom or flsah the rom first then the boot.img??!! The latter method was reccomendded by devs in the HOX section and the former one was used in ours?
I tried ROM then kernel on my cousins phone... Bootlooped.. Started fresh, flashed kernel then ROM and works perfectly every time
Sent from my One X using Tapatalk 2
Another question is the ss below, the total amount of data doesn't add up correctly....is this a bug or was it already predetermined like this?
Sent from my One X using xda premium
CalamitySir said:
Then how do I downgrade the hboot?
Click to expand...
Click to collapse
Tool here (but requires a Linux machine): http://forum.xda-developers.com/showthread.php?t=1982442
The total amount of data doesn't add up. Is this a bug in CM10?
Sent from my One X using xda premium
I'm still not seeing the "tons" of questions.
iElvis said:
I'm still not seeing the "tons" of questions.
Click to expand...
Click to collapse
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
CalamitySir said:
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
Click to expand...
Click to collapse
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
iElvis said:
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
Click to expand...
Click to collapse
ok. does fastboot makes me unable to downgrade the android version, i tried to flash 4.1.1 from 4.1.2, i did it separately and it didnt work, stuck at bootloop... any idea?
Well you have to flash the boot.img from the 4.1.1 rom. Maybe try flashing the older gapps http://goo.im/gapps/gapps-jb-20120726-signed.zip I would also wipe cache, dalvik and system. Use flashimagegui for kernel flashing so you dont need to use fastboot and a pc http://forum.xda-developers.com/showthread.php?t=1963896
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
smolck said:
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
do i have to follow this sequence to wipe everytime?
Usually if its same rom u dont need to factory reset[wipe data] but ive been wiping system alot each time though.
Okay so i ran synergy rom for a bit, loved it and worked good.
I tried flashing CS SG3 ROM
I couldn't get it to boot all the way up, i tried everything odin back to stock and retried, wiping system , everything.
still couldn't get it to boot all the way up so i gave up and ended up going to GALAXY MOD It worked perfectly and i loved it.
But today I tried flashing release 15, it also will not boot up. But when going and flashing release 14.1 again it works perfectly.. does anyone know what my issue is or how to fix it? I'm so confused... do they have something similar that could possibly be the issue?
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
GoonAssJuan said:
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay. I will be trying this. thank you.
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
barrackOBAMA said:
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
Click to expand...
Click to collapse
I've tried this. lol
So my fiance has had this phone for 2 years, she FINALLY let me root it. I have a SGH-T679, flashing for that is simple, i am able to get a custom recovery flashed via the stock recovery.... On this device it says to flash a custom kernel. to get a custom recovery. im having trouble with this on the stock rom. Everytime i have tried to flash a kernel, for instance basic with a twist, the phone will NOT reboot. idk if im missing something or what, if at all possible can someone help me out so i can get this done for her. like i said on my device flashing is extremely simple, on that all i have to do is wipe rom via cwm or twrp, flash rom and gapps (plus other goodies) and reboot. this phone you apparently cannot do this. Please help me out.
Also I should note I do have root on her device, and when I did try heimdall the device was stuck on boot animation. Left it there for 20 mins.
Sent from my super fast AOIP SGH-T679!
Did u tried using sgs Kernel flasher to flash That kernel? Cuz thts how I flashed the kernel on my phone
Sent from my SGH-T959V using XDA Premium 4 mobile app
Lumin30 has a pretty awesome guide posted somewhere in here. He's helped many with it.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
I'm afraid to try that kernel again. But I will give it a try tonight
Sent from my super fast AOIP SGH-T679!
Are you still engaged?
Sent from my SGH-T959V using xda app-developers app
flashing on this is also extremely simple you just have to flash the custom kernel on stock GB with SGS kernel flasher then you have the CWM you know and love
Yes I am, so when I thought it was a boot freeze it wasn't it just takes forever to restart because of the config it has to go through. Thanks for all the help. Maybe I will try to tackle the ROMs for this device
Sent from my super fast AOIP SGH-T679!
tazmaniondvl said:
Yes I am, so when I thought it was a boot freeze it wasn't it just takes forever to restart because of the config it has to go through. Thanks for all the help. Maybe I will try to tackle the ROMs for this device
Sent from my super fast AOIP SGH-T679!
Click to expand...
Click to collapse
try the 4.2.2 jellybean roms they work flawlessly other then gps
Hmm can I flash those over stock or do I have to flash mtd GB?
Sent from my super fast AOIP SGH-T679!
tazmaniondvl said:
Hmm can I flash those over stock or do I have to flash mtd GB?
Sent from my super fast AOIP SGH-T679!
Click to expand...
Click to collapse
i flashed over to beanstalk from stock GB with custom recovery <-----you can choose any other 4.2.2 but make sure its Aries build...they simply flash like normal then it reboots by itself back into newer CWM recovery then finishes the flash then you have to manually go into recovery after first boot to flash over the gapps....most roms in the Development threads have the how to install and the proper downloads
So I can flash a 4.2 over stock. I already know gapps and all that. Any wipes need done?
Sent from my super fast AOIP SGH-T679!
tazmaniondvl said:
So I can flash a 4.2 over stock. I already know gapps and all that. Any wipes need done?
Sent from my super fast AOIP SGH-T679!
Click to expand...
Click to collapse
Factory Data and cache and dalvik cache in the advanced part then instal but to be safe after you finish with the gapps wipe cache and dalvik again then reboot and wala 4.2.2 JB fully working other then gps unless it says in the roms channel log
I have flashed many 4.3 Roms and can not get any of them to boot. I have followed all install instructions but can't get past gs3 screen. Any ideas?
Sent from my SCH-I535 using xda app-developers app
im having a similar problem to yours..i mean after i do a fresh install+gapps it works..but after i go back to recovery and install my other files it wont go past the gs3 logo no idea why.
Yep frustrating any other ROM is OK just 4.3 not working, sucks.
Sent from my SCH-I535 using xda app-developers app
I've flashed every 4.3 and all booted. Try just flashing ROM first. Let sit a few minutes then flash gapps. I also use the eclipse ROM gapps for all. No issues.
Sent from my SCH-I535 using xda app-developers app
I also have the same problem when I try to reboot on 4.3 Roms. First boot up is fine. But when I go into to recovery it won't boot back up unless I reflash the ROM from the start. If someone tries flashing ROM and gapps separately let us know if it fixes it.
Sent from my SCH-I535 using Tapatalk
Tried eclipse ROM and apps. No different. Initial boot works and ROM runs fine but reboot freezes up on gs3 screen. What is getting scrambled and is there a way to fix this.
Sent from my SCH-I535 using xda app-developers app
I've never had this issue. What I've done/used to flash all 4.3 roms was use the super wipe tool found in the general section(the one that wipes data, system and caches only) and then run it once and flash Rom+ gapps as instructed. I use twrp as well. Also, perhaps it's a stock 4.3 kernel and maybe flash a kernel straight after you flash the rom and gapps. Rom> gapps>kernel . Hope it helps
Sent from my SCH-I535 using Tapatalk
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
http://forum.xda-developers.com/showthread.php?t=2097365
[Mod][Utility] Wiping Tools - Simple and Fast
Sent from my SCH-I535 using Tapatalk
I used ez recovery from the play store and used cwm touch recovery and I no longer have the reboot issues. Even if you're using cwm, I would just download ez recovery and try it.
Sent from my SCH-I535 using Tapatalk
Use ez recovery to flash the ROM or install cwm and then flash through that?
Sent from my SCH-I535 using xda app-developers app
I had a similar problem when I first tried 4.2 but I've found two ways that have always worked for me
Full wipe (I wipe everything 3 times, but I'm sure that's overkill)
Flash rom
Flash gapps
Reboot
If it gets stuck on any screen wipe the cache and dalvik cache
Reboot
The other method I've only used with Dirty Unicorns
Full wipe
Flash rom
Reboot
Once the rom reboots, reboot back into recovery
Flash gapps
Reboot
Wait 10 minutes
You can either reboot again or just use as is
But if nothing is working you can odin back to stock
Then use this tool to root, unlock the bootloader, and flash the custom recovery of your choice http://forum.xda-developers.com/showthread.php?t=2332825 (it even works on a mac)
(This is what I always use to root, unlock the bootloader, and flash recovery whenever I have to flash back to stock)
After I do that I always reboot and use Rom Manager to flash the latest recovery before flashing anything else.
These 2 roms have been 100% stable for me
http://forum.xda-developers.com/showthread.php?t=2484256 (4.3.1)
http://forum.xda-developers.com/showthread.php?t=2469789 (4.3 I've never tried the weeklies just the lastest stable build)
Hope it helps
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Juice3250 said:
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
You do realize that the recoveries built into ez recovery are over a year old. I wouldn't flash those under any circumstances. Only use ez recovery to flash from the custom slot.
Sent from my SCH-I535 using Tapatalk 2
Thanks for correcting me on that one. My bad.
Sent from my SCH-I535 using Tapatalk