[Simple Method] How to get OTA/Kies update on a Rooted phone - Galaxy Note II General

Well I am an average user but been using Droids for three years now. Anyway, lets come to the point.
◘ This is for the persons who can't stay unrooted (like me).
◘◘ This is for those persons who have rooted his/her device with Chainfire's OR Chenglu's method, can't say about any other recovery/custom kernel.
◘◘◘ And most importantly for those who DO NOT want to lose their data every time.
Just fyi, if you go in to Download mode/Odin mode (Vol Down+Home+Power), you will see two things there at the bottom saying,
CURRENT BINARY and
SYSTEM STATUS.
► Now if you want to receive OTA updates or via Kies you MUST see those two things stay as OFFICIAL. If you see one of them as Custom, whatever you do you WILL NOT receive any official OTA/Kies update. I've been trying to resolve this thing for last two days, but unsuccessful on all try, regardless of the matter that I unrooted, flashed Stock kernel back, used Triangle Away to reset counter and stay on Stock recovery, everything!
So what you need to do is pretty simple actually. You are rooted? Cool. No need to unroot and do lot of things. You just need to have the last official ROM of your country. And then you go on, open Odin and Flash it. So now you are automatically unrooted and most importantly both Binary and System status will now be OFFICIAL, and that's what you needed. So now turn on your device, check for OTA update, and it will pop up and be installed successfully. Same goes for Kies. So now you are updated. And you WILL NOT lose any data. Now go on and root again with your desired recovery/root method.
When you are NOT rooted and everything is Official you will see the below (Red marked circle) icon at status bar when you check for OTA update. This icon is very important actually, it means that you are connected to OTA server.
And when your phone is updated to the latest available software you will see this pop up.
But when you are rooted with Stock recovery you WILL NOT see that small icon on status bar and OTA update will keep saying 'Checking for updates' forever and it will never ultimately connect to OTA server.
And when you are rooted with Advanced recovery you'll see this,
Now you can obviously skip all these and just download the latest ROM. But then again the latest OTA updates are so tiny, for example the last update is just 12 MB, so will you download a 1 GB ROM for a 12 MB update? If you have a flying connection then kindly go ahead, I don't have so I gotta think about alternatives, like above.

jujuburi said:
But when you are rooted with Stock recovery you WILL NOT see that small icon on status bar and OTA update will keep saying 'Checking for updates' forever and it will never ultimately connect to OTA server.
Click to expand...
Click to collapse
I was rooted with stock recovery, still i have got update of 12.4MB, and installed successfully too.Important thing is not 'root' but system status 'official'
Though i never prefer this method, 2 out of 10 time it mess up things. I have just did today to check weather i can get OTA or not, and it can preserve root or not.
If you want best performance and never want to carry old junks to new ROM,There is nothing better then flashing full ROM with PC odin (clean Install).

dr.ketan said:
I was rooted with stock recovery, still i have got update of 12.4MB, and installed successfully too.Important thing is not 'root' but system status 'official'
Click to expand...
Click to collapse
But why it isn't happening for me
I am on Stock recovery too! and the System Status is never official unless I re-flash a full ROM!

Whenever post root(& reseting counter) i do wipe cache and data, it just bring status to 'official' for me.
Even this time mine system status is 'official' like before.

dr.ketan said:
Whenever post root(& reseting counter) i do wipe cache and data, it just bring status to 'official' for me.
Even this time mine status is official like before.
Click to expand...
Click to collapse
Oh buddy, now I get it. You do a full wipe post root? Hmm! That removes everything from the device and I really don't wanna do. Can't miss all the imp things each time

I never miss anything, when i wake up in the morning my device is ever ready for wipe without worrying me lossing something, due to this
http://forum.xda-developers.com/showthread.php?t=1837984
Hardly it takes 15 min to get my data back, and for that it keeps my device clean

dr.ketan said:
I never miss anything, when i wake up in the morning my device is ever ready for wipe without worrying me lossing something, due to this
http://forum.xda-developers.com/showthread.php?t=1837984
Hardly it takes 15 min to get my data back, and for that it keeps my device clean
Click to expand...
Click to collapse
Knew about Nandroid. But sadly TB gives me problem too often. Anyway I'll keep that in mind.

Not nndroid, nandroid just for emergency
I never have any issue with Titanium, yes one rule I keep in mind, never restore system junk.

