Hi Everyone.
Ok, So my phone was on Stock MJ1, Rooted with Kingo (Knox 0x0) and I had Xposed tweaks. (Its the 900W8)
I was screwing with the BUILD.PROP file and changed the value of dalvik.vm.heapgrowthlimit=128m to 124
Now I have a bootloop!
Please help!
Is there a way to re-insert a backup of my build.prop file into root? Maybe with ADB or something?
I dont want to wipe my phone or trip knox and I dont know what to do.
Im completely stuck.
JF-GINO said:
Hi Everyone.
Ok, So my phone was on Stock MJ1, Rooted with Kingo (Knox 0x0) and I had Xposed tweaks. (Its the 900W8)
I was screwing with the BUILD.PROP file and changed the value of dalvik.vm.heapgrowthlimit=128m to 124
Now I have a bootloop!
Please help!
Is there a way to re-insert a backup of my build.prop file into root? Maybe with ADB or something?
I dont want to wipe my phone or trip knox and I dont know what to do.
Im completely stuck.
Click to expand...
Click to collapse
You are basically hosed. You will have flash a stock system.img and cache.img.
ADB won't be active in a bootloop.
You could try flashing a zip with just the right build.prop in it. I don't know if and how that's possible though, but I think it is.
designgears said:
You are basically hosed. You will have flash a stock system.img and cache.img.
ADB won't be active in a bootloop.
Click to expand...
Click to collapse
Is it possible to flash the original build.prop using the stock recovery like Macbreq suggested?
If not, then if i trip my knox and put cwm on it could i flash it them or is my cache damaged too much to boot?
If i can only recover the way you suggested, how do i do this?
Put it in download mode and flash MJ1 stock rom with ODIN...
You shouldn't loose all your stuff and it will just need to be rooted again... Easy...
ultramag69 said:
Put it in download mode and flash MJ1 stock rom with ODIN...
You shouldn't loose all your stuff and it will just need to be rooted again... Easy...
Click to expand...
Click to collapse
I dont know my full CSC code,..Where can I find Stock (rogers) MJ1 without this? I think from memory its RWC-N900W8VLUBMJ1.....Does it matter?
Will this also trip my Knox?
JF-GINO said:
I dont know my full CSC code,..Where can I find Stock (rogers) MJ1 without this? I think from memory its RWC-N900W8VLUBMJ1.....Does it matter?
Will this also trip my Knox?
Click to expand...
Click to collapse
OK, if its stock go to recovery mode. It will tell you your CSC code at the bottom of the screen...
Then try sammobile.com to find your stock rom.If you can't find there you might have to try searching further afield but I don't know where, sammobile generally has what I want.
If you can't find any way to do this you may need to do an emergency firmware recovery by Kies 3 BUT you will loose all data... You will have a working phone though. Just remember that Kies 3 will upgrade to the latest firmware thats out so if you have root and an old bootloader and a new firmware is out with the anti-root firmware you will trigger Knox to get root back...
ultramag69 said:
OK, if its stock go to recovery mode. It will tell you your CSC code at the bottom of the screen...
Then try sammobile.com to find your stock rom.If you can't find there you might have to try searching further afield but I don't know where, sammobile generally has what I want.
If you can't find any way to do this you may need to do an emergency firmware recovery by Kies 3 BUT you will loose all data... You will have a working phone though. Just remember that Kies 3 will upgrade to the latest firmware thats out so if you have root and an old bootloader and a new firmware is out with the anti-root firmware you will trigger Knox to get root back...
Click to expand...
Click to collapse
Thanks, The Csc code says: RWC so I guess I can use any RWC MJ1 firmware...
BTW, I dont know if its just samsung, but can I not just flash my old build.prop using stock recovery?
It also gives an Apply update from ADB in recovery... Is it possible without reflashing this way?
JF-GINO said:
Thanks, The Csc code says: RWC so I guess I can use any RWC MJ1 firmware...
BTW, I dont know if its just samsung, but can I not just flash my old build.prop using stock recovery?
It also gives an Apply update from ADB in recovery... Is it possible without reflashing this way?
Click to expand...
Click to collapse
I wouldn't, any thing goes wrong its likelier to trigger Knox, especially as you are playing around with download mode. Personally I'd just reflash the firmware and move on from there...
ultramag69 said:
I wouldn't, any thing goes wrong its likelier to trigger Knox, especially as you are playing around with download mode. Personally I'd just reflash the firmware and move on from there...
Click to expand...
Click to collapse
Thank you! I did exactly what you said and you where 100% correct.
Just in case anyone suffers a bootloop from screwing around, this is a perfect solution.
I found my Stock firmware from here :
http://samsung-updates.com/device/?id=SM-N900W8
I Flashed it and everything booted without tripping knox and my stuff was all intact! It just put stock overtop.
All I had to do was re-root, re-install my mods and delete the bloat again... 20min later I was back where I started.
If anyone wants a tutorial on how to do this this, go here:
http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Thanks again everyone, especially ultramag69
JF-GINO said:
Thank you! I did exactly what you said and you where 100% correct.
Just in case anyone suffers a bootloop from screwing around, this is a perfect solution.
I found my Stock firmware from here :
http://samsung-updates.com/device/?id=SM-N900W8
I Flashed it and everything booted without tripping knox and my stuff was all intact! It just put stock overtop.
All I had to do was re-root, re-install my mods and delete the bloat again... 20min later I was back where I started.
If anyone wants a tutorial on how to do this this, go here:
http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Thanks again everyone, especially ultramag69
Click to expand...
Click to collapse
No problem, glad to help :good:
Related
Hi.
I don't know if someone can help me, but I really don't know what to do with this problem.
I bought one G900M (version from Brazil) on the release date and after a few weeks I install a custom rom and the TWRP recovery.
The problem is: I tried to go back to the stock ROM, but I still have the recovery with the CUSTOM "mark".
I tried to re install many times, do a wipe/format from the recovery, with no success.
I always receive the message when I try update the phone by OTA what say "The operating system on your device has been modified in an unauthorized way. Try downloading...
I appreciate any help.
mrhizzo said:
Hi.
I don't know if someone can help me, but I really don't know what to do with this problem.
I bought one G900M (version from Brazil) on the release date and after a few weeks I install a custom rom and the TWRP recovery.
The problem is: I tried to go back to the stock ROM, but I still have the recovery with the CUSTOM "mark".
I tried to re install many times, do a wipe/format from the recovery, with no success.
I always receive the message when I try update the phone by OTA what say "The operating system on your device has been modified in an unauthorized way. Try downloading...
I appreciate any help.
Click to expand...
Click to collapse
You tripped Knox when you rooted. There's no way to undo this.
dynospectrum said:
You tripped Knox when you rooted. There's no way to undo this.
Click to expand...
Click to collapse
But I'm not talking about Knox. I'm talking about the OTA update.
I reinstall the original firmware, stock version. Should work, no? Or Samsung changed the things again?
Im with a similar problem... root my device now OTA dont work... i think maybe someone has a flashable original firmware and you patch the same way you root your device.... Other option is ODIN restore to default :/ wich nobody want that
Its true
You tripped Knox when you rooted. There's no way to undo this.
If you want to update Just download the stock firmware ( samobile ) and flash with odin
Not true. My knox is still 0x0, I have root, but i have the same message from OTA.
The ART is the problem.
Just bought a GS5 Sunday from a friend. I'm not new to rooting or Samsungs. The phone was already updated to BOA8 Lollipop. I've seen things saying that I'll need to odin to 4.4.4. Is there a way to root without doing that? Will Odin mess with the EFS partition at all? Thanks!
sRs DoLLaR mEnU said:
Just bought a GS5 Sunday from a friend. I'm not new to rooting or Samsungs. The phone was already updated to BOA8 Lollipop. I've seen things saying that I'll need to odin to 4.4.4. Is there a way to root without doing that? Will Odin mess with the EFS partition at all? Thanks!
Click to expand...
Click to collapse
You will have to Odin to 4.4.2, NCG. This is the only firmware that can be rooted. You can then upgrade to any firmware and keep root.
Tulsadiver said:
You will have to Odin to 4.4.2, NCG. This is the only firmware that can be rooted. You can then upgrade to any firmware and keep root.
Click to expand...
Click to collapse
Ok thanks. Any guides? I've found one but want to make sure its the correct one. I also had the IMEI "repaired" (not for any illegal reasons) will using Odin for this undo that? That's why I asked about the EFS.
[QRCODE][/QRCODE]
sRs DoLLaR mEnU said:
Ok thanks. Any guides? I've found one but want to make sure its the correct one. I also had the IMEI "repaired" (not for any illegal reasons) will using Odin for this undo that? That's why I asked about the EFS.
Click to expand...
Click to collapse
Can't imagine Odin messing with IMEI but I'm no expert. The guide depends on what you want to end up on. If you like OA8, use this guide. Go down to the notes #4to see how to root. After you root with towelroot download SuperSU from the play store, update its binaries and reboot. Download then open and install busybox. Install safestrap and hit install recovery. If it says that it is installed, you are good to go.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546
Hey there, I'm an idiot... I tripped KNOX and now phone is stuck on Tmobile boot screen. With so many different ways to do things and so many variants of this frickin phone and Android it seems the rules are every changing.
So my questions:
1.) How can I get this thing back to working? Can I flash a factory image with ODIN? If so which factory image do I use and what version of ODIN and what boxes need to be ticked in ODIN?
2.) Will #1 reset KNOX? Can KNOX be reset?
3.) Whats the best method to get the thing rooted so I can put a ROM on it. I hate TouchWiz. I tried using this method but it landed me here... http://www.androidrootz.com/2014/04/how-to-root-galaxy-s5-recovery-root.html
Thanks in advance....
Can I just flash the corresponding firmware with ODIN? Is it that simple? Does the firmware version displayed in factory recovery always correspond to the firmware to flash with ODIN? Any insights would help!!!! Thanks for your time!
sammobile dot com, grab a stock ROM for your model S5 (G900T), flash with ODIN
KNOX is permanently tripped now, no way to reset
your knox is permanently tripped, so might as well do what you want with the phone.
if you can get into download mode, you should be able to flash a recovery through ODIN, and then flash the rom of your choice. if that doesn't work, follow Detection's post above and flash a factory Tmobile rom through ODIN and start again.
That's all great thanks all, but does the firmware have to match the version that corresponds to the recovery that is currently on it? For instance, if I flashed 5.1.1 me thinks I wouldn't be able to root it or downgrade it thereafter, correct?
[bor]Its the loosey goosey instructions for multiple methods of doing the same thing for various android versions that make this sketchy. I found it easier to flash my HTC magic with jesus freak and a gold card than it is to flash this thing...or maybe my brain is decaying. Anyway, not what I expected for a common android phone. [/eor]
Hello!
Im sending my device for varranty (pink line) so i wanted to clear my phone and flash back everything to stock.
after all (i tried both odin and kies3) also i extracted and flashed recovery.img made into .tar. i still see the info on Android Recovery
samsung/hero2ltexx/hero2lte6.0.1./MMB29K/G935FXXU1BPLB
apart of knox trip its obviously a trace of root beign done and obviously theres some system modification still present on device.
What else can i do to get rid of that info?
I'm having the same issue!!
kartonick said:
Hello!
Im sending my device for varranty (pink line) so i wanted to clear my phone and flash back everything to stock.
after all (i tried both odin and kies3) also i extracted and flashed recovery.img made into .tar. i still see the info on Android Recovery
samsung/hero2ltexx/hero2lte6.0.1./MMB29K/G935FXXU1BPLB
apart of knox trip its obviously a trace of root beign done and obviously theres some system modification still present on device.
What else can i do to get rid of that info?
Click to expand...
Click to collapse
I used a German ROM when rooted and now back to stock using my country's (Netherlands) provided STOCK ROM from sammobile but phone is still showing the German buildnumber along with the hero3ltexx build fingerprint. I hope someone answers us with a solution for this!
[Sorted out] I did not root, however my s7 edge does not allow me to use s health claiming root after reinstalat stock via odin. Any solution for that?
Did you trip the Knox counter? If you did, there's no way back
The knox was changed, but I wonder how could that be that it was a stock rom?
Br9 said:
The knox was changed, but I wonder how could that be that it was a stock rom?
Click to expand...
Click to collapse
Did you install TWRP or made any changes in the bootloader.
Once the boot loader has been modified in any way. \it will trip knox.
No. I just reinstalled stock via odin, there was no twrp installation.
Br9 said:
No. I just reinstalled stock via odin, there was no twrp installation.
Click to expand...
Click to collapse
why did you have reinstall stock /
if you have reinstall stock that means something was done to your phone, which caused your phone to think knox is tripped.
So what happened that you ned to reflash your phone ?
System crashes with crashes
Are you the original owner of this phone?
If you try to root it or install anything non-Samsung, it will trip knox and there is no turning back.
Flashing Samsung ROMs via Odin won't trip knox....
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Br9 said:
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Click to expand...
Click to collapse
I think you just have to add or modify a line in system/build.prop and it will work. For that, you have to be rooted.
Take a look here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Sorted out. I was able to reuse the app by going back to 6.0 via odin, configuring the app and upgrading via OTA to 7.0