Develop Bugs

[Q] Can I realy just flash to CM10.1 or do I still need to root first?

I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?

You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.

Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.

I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.

Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.

[Solved] [Q] SGH-T999 Rooted bad, phone stuck on start screen

Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.

Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.

Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.

Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.

Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this

Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?

Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.

buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened

Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.

Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.

Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems

:good:

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*

buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.

Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums

buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app

[Q] Now stuck PLS HELP

This is my very first post i have found many solution on this forum which helped me & my friends But need help with this 1
Ok here goes my Story
I have recently brought s3(used) it was on 4.3 & rooted with philz touch 6 didn't check the firmware details etc
As i was playing with philz touch 6 & did something which i remember was to clean rom or some thing now the phone boots & shows Samsung Galaxy SIII & stops there
I think its on I747UCUEMJ2 Modified ROM » Root, KNOX Disabled, SE-Linux Disabled not sure
Is there a way to get it back ..?

If you are able to access download mode, you could easily flash a custom ROM.

S i can access download mode
Can i go back to stock or only custom firmware from now on..?

vipimg said:
S i can access download mode
Can i go back to stock or only custom firmware from now on..?
Click to expand...
Click to collapse
If I were you, I would go to a custom firmware. That is if you have a custom recovery like ClockWorkmod or TWRP. But you can flash stock, at least to my understanding. But I'd look into that.
(Your bootloader will need to be unlocked too)

I am on Clockworkmod v6.0.3.1 the thing is i don't want a custom firmware 2 many problems
I would like to load stock buy have read most of them get their phones bricked

vipimg said:
I am on Clockworkmod v6.0.3.1 the thing is i don't want a custom firmware 2 many problems
I would like to load stock buy have read most of them get their phones bricked
Click to expand...
Click to collapse
If you were on the 4.3 official stock ROM that was pushed out, you have a possibility of bricking your device downgrading to lets say the 4.1.2 stock ROM.
A custom ROM isn't bad though. If you do like Touchwiz based ROMs you may be able to find one in the development section.
Sent from my Nexus 7 using Tapatalk 4

I am in need of stock so that i an connect to kies & back up useful info
A good custom rom for daily use which do u prefer ...?

vipimg said:
I am in need of stock so that i an connect to kies & back up useful info
A good custom rom for daily use which do u prefer ...?
Click to expand...
Click to collapse
What information are you wanting to backup?
You'll have to find your ROM of choice. If you want a reliable ROM then I'd recommend something that is stable, which should always be said in the thread,
Sent from my Nexus 7 using Tapatalk 4

Notes,contacts ,sms etc
Will check out stable Rom

vipimg said:
Notes,contacts ,sms etc
Will check out stable Rom
Click to expand...
Click to collapse
Contacts could be backed up if you sync with your gmail account. SMS can be done by an application on the market. Notes that are synced on Evernote or Keep should just be there.
Sent from my Nexus 7 using Tapatalk 4

ok will check it out

Ok i have downloaded some Rom (all different ) i get status 7 when installing it & re do the script i get status 6 error
Any ideas about it ..?

So i waited for a while to get my answers or solution still nothing
Got bored looking @ my s3 lying as a paper weight as decide to downgrade to the stock firmware 4.1.1 by odin
Read many user's post about downgrading from 4.3 to stock 4.1.1 will brick the phone BUT it works with out problems & on the first try
Really Happy that now its on stock & can do a update/backup my stuffs .........

Note II (n7100) - Constant freezing and rebooting

Hi,
Have a Note II as an alternative phone. Apparently, the phone worked correctly until last month. It started to reboot, not too much, but it happened. Well, I tried to give a solution changing the ROM (when it started with the problem I was in 4.4.2 OmniROM). My first try was with Omega ROM, cause it was my first custom ROM when I bought the phone with 4.1.2 in, but the problem persist (maybe increment the number of reboots-freezes/day) so I changed it again to Android Revolution HD, but it only increment the reboots/freezes.
It seems that it's not a ROM installation problem or something like that, maybe it's a hardware problem, but I would like to hear your opinions about it.
Now the phone have:
TWRP recovery
Rooted
Android Revolution HD
I am thinking on put the stock ROM and bootloader with Odin. What do you think?
Thanks!

Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.

My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105

mat9v said:
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
Click to expand...
Click to collapse
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Edit:
jakuburban said:
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
Click to expand...
Click to collapse
Did you repair it even with custom ROM? Samsung does not accept it, right? Anyway, my phone is not in guarantee time.
Thanks!

Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105

pep0te said:
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Click to expand...
Click to collapse
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.

jakuburban said:
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
Click to expand...
Click to collapse
Hope I can fix it by other way then . Thanks!
mat9v said:
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
Click to expand...
Click to collapse
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.

pep0te said:
Hope I can fix it by other way then . Thanks!
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
Click to expand...
Click to collapse
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.

mat9v said:
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
Click to expand...
Click to collapse
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!