dr.ketan said:
Whenever post root(& reseting counter) i do wipe cache and data, it just bring status to 'official' for me.
Even this time mine system status is 'official' like before.
Click to expand...
Click to collapse
Hi there buddy
I also wiped data post root (cf auto root) and status in download mode was official but as soon as I restarted the mobile and rechecked the status in download mode it was set to custom with binary counter 0. Couldnt find a way to keep the status to official after the restart. Did u have any such issue???
Sent from my GT-N7100 using Tapatalk 2

No i don't have such issue. It remains 'official'

dr.ketan said:
No i don't have such issue. It remains 'official'
Click to expand...
Click to collapse
Hmmm... any idea what might b the issue. Tried to keep it official by doing fact reset twice to make sure that I didnt miss anything but didnt help.... any advise/idea?
Sent from my GT-N7100 using Tapatalk 2

Using any mod?
Sent from my GT-N7100 using xda premium

dr.ketan said:
Using any mod?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Nope pure stock n below is what I did.
1. Flashed cf auto root through odin to gain root
2. Went to recovery n did clear cache n fact reset
3. Once booted, installed triangle away to reset counter
4. After boot, went to download mode to check the details. All was official with counter 0. Noticed that in about phone--> status it also showed normal till then.
5. Then restarted and about phone--> status was modified so went to download mode to check n there also status was custom....
Now do u think I did something wrong ? I dont mind fact resetting again if u can guide me through and identify my fault as I m home early from the bank tonight...
Sent from my GT-N7100 using Tapatalk 2

You have reset before triangle away, which basically modify system. So I think you should wipe cache, wipe data, and again wipe cache (what you doing) after resting counter.
You can do it right now as you already have reset counter.
Sent from my GT-N7100 using xda premium

dr.ketan said:
You have reset before triangle away, which basically modify system. So I think you should wipe cache, wipe data, and again wipe cache (what you doing) after resting counter.
You can do it right now as you already have reset counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
So if in the current state, if I fact reset now, will it be official again????
Sent from my GT-N7100 using Tapatalk 2

Wipe cache and data from recover and again wipe cache from recovery.
It should be official except something messed up to your device.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I was rooted with stock recovery, still i have got update of 12.4MB, and installed successfully too.Important thing is not 'root' but system status 'official'
Though i never prefer this method, 2 out of 10 time it mess up things. I have just did today to check weather i can get OTA or not, and it can preserve root or not.
If you want best performance and never want to carry old junks to new ROM,There is nothing better then flashing full ROM with PC odin (clean Install).
Click to expand...
Click to collapse
I am confused:
Obviously you are rooted, and (from your other threads) you use nandroid (and titanium) the former of which require CWM recovery. How are you on stock recovery?
Sitting there in its box is a n7100 I have not opened yet. Do you recommend as is out of the box flash it with pre-rooted stock? Will it be able to receive OTA's and work with Kies? I understand you do not like OTA's, in which case wait for the next pre-rooted stock and apply Titanium restore after flashing? If I choose to apply the OTA will I lose root? I understand there is an app OTARootKeeper...
Thanx doc! (colleague!)

I used Triangle Away today to reset counter and system status back to official and normal, worked just fine. I had OTA of about 73 M this morning and my ROM is ME6 ( UK BTU) dated 31/05/2013. Of course this removed root but I used cf autoroot via PC Odin. I didn't have the superSU app afterwards, but just downloaded it from Play store.
NB I ticked "Allow tracker to run" in Triangle Away.
Sent from my GT-N7100 using Tapatalk 2

phochiom said:
I used Triangle Away today to reset counter and system status back to official and normal, worked just fine. I had OTA of about 73 M this morning and my ROM is ME6 ( UK BTU) dated 31/05/2013. Of course this removed root but I used cf autoroot via PC Odin. I didn't have the superSU app afterwards, but just downloaded it from Play store.
NB I ticked "Allow tracker to run" in Triangle Away.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
1. Is your bootloader normal too?
2. Strange, CF should have installed SuperSU, should it not?

drgkt said:
1. Is your bootloader normal too?
2. Strange, CF should have installed SuperSU, should it not?
Click to expand...
Click to collapse
What do you mean by "normal" bootloader, now it's DME6 (was ALJ1 before update)
Yes strange, I had superSU before update, afterwards I rerooted with CF autoroot, the icon was there in app drawer, but when you launch the app it says no binary found and it can't download it. I just reinstalled it from Play store.
I think this happened to someone here on this forum, not sure if it was specifically on Note 2 forum.
Anyhow, the ROM is running just fine now, rooted and all Normal in status and 0 counter and official in download mode.

