Develop Bugs

Help!

So i did the ULVH1 update through ODIN, followed the instructions. Once i was on ODIN picked the file for it. Ran it at firt it said Boot! Then Pass! So phone trys to reset but i get stuck on the reboot screen! Did i just brick the phone? Im rooted and using a custom rom (jedi mind trick v7). I need help on this.
Oh onre more thing. When i was stuck on the reboot. I tried getting into CWM and it got me through. Aren't i suppose to be unrooted already once this update occured?

Reboot loop? If you can get into CWM, you can always wipe, flash, wipe cache to fix things. If you can get into CWM you're still ok.
Now the thing about unroot and recovery, there's sort of different things. You can be unrooted, but still have CWM. CWM just lets you flash new ROMs that aren't manufacturer certified, I believe. I forget the details. So booting into ICS you could be unrooted, but the recovery is still CWM/TWRP

You are much better off using TWRP then CWM.

premiatul said:
You are much better off using TWRP then CWM.
Click to expand...
Click to collapse
Would you still use TWRP to flash roms that the OP recommends using CWM or CWM Touch?
I also understand NAND backups you made with CWM won't be restored successfully by TWRP?

So I got it to work. Im a noob on this stuff, so i wasnt sure if the file that XDA had was bad or not. I used a diff. one from phandroid.com. Went through ODIN and it went through with no problem. Lost root and CWM. Basically im back to stock. I eventually rooted again and CWM. But the funny part about it is that why do i still have my pics on the gallery? I thought this deletes everything? Like i said. Im a noob! lol. Everything seems working fine. Screen shots (went back the old way, instead of Power and Volume down.) Also, ISIS is that on google play? :good:

No flashing back to stock does not erase your internal storage.
Sent from my SGH-T989 using xda app-developers app

[Q] Help with New T-Mobile Jelly Bean OTA at Sammobile- T999UVDLI6

I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?

You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium

ktetreault14 said:
You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So because I had CWM recovery it failed?

Yea
Sent from my SGH-T999 using xda premium

Rooting after upgrade
Fonz said:
I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?
Click to expand...
Click to collapse
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.

Wipe-o-rama
fishguts said:
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.
Click to expand...
Click to collapse
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it

Hmmm
Fonz said:
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it
Click to expand...
Click to collapse
Okay, I retraced my steps and everything still works fine for me...so I did some things to break my phone a bit to see how this can fail, and came out with a few results.
Using Odin, uncheck the "Auto Reboot" option, I think this ROM will reflash to stock upon reboot unless disabled, it's a "feature" found in the Galaxy Tab 2 also. CWM 6.0 will take care of that, as they ask you to disable that "feature" upon reboot from CWM. Now, in order to get there, you need to go directly from Odin mode to recovery. So here's what I did exactly to get the results that you are asking for:
Using Team Win Recovery Project (TWRP Recovery), I wiped dalvik, cache, system, data, and factory reset, and then I opened Odin, unchecked "Auto Reboot" option, flashed T999UVALH2 back to stock, rebooted into android recovery, factory reset, reboot back into android recovery, flashed T999UVDLI6, and then rebooted into android recovery, did a factory reset, and rebooted into Odin mode, where I kept that same box unchecked, and flashed TWRP recovery. After it flashed, I unplugged my cable, and rebooted directly into the custom recovery where I flashed SU. Booted my phone and I have root access with JB. Now, if you don't want to use TWRP as your recovery, then you should use the latest version of CWM.
I was typing this as I was doing it, so I know for sure this works. At least, for my phone it does. Good luck and I hope this helps!

Awesome. Thanks for taking the time to troubleshoot for me. I will try today and report back
Sent from my SGH-T999 using Tapatalk 2

Please clarify
I am fully stock and using stock recovery and I am getting an error regarding :E:signature not being valid when I try to flash. I have applied OTAs that my phone received in the past. Dose this mean I need to revert back to the default firmware image also or is there a different issue? Thanks

I've been flashing OTA leaks with CWM. Both ICS and JB. I don't lose CWM recovery. This process is a lot easier than some people think. I have never needed stock recovery to update to the OTA leaks.
1) Stop using CWM v5. Its time to upgrade to v6.
2) Get T999UVALH2 on your phone. Whether you have UVALEM and use the official OTA update to UVALH2, or do a full install of it. You need UVALH2. I personally still had a UVALEM nandroid, so I restored then factory reset. Then backed up the clean install. Then I ran the OTA through the phone settings > About phone > Software updates. Now I had UVALH2. Guess what? Nandroided that, too.
Also, make sure you flash the UVLH2 modem if using another version.
3) If needed, get CWM on there through Odin. Or if you got a prerooted version, get CWM on there through other means.
4) Download the OTA update here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware
5) Flash update with CWM. Upon exit, it will ask you about recovery and root.
Now you have the new leak, CWM recovery, and root.

CWM 6 did the trick. Still rooted and running JB
Sent from my SGH-T999 using Tapatalk 2

[Solved] $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)

