Database Info

[Q] Rooting Samsung Galaxy i5500

Hello all,
I have had my Galaxy i5500 for awhile now and have used odin to flash updates for the firmware etc.
I have recently rooted my phone using Superoneclick and this worked fine. Overclocked the phone, and ran a number of Apps using SuperUser Access to gain all the benefits from this.
I installed Titanium Backup and Installed it on my SD Card, this caused a number of problems and I had to pull the battery on my phone to reboot it. Anyway it then hung at the GT-I5500 screen and I ended up having to download a new firmware (not custom) and use Odin to update it.
I now have a working phone, however I now can't root it. I have tried Superoneclick, that no longer works. I have also tried Universal Androot..with that I get an error message of Root Failed - No Fu Guu (or something like that) and I have just tried using z4root... with that it says acquiring Root Shell and then it just kicks me out...have checked and it's not rooted.
I also can't seem to access the reboot menu on my phone (the one where you press a couple of buttons to enter the menu where you can factory set your phone.
Can anyone shed any light on this? Other than these problems mentioned, the phone works as it should

Solved....
It took awhile of trying different root software but.... after reflashing my phone with another stock rom, I found Super One Click still didn't work, nor did z4root or universal Androot (I'm guessing it would have worked without reflashing a different rom).
I did however find that Unlock Root 2.2 worked! My phone is now flashed, no error messages and I have Superuser Access!! Now time to install a custom bootloader and start with the custom roms!!

[Q] 'custom' status with official rom

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

Completely Unrooted SM-900W8 that had Root de la Vega

These are the following steps that worked for me. For the record I was upgrading to a newer stock firmware from an older rooted stock firmware. I believe you can use the same version as your current stock firmware too. If this does not work for you please don't hold me accountable.
Steps
- Installed latest Kies 3 beta (for usb drivers). After install insure Kies is closed.
- Obtained latest Odin 3.09
- Downloaded my phones firmware from Sammobile.com (latest firmware for my model/country/provider with no upgraded boot loader) and extracted the .zip file leaving me with a myphonefile.tar.md5 and an SS_DL.dll file. It's very important to grab the right model/country/carrier or you could be in for a world of hurt. Only thing I hate about Sammobile is it requires registration to download firmware even though the whole process was painless.
- Backed up all apps with Titanium Backup to my external SD Card, and copied all contents to my PC then wiped my SD Card.
- Went to settings->general->security and INSURED REACTIVATION LOCK WAS NOT SELECTED.
*note before beginning the following process I REMOVED NO ROOT APPS from my phone eg. framework xposed, wanam xposed, superuser, titanium backup, root explorer, adblock.
- Powered down phone and removed SD card.
- Held volume up + home +then power to get to stock recovery menu.
- Selected Wipe/Factory Reset Phone then selected yes. (note - volume up and down moves selection, and power selects)
- Repeated Wipe/Factory Reset step again just to be safe, as per a post I read.
- Then selected reboot
- On reboot I immediately held volume down + home and then power to prompt odin download mode. Then pressed volume up to confirm.
- Opened Odin 3.09 on PC (Windows 7, SP1, 64-bit) and then connected my phone via the usb3 cable that was included with my phone (my computer has usb3 ports and the connection speed is awesome). Under ID:COM my phone's com connection showed up in the box and turned light greeny blue. The only options selected were Auto Reboot and F. Reset Time (this was by default).
- Clicked on AP (guess it's PDA on old versions of Odin) and browsed to and selected myphonefile.tar.md5. It took about a minute for Odin to run a hash check on myphonefile.tar.md5.
- Once the hash check finished successfully (via the message box) I clicked on start. Once the flash completed my phone auto-rebooted. I stared at the Samsung logo that eventually dimmed and my phones blue notification light pulsated like a heartbeat for what seemed like eternity but after a minute or two my phone booted into android.
I was greeted with the initial setup screens that I had when I purchased the phone.
After setting up my google account, wifi etc. I immediately went into settings->general->security and unchecked Auto update security. I then waited for my phone which downloaded about 21 app updates. Once it finished I rebooted into download mode (drum roll)........
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void 0x0
Sorry this is so drawn out, just hoping someday it might help a couple peeps.

Sounds great.
1). Was your KNOX 0x1 before doing thus?
2) does software uodate work now or still says device modifued?
3) which w8 soft u downloaded,? It does no go by date, which us newest?
4) u never installed custom recovery?
Thank you
Sent from my SM-N900W8 using xda app-developers app

odeccacccp said:
Sounds great.
1). Was your KNOX 0x1 before doing thus?
2) does software uodate work now or still says device modifued?
3) which w8 soft u downloaded,? It does no go by date, which us newest?
4) u never installed custom recovery?
Thank you
Sent from my SM-N900W8 using xda app-developers app
Click to expand...
Click to collapse
Knox was always 0x0 even after root. Everything went back to official, software updates,OTA all work as expected. Went from MI5 rooted to MJ1 stock. Never installed a custom recovery that would of definately tripped knox. Already rerooted MJ1 with Universal Root De La Vega. Xposed framework,wanam xposed has status official and knox still 0x0.
Sent from my SM-N900W8 using XDA Premium 4 mobile app

Thanks a lot.
I have a rooted N900L with kingoapp.com method.
I'm in Korea and found out that MJ9 firmware came out this morning.
Words are new firm has greatly increased WiFi stability so I was seriously thinking of unrooting, go back to stock rom, upgrade and the root again.
Finding ways of getting back to stock rom without tipping the KNOX flag, sure your thread gives me a lot of help. :good:

Thank you for pointing me to that stock firmware. It got me out of a horrible mess from a bad firmware flash. I was getting force-closures everytime the Samsung Keyboard was activated, as well as almost any stylus functions. Now they seem to be working again.

Galaxy S7 says "custom" but is not rooted. Need help.

I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg

SirMilkaPeach said:
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
Click to expand...
Click to collapse
This just happened to me and I the problem was that I had Secure Startup enabled under Lock screen and security. I just disabled it and re-rooted it and that fixed the problem. Hope it works for you.

HELP theres somthing wring with my phone

i have a samsung galaxy note 4 (SM-N910C) running android 6.0.1 and its been with me for almost 3 years. but recently i rooted it multiple times using odin and chainfire cf autoroot the first time i rooted my phone succesfully then i figured that i wasnt able to use snapchat so i completely unrooted. then i realised that xposed was what caused snapchat to stop working not the actual rooting. so i rooted my device using the same method and it worked succesfully. but this time i THINK i messed around with the build prop file but at that time i didnt know. so a couple of days later i completely reset my phone( just because i got a new work phone but NOT because i thought somthing was wrong with the build prop file) so my device wasnt rooted.then when i installed snapchat again and it didnt work.then i went to see if there were any software updates and it said the i had an unothorised OS.then i went to my device status and it said costom instead of original which was weird because i reset it. so i starting think abought what could have gone wrong and i thought about the build prop. i tried everything to get the device status to original like triangle away (i had to root it to install triangle away tho) but it didnt change the device status but snapchat worked thank god. however private mode didnt work so i tried to install samsung USB drivers and connect it to my phone usibg odin but things got even more copmlicated. i dont know what to do
any ideas?

flash stock rom via odin ?