Related
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:
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Original Samsung Stock Recovery Request
Hello, friend!
Can you get me that "original Samsung stock recovery" you mentioned, please?
Recently, I flashed a CWM file on my GT-I9192 and it doesn't work properly.
I'm searching everywhere and I couldn't find anything that helped me out...
So you're my savior...:laugh
Please attach the file or show me the link... So you will help not just me, but too many people that just messed up their phones..:angel::good:
Best regards from Brazil.
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
http://forum.xda-developers.com/showthread.php?t=2565758
...
work perfectly on my seranoltexx.
gogoland2002 said:
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
...
Click to expand...
Click to collapse
This thread is about UNROOTING and not how to root...
cemimo said:
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Click to expand...
Click to collapse
This how-to is about a phone with an older bootloader without knox.
So if you have a knox free bootloader, this description leads you back to full warranty conditions
help
Peter Semper said:
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
Click to expand...
Click to collapse
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
mason01983 said:
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
Click to expand...
Click to collapse
flash twice the firmware in odin, sometimes baseband isn't flashed
Didn't work for me either.
Starting from CM11, wanted to flash latest stock ROM with KNOX boot loader removed - downloaded my local carrier-specific firmware from Samsung updates, then proceeded to use the tar and md5 -rt tools on a Mac, failed signature. So did it in Windows using 7zip and it managed to flash. Did it twice to ensure baseband was flashed.
Flashing the stock recovery then doing the same still gives me a custom version
Anyone has any ideas on how to return to stock? I'm on non-KNOX boot loader.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I had cm 4.4.2 on my I9195 I have to re flash with odin to go back to clockwork mod then flash original firmware twice and it worked just waiting for the ota update now
problem
It did work flashing original firmware twice however I go into recovery mode and I have a dead android with a red triangle and the words no command
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Tyhjäntoimittaja said:
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Click to expand...
Click to collapse
Which recovery?
splitterzelle said:
Which recovery?
Click to expand...
Click to collapse
Samsung stock recovery which is attached in the first post.
Same prob.
Tyhjäntoimittaja said:
Samsung stock recovery which is attached in the first post.
Click to expand...
Click to collapse
Same here. I've got problems with that Android Stock recovery file. After flashing it, when I tried to go into recovery mode, the dead android logo appeared. However if I reflash CWM everything goes ok. Where can I find another stock android recovery file?, it seems that this one only works for some specific sort of models. Mine is: GT-i9195L. (the "L" doesn't really matter).
Thanks.
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Brinith said:
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Click to expand...
Click to collapse
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Skipjacks said:
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Click to expand...
Click to collapse
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Brinith said:
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Click to expand...
Click to collapse
No. The bootloader is not packaged with a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Brinith said:
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Click to expand...
Click to collapse
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Skipjacks said:
No. The bootloader is not packago$h a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Click to expand...
Click to collapse
Im not sure if its Knox,but Knox is definitely now installed onto my phone. (KNOX warrenty void 0x1). Oh well my warranty is over so i don't really mind. But still, i want to know what that error (in above post) was as it didn't let me boot or go into recovery and only worked again once I reflashed.
And the reason why i flashed was that people say that updating the modem.bin and NON-HLOS would improve cell reception, and such. Which so far seems to be true, getting better signal in general (for wifi, uped by 10db than before so pretty significant), since i just flashed 4.4.4 for updated bootloader and modem since i already have Knox now.
i need help for my s4 gt-i9505
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]
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.