Hi, i want to install custom roms for my sgh-i747m s3 which is from bell canada. But im kinda confused on what rom to install. Im fine with kitkat roms with theme support. Can i ask you guys on what custom rom should i install which can be used as a daily driver (stable) ?
I currently have i747MVLUEMK5 bootloader and i already install philz touch and already created a backup
Sent from my SGH-I747M using XDA Free mobile app
@xtrap said:
Hi, i want to install custom roms for my sgh-i747m s3 which is from bell canada. But im kinda confused on what rom to install. Im fine with kitkat roms with theme support. Can i ask you guys on what custom rom should i install which can be used as a daily driver (stable) ?
I currently have i747MVLUEMK5 bootloader and i already install philz touch and already created a backup
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
Here are the CM11 snapshots. They haven't posted a new one in quite a while.
The nightlies are here and they're much more recent builds. There doesn't seem to be a whole lot going on with kitkat right now. I've run the nightlies recently and they were nice and stable.
There is an unofficial CM12 thread maintained in the developer section of the forum here. Its pretty solid, but it is still working through some issues with camera, ril, etc.
jason2678 said:
Here are the CM11 snapshots. They haven't posted a new one in quite a while.
The nightlies are here and they're much more recent builds. There doesn't seem to be a whole lot going on with kitkat right now. I've run the nightlies recently and they were nice and stable.
There is an unofficial CM12 thread maintained in the developer section of the forum here. Its pretty solid, but it is still working through some issues with camera, ril, etc.
Click to expand...
Click to collapse
I can flash d2lte custom rom for i747m canadian s3 right ?
Does installing custom rom can brick my phone?
And how do i uninstall them ?
Sent from my SGH-I747M using XDA Free mobile app
You can flash any ROM that is made for the d2lte, no others. For ROMS that are based on a Samsung i747 kernel, the success of getting everything working on the ROM can be hit and miss.
Custom ROMs do not usually touch the bootloader or modem. If you're not sure, carefully read through thr thread before flashing.
You can't uninstall a ROM, you can only overwrite it with another ROM or you restore a previous ROM from your nandroid backup.
audit13 said:
You can flash any ROM that is made for the d2lte, no others. For ROMS that are based on a Samsung i747 kernel, the success of getting everything working on the ROM can be hit and miss.
Custom ROMs do not usually touch the bootloader or modem. If you're not sure, carefully read through thr thread before flashing.
You can't uninstall a ROM, you can only overwrite it with another ROM or you restore a previous ROM from your nandroid backup.
Click to expand...
Click to collapse
Does custom rom change kernel while im flashing them using custom recovery ?
Sent from my SGH-I747M using XDA Free mobile app
Can i install cm 11-m12 snapshot? Is there any chances of bricking my device while installing it?
One more thing before i flashed philz touch theres some lone saying in the stock recovery "qualcomm secure boot:enabled" i dont have any idea on its purpose
Sent from my SGH-I747M using XDA Free mobile app
the CM ROMs do not contain the kernel.
yes you can flash the CM 11/12 snapshots (d2lte).
there is ALWAYS a chance of bricking a device when flashing custom ROMs , but you should be fine.
the "qualcomm secure boot:enabled" message , means the bootloader is in a secure folder ( :thumbup: @audit13).
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
the CM ROMs do not contain the kernel.
yes you can flash the CM 11/12 snapshots (d2lte).
there is ALWAYS a chance of bricking a device when flashing custom ROMs , but you should be fine.
the "qualcomm secure boot:enabled" message , means the bootloader is in a secure folder ( :thumbup: @audit13).
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Thumbs up for the reliable members of XDA
Sent from my SGH-I747M using XDA Free mobile app
I found this on another forum re: Qualcomm secure boot:enabled
Secure boot is for downgrade and patch protection.
Write protection is same patch protection to avoid 3rd party to patch any partitions.
You can always flash stock any condition. but stock should be same or latest.
Click to expand...
Click to collapse
I can not vouch for the accuracy of the statement.
I am frequently seeing reports that CM12 and the most recent nightlies of CM11 require a KitKat bootloader and modem, NE/NF at a minimum. (But then I have one or two state that they are having no problems with the 4.3 bootloader and modem.) If you go with CM11/12 and have connection issues you may need to upgrade past MK5 to resolve them.
dawgdoc said:
I am frequently seeing reports that CM12 and the most recent nightlies of CM11 require a KitKat bootloader and modem, NE/NF at a minimum. (But then I have one or two state that they are having no problems with the 4.3 bootloader and modem.) If you go with CM11/12 and have connection issues you may need to upgrade past MK5 to resolve them.
Click to expand...
Click to collapse
This is a great point.
Look in your settings -> about phone and see what baseband it says you have. Then have a look in the firmware section in sammobile.com, look up i747m then find your firmware number. Just to get a feel for how old it is.
Before you flash a custom ROM make a backup. Once you flash your custom rom , if you find you have no signal or a blank imei, don't panic. Restore you backup and see if signal, data, and imei come back. A modem that doesn't work with your ROM will look like a blank imei. Don't just start googling lost imei, it won't help, and you might make the problem worse.
And if you root your stock ROM, before you flash anything enter this in a terminal.
Code:
su
reboot nvbackup
That will fix a Samsung derp and give you a working efs backup instead of a blank one, making it a lot less likely you ever actually lose your imei.
jason2678 said:
And if you root your stock ROM, before you flash anything enter this in a terminal.
Code:
su
reboot nvbackup
That will fix a Samsung derp and give you a working efs backup instead of a blank one, making it a lot less likely you ever actually lose your imei.
Click to expand...
Click to collapse
Another great point.
This is supposed to poputlate a partition(s) left empty by Samsung. I have done this to my Captivate and to my SGS3. The partition is not overwritten during flashing stock or custom roms and serves as a permanent nvdata backup.It is used to automatically rebuild the imei/nvdata if it is fouled during flashing. It is unknown as to why Samsung left it empty. My guess is that the partition would be specific to each phone and would therefore require each phone to be individually handled to populate the partition instead of batching entire production runs.
Help
dawgdoc said:
Another great point.
This is supposed to poputlate a partition(s) left empty by Samsung. I have done this to my Captivate and to my SGS3. The partition is not overwritten during flashing stock or custom roms and serves as a permanent nvdata backup.It is used to automatically rebuild the imei/nvdata if it is fouled during flashing. It is unknown as to why Samsung left it empty. My guess is that the partition would be specific to each phone and would therefore require each phone to be individually handled to populate the partition instead of batching entire production runs.
Click to expand...
Click to collapse
Hi im currently running a custom rom
(Unofficial CM12 5.0.2 by matrixzone but when i try to restore my backup i seem to be stucked in android is upgrading bootscreen after finishing optimizing X/114 apps it goes to "starting apps" and never gets pass it. It just keeps on loading and loading.
My phone is sgh-i747m MK5 bootloader the custom rom change my phone version in the details below. Can i just flash back a stock rom using odin? Anyway i already press thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
jason2678 said:
Here are the CM11 snapshots. They haven't posted a new one in quite a while.
The nightlies are here and they're much more recent builds. There doesn't seem to be a whole lot going on with kitkat right now. I've run the nightlies recently and they were nice and stable.
There is an unofficial CM12 thread maintained in the developer section of the forum here. Its pretty solid, but it is still working through some issues with camera, ril, etc.
Click to expand...
Click to collapse
Hi im currently running a custom rom
(Unofficial CM12 5.0.2 by matrixzone but when i try to restore my backup i seem to be stucked in android is upgrading bootscreen after finishing optimizing X/114 apps it goes to "starting apps" and never gets pass it. It just keeps on loading and loading.
My phone is sgh-i747m MK5 bootloader the custom rom change my phone version in the details below. Can i just flash back a stock rom using odin? Anyway i already press thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
@xtrap said:
Hi im currently running a custom rom
(Unofficial CM12 5.0.2 by matrixzone but when i try to restore my backup i seem to be stucked in android is upgrading bootscreen after finishing optimizing X/114 apps it goes to "starting apps" and never gets pass it. It just keeps on loading and loading.
My phone is sgh-i747m MK5 bootloader the custom rom change my phone version in the details below. Can i just flash back a stock rom using odin? Anyway i already press thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
Are you trying to restore the backup using the same make of custom recovery with which you made the backup?
If you made the backup with TWRP you can not restore it with Philz.
Also coming back from any of the 5.0.x Lollipop roms you may well have to perform a complete wipe. Not only must you wipe cache, dalvik cache, and data; you may also have to reformat system or even your internal sdcard. I have read of a few instances where the person had to restore a stock recovery and do a factory reset with it, for some reason this seems to reset differently than doing a factory reset from within a custom recovery. (I don't recall the details.)
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?
Hey guys so I just got this phone today. I'm use to how to root, install custom recovery and installing ROMS. Whats the difference with this phone? Where do I start so I can start instaklibg custom roms. Im pretty lost and just wanna make sure I dont get a brick. I have the tmobile verison (t999) and was looking at that wicked rom.
Start with the stickies. ALL OF THEM. They're your bible for all things T999 S3 related.
Sent from my SGH-T999
whytechapel_x said:
Hey guys so I just got this phone today. I'm use to how to root, install custom recovery and installing ROMS. Whats the difference with this phone? Where do I start so I can start instaklibg custom roms. Im pretty lost and just wanna make sure I dont get a brick. I have the tmobile verison (t999) and was looking at that wicked rom.
Click to expand...
Click to collapse
Following this Video will help you out with getting your S3 rooted and a custom recovery installed:
http://www.youtube.com/watch?v=ukpBDTZQ_bM&feature=iv&annotation_id=annotation_948009
After your phone is rooted and you have the recovery installed, go to the play store and install rom manager, open rom manager and install clock work mod recovery (it will just update the current version of the clock work mod that is on your phone from flashing one of the required zips) if you dont update your recovery you will get problems when trying to flash a rom.
Once rooted and recovery is updated go to the original android development section or android development section and choose a rom that interests you (if touchwiz just download the rom, if its cm, aokp, aosp or aospa youll most likely need to download the rom and Gapps which are google apps).
once you have your desired rom and Gapps (if required) reboot into recovery (hold volume up, home button and power button, once you see blue text in the left hand corner let go of just the power button until the recovery shows up) then do backup of Your current rom.
once you have made a backup, do a full wipe: wipe cache, wipe dalvik cache, wipe data factory reset, then install the rom You chose, then install the Gapps (if required) then reboot the devie.
once you reboot the device let it sit for 5-10 minutes some roms take longer than others to boot up for the first time and even though the phone has booted up, its good to just let it sit for a few minutes and to let everything settle. now you're ready to go through the setup.
now you're rooted and have a custom recovery and rom installed, Stay away from the international S3 threads, flash anything from there and you'll brick your phone, just flash things that are meant for your device :highfive: YOUR WARRANTY IS NOW VOID
No crazy brick bugs like the i777. Follow his rooting method but look into twrp. Its far more robust and user friendly for a custom recovery. Impossible to brick you phone flashing a ROM its in these forums for att or T-Mobile.
Happy flashing and good to have you
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
No crazy brick bugs like the i777. Follow his rooting method but look into twrp. Its far more robust and user friendly for a custom recovery. Impossible to brick you phone flashing a ROM its in these forums for att or T-Mobile.
Happy flashing and good to have you
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
TWRP is nice and has a lot of options, but in my opinion Cwm is more reliable.
Personal preferences I guess.
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
Before you do all that make sure you Backup your NV items basically your IMEI, this phone has a tendency to lose that randomly without that you have a mp3 phone won't work like it's suppose to. Some say Cwm was causing it but truth be told there are more users with Cwm than twrp so the stats really are unfair. This is the most important step check around the forums there's about 2 or 3 ways you can do this.
Sent from my SGH-T999 using xda app-developers app
S4 comes out in like next week.
Sent from my SGH-T999 using xda app-developers app
re: best rom
whytechapel_x said:
Hey guys so I just got this phone today. I'm use to how to root, install custom recovery and installing ROMS. Whats the difference with this phone? Where do I start so I can start instaklibg custom roms. Im pretty lost and just wanna make sure I dont get a brick. I have the tmobile verison (t999) and was looking at that wicked rom.
Click to expand...
Click to collapse
Welcome to the Galaxy S3 community!
You have made a very wise choice by choosing the Wicked v9.1 custom rom.
It really is the best you will find for your phone here on xda.
I have flashed and tried them all including CM10, AOKP, AOSP and even the ported roms and the only
rom which I found to be good enough to be a commercial retail product is the Wicked custom rom.
You will not go wrong with it.
Good Luck!
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
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.
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