Hello there,
I'm new to Android (got me note 2 three days ago) and I rooted the phone yesterday, I flashed cm ROM into the note, because It was as simple as an iPhone, and it was fast, but I lost some of the greatest features that note 2, offers which are the multiscreen and the S-Pen features, I have posted a help thread about that and they replied that I need a Touchwiz ROM, I went to my close friend Google and searched for Touchwiz rom(s) but there were way too many, can you recommend a good light one with nice interface and noob-friendly? I would really appreciate it.
With regards,
OverDub
Sent from my GT-N7100 using xda app-developers app
It's hard to say which is best. A twizz rom is a stock based rom. If you want a rom with lots of features I'd look at one of the note 3 based roms like ditto. If you want something light any rooted stock rom will do then you can use titanium backup to freeze or remove anything you don't use. If you want to increase battery life then check out apps like greenify and receiver stop. They help to stop rogue programs running in the background
Sent from my GT-P3110 using XDA Premium 4 mobile app
Thanks for your help, seems that dn3 is good but I have a question, I'm using a Cyanogenmod ROM, will upgrading from cm to dn3 cause me any problems?
Sent from my GT-N7100 using xda app-developers app
No there will be no problem at all. If you are already on a 4.3 bootloader you will be fine If you aren't you just need to flash either the wifi patch or devil kernel to get wifi. I am on the n7105 which is slightly different. If you follow any of Dr ketan's guides you will not go wrong. Airview pen window and quad screen multi window are all pretty cool features in dn3
Sent from my GT-N7105 using XDA Premium 4 mobile app
You can try Tiagra ROM, its supposed to be 4.3 Touchwiz ROM with the features of Note 3.
sawdoctor said:
No there will be no problem at all. If you are already on a 4.3 bootloader you will be fine If you aren't you just need to flash either the wifi patch or devil kernel to get wifi. I am on the n7105 which is slightly different. If you follow any of Dr ketan's guides you will not go wrong. Airview pen window and quad screen multi window are all pretty cool features in dn3
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you a bunch, I'm running a 4.3.1 jellybean CyanogenMod, im I going to need to flash a WiFi patch or a kernel ?
Sent from my GT-N7100 using xda app-developers app
Just do a full wipe (is a must and most advisable) when you jump from 1 rom to another.
If you are not sure which bootloader you are in now (noobproof in my opinion) :
1) try download all the files you need first, and put them all on the SD card (ROM, Wifi patch N7100 dr. ketan).
2) Full wipe (if you are on philz cwm, do a clean wipe to flash new rom), and flash new rom.
3) let it boot. Try the wifi, if it doesn't work, it means you are on the old bootloader, then you have to follow the wifi patch instructions (or flash devil kernel on my device N7105).
antique_sonic said:
Just do a full wipe (is a must and most advisable) when you jump from 1 rom to another.
If you are not sure which bootloader you are in now (noobproof in my opinion) :
1) try download all the files you need first, and put them all on the SD card (ROM, Wifi patch N7100 dr. ketan).
2) Full wipe (if you are on philz cwm, do a clean wipe to flash new rom), and flash new rom.
3) let it boot. Try the wifi, if it doesn't work, it means you are on the old bootloader, then you have to follow the wifi patch instructions (or flash devil kernel on my device N7105).
Click to expand...
Click to collapse
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
OverDub said:
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Better flash MJ5 bootloader than Wifi-patch. A lot of people reported problems without new bootloader. MJ5 is knox-free.
OverDub said:
Thank you for the reply, I have the ROM manager app which is associated with CWM, it has the (install a ROM from SD card) option, and if u press it There are two checks which are (wipe data) and (wipe cache).
Is it safe to use the ROM manager way of installing a ROM ?
P.S: I used the ROM manager way yesterday to change ROMs from cm 10.2 to cm 10.2 nightly and it worked perfectly.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
antique_sonic said:
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
Click to expand...
Click to collapse
Good advice. Most people seem to have more success with phils revovery on DN3. Aroma can be buggy at times and different recoveries can struggle with aroma
Sent from my GT-N7105 using XDA Premium 4 mobile app
antique_sonic said:
You can try what dalanik suggest for the bootloader.
as for the flashing of DN3, I would suggest u flash Philz CWM, or TWRP. I myself use Philz CWM (I always use his since Note1, and so far give me less headache in my personal opinion/experienced).
Anyway, CM10.2 to CM10.2 nightly are still the same base CM. When you want to jump into TW from CM, I would highy recommend to do a full wipe. And the full wipe is the best do from recovery.
I'm sorry, I have no idea on using ROM manager to flash ROM on Note device. I left it long time ago. Galaxy S1 is my last device to use ROM manager.
Click to expand...
Click to collapse
Well , I Wiped , cleared cache and dalvik cache, then flashed the DN3 rom , now im stuck in a bootloop after the DN3 finished installing, i cant access my recovery menu , i tried flashing philz and still cant access, the only thing i can access is the download mod[VolumeDown+Home+Power]
I would really appreciete some help because i might have bricked my phone, im a completely new to this, so please help in the "noob" language.
OverDub said:
Well , I Wiped , cleared cache and dalvik cache, then flashed the DN3 rom , now im stuck in a bootloop after the DN3 finished installing, i cant access my recovery menu , i tried flashing philz and still cant access, the only thing i can access is the download mod[VolumeDown+Home+Power]
I would really appreciete some help because i might have bricked my phone, im a completely new to this, so please help in the "noob" language.
Click to expand...
Click to collapse
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
antique_sonic said:
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
Click to expand...
Click to collapse
I followed your steps , by going into recovery and doing a full wipe , then flashing it, but i ended up in a bootloop, thanks for the quick reply
antique_sonic said:
So... you really did it from ROM manager ? I guess you are faster then I reply earlier.
ok.. Now you go to this website : http://www.mediafire.com/?v6cyi52g2ydbd
and then download : philz_touch_5.00.5-n7100.tar.md5
after that you can flash it from PC Odin (since you said u still can go into download mode).
Once you see pass and your phone reboot, press vol up + home + power to go into recovery. You shall see Philz CWM there.
here is how to flash PHilz from PC Odin :
http://forum.xda-developers.com/showthread.php?t=2028103
(go to post #2)
Click to expand...
Click to collapse
Thank you so much for solving this , i now have my old CM 10.2 Nightly , so now DN3 is a no for me because of what happened , any similar roms you can recommend ?
Thank you again
OverDub said:
Thank you so much for solving this , i now have my old CM 10.2 Nightly , so now DN3 is a no for me because of what happened , any similar roms you can recommend ?
Thank you again
Click to expand...
Click to collapse
btw.. which version of CWM Philz installed on your phone ?
if you want the Note3 features, I only know DN3. Sorry I rarely see the N7100 ROM, because I only own a N7105.
But if you don't care about Note3 feature, I believe N7100 got so many rom you can try....
antique_sonic said:
btw.. which version of CWM Philz installed on your phone ?
if you want the Note3 features, I only know DN3. Sorry I rarely see the N7100 ROM, because I only own a N7105.
But if you don't care about Note3 feature, I believe N7100 got so many rom you can try....
Click to expand...
Click to collapse
My CWM is 6.0.4.3 and the philz i downloaded before you told me to download 5.00.5 was 6.70.9 , i think its the latest.
OverDub said:
My CWM is 6.0.4.3 and the philz i downloaded before you told me to download 5.00.5 was 6.70.9 , i think its the latest.
Click to expand...
Click to collapse
yep correct.
If you ever consider to try again, inside Philz, when you choose wipe data/factory reset, there's option something like "Clean wipe to install new ROM". choose this one. It will do necessary wiping + formatting system/data and necessary formatting. Then you can wipe cache & dalvik. Then you can go on on flashing again.
Or... The best way that I always use, is to clean the internal storage (if I jump from TW to AOSP or the other way around), by using Zoots script. This script (custom wipe => mega wipe), will remove everything inside the internal storage. It will make a very clean place (until your backside ) to flash new ROM.
Link : http://forum.xda-developers.com/showthread.php?t=1983489
Use it with Philz 5.0.0.5
Just an opinion, if you would ever like to try again in the future.
All recoveries can be a bit buggy with aroma and bootloop is common. Sometimes turning the phone on and off works sometimes it can take 3 or 4 attempts to work so don't panic. I don't think one of us has never had a bootloop with aroma. As antique_sonic said I think earlier versions of phils play better with aroma. I think it's version 5.15 not 5.05 that's the one I used anyway
Sent from my GT-N7105 using XDA Premium 4 mobile app
sawdoctor said:
All recoveries can be a bit buggy with aroma and bootloop is common. Sometimes turning the phone on and off works sometimes it can take 3 or 4 attempts to work so don't panic. I don't think one of us has never had a bootloop with aroma. As antique_sonic said I think earlier versions of phils play better with aroma. I think it's version 5.15 not 5.05 that's the one I used anyway
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
5.15 it is :highfive:
Related
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Flash a newer recovery prior to flashing CM10.
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Sent from my SGH-I747M using xda premium
such as
SaneinOne said:
Flash a newer recovery prior to flashing CM10.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Such as...
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
okay
GlassRaven said:
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
Click to expand...
Click to collapse
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
EdwinForTheWin said:
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
Click to expand...
Click to collapse
I don't really recommend that as that could cause unwanted trouble. From my experience, I just followed the rooting guide that I posted, flash a custom recovery, and flashed the Cyanogenmod 10. Another tip, if you don't want to lose your contacts, make a backup of it before flashing a ROM. Preferrably you write them in a paper so it would be easier. If you have important messages, use an SMS/MMS backup tool to save them. As for applications, make a list of applications that you consider are essential for you so you could just redownload them. Starting out in a custom ROM is really hard at first but you'll get used to it.
Its safety is directly proportional to your ability to follow directions.
Your first mistake was you used the app to unlock the VERIZON S3 bootloader.
All other versions of the GS 3 have unlocked bootloaders.
You should definitely do some more research before you attempt root and custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Can you just use ROM Manager after rooting and flashing the stock ROM to download CWM, then CM10? And is the CM10 you're using on your Rogers phone compatible? I don't see a Rogers version on the CM site. Did you use the AT&T one?
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
tonymtl said:
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
Click to expand...
Click to collapse
What does touch recovery do? And do I have to use that link to flash it, or can I use ROM Manager? And if I were to use that link, I would DL the zip, boot my phone into download mode, plug in, open Odin, make sure auto reboot and F reset time are checked, load the .tar into the PDA, and click start? What happens to the previous ROM that was there?
And when I first root my phone, and load the stock rom, do all of my apps remain? I haven't rooted yet, for my Rogers phone.
A touch recovery lets you touch the screen as apposed to using the volume rocker.
You will keep all your data.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the help! Another question, if I would like to unroot my phone, and decrease the flash counter, is there a thread I should see for the I747MVLLH1? I know about triangle away, but Rogers/my model isn't supported for that.
Triangle away does support Rogers gs3
Thanks! So should I flash CM10 through ROM Manager, or through the link that was posted? I'm not exactly clear on how to flash the ROM through the link though. Does flashing a new ROM erase the previous ROM? And 'wiping cache' doesn't wipe your data/apps right, only 'wipe Data and Cache'? And I don't really need to bother with kernels too right?
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
tonymtl said:
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
Click to expand...
Click to collapse
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Yes it will ask you if you want to wipe, if you download cm10 ROM from ROM manager it will ask you if you want the latest gapps. You can get ROM toolbox or titanium backup to backup your apps and restore them after flashing rom. Backup is just in case but you can always flash stock ROM later if anything goes wrong.
ily112 said:
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Click to expand...
Click to collapse
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
s0ulja said:
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
Click to expand...
Click to collapse
How exactly would I flash through cwm recovery?
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that
zachdees said:
In all my previous posts requesting help of why my phone wont boot 4.4.2 ive never gotten a clear answer or any troubleshooting steps.
when i flash 4.4.2 with any recovery it goes to rom logo and doesnt boot past that. the only rom ive been successful with flashing is omni rom. whats the difrence between omni rom and any other regular 4.4.2 rom/
all i want to do is use carbon kk i had 4.4.2 working once before i flashed 4.3 and the wifi fix and after i flashed the wifi fix my phone stopped booting into 4.4.2 ever since ive been trying to get a odin wifi fix removal for my phone. i want to see if that will fix it but no one will help
also in cwm recovery upon wiping
you get an android_secure not found or somthing like that
Click to expand...
Click to collapse
The android secure issue you see is actually nothing. It is stating it cant find that directory on you sdext partition which you dont have unless you partition your sdcard.
Now why you cant boot 4.4 is kind of odd. I have gone between all versions for our phone aosp and touch wiz without any problems. I would suggest installing twrp and then running billards back to stock mc2 with counter reset (located in development section). Make sure you read the op for that thread and follow his directions. After flashing that before rebooting flash a root.zip (dont use twrp's root). Once your booted you can use odin or an app to flash cwm or philz (6.07.9 recommended) then you can flash any 4.4 you want. Just remember to wipe/format your internal sdcard (data/media) before going to 4.4.
Sent from my SPH-L900 using XDA Premium 4 mobile app
My phone won't let me format the internal sd card it seems like Its locked or something also I've done back to stock 5 times and no luck
Which recovery and how are you trying to format internal?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.
tx_dbs_tx said:
Do what jlmancuso said. This will format your internal sd as well. Just go back to stock unrooted MC2 and don't bother with flashing the root till its back up and running stock unrooted. Once you do that use the Samsung Note 2 Toolkit (version 2 not 3) and choose the ALL IN ONE Root,recovery, busy box, etc option and choose the twrp recovery not clockwork. Once you get it rooted and on twrp recovery, immediately flash Phil's recovery. 6.07 version (or whichever version that has already been recommended). Then wipe everything as usual including dalvic, cache, internal sd. Then flash stock rooted MK4 in lorjay's thread. then use ODIN on your PC to flash the wifi fix. Do a prl and update profile while on stock rooted MK4. Once you are at this point you can then flash any KK rom and it should work fine. just make sure you set your phone down and let it complete the initial boot as it sometimes takes a few minutes to boot. If this does not work then you're screwed LOL. Good luck.
Click to expand...
Click to collapse
The red additional steps are unnecessary and make little sense. Otherwise, yup.
I'm of the hunch-ish opinion that it is the "wifi fix" that causes lots of these problems in the first place. Most everyone who flashes 4.4.2 builds and that has issues usually share the common thread of having that "wifi fix" on their phone....and that is a hunch, yes, purely on my part. In any case MK4 (radio, ROM, etc) is in no way needed to flash 4.4.2 builds.
I Have done every flash to stock with counter reset. and no matter how many times ive tried it still bootloops i need a DIRECT WIFI FIX REMOVAL
There is no such thing. All the wifi fix is a flash of the param.bin which is in the mk4 odin file. Also those who took the ota have it. It in no way effects aosp!
Are you flashing anything besides the 4.4 rom?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app
thunderwagn said:
Are you also performing the data wipe and factory reset AFTER FLASHING THE ROM AND GAPPS? Many miss this required step.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I have never had to do that but it wont hurt to try it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over
zachdees said:
i have always payed close attention to that step. im almost to the point of selling my phone for the note 3 this journey is almost over
Click to expand...
Click to collapse
That is definitely a good idea...considering that last I knew Note 3 has yet to get working 4.4.2 builds.
i have galaxy note 2
how im install DN3(Ditto Note 3) ROM 4.2.2 Exactly?
Because he has Not moving after I install what it says on the site
oraned said:
i have galaxy note 2
how im install DN3(Ditto Note 3) ROM 4.2.2 Exactly?
Because he has Not moving after I install what it says on the site
Click to expand...
Click to collapse
Just install TWRP and do Full Wipe , then install the ROM.
oraned said:
i have galaxy note 2
how im install DN3(Ditto Note 3) ROM 4.2.2 Exactly?
Because he has Not moving after I install what it says on the site
Click to expand...
Click to collapse
You mean 4.4.2? Install the latest philz touch recovery or Twrp 2.6.3.1 and higher wipe all partitions including internal , leave your external (SD card ) alone then install zip .if you are using philz touch recovery it will ask you to update binary after you choose to install zip like this "(x)update binary" uncheck that so (x) becomes ( ) and go ahead with install [no such update binary request is there when flashing via Twrp]. Also sometimes the screen is stuck on Samsung note 2 but people have successfully flashed it on the 2nd or 3rd attempt and it's a beta ROM so expect some bugs and you'll find most of your answers in the DN3 thread
Sent from my GT-N7100 using xda premium
after installing you can try wiping dalvik cache also
Sent from my GT-N7100 using Tapatalk
Installation was giving problems to me also.
I Just Installed TWRP 2.6.3.2 , wiped and installed the rom.
It started working now.
Link for TWRP
http://www.4shared.com/file/qCkdOhL1ba/openrecovery-twrp-2632-t03gimg.html
1. Download Rom and place it on External SD card
2. Install latest latest TWRP 2.6.3.2 using ODIN
3. Boot into TWRP and go to Wipe -> Advanced Wipe (wipe everything except extr_sdcard, do it twice)
4. Flash the Rom
5. Reboot System
6. Let it settle for 10 mins and then Enjoy
WiFi isn't working? Flash MJ5 bootloader using Odin
If you get S Planner FC, uninstall S Planner widget using Titanium Backup.
Spontaneous reboots every few minutes? Turn of Smart Stay.
Need 40% better battery life and 400 more MB of free RAM? Uninstall 50+ bloatware apps such as Samsung apps, google apps packages that you don't use...
dn3 4.4.4
Once you goto "Install Zip" in philz, uncheck "Update old binary" and then flash the zip, everything will be fine. I never had any problems with philz..:good:
Hi gurus..
can I flash newer DN3 5.5 over DN3 5.2+ directly?
coz I saw someone did in the youtube once...
I dont want to wipe data and setup all again everytime new version came out..
btw @DimitriXRS what do you mean need to off Smart Stay.. is it a bug?
and how bout MJ5 bootloader how do I check it?
thanks..
krobar77 said:
Hi gurus..
can I flash newer DN3 5.5 over DN3 5.2+ directly?
coz I saw someone did in the youtube once...
I dont want to wipe data and setup all again everytime new version came out..
btw @DimitriXRS what do you mean need to off Smart Stay.. is it a bug?
and how bout MJ5 bootloader how do I check it?
thanks..
Click to expand...
Click to collapse
Yes, just flash as normal no wipe.
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
ok I will try that now ... I hope youre right!
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Well, yeah, that's the reason,
According to gr8nole, bootloader is responsible for this, the updated version of bootloader have this problem
Sent from my SM-T211 using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
No, it can happen if you are on 4.1.2 too, it happened to me on my SM-T211 while running 4.1.2 and I did used a software method to reboot to recovery and was stuck in recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
jonstowe78 said:
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
Click to expand...
Click to collapse
Yes
Unless someone makes a fix for that!
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Ditto that. I got the firmware from sammobile.com & flashed (AP mode in Odin 3.09) and I was no longer stuck. At that point, I had stock 4.4.2. I then flashed phil via Odin 3.09 (AP) - the gr8nole version (check the nolekat thread) and was able to install any ROM I wanted.
Good luck
ameva said:
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
Click to expand...
Click to collapse
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
ameva said:
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
Click to expand...
Click to collapse
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
@gr8nole Please prepare two PARAM image from JB and KitKat firmware. Try both PARAM on your device, maybe one of it is the solution of this recovery bootloop issue.
To create Odin flashable param:
Code:
tar -H ustar -c param.bin > param.tar
md5sum -t param.tar >> param.tar
mv param.tar param.tar.md5
sscsps said:
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
ameva said:
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
Click to expand...
Click to collapse
No, not the pre-installed apps, but the apps you installed will be uninstalled is you perform a wipe operation from recovery(custom)
It's just a apps wipe, it will leave only personal data like photos, songs, etc.
Sent from my SM-T211 using XDA Free mobile app
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
ameva said:
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
Click to expand...
Click to collapse
You can flash it without any risk of anything being deleted, flashing recovery won't delete anything (neither any app)
Cache memory stores dynamic things which helps apps to run smoothly, if you wipe that, your apps will have to make that memory again(when it runs for the first time/first time after you clear cache) to run smoothly in future, but Delvik cache helps android to run smoothly, every rom need different things to run smoothly, so we need to clear previous rom's Delvik cache in order to allow new rom to create is own Delvik cache of its own, this is the reason the first boot takes a bit longer time to compleat because it takes time to write is own Delvik cache, sometimes, different roms' Delvik cache conflicts, so it can be like you get stuck on boot screen, just clear Delvik cache to fix it
Hope it is clear, I might be wrong, but this is what I think it is!
Sent from my SM-T211 using XDA Free mobile app