Related
It seems that the ClockworkMod guys just released an official Recovery build for all the GS3 variant including AT&T:
Normal:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.4.5-d2att.img
Touch:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.5-d2att.img
I created CWM-flashable ZIPs of these two recoveries (and the Team Epic v4 recovery). You can use those to switch recoveries easily if you want to try these out.
http://forum.xda-developers.com/showpost.php?p=28612095&postcount=558
The touch recovery is nice.
works
drothenberger said:
I created CWM-flashable ZIPs of these two recoveries (and the Team Epic v4 recovery). You can use those to switch recoveries easily if you want to try these out.
http://forum.xda-developers.com/showpost.php?p=28612095&postcount=558
The touch recovery is nice.
Click to expand...
Click to collapse
Touch zip works perfect now rm manager is usable; ) thank u!!
Hey looks like they updated cwm again would you be so kind as to hook us up with another flashable zips
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
So flashing the Touch is supposed to have an icon now on the phone? I flashed and CWM did update but no Touch Icon on the phone.
jroyalty7 said:
Hey looks like they updated cwm again would you be so kind as to hook us up with another flashable zips
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Without cwm none of this hacking would have been possible show some support buy the app ....
Yell at me if u want but I won't care cause I'm right ..
jroyalty7 said:
Hey looks like they updated cwm again would you be so kind as to hook us up with another flashable zips
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
A couple of issues:
- It seems like ext SDcard support was removed (it was not working on 5.8.4.5 too)
- Backups still have 1970 date
drawde40599 said:
Without cwm none of this hacking would have been possible show some support buy the app ....
Yell at me if u want but I won't care cause I'm right ..
Click to expand...
Click to collapse
I agree. When I made the first set of zips I had never used ROM Manager and didn't realize he charged for installing the touchable recovery when flashed through ROM Manager. He says you can do it yourself if you want to download it from his website for free, but I don't think it's right for me to make that any easier.
You can get the regular recovery directly from ROM Manager. That's probably easiest.
Touch doesn't have a working status bar during backup/restore. Leaves you sitting there wondering if anything is going on....if it weren't for the phone heating up one would think its frozen....date is also still screwed up
Sent from my SAMSUNG-SGH-I747 using xda premium
Going back to Team Epic CWM v5, until Koush gets ext-sdcard working...
timeToy said:
A couple of issues:
- It seems like ext SDcard support was removed (it was not working on 5.8.4.5 too)
- Backups still have 1970 date
Click to expand...
Click to collapse
Call me silly but ext SDcard, u mean external? cause if so it was working on my 5.8.4.5 i just flashed dietics from my external.
Swiftks said:
Going back to Team Epic CWM v5, until Koush gets ext-sdcard working...
Click to expand...
Click to collapse
yea works for me on the 5.8.4.5 version.... i just ran a nandroid backup and it went to my external.
djkinetic said:
Call me silly but ext SDcard, u mean external? cause if so it was working on my 5.8.4.5 i just flashed dietics from my external.
Click to expand...
Click to collapse
mrRobinson said:
yea works for me on the 5.8.4.5 version.... i just ran a nandroid backup and it went to my external.
Click to expand...
Click to collapse
Yeah... but if you update to version 5.8.4.6 (released just an hour ago) it totally removes external sd card support; for zip flashing, backups, restores, etc.
Could have sworn I read somewhere that 5.8.4.5 external sdcard support was broken when restoring a backup???? Don't know why he would have removed it if there was nothing broken... Koush is weird like that though.
Anyway, the Team Epic version has everything working except the date issue, which is also present in koush's builds too.
5.8.4.6 looks like it removed External SD support...wonder why...gonna flash back to .4.5
Made a backup with TeamEpic v4, tried flashing CM9, got a version error, flashed 5.8 Touch CWM, rebooted recovery. Tried to flash backup, error restoring /system. Reflashed the ROM I was running, which seemed to go fine. Rebooted and just stayed in the boot screen for over 10 minutes with the blue light on solid. Used Odin to flash to stock tar, completed successfully, rebooted, sat at boot animation (had the AT&T screen in it) for 10 more minutes. I'm beginning to think I ****ed my phone. Please advise.
yokken said:
Made a backup with TeamEpic v4, tried flashing CM9, got a version error, flashed 5.8 Touch CWM, rebooted recovery. Tried to flash backup, error restoring /system. Reflashed the ROM I was running, which seemed to go fine. Rebooted and just stayed in the boot screen for over 10 minutes with the blue light on solid. Used Odin to flash to stock tar, completed successfully, rebooted, sat at boot animation (had the AT&T screen in it) for 10 more minutes. I'm beginning to think I ****ed my phone. Please advise.
Click to expand...
Click to collapse
Turn off your phone and boot into recovery. Doesn't matter if it's stock recovery. Do a data wipe. Then load stock fw again with Odin. You"ll be good.
Dx9 said:
Turn off your phone and boot into recovery. Doesn't matter if it's stock recovery. Do a data wipe. Then load stock fw again with Odin. You"ll be good.
Click to expand...
Click to collapse
I cannot get into recovery, I cannot do a data wipe. I told you, even after Odin it just sits at the boot screen.
yokken said:
I cannot get into recovery, I cannot do a data wipe. I told you, even after Odin it just sits at the boot screen.
Click to expand...
Click to collapse
So you can't turn off the phone and volume up, home button and power button to get into at least stock recovery? I did the same as you today.
Dx9 said:
So you can't turn off the phone and volume up, home button and power button to get into at least stock recovery? I did the same as you today.
Click to expand...
Click to collapse
If I hold them all long enough, it shows Samsung Galaxy S III, then shuts off. If I let go as soon as it vibrates, it just goes into normal boot animation.
Right when Samsung pops up let go of the power button. Try that. The first Samsung Logo that appears
---First off, let me preface this by acknowledging the fact that, yes, I am indeed a noob. And I'm sure some of the info I'm going to put in here probably isn't needed, but as I said, I am a noob, and thus am not entirely sure what is relevant and what is not. I also apologize if some of what I say and/or what I did doesn't make sense and/or is idiotic, but again, noob. That being said I don't have any techie friends and never really had a nack for this kind of stuff, but hey gotta start somewhere right? So, that being said, here's my dilemma:
This all started last week when I was downloading the CyanogenMod Nightlies *Rom. The download started and was going along just fine when my phone suddenly turned off and starting vibrating and then wouldn't turn back on. Everything I would press power it would just start vibrating in regular one second intervals over and over. Finally I remove the battery. It turns back on fine. Download resumes. And... Bam! Happens again. This time I try the same remove to no avail and about 15 minutes later I'm thinking that this is it for my phone when it finally reboots. So I decide, alright, lemme just download this Rom and try to flash it, or at the very least just restore the phone and hope this is a software issue. So I had also just downloaded Rom Manager and was going into recovery via Clockworkmod recovery as the instructions prompted me to in the CyanogenMod tutorial. Now every other time I have installed a new Rom I just manually boot into recovery as the phone turns on. This time I boot into the Clockworkmod recovery though cuz I wanna follow the directions to the "T" and I proceed to selecting the factory reset and it wipes the data and freezes when wiping the cache. So I'm sitting there like, "Oh s**t, what do I do now?" I let it sit for fifteen minutes hoping it will magically unfreeze and all will be right in the world, but it doesn't and I reset the phone via the power button. Then it boots up and tells ne there a issue with my custom OS and I'm not really are what to do here. So, i reboot it and it acts like the reset was successful and prompts me to set up my phone like I just flashed the Jedi Mind Trick Rom I've been using. So I tried again, and same thing. Got stuck on clearing the cache. Luckily it lets me set up the phone again after I interrupt the frozen factory reset. This time I try to boot into recovery manually, pressing the hard keys, and all the phone does is restart. So I try again. And again. And again to no avail. I look up the key sequence thinking I may have forgotten it and am doing it wrong, but after trying every combo I can find online, it still doesn't work. So I give up and go into recovery via clockworkmod and restore my phone to my very first nandroid backup I made before I ever started messing with custom roms, and everything goes fine it seems until it gets to a command about something revolving cache and it freezes again! I eventually have to reset it and it gets stuck in a loop where the Samsung logo comes up, it makes a loud annoying beeping noise for a few seconds before it turns off and does it all over again. Now I'm sure I've bricked my phone. I take out the battery, wait, put it back in, but still nothing. I do this a few more times, wait and hour, and it finally boots up. So now I try to go into recovery manually again, but still just get the phone resetting. I try to go uninstall clockworkmod and go into recovery via Rom toolbox pro, but I still get the clockworkmod recovery rather than the phone's normal recovery I used to be able to get to before I ever installed clockworkmod. So I'm stuck here. I know that's a lot of info, but I didn't want to leave anything out incase it was important. Thanks in advance for any advice and/or directions you can give me. *
P.S. I read in someone's post here that the first issue of the phone turning off and vibrating could be the result of a bad power sensor. So I wanted to add that since this two mysterious restarts and vibrations, nothing like that has happened in the... Approximately 5 days since (for whatever that's worth). *
Thanks again, and I apologize for any ignorance you have encountered while trying to read this post.
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
whatiznt said:
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Ok. Checked it out and got twrp. I clicked install openrecoveryscript. It downloaded. Didn't restart or anything. Now can I just flash the new Rom I want directly from there then? All it says it that I must have installed the recovery script. Just wanted to know though, is it still right that when I reboot into recovery it goes to the cwm recovery? Just wanna make sure before I go messing up my phone.
Thanks!
mintharis said:
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
Click to expand...
Click to collapse
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
VoiD_Dweller said:
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
Click to expand...
Click to collapse
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
jalight27 said:
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
Click to expand...
Click to collapse
Yes, the darkside scripts were used in older cwm recoveries because the default wipes didn't do the job. As for switching away from cwm I'm guessing you want to jump to twrp. You can do that by following the instructions at http://teamw.in/project/twrp2/101
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Thanks for the steps there. Pretty much did a combo of what everyone was saying. Went back to an older version of cwm and used darkside wipes. Then wouldn't you know? It worked! Yay for me. So I'll just keep my older version of cwm, for now at least. Well, anyway, thanks to everyone for helping me figure this out. Much obliged!
jalight27 said:
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
Click to expand...
Click to collapse
Forever like being 10 minutes min, maybe 15
ClaireH said:
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Click to expand...
Click to collapse
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
fe1ixs said:
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
Click to expand...
Click to collapse
Yep, same thing I ended up doing, thought I posted that but I guess I never did. I ended up using the darkside wipes and going back to an older version like you and someone else said. Now everything's just fine. And btw, to get into recovery from boot just restart it holding power, volume up, and volume down at the same time. Then once you see the Samsung logo let go of the power button but keep holding volume up and down till you see the recovery menu.
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
I was installing a 4.2 build along with 4.2 gapps.. Something was funky so I wanted to re-do it. When I went to flash the zip from internal sd card, it wasn't there. Nothing is there. All my backups are gone as well. I tried to restore, and it says it can't find any files. I can get into recovery mode, but I have no clue what to do from here?!
Please help!
Thanks
odin back to stock once that is done reboot into recovery and factory reset then start over this happened because your recovery is outdated
Is there a folder named 0?
Sent from my SGH-I747M
yulet said:
Is there a folder named 0?
Sent from my SGH-I747M
Click to expand...
Click to collapse
forgot about that
yulet said:
Is there a folder named 0?
Sent from my SGH-I747M
Click to expand...
Click to collapse
Yes, there are 3 files when I go to choose zip from internal sdcard... They are:
0/
legacy/
obb/
if i remember right 4.2 moved all your files to 0 because of multi-user support thats where all your files are if you can move them back you should be able to get to your backup
jerrycoffman45 said:
if i remember right 4.2 moved all your files to 0 because of multi-user support thats where all your files are if you can move them back you should be able to get to your backup
Click to expand...
Click to collapse
Ahh okay. I found the zips to reflash 4.2 so I'm just going to do that. Didn't see any of my backups though? Are those somewhere else?
not sure exactly have not used 4.2 yet just read up on it do a search in the thread you got the rom in and you will find a answer
I'll try looking. Because I have to restore. None of my stuff from Titanium Backup is there anymore. All my stuff is gone, except pictures, those stayed.
alright good luck
Does anyone know if the backups are somewhere else? Or are they basically gone? Can't find anything
Sent from my SGH-I747 using xda app-developers app
Boot loop - I think.....
I was running cwm nightlies for a year or more, i was using rom manager to update the nightlies on a regular basis with no issues, then i went to the stable cwm10 rom with no issue, again with rom manager, now after a while of enjoying that, I tried to return to stock and lay low for a while, I just backed up everything with TB and flashed a stock rom using odin, well now my gs3 just sits on the samsung logo as it pulses, this does not change, I have tried to flash and reflash the stock rom and others, i have tried to flash and reflash stock recoveries and custom recoveries too. I just dont have the needed knowledge or experience to get passed this issue, until i get it fixed, i have nothing.......... : (
ywngmn454 said:
I was running cwm nightlies for a year or more, i was using rom manager to update the nightlies on a regular basis with no issues, then i went to the stable cwm10 rom with no issue, again with rom manager, now after a while of enjoying that, I tried to return to stock and lay low for a while, I just backed up everything with TB and flashed a stock rom using odin, well now my gs3 just sits on the samsung logo as it pulses, this does not change, I have tried to flash and reflash the stock rom and others, i have tried to flash and reflash stock recoveries and custom recoveries too. I just dont have the needed knowledge or experience to get passed this issue, until i get it fixed, i have nothing.......... : (
Click to expand...
Click to collapse
i would do a factory reset in recovery
jerrycoffman45 said:
i would do a factory reset in recovery
Click to expand...
Click to collapse
i cant get into recovery..........
i can get into download mode, but not recovery, is there a technique to force it into recovery ?
what button combo are you trying should be volume up+power+ home and let go of power soon as you see the blue print at top of screen do this after a battery pull
jerrycoffman45 said:
what button combo are you trying should be volume up+power+ home and let go of power soon as you see the blue print at top of screen do this after a battery pull
Click to expand...
Click to collapse
wow, that seemed so easy, i have used root and custom roms and recoveries for so long now, that i completely forgot about the default way to get into factory recovery, it worked and now i am up and running, thanks for the support dude, i have never wanted to go backwards but now it is ok that i did,
glad you got it fixed
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