Related
this is the first time iam going to update a samsung tab
i just downloaded the firmware from samfirmware, then extracted the file it has only 1 file in it
( P6200DXLPB_P6200OLBLP8_P6200DXLP5_HOME.tar.md5 )
where do i place this file in odin? please correct me if iam going wrong. i have waited a long time for the ics update to hit india but it still hasnt
iam using the singapore firmware now!
[email protected]!
OneMoreMember said:
where do i place this file in odin?
Click to expand...
Click to collapse
In the PDA section.
Sent from my GT-P6210
thanks mate i got that, but iam having wifi problems with the singapore firmware, is there a way i can go back to honecomb 3.2 i tried flashing it via odin but its stuck on the samsung logo, i can install 4.0.1 back but its not letting me downgrade. what has to be done to downgrade? help will be appreciated
No one on XDA who can tell me how to do this ?
OneMoreMember said:
No one on XDA who can tell me how to do this ?
Click to expand...
Click to collapse
Install custom recovery then flash the Galaxy ROM HD.
Envoyé depuis mon GT-P6200 avec Tapatalk
also, when making major changes like that, its best to do a "factory reset", which should be an option available in Recovery Mode.
"Why would that help?", well, Android is a modular OS, composed of lots of different apps. Most of these apps store their current settings in your device's /data partition. Generally, when booting up, the various parts all try to launch and then check to see if there are stored settings available for use. If there are, the apps try to load those settings and use them. If you have suddenly changed from one ROM to another, many of these apps are going to be different versions, often different enough to cause the old settings to not work right.
When you do a "factory reset", (among other things) the /data partition is erased, so the apps all get a chance to write their own fresh settings, and thus your device will actually be able to boot up
this doesnt belong in development section..
Sent from my GT-S5830 using Tapatalk 2
hi ..
after i suffer my self from brick loop due to restoring one single nandroid backup from TWRP recovery , and after searching whole internet and forums to find solutions , also after Samsung service center failed to recover the phone from this issue..
i decided to share with you this script for solving the boot loop and system failure ..
the problem occurred after restoring from TWRP Recovery and the main issue is the corrupted the efs partition .
so for those people and users who are suffered from this same problems and cant get to run adb shell commands through recovery i did this script to bae flashed from custom recovery ..
CREDIT
sure and first of all many thanks to( Steve Lazarus) for posting his valuable third about this problem.
main thread :
http://forum.xda-developers.com/showthread.php?t=2471421
and thanks to Backachu for finding the idea of solving this miserable issue .
Wesamothman for sure without him i cant do nothing ,,thanks bro.
Steps :
download this flashable zip file :
http://www.mediafire.com/?k32kvbgb2dc9qde
put it in external SdCard
flash it using your custom recovery .
you must be rooted .
enjoy your phone back...
this script is working even without reverting to stock ROM .
please just press that thanx button if you like it
this is how to show your thanks ,
thank you sir
Wow thank you.got my device replaced because of this issue. But now I'm on the safe side no matter what happens. Thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
Btw: can we expect an assassin Rom for note 3?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thank you. Will try this is samsung service center doesn't manage to fix my phone.
Is it okay to:
1)Flash stock firmware
2)Root with chainfire's kernel
3)Do your manipulation
?
Thank you
good!
Firasusman thanks for sharing! No problem till now, but good to have in case of bad things happened!!!
Firasusman thanks for sharing! My phone was dead by 3 days. I flash by this zip and everything working great . THANK THANK THANK YOU!
Will this also work for the Galaxy S4?
hav0c said:
Will this also work for the Galaxy S4?
Click to expand...
Click to collapse
i dont have S4 ,
maybe ..
you can try ,
you will not be harmed...lol
Raphy511 said:
Thank you. Will try this is samsung service center doesn't manage to fix my phone.
Is it okay to:
1)Flash stock firmware
2)Root with chainfire's kernel
3)Do your manipulation
?
Thank you
Click to expand...
Click to collapse
yes
So, I can do a nandroid backup and restore it without brick my phone??
sayou94 said:
So, I can do a nandroid backup and restore it without brick my phone??
Click to expand...
Click to collapse
This fix is when you get bootloop after you use twrp restore option ...
The restore issue seems to be that the recovery was not successfully developed to the needs of the lte note3 variant.
So then Knox flag is set. And your efs get corrupted.
even samsung operation declines to fix it due to that.
This script that is developed by firasusman. .. thanks to him... can be flashed even from the twrp recovery that caused all issues of that matter only.
Then you can get your device back to life.
Anybody tried the zip?
Hi, today i tried to restore my stock rom using twrp and it keeps restarting on the galaxy note 3 screen. Can i use this method to fix my phone?
chuaws said:
Hi, today i tried to restore my stock rom using twrp and it keeps restarting on the galaxy note 3 screen. Can i use this method to fix my phone?
Click to expand...
Click to collapse
Yes..!
Thanks OP...save my day! :good::highfive:
firasusman said:
hi ..
after i suffer my self from brick loop due to restoring one single nandroid backup from TWRP recovery , and after searching whole internet and forums to find solutions , also after Samsung service center failed to recover the phone from this issue..
i decided to share with you this script for solving the boot loop and system failure ..
the problem occurred after restoring from TWRP Recovery and the main issue is the corrupted the efs partition .
so for those people and users who are suffered from this same problems and cant get to run adb shell commands through recovery i did this script to bae flashed from custom recovery ..
CREDIT
sure and first of all many thanks to( Steve Lazarus) for posting his valuable third about this problem.
main thread :
http://forum.xda-developers.com/showthread.php?t=2471421
and thanks to Backachu for finding the idea of solving this miserable issue .
Wesamothman for sure without him i cant do nothing ,,thanks bro.
Steps :
download this flashable zip file :
http://www.mediafire.com/?k32kvbgb2dc9qde
put it in external SdCard
flash it using your custom recovery .
you must be rooted .
enjoy your phone back...
this script is working even without reverting to stock ROM .
please just press that thanx button if you like it
this is how to show your thanks ,
Click to expand...
Click to collapse
I took the card out and used a reader to move the file directly from my laptop.
Flashed and now everything is working perfectly again. You are a miracle worker. Thank you so much.
With extcard
Envoyé de mon SM-N9005 en utilisant Tapatalk
Thanks so much dood. Huge weight off my mind.
Back to happily flashing. :laugh:
You are a true life saver
Thank you so much.
lindarne said:
You are a true life saver
Thank you so much.
Click to expand...
Click to collapse
+1
Envoyé de mon SM-N9005 en utilisant Tapatalk
Hi,
I have a GT-N8010. Over the couple of years I've had it I've regularly flashed ROMs. At one point last year I flashed one (official) which resulted in the tablet insisting it was a GT-N8000, to the extent it wouln't flash 8010 roms (one of the components would fail). I assume the official flash had probably tweaked the partition table?
Anyway I then moved on to omnirom which had been working well, but I'd noticed some lag. Realising official 4.4.2 was out for the 8000 I decided to flash it (after all this would be easy for my device).
The flash started well, and I could see the various sections being flashed. I left it. The odin 3.09 status was green indicating things had worked, but the tablet was on the "simple" download (emergency?) screen showing the robot and "Downloading... Do not turn off target!!" only.
Any press of any hard button brings the tablet to this mode. press/hold power for 10s turns it off for it to only return to this panel.
It IS detected in Odin, and I've tried a couple of different things:
- flashing Philz cwm recover (8000 and 8010)
- flashing twrp recovery (8000 and 8010)
- flashing the 4.4 official build again
- trying the most recent N8000 4.1.2 official build
In all cases now the flash starts, but whether it's boot.img first in the file, or recovery.img (and presmably others) I'll just get something like
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
I'm thinking of trying a few more roms, but does anyone have suggestions?
I can only guess that in theory the device is still recoverable - at least it's booting into an odin friendly mode.
Is this a sign of totally corrupted storage/partition table?
I've NEVER manually ticked the partition table box in odin, though my guess is it happened at some point some where (a pit file in an official image.. would this still cause partition?)
What are some things worth trying? What order (safer -> more risky)
I just build the tweaked 4.4 image (for a 8010) using the instructions at http://forum.xda-developers.com/showthread.php?p=53112094
I also switched back to odin 3.07 (from 3.09)
It fell over on boot.img
Mine is also showing n8000 in download mode (I have n8010) and it won't let me get back to latest official 4.1.2, I'm using the n8000 leak now. I was able to flash a 4.0.4 firmware and use ota to 4.1.2, but in download mode was still showing n8000 so I flashed back the leak. I hope we are going to be able to flash the n8010 4.4.2 when released.
I'm also searching for a ICS or jb stock fw, but one with distinct files for boot loader, CSC, ap, modem, just like the leak had. I can't find one for n8010, got one but is for n8000.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
Mine is also showing n8000 in download mode (I have n8010) and it won't let me get back to latest official 4.1.2, I'm using the n8000 leak now. I was able to flash a 4.0.4 firmware and use ota to 4.1.2, but in download mode was still showing n8000 so I flashed back the leak. I hope we are going to be able to flash the n8010 4.4.2 when released.
I'm also searching for a ICS or jb stock fw, but one with distinct files for boot loader, CSC, ap, modem, just like the leak had. I can't find one for n8010, got one but is for n8000.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I've now tried flashing a variety of images using a few different odin levels. Every single flash fails so far on the first image it tries to flash.. and comes back with failed.
So the tablet is in the enticingly not-dead "downloading" screen but that is all it will do - no recovery, no boot, won't even stay powered off (until battery runs out).. ONLY this screen. I can't help but think if I knew what to do, it might still be recoverable....
I've tried N8010 roms, N8000 roms, different recoveries. All result in the same failure.
Running out of ideas here other than to take a punt on a warranty return (I'm not even sure it's in warranty), which could get rejected. I guess the fact it doesn't boot/display any data top right (which my I9505 phone does - I think the 8010 is in emergency download mode...) means they're unlikely to know why it got into this state and may just resurect (jig?)
I should mention I did find a N8010 pit, and tried flashing that. that's the first time I've EVER tried going for a pit. Even this failed!
If you found a n8010 firmware with separate files for bl, ap, CSC and modem please give me a link for it.
Sent from my Nexus 5 using Tapatalk
If you haven't already, uninstall and reinstall the drivers for the tablet.
Also, try a different USB port and cable (if you can get your hands on another one).
I had the same thing happen to me (with the FAIL message) and I spent many, many hours trying software fixes only to find it was a bad cable. It would connect and recognize the device but not let me flash the image through ODIN.
Good luck!
triumvirant said:
If you haven't already, uninstall and reinstall the drivers for the tablet.
Also, try a different USB port and cable (if you can get your hands on another one).
I had the same thing happen to me (with the FAIL message) and I spent many, many hours trying software fixes only to find it was a bad cable. It would connect and recognize the device but not let me flash the image through ODIN.
Good luck!
Click to expand...
Click to collapse
Thanks for the tip. I do have a spare (somewhere) - this is the original, but it's a good thought......
I'll try the drivers replacement too, though I've already tried flashing from 2 different systems
I'm still hoping to find a good rom/pit combination to at least try... finding pit files is hard!
I'm near the store where I purchased the tablet tomorrow, which gives me one more (late?) night of attempted repairs.
planetf1 said:
Thanks for the tip. I do have a spare (somewhere) - this is the original, but it's a good thought......
I'll try the drivers replacement too, though I've already tried flashing from 2 different systems
I'm still hoping to find a good rom/pit combination to at least try... finding pit files is hard!
I'm near the store where I purchased the tablet tomorrow, which gives me one more (late?) night of attempted repairs.
Click to expand...
Click to collapse
The pit you find will be for stock rom. When you run a pit file you need to make sure you have stock tar.md5 rom.
KDKobes said:
The pit you find will be for stock rom. When you run a pit file you need to make sure you have stock tar.md5 rom.
Click to expand...
Click to collapse
Thanks, I did that... no joy... though only with pit for 4.0.4, I wasn't able to locate anything newer. Given up now
planetf1 said:
Thanks, I did that... no joy... though only with pit for 4.0.4, I wasn't able to locate anything newer. Given up now
Click to expand...
Click to collapse
I pm'd you about your issue. Check your private messages.
KDKobes said:
I pm'd you about your issue. Check your private messages.
Click to expand...
Click to collapse
I had the exact same problem
I flashed the pit for n8000 and my n8010 is now running very well 4.4.2
If you want this spit fike' pm me
Envoyé de mon GT-N8010 en utilisant Tapatalk
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
planetf1 said:
Hi,
I have a GT-N8010. Over the couple of years I've had it I've regularly flashed ROMs. At one point last year I flashed one (official) which resulted in the tablet insisting it was a GT-N8000, to the extent it wouln't flash 8010 roms (one of the components would fail). I assume the official flash had probably tweaked the partition table?
Anyway I then moved on to omnirom which had been working well, but I'd noticed some lag. Realising official 4.4.2 was out for the 8000 I decided to flash it (after all this would be easy for my device).
The flash started well, and I could see the various sections being flashed. I left it. The odin 3.09 status was green indicating things had worked, but the tablet was on the "simple" download (emergency?) screen showing the robot and "Downloading... Do not turn off target!!" only.
Any press of any hard button brings the tablet to this mode. press/hold power for 10s turns it off for it to only return to this panel.
It IS detected in Odin, and I've tried a couple of different things:
- flashing Philz cwm recover (8000 and 8010)
- flashing twrp recovery (8000 and 8010)
- flashing the 4.4 official build again
- trying the most recent N8000 4.1.2 official build
In all cases now the flash starts, but whether it's boot.img first in the file, or recovery.img (and presmably others) I'll just get something like
boot.img
NAND Write Start!!
FAIL!
I'm thinking of trying a few more roms, but does anyone have suggestions?
I can only guess that in theory the device is still recoverable - at least it's booting into an odin friendly mode.
Is this a sign of totally corrupted storage/partition table?
I've NEVER manually ticked the partition table box in odin, though my guess is it happened at some point some where (a pit file in an official image.. would this still cause partition?)
What are some things worth trying? What order (safer -> more risky)
Click to expand...
Click to collapse
Same for you [emoji4]
Envoyé de mon GT-N8010 en utilisant Tapatalk
---------- Post added at 12:18 AM ---------- Previous post was at 12:06 AM ----------
So, here is what was the solution for me:
Go to this thread http://forum.xda-developers.com/showthread.php?p=41158546
Install the pit file for n8000 given in the op (don't forget to check "repartition" in odin)
This resolved the problem for me when i flashed official 4.4.2 for n8000 on my n8010
Envoyé de mon GT-N8010 en utilisant Tapatalk
nic.stl said:
I had the exact same problem
I flashed the pit for n8000 and my n8010 is now running very well 4.4.2
If you want this spit fike' pm me
Envoyé de mon GT-N8010 en utilisant Tapatalk
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
Same for you [emoji4]
Envoyé de mon GT-N8010 en utilisant Tapatalk
---------- Post added at 12:18 AM ---------- Previous post was at 12:06 AM ----------
So, here is what was the solution for me:
Go to this thread http://forum.xda-developers.com/showthread.php?p=41158546
Install the pit file for n8000 given in the op (don't forget to check "repartition" in odin)
This resolved the problem for me when i flashed official 4.4.2 for n8000 on my n8010
Envoyé de mon GT-N8010 en utilisant Tapatalk
Click to expand...
Click to collapse
The pit file to flash is named Note10_PIT.zip
Envoyé de mon GT-N8010 en utilisant Tapatalk
I tried that pit file on my n8010, not working for me. Is the same pit file for both n8010 and n8000 ?
Sent from my GT-N8000 using Tapatalk
KoRoZIV said:
I tried that pit file on my n8010, not working for me. Is the same pit file for both n8010 and n8000 ?
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
Did you take it from the link i gave ?
After i flashed official kk, i phone stuck in download mode ...
Then i flashed the pit file from the link i gave in the above post ... and it works for me
Envoyé de mon GT-N8010 en utilisant Tapatalk
Yes, gave me an error.
My device is functional but in download mode is seen as an n8000, this is what I need to fix.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
Yes, gave me an error.
My device is functional but in download mode is seen as an n8000, this is what I need to fix.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ah ok ...
Mine shows n8000 in download mode too
I think that if you want too go back n8010 in download mode, you need to flah n8010 but for 4.4.2
You are now in 4.4.2, aren't you ?
Envoyé de mon GT-N8010 en utilisant Tapatalk
Yes, I have the leaked kit Kat on it.
Sent from my Nexus 5 using Tapatalk
Ok
So let's wait a pit file for n8010 on 4.4.2
Or the official 4.4.2 for n8010
Envoyé de mon GT-N8010 en utilisant Tapatalk
nic.stl said:
Ok
So let's wait a pit file for n8010 on 4.4.2
Or the official 4.4.2 for n8010
Envoyé de mon GT-N8010 en utilisant Tapatalk
Click to expand...
Click to collapse
You can create a pit from your device or someone who is willing to do it through Heimdall main thread located here. Once you plug in device and install drivers it will make a pit for your device.
KDKobes said:
You can create a pit from your device or someone who is willing to do it through Heimdall main thread located here. Once you plug in device and install drivers it will make a pit for your device.
Click to expand...
Click to collapse
Thank you for the link
Not necessary for the moment as i have n8000 pit file in my n8010.
I'll use your link as soon as n8010 4.4.2 is out and installed
Envoyé de mon GT-I9100G en utilisant Tapatalk
Dear people of the internet,
I am proud to represent the few countries that remain untouched regarding the OTA update on the SM-G920F.
I'm wondering since I've not gotten the update, if I could flash it and it would be like a normal Over The Air update process?
I do not want to trip the Knox counter since I'd like to sell the phone in the future or just be covered by my warranty.
So. TLR, Can I get the 6.0.1 update like OTA but flashing it? Will it void my warranty? Will it trip knox counter? Will it automatically
become rooted(something I don't want)?
I've heard some people getting fail in Odin(hidden.img), how can I prevent that if I do flash it?
Thanks in advance
TLDR: yes, no, no, no
Gesendet von meinem SM-G920F mit Tapatalk
Falster said:
TLDR: yes, no, no, no
Gesendet von meinem SM-G920F mit Tapatalk
Click to expand...
Click to collapse
So it's basically safe to do? And it works just like an OTA update?
leontin2012 said:
So it's basically safe to do? And it works just like an OTA update?
Click to expand...
Click to collapse
usually flashing a stock rom via odin does not trip your knox, except if then you flash a custom rom and then install superSU.. btw YES, if you flash MM via odin will work as an "OTA"
I tried to flash stock to my s6 and it failed and the knox counter went up so voided the warranty it's a brand new phone not happy wanted three stock on the phone now it's not covered not amused tbh can't even root the phone tried pingpong root failed android l knew what I was trying to do . So yes even if u flash with odin the counter will go up I wouldn't risk it tbh
neo84942011 said:
I tried to flash stock to my s6 and it failed and the knox counter went up so voided the warranty it's a brand new phone not happy wanted three stock on the phone now it's not covered not amused tbh can't even root the phone tried pingpong root failed android l knew what I was trying to do . So yes even if u flash with odin the counter will go up I wouldn't risk it tbh
Click to expand...
Click to collapse
Thank you, I won't flash because of you.
Personally it's up to you but flashing a stock rom won't trip Knox. I flashed a stock FW to remove bloat and everything was absolutely fine.
I'll be flashing a stock 6.0.1 as soon as I can actually find one on here.
Devlinukr said:
Personally it's up to you but flashing a stock rom won't trip Knox. I flashed a stock FW to remove bloat and everything was absolutely fine.
I'll be flashing a stock 6.0.1 as soon as I can actually find one on here.
Click to expand...
Click to collapse
Here's the 6.0.1 firmware for G920F: http://www.sammobile.com/firmwares/database/SM-G920F
Flash it if you wan't and would you please provide me with necessary information regarding the
process?
Thanks!
I'm downloading the French version which is unbranded but it's going to take a while as it's from Sammobile.
Devlinukr said:
I'm downloading the French version which is unbranded but it's going to take a while as it's from Sammobile.
Click to expand...
Click to collapse
Use this tool [TOOL] SamFirm - Samsung firmware downloader & checker it takes only a few minutes to download a firmware.
Sent from my SM-T800 using Tapatalk
Oh sorry nvm. Didn't saw the other comments. I hate the new design of xda. I can't see the comments in a post -_-
So so tempted....waiting for 02 uk is painful lol
Sent from my SM-G920F using Tapatalk
alexpowermetal said:
Use this tool [TOOL] SamFirm - Samsung firmware downloader & checker it takes only a few minutes to download a firmware.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Cheers for future updates dude but I was doing some chores anyway so I just waited
Just powered up from the update, like the new ui, no visible problems so far :good:
---------- Post added at 01:34 AM ---------- Previous post was at 12:58 AM ----------
So to answer the previous question,
1. Download the French XEF rom, extract the rare file to somewhere you can find it.
2. Fire up Odin on your PC.
3. Click on the AP setting and select your extracted file.
4. Put your phone in download mode and connect it to your pc via USB.
5. Wait for your phone to be recognised and press start in Odin.
6. Wait until Odin is completely finished and your phone reboots, this takes a while, don't panic just wait patiently.
7. Disconnect from PC and enjoy.
My phone is the SM-G920F variety, which I had previously debranded from 3 mobile.
I put the language setting to French for the update and switched it back after, no idea if this was important, just read some guy said he did it in another thread. I doubt it's necessary.
Devlinukr said:
Cheers for future updates dude but I was doing some chores anyway so I just waited
Just powered up from the update, like the new ui, no visible problems so far :good:
---------- Post added at 01:34 AM ---------- Previous post was at 12:58 AM ----------
So to answer the previous question,
1. Download the French XEF rom, extract the rare file to somewhere you can find it.
2. Fire up Odin on your PC.
3. Click on the AP setting and select your extracted file.
4. Put your phone in download mode and connect it to your pc via USB.
5. Wait for your phone to be recognised and press start in Odin.
6. Wait until Odin is completely finished and your phone reboots, this takes a while, don't panic just wait patiently.
7. Disconnect from PC and enjoy.
My phone is the SM-G920F variety, which I had previously debranded from 3 mobile.
I put the language setting to French for the update and switched it back after, no idea if this was important, just read some guy said he did it in another thread. I doubt it's necessary.
Click to expand...
Click to collapse
So you didn't get any problems whatsoever when you flashed through Odin?
Nope.
Phone is fine and dandy.
Devlinukr said:
Nope.
Phone is fine and dandy.
Click to expand...
Click to collapse
Did you do a factory reset before updating? Did you backup anything, and if so, how can I do that?
You didn't have to do anything with a pit file?
Verstuurd vanaf mijn SM-G920F met Tapatalk
I already posted every step I took from beginning to end.
There weren't any hidden steps, I didn't factory reset, I didn't flash any other files. I lost no data and I'm still on BTU.
I'm sorry, but, do I need to download the French version?
It's unbranded.
It's makes no difference at all, just change the language back to whatever afterwards. I'm in the UK and it works flawlessly.
Hi All,
I a strange thing happened yesterday. My S6 got stuck and when I did a force restart it ended up in a boot loop. To worsen the problem my device had reactivation enabled. I found out that my recovery is not loading also. I guess its due to the reactivation security.
So far I have tried the following:
1. Tried to install the stock firmware
2. Tried to install new stock firmware (marshmellow)
3. Tried Kies and Smart Connect (did not do anything)
I'm pretty much clueless at this point. Any help is appreciated.
Thanks in advanced...
Any captains to help?
Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again
emcardle660 said:
Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again
Click to expand...
Click to collapse
Thank you very much for the input. Do you feel that when I flash the original firmware it did not apply the recovery.img that was inside the tar ball? I could manage to create a tar ball with only the recovery image but in that case will it trigger the knox counter and void warranty?
Again, I really appreciate your feedback. Thanks mate
BTW I tried with both Odin and smart connect. Nothing helped. They both complete and say it went well but after restart its simply another boot loop
When you flash stock with odin it should say pass and should boot or visit Samsung for fix
tazaga said:
When you flash stock with odin it should say pass and should boot or visit Samsung for fix
Click to expand...
Click to collapse
It does say PASS. But when it reboots I end up with the boot loop again.
BTW Reactivation lock is ON. Could this be a problem?
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
Thank you very much. I will surely try this tonight. I will post my findings here.
Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
One quick question before I flash this and trip knox. On your device was Reactivation set to ON?
I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)
Jonny5isalivetm said:
I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)
Click to expand...
Click to collapse
Ha ha, very true about Knox. And yes in download mode it shows if Reactivation is ON or OFF. The purpose is to not allow anyone to factory reset the device if this is turned on. Hence the unavailability of the recovery mode.
I would really appreciate it if you could check and let me know. Thanks in advance mate
OK will do but she at work till 5
Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
No worries mate, thanks for been available and the guidance...
Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
Any updates please?
I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?
Jonny5isalivetm said:
I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?
Click to expand...
Click to collapse
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.
MAHASONA said:
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.
Click to expand...
Click to collapse
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you
huzi7868 said:
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you
Click to expand...
Click to collapse
Thanks for the info. But as mentioned recovery is not available in Reactiation - ON mode. Its a security feature they provide to prevent people from stealing your phone.
Can't you disable reactivation lock by deleting your Samsung account ? : http://androiding.how/unable-to-disable-reactivation-lock-on-galaxy-s6-try-this-fail-safe-trick/