Basically this is what happened, I rooted my phone using TeamEpic-Root-from-Recovery-v5.zip and CWM-Recovery-LTE-SGS3-v5.tar.zip with Odin without any problems. Then I tried tampering with the framework-res.apk and I thought I did it correctly, I replaced it with the current res in the /system/framework folder of the internal sd. Then I rebooted my phone and bam stuck at the Samsung Galaxy S III screen. I've now tried finding a way to get into the internal sd card to replace the framework-res.apk back to original but my computer wont recognize it when in recovery or downloading mode. I have trying reflashing Clockworkmod several times and I've tried wiping the cache and factory reset. When I factory reset it says error mounting sd card, aborting. I am now out of ideas as to how to fix it and I'm not sure what to do with PIT files, which could be a possible solution. I am running Tmobile's Galaxy S3 T-999 16gb. All that being said, anyone who can help me get my phone back up and running I will reward you with $10 through paypal, because that's how desperate I am to fix my phone before someone finds out I bricked it!

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app

camacho.kyle said:
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, what do you mean by reinstall drivers, like kies? I can't flash any rom's because I can't transfer the zip files over to the sd card since my phone won't recognize it since it won't go past the samsung screen. All I can do is flash clockwork mod from odin like .md5 and .tar. If I install a lower version of Odin what version did you use, and do you think flashing clockwork mod will be able to replace the framework-res.apk through odin?

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
iAmYoungSpiffy said:
Thanks for the reply, what do you mean by reinstall drivers, like kies?
Click to expand...
Click to collapse
Reinstall the drivers for Odin, and you can even try reinstalling Kies too. Make sure you restart your pc after you reinstall kies and the drivers.
Sent from my SGH-T999 using xda app-developers app

Are the files you flashed for a I9300? They do not look familiar to me.

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Aerowinder said:
Are you using a SGH-T999 or an I9300? If the former, use the links in my signature. Should fix it if it's not hosed.
Uninstall Kies (and the drivers if the Kies uninstall doesn't do it).
You may want to Odin a stock rom. If you do, it it before flashing a recovery.
Click to expand...
Click to collapse
He's using a T999
Sent from my SGH-T999 using xda app-developers app

camacho.kyle said:
He's using a T999
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Do you think changing the clockworkmod .tar.md5 file and flashing something different will have any affect? If so, what do you suggest?

Check out my signature, it has everything you should need (save the OS you want).

Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Wow thanks for that clockworck mod! It has much more features than v5 I'm gonna play around with it and see what I can come up with.

Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Thank you for the files, I'm now able to flash roms from my sd. I"ve flashed your clockwork and superuser. However, when I load up the phone I'm still getting stuck at the samsung logo

no external sdcard?

Did you try to flash another rom? What were you using, and what did you flash?

Why are you trying to fix a bricked ROM with CWM?
Just Odin a stock rom, and work from there. I don't know why you would keep trying to reflash recovery, that isn't going to do squat for you.

Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott

mt3g said:
no external sdcard?
Click to expand...
Click to collapse
I do, 64gb

Aerowinder said:
Did you try to flash another rom? What were you using, and what did you flash?
Click to expand...
Click to collapse
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?

You can't flash a rom from your external sdcard? or your internal? or either?

sbaeder said:
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
Click to expand...
Click to collapse
I've now tried flashing Team Epic's ROM and I've wiped all cache restored to factory settings wiped dalvik cache, no progress.

mt3g said:
You can't flash a rom from your external sdcard? or your internal? or either?
Click to expand...
Click to collapse
Now that I updated my clockwork mod I'm able to flash from my sd card. Trouble for me is finding the right ROM that is compatible and appealing. I've tried a few now and whenever I flash them I go to boot up the phone and I get stopped on the samsung galaxy s iii logo. There has to be a way to wipe everything and flash a fresh clean rom. I've stayed up till 2 in the morning only to get up at 6 in the morning two nights in a row now totaling almost 10 hours of trying to fix my phone

iAmYoungSpiffy said:
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
Click to expand...
Click to collapse
From this quote it seems that you are flashing TWRP recovery and the flashing CWR right after it. That makes no sense. I don't use CWR on this phone but have used it before. So I'm not sure that LTE should be in the description as T999 isn't an LTE device. I could be wrong though. You can get an Odin-able version of either TWRP or CWR from this page.
Go here and download the stock image TMO T999UVDLJA. Follow the directions in the OP (make sure you unzip it first. Read and then read it again) . Fire up Odin and put the Root66 tar in the PDA slot (nothing in PIT). Flash the Root66. It will take about 5 minutes or so. Once it says Pass it should reboot. It WILL bootloop. If you have already flashed EITHER TWRP or CWR, then boot into recovery and Factory Reset. If you haven't flashed EITHER TWRP or CWR, then pull your battery and boot back into Download Mode. From there you put EITHER TWRP or CWR into the PDA slot and flash it. Pass. The reboot into recovery and Factory Reset.
First boot will take the longest bc it has to rebuild the /cache and /dalvik-cache. Let's get you up and running before you move on to flashing a custom ROM, OK?

Im still here having problems booting 4.4.2

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.

[Q] HELP! Can't get out of Custom Recovery

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