pep0te said:
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
Click to expand...
Click to collapse
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE

mat9v said:
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
Click to expand...
Click to collapse
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.

pep0te said:
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
Click to expand...
Click to collapse
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law

mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Amazing, alright now. Hope I can fix this usual problem...
Thanks for your complete and helpful answers!

mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app

pep0te said:
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).

mat9v said:
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
Click to expand...
Click to collapse
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app

pep0te said:
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, exactly.

mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Okay, I will do it then. Thanks a lot! :fingers-crossed:

mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!

pep0te said:
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
Click to expand...
Click to collapse
To fully reset the counter it has to be done in certain order. I do not remember exactly in which order the sequence of events should proceed but it went something like this:
- run triangle away
- reboot
- enter download mode (odin version)
- flash stock rom
If you reboot even once to custom rom (this I'm certain) or even custom recovery (I think) the triangle away effect will be gone and the count returns to 1 because it detects custom rom/kernel.

[Q] Where to start?

Hello there,
My gf just got a Galaxy Tab 3.0 7 inch SM-T210 with Android 4.1.2.
Now i want to put a custom firmware on it like CM or anything like that.
But where to start?
Im not into Samsung and have no idea. Dont see any guide gifing with tips or so...
Can someone guide me in the right direction?
I did read about CWM and TWRP, download ODIN and flash it. But is that all?
With HTC i had to unlock bootloader first, flash boot.img etc etc.
Thanks!
Greetings!

can i help
Azerox said:
Hello there,
My gf just got a Galaxy Tab 3.0 7 inch SM-T210 with Android 4.1.2.
Now i want to put a custom firmware on it like CM or anything like that.
But where to start?
Im not into Samsung and have no idea. Dont see any guide gifing with tips or so...
Can someone guide me in the right direction?
I did read about CWM and TWRP, download ODIN and flash it. But is that all?
With HTC i had to unlock bootloader first, flash boot.img etc etc.
Thanks!
Greetings!
Click to expand...
Click to collapse
hi from what im understanding ur wanting to root it and install custom firmware
here is a video i used from rootjunky to root my tablet with twrp
https://www.youtube.com/watch?v=BDShwBHRjUE
hope it helped

@first there is no cm for this tab. All custom roms based on stock rom or 4.2.2 port from sm-t110
There is no need to unlock bootloader like HTC. No seperate flash of Boot.img...
Install cwm or twrp recovery with Odin. Check threads for Odin install instructions. Its easy going
Cwm:
http://forum.xda-developers.com/showthread.php?t=2433853
Twrp:
http://forum.xda-developers.com/showthread.php?t=2653391
If you only want to root flashable ZIP for root is attached in recovery threads.
If you want to try custom roms check index thread for sm-t210 Roms.
http://forum.xda-developers.com/showthread.php?t=2755532
Sent from my One using XDA Free mobile app

rbotz said:
@first there is no cm for this tab. All custom roms based on stock rom or 4.2.2 port from sm-t110
There is no need to unlock bootloader like HTC. No seperate flash of Boot.img...
Install cwm or twrp recovery with Odin. Check threads for Odin install instructions. Its easy going
Cwm:
http://forum.xda-developers.com/showthread.php?t=2433853
Twrp:
http://forum.xda-developers.com/showthread.php?t=2653391
If you only want to root flashable ZIP for root is attached in recovery threads.
If you want to try custom roms check index thread for sm-t210 Roms.
http://forum.xda-developers.com/showthread.php?t=2755532
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, i found out how it works. Real easy.
Only problem i have now is that ALL the ROMs seem to be alot of crap.
Not working, resolution problems or FCs. And yes i use the T210 versions and no other.
Also recoverys are baaad. Lol now i know why i will never get a Samsung ... crap casing, crap software.

Azerox said:
Thanks, i found out how it works. Real easy.
Only problem i have now is that ALL the ROMs seem to be alot of crap.
Not working, resolution problems or FCs. And yes i use the T210 versions and no other.
Also recoverys are baaad. Lol now i know why i will never get a Samsung ... crap casing, crap software.
Click to expand...
Click to collapse
If u would like i could upload a list of build.prop tweaks to use to improve over all performannce like image battery life wifi speed stuff like that just over all makes the tab run smoother

Azerox said:
Thanks, i found out how it works. Real easy.
Only problem i have now is that ALL the ROMs seem to be alot of crap.
Not working, resolution problems or FCs. And yes i use the T210 versions and no other.
Also recoverys are baaad. Lol now i know why i will never get a Samsung ... crap casing, crap software.
Click to expand...
Click to collapse
Try looking at the specs of each ROM and compare it with yours. I am currently running S.E.A.L ROM
with the Black hawk kernel I am finding it faster than the Stock ROM and also way less bloatware.
Try this or the RocketTab Rom and Blackhawk. These tend to work the best for most SM-T210 and R.