This is getting frustrating!
Once a full uk rom became available I did a full, clean install using Mobile Odin to retain root. When I check status immediately the report is 'official'. Now the problems begin. I have tried a restore from Titanium Backup, a manual install of all my apps one by one and also just letting Google Play do its stuff, and after each sometimes within a couple of hours, this last time I managed overnight, my status is reported as 'custom'.
Any ideas as to what is causing this please?
Which status you're talking from? The one in the settings? That happens sooner or later when the Note is rooted, the systems seems to check this from time to time and set the status to "Custom". But why bothering, it does not harm. Even OTA do work with that.
The status custom in Odin download mode is a different store (but it remains official as long as not recovery or other non-Samsung flash is done).
Yes, the one in settings. Once the status changes to custom if I tap 'software update' then do a check I get a message saying my device has been modified so updates unavailable.
Then you did anything else, my status there is also custom, but I was offered the latest OTA without problems. Nevertheless, I downloaded the latest update from sammobile and flashed it with Mobile Odin. So I don't care about that status.
You are rooted ??
If so run Triangle away to reset rom counter .
Flash stock rom via Odin then factory reset should put device to normal status .
Root can interfere with or prevent OTA use Kies and reroot .
jje
Why so complicate?
Get the update/rom from sammobile or here, use Mobile Odin and flash the update on the tablet. With the pro version, the tablet remains rooted and everything is fine. Mobile Odin is an excellent tool and worth the few bucks to get the pro version.
Odp: [Q] 'custom' status with official rom
I have the same problem. I tryied to install script sd2internalsd and Iinstall busybox and i think that orogram change my status to custom. Now - my note cant take an update.
I try use Triangal away but das not work. Any idea?
tapnięte z mojego Note'a 10.1 3G
Related
After installing Triangle Away 2.60 just to check the counter, (which showed 0) my Device Status has changed from Official to Custom.
It was Official before running Triangle Away to reboot into the counter screen.
I did not commit any changes!
Note 10.1 JB 4.1.2 STOCK ROOTED
What gives?
UPDATE:
Using Triangle Away's Workaround: System modified workaround seems to have returned the Device Status back to Official.
Just a quick question, did you root with the exynos exploit then upgrade to the newest version of JB?
I found that using the exynos exploit would set my status to custom even after flashing stock rom...
nope, it was not rooted before
Please to tell me why?
Hy guys, i turn to recovey mode. how about "system status" why that always showing custom not official? any one can to tell why? thanks.
Maybe you flashed a custom rom or recovery into your device.
Hard to say given so little information.
Strange thing...
I successfully rooted with the Framaroot method.
I think it's one of the most discreet rooting method since it doesn't require to modify the recovery nor to flash anything with Odin.
I think it just uses the Exynos exploit in some way, and since my stock firmware JB 4.1.2 (N8000XXCLL3) is not one of the more recent ones (that probably fix the exploit) I could root with it.
After that I could happily see that my device status was still "Official".
I checked that well after rebooting more than one time. I also checked that the status was "Official" also in "Download mode".
Anyway, after a couple of days of normal usage (I didn't do anything strange with the root, apart from accessing some system file) I saw that my status had changed to "Custom" .
My suspect is that there's some Android service that periodically (yet infrequently) checks for a rooted device, changing the device status accordingly if it finds some trail of root.
Stranger yet is that, upon rebooting once again, my status has now come back to Official
So... does anyone knows better what triggers the device status from Official to Custom and back to Official when there's no modification in the stock Rom?
Exynos exploit changed mine to custom, tried 3 times to get rid of it, always went to modified then custom after a few minutes/ hours. I'm cool with it tho, doesn't hamper what I do with my note. I've seen others reporting similar scenarios
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Njord0 said:
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Click to expand...
Click to collapse
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
kkretch said:
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
Click to expand...
Click to collapse
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Njord0 said:
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Click to expand...
Click to collapse
Without a stock 4.1.2 firmware for your device it looks like you are going to have to do a factory reset to use Kies.
I think your options are limited..........
Have you considered using a firmware from another country?
You know there is a backup program called Helium that does not need root, you may want to consider using it to backup all of your data and then do a factory reset.
I don't know if I have helped you any............
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.