Related

Updated OTA - Now my tab seems broken

Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.
vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?
GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.
vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.
I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.
I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly

Removing "Custom" from the boot screen for a return

Hello everyone,
I've been looking around the forum but I haven't been able to find an answer to this. Right now I have a rooted Samsung Galaxy S4 from Verizon (I rooted it using this method: http://forum.xda-developers.com/showthread.php?t=2290798). The device is currently fully rooted with the original ROM in place (I have not installed ANY custom ROM's ever). I am looking to return the phone to the store tonight but when I unroot through SuperSU and then do a factory wipe (through the settings tab not through any special program) I get the "Custom" message upon booting up again. I have tried rooting/unrooting a number of times with no success. My current position is as follows: I am rooted using the aforementioned method, I have not installed a custom ROM so I assume that I am on the stock ROM, I have installed SuperSU and TriangleAway (TriangleAway says that I have a 0 flash counter). If anyone has any advice I would greatly appreciate it as I might need to return the S4 to the store within the next 2 hours to get my refund. Thanks in advance for any information you can provide and I apologize for the quickness of my request.
Truncated link for the root method
It looks like the forum truncated my link. Here is the full address for the root method I used: http://forum.xda-developers.com/showthread.php?t=2290798 . Thanks again!
What I would do is go to the Android Development forum and download Sextape's one click restore for MDC. It will wipe everything from the internal card and reset you back to MDC. Take the OTA to MDL if you wish.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2258827
Pretty sure it will wipe out any custom indications. I've used the one-click methods for years on the E4GT and here on the S4. Very convenient.
I just went through the same thing. What I did is triangle away, defrost any system apps that maybe frozen disable supersu, reboot, and wallah "official". I repeated these steps twice as the first time it did not take.
P.s. when I ran a frozen system app filter in TB I saw an app called sys scope that was frozen and I don't recall ever freezing that app. Hell, i don't even know what it does but I defrosted it anyway
and all is well
Sent from my SPH-L720 using xda premium
Triangle away doesn't work for MF9 just yet I believe, but it did for MDC. Can always Odin back there, then run triangle away. Ughh, i hate trips to the sprint store
Sent from my SPH-L720 using Tapatalk 2

[Q] (Root not happening) S4 i9500 {4.3 - I9500XXUEMJ8} {CSC - INU} {How to root now?}

Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Here too
avineshwar said:
Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Click to expand...
Click to collapse
Yep, I can´t re-root it again it seems the CF-Auto-Root-ja3g-ja3gxx-gti9500.tar its not working for the i9500XXUEMJ8 versión, well time to wait to an updated CF-Auto Root :crying::crying::crying:
I9500XXUEMJ5 root working (almost working)... i cant run some app, without root all apps working great ;/
Weird. I rooted using CF Auto Root after flashing 4.3 MJ8, it always worked! I never did OTA update though, always used Odin and full wipe.
avineshwar said:
Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Click to expand...
Click to collapse
The rooting worked so far for me. Have you enabled KNOX? They enhanced the security features and as far as I heard KNOX-enabled devices can't get full root. Verify whether it is enabled or not. I'm not sure whether the user enables it or not but that may be the reason. I'm also not sure whether this KNOX security really affects I9500 models. I9505 models are definitely affected.
jujuburi said:
Weird. I rooted using CF Auto Root after flashing 4.3 MJ8, it always worked! I never did OTA update though, always used Odin and full wipe.
Click to expand...
Click to collapse
Probably I never full wiped.
The apps and all other data is retained (normally all is retained when we update rom via odin).
Factory reset (full wipe) was never required earlier to get root to work.
Knox is not on from my side though I get some notifications always that some app tried to access something and Knox blocked that. But I guess that is something else because we need to manually activate Knox after opening the Knox app.
Sent from my GT-I9500 using xda app-developers app
kci83 said:
I9500XXUEMJ5 root working (almost working)... i cant run some app, without root all apps working great ;/
Click to expand...
Click to collapse
It did worked for me too but only at times.
When I updated rom switcher app, root was gone and it never happened again!
Sent from my GT-I9500 using xda app-developers app
anyone with any solution for this?
anyone with any solution for this?
Solved!
Sent from my GT-I9500 using xda app-developers app
what was the solution? did you need to do a fullwipe? or used another method for rooting?
im on 4.2.2 MG9 and would like to update to 4.3 and have root without the know issue.
thanks.
Backup and Factory reset and cache clear after updating to 4.3
Then you'll get stock Samsung 4.3
Follow the same method to root (auto root) or alternatively flash super su via cwm/twrp/stock recovery.
resitm said:
what was the solution? did you need to do a fullwipe? or used another method for rooting?
im on 4.2.2 MG9 and would like to update to 4.3 and have root without the know issue.
thanks.
Click to expand...
Click to collapse
avineshwar said:
Backup and Factory reset and cache clear after updating to 4.3
Then you'll get stock Samsung 4.3
Follow the same method to root (auto root) or alternatively flash super su via cwm/twrp/stock recovery.
Click to expand...
Click to collapse
Thank you. Will this trip the knox thing?
After using CF-AUto root you need to update Super SU App on first boot.
Then Open SuperSU app and choose to install SU Binary without using a custom recovery.
Then reboot.
Then install Titanium backup pro and use it to free all Knox related files.
There are 7 of them and you need to remove all of them.
Remember you need to install a custom recovery to install busybox. (atleast in my case)
Install http://forum.xda-developers.com/showthread.php?t=2489234 via ODIN.
Once you are on custom recovery.
Use busybox installer to install busybox.
reboot.
You are done.
resitm said:
Thank you. Will this trip the knox thing?
Click to expand...
Click to collapse
No mate.
Wait for a future update to trip that.
In the mean time, I'm trying to trip that since it isn't very difficult just lazy to try everything since everytime 1 thing fails, I need to restore the whole data and if takes much of my bandwidth.
Hope you understand.
And the device status will also remain custom.
P.S. Touchwiz UI from Samsung will hang on a later date due to some app compatibility issue (I'm not sure which app but I can tell a large set of apps and it will hang due to any one from that list) so it is preferred to shift to some other launcher on pre hand.
Sent from my GT-I9500 using xda app-developers app
thank you both avineshwar and ajhavery.
i really wanted to update but i guess i am going to wait for a while. lots of issues seem to be happening once rooted. also dont want to lose warranty with the knox thing.
it seems the custom roms such as arrow and crash also have sound issues, FC issues on some apps.
i guess ill wait and see. maybe once the nexus 5 is out i can sell the i9500 and get the nexus 5.
resitm said:
thank you both avineshwar and ajhavery.
i really wanted to update but i guess i am going to wait for a while. lots of issues seem to be happening once rooted. also dont want to lose warranty with the knox thing.
it seems the custom roms such as arrow and crash also have sound issues, FC issues on some apps.
i guess ill wait and see. maybe once the nexus 5 is out i can sell the i9500 and get the nexus 5.
Click to expand...
Click to collapse
Waiting is good.
Don't sell your phone though (for obvious reasons).
You've got much to explore.
When it comes to selling, you'll get money whenever you do that so keep that option as your last bet.
Custom roms aren't really preferred from my side until you are a die hard modification fan!.
Rooting is the only problem (which is solved now I guess) on the latest firmware.
Rooting won't do any problem, believe me (except warranty).
Sent from my GT-I9500 using xda app-developers app
avineshwar said:
Waiting is good.
Don't sell your phone though (for obvious reasons).
You've got much to explore.
When it comes to selling, you'll get money whenever you do that so keep that option as your last bet.
Custom roms aren't really preferred from my side until you are a die hard modification fan!.
Rooting is the only problem (which is solved now I guess) on the latest firmware.
Rooting won't do any problem, believe me (except warranty).
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
hello again, i am asking this question because i cant post in the development forum yet.
i downloaded 3 files from the OP http://forum.xda-developers.com/showthread.php?t=2317105
the PDA, CSC and modem. all for MJ8, downloaded PDA is odex.
when i flashed 3 of the files with ODIN like shown in op my device. After i restarted i got errors for Unfortunately, the process com.google.process.gapps .
i searched on google and did what was suggested, like clearing dalvik cache, resetting default apps, uninstalling the play store update etc.
the phone was unusable, the errors popedup every second.
I had to go back to the MG9 4.2.2 firmware.
What did i do wrong?
have you guys tried the method mentioned in the post. it prerooted and knox free 4.3 firmware.
resitm said:
hello again, i am asking this question because i cant post in the development forum yet.
i downloaded 3 files from the OP http://forum.xda-developers.com/showthread.php?t=2317105
the PDA, CSC and modem. all for MJ8, downloaded PDA is odex.
when i flashed 3 of the files with ODIN like shown in op my device. After i restarted i got errors for Unfortunately, the process com.google.process.gapps .
i searched on google and did what was suggested, like clearing dalvik cache, resetting default apps, uninstalling the play store update etc.
the phone was unusable, the errors popedup every second.
I had to go back to the MG9 4.2.2 firmware.
What did i do wrong?
have you guys tried the method mentioned in the post. it prerooted and knox free 4.3 firmware.
Click to expand...
Click to collapse
Probably you want to upgrade to 4.3?
If so goto sammobile.com and find the latest firmware for your device from there, download and flash the same via odin.
You're now on 4.3!
Once done you can root from the auto root method by chain fire.
Sent from my GT-I9500 using xda app-developers app
avineshwar said:
Probably you want to upgrade to 4.3?
If so goto sammobile.com and find the latest firmware for your device from there, download and flash the same via odin.
You're now on 4.3!
Once done you can root from the auto root method by chain fire.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
that would be the easiest and best solution but i am worried about the knox issue, losing the warranty and also having to sell the phone later on for a lower price.

[Q] device status : custom

how can i fix this?
i think the xposed modules messed up my rom and now ive lost my root because i updated my firmware to XXUGNG4,
my counters are still 0x0,
but my device status says its custom even though im on stock odexed rom,
is it possible to fix this w/o odin?
because i dont have a p.c,
and if flash a fresh stock rom will my device status change to official?
and what are the chances of triping my counters?
wipe data/cache in the stock recovery.
wanam xposed also has the option to fake your status to "official", dont know whether it works though.
Lennyz1988 said:
wipe data/cache in the stock recovery.
Click to expand...
Click to collapse
i tried that but sadly it still says custom and eventhough i uninstaled the modules the mods still sticks with the apps,
like the exit button on the browser and the silent shutter sound of the cam,
eprov said:
wanam xposed also has the option to fake your status to "official", dont know whether it works though.
Click to expand...
Click to collapse
yes it does have that option but i lost my root bcoz i updated my os,
switchblade00 said:
i tried that but sadly it still says custom and eventhough i uninstaled the modules the mods still sticks with the apps,
like the exit button on the browser and the silent shutter sound of the cam,
Click to expand...
Click to collapse
Factory reset and anything wont work to make it official. If that would have been the method, why was triangle away introduced. :/
Nothing will hapoen till you get your root access.
Obtain root access, try wanam, because triangle away does not work for i9500.
Can try reflashing the stock rom, it might be of little use though.
Till you get yourself root, nothing good can happen...
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Factory reset and anything wont work to make it official. If that would have been the method, why was triangle away introduced. :/
Nothing will hapoen till you get your root access.
Obtain root access, try wanam, because triangle away does not work for i9500.
Can try reflashing the stock rom, it might be of little use though.
Till you get yourself root, nothing good can happen...
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Finally i found the way to fix it...
Flashed a fresh stock rom using odin...
Cool
Thank me if I helped
Sent from my Samsung Galaxy S4 via XDA app.

[Q] What? Custom Status?

I have a Samsung galaxy s4 running 4.2.2 AT&T, Recently I used triangle away and SuperSu to get rid of root and to get the official device status. I went into Odin and it said failure and I noticed that it said custom in the device status. So then I went to motorchopper how I rooted in the first place and did that and it also said "rooting... Failure" so now the questions is how do I get root access back so I can unroot it and then flash the official 4.2.2 and then get 4.4.2?
Flashing 4.2.2 in Odin will remove root. Why do you want to go to 4.4.2? You will no longer be able to use twrp or cwm if you do.
Sent from my Nexus 5 using XDA Free mobile app
Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical
OhDreamsNo said:
Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical
Click to expand...
Click to collapse
I don't know what the current status of your device is or what you're ultimately trying to achieve. But I would recommend you stay on 4.2.2, mdl, firmware and flash a 4.4.2 custom rom.
Sent from my Nexus 5 using XDA Free mobile app
Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this
OhDreamsNo said:
Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this
Click to expand...
Click to collapse
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu
OhDreamsNo said:
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu
Click to expand...
Click to collapse
I think at this point I'd flash the stock 4.2.2 firmware from sammobile.com in Odin and start over. But watch out for the device wanting to update itself after the Odin flash. If it does you'll lose the ability to use twrp or cwm. To avoid it, root with motorchopper, but on a custom recovery and flash a custom Rom. There also three files you can freeze our delay on the device that neuteres the updates. I only remember one of them, FWUpgrade
Sent from my Nexus 5 using XDA Free mobile app

Categories

Resources