Ok, first of all, new to rooting and all that follows. However, I'm not new to forums and if this is in the wrong category, or if I overlooked a similar post, I am sorry. Feel free to redirect me to wherever you see fit. I know just too well how similar posts can be annoying, but I feel like I've exhausted Googlesearching and looked everywhere I can think of.
So, I have a Note II. N7100, Android 4.4.2 and I want to root it. Googlesearching has found me a lot of nice looking ROMs, and besides looks the added functions tempt me. Wont be long until I upgrade to a Note 4 or 5 anyway, figure I might as well. For what its worth, I live in Norway, and AT&T does not exist over here, nor does any other major american carrier. USB debugging was on the entire time.
I got the Odin V3.10, and appropriate clockworksmod files, and thought everything was peaches. Into download mode (after backing up ofc), Odin finds it, I upload everything and Odin says "PASS" in nice, green letters. When it reboots, it looks the same as before, but.. "Unfortunately, SuperUser has stopped", Titanium backup does not work since it apparently isnt rooted. Root Checker says the same. However, when checking for updates my phone displays "The operating system on your device has been modified in an unautorized way. Try downloading software updates using Samsung KIES on your PC, or visit a customer service center."
Read alot about devices having to be unlocked from carrier, however all google searches on "how to check for carrier lock on Note 2" yields numbersequences I have to input into the dialler and dial. None of the sequences give anything other than "Connection problem or invalid MMI code". I honestly dont remember if its carrier locked or not.
I came across an article here on XDA saying that with the later versions of android, KNOX has become an issue when trying to root, but someone had found a way around it. I downloaded MJ5BLPatch.tar.md5, uploaded to my phone via Odin, and here it fails, looses connection with the device and cant reconnect. Phone displays something alon the lines of "Invalid magic code" or the similar in red text.
I am the newb here, looking for help, and if I screwed up big somewhere I am cool with a little flaming. I just want to squeeze this for what use I can before upgrading, and probably rooting that too.
Any help as to how I can root it and load custom ROMs? I appreciate any and all help, sincerely.
Forget that MJ5 bootloader related stuff.
Reflash CWM using Odin and untick auto reboot, run through and reboot manually.
After reboot into recovery flash SuperSu.zip, start supersu after reboot system and disable knox by following the advices from app.
Thank you very much. i feel exceedingly stupid, I had been using the guide found on Note2root.com, when I applied step by step from this guide (http://forum.xda-developers.com/showthread.php?t=2143479) everything worked out. hope this may be of help to anyone having the same issues.
Again, thank you very much for your help.
Related
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!
I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.
garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY
Okay, so I have a T Mobile SGH t999l, a few months back I rooted it, that went smoothly. I then kept it rooted for a couple of months. Later, I wanted to restore my device to factory settings, (and did so very smoothly) but I forgot to uninstall superuser for unrooting it. It still works fine, but when I checked it with root checker (pro), I got error messages saying my phone was not properly rooted. Ever since then, I've been afraid to root my phone again. Someone, please help me get my phone back up, working, and rooted again (and a step-by-step guide, if I have to do it some special way now (if not, please, just tell me so)).
What build are you running? If you have a custom recovery installed, just flash the latest SuperSU from chainfires thread.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
What build are you running?
Click to expand...
Click to collapse
I'm running JSS15J.T999LUVUBMK.
PS. On second thought, could you include a detailed step-by-step guide on what to do, because I actually feel a bit uncomfortable doing this on my own.
There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
There are several ways to gain root, all of which are well
documented. Im not going to rewrite another guide on it, just too much when its been done already.
Go to the firmware thread linked in my sig and download the root66 firmware for your device. Flash via odin and you will be rooted. You will find instructions in the same thread, or the root66 thread and many other places via search.
Just backup important data first, just in case.
And check the other sticky threads too for alternatives and more info.
If you have a specific question about any of ill be glad to answer it, theres just no sense in rewriting whats already been done. Dont take it the wrong way.
Two things, stay away from the toolkit if you find it, and most odin instructions are for Odin v3.07. If you use v3.09, the only difference is use AP instead of PDA, they are the same. Youll understand if you run into it.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you %100 sure (given my specific predicament) this will work? No offense, but it sounds kind of generic, given one specific set of circumstances.
You can never be 100% when doing anything to your device. But as a general rule, if you are having problems, odin flashing stock firmware and factory resetting is the best chance of fixing stuff. Root66 is pretty much the same thing, only pre rooted, with knox removed. Its as close as you can get to 100% stock rooted on 4.3.
The only real issue is usually if you are still running base firmware build 4.1.2. At this point there is no warranty bit and you can still flash older firmware. Once on 4.3 this changes. So if youre already on 4.3 firmware, theres nothing to really lose by reflashing it or updating to the newer 4.3.
I wouldnt call it generic, as I stated above, this is often the best chance of getting things working the way you want. Its solved countless issues.
In the end its up to you what route you want to go. If youre not comfortable with my recommendation, I suggest you read up on other alternatives and choose what you are comfortable with. Wont hurt my feelings either way. Its your device and your risk, so be comfortable with what you are about to do.
Sent from my SM-N900T using Tapatalk
Try to take risk it never harms, Those who never did a mistake they never tried anything u learn from your mistakes.
Just got the T-mo T999 was on stock 4.3 flashed the cf root with ODIN, Rotted used GO im to flash the recovery BAM DONE. Stock rooted with recovery installed.
Now searching for a ROM.
Thanks
Thankyou for the help you all gave me, it worked!!!
Please, HELP!!!
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!
I have a problem
Give me a break said:
I was trying to install an Xposed module, but I don't remember which one, and I don't remember anything after that. Now my phone is not working (at least, not like you'd expect it to) anymore. Whenever I try to do much of anything, it starts displaying messages like "Unfortunately, '.............' has stopped", or "Unfortunately, the process '.............' has stopped". The most notable being, "Unfortunately, Google play Services has stopped", and "Unfortunately, the process com.google.processes.gapps has stopped". Please, HELP!!!
Click to expand...
Click to collapse
It works well enough, after I get through all the original errors I can call (and receive calls), and receive texts, but I can't use the keyboard, or any of the apps involving any form of Wireless Data (eg. Wi-Fi, Bluetooth, 3G/4G or any other cellular data) or GPS.
In your op you wanted to just be stock but rooted and stable, correct? Did you ever flash the root66 firmware I originally suggested?
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
I'm posting this in a few places because I'm not sure which is more active, feel free to move/delete.
The past few hours have been a nightmare. I was trying to root my Galaxy S7 (SM-G930W8) so I could uninstall some of the bloatware and install some apks.
I first went to mobilesiri (Can't post links yet) to try and root my phone. I couldn't find the samsung usb driver but I figured since my phone could connect to my computer and it recognizes it perfectly, it should be fine, so I skipped that step. Through some searches I came across androidmtk's guide which seems a lot more thorough, so I compared the two guides and decided to follow the latter. That being said I downloaded the version of Odin in the first guide as it seemed less risky to do a one-click root than something more advanced, and since they were both using Odin, I figured there's no harm. Running through the steps I hit "start" in Odin and it started working, but it said "reset" when I clicked start, so I thought that was odd. A few auto-restarts later and it said "pass" but when it started to boot up there was a "recovery is not seandroid enforcing" message in red at the top left.
At this point I thought maybe it worked, and the second guide told me to look for SuperSU in the apps, but it wasn't there. What's more is the software update no longer worked, and my device status was custom... basically the worst of both worlds. At this point I figured what's best is to find a stock firmware from Samsung. No such luck, even chatting with live tech support, it seems this is only done through kies, smart switch, or the phone itself. I did find something on Samsmobile which after a painfully throttled 2 hour download, gave me a version of odin they wanted me to use, along with the firmware for my specific model. I went through their instructions word for word, and it seemed to have worked. I booted up my phone, and the status said "official", so I figured it worked.
Not wanting to have all that time go to waste, I tried doing the 2nd guide, (Androidmtk) again, being really careful not to miss any steps. Same red error message, same custom status. I now have the Samsung firmware so I went back to that, and again the status said official, but now I'm having a whole bunch of issues. The keyboard sometimes doesn't come up, I can't type on it when it does, it comes up really late, the shift key flickers, sometimes it will type one character in, then as soon as I type another, it replaces it, so I can't actually type a string of characters together. The manual software update says failed processing after it tries to register the device. I heard that maybe updating through kies might work, except now I can't get the phone to connect to kies, even after running through the troubleshooter and restarting my computer.
I'm at a loss. I would love to have a rooted version of the phone but at this point just a functioning factory reset would be heavenly. Any help would be kindly appreciated!
Initial Steps before Restore
Faster firmware download - Download and Install
Remove any samsung USB drivers.
Close your browser. Reboot computer.
Download G930W8 firmware - https://desktop.firmware.mobi/device:452
The rest follow my Galaxy S7 Canadian Thread
Let me know. :good:
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
error : can't load losq-v
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
KFC99 said:
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
Click to expand...
Click to collapse
The reason is losq-v is the start of the filename pretty sure you can just press tab and it will autocomplete so the command would be "fastboot flash system losq-v"(after losq-v type rest of your filename or press tab to autocomplete (do not add a space in between losq-v and rest of filename))
Sry for forgetting that I did it like that to future proof the guide
camera not working
kamilkamjy said:
camera not working
Click to expand...
Click to collapse
Well it should. Ask the guys in the a71 group
Can it flash on U3 ui2.5 or 2.1?
Blocklisted said:
Well it should. Ask the guys in the a71 group
Click to expand...
Click to collapse
LoL
Posting "tutorials" in XDA is something else than copy and paste things you expect to work but never tested yourself.
Two persons get in trouble by the crap you copy and pasted here, and instead of take responsibility when things go bad, the only crap you can say is: ask THE GUYS in telegram rofl
What age are you? 12?
I hope no one follow this crappy " tutorial" here...
Odin Recovery Fails
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying magisk patches etc.... I never saw anyone confirming any method that would have worked. Whatever I tried to do it either didn't work or I couldn't do it because of lack of skills or it wasn't possible. For example when I tried to use magisk in the descriptions I had install buttons in the manger but I'm missing these on my phone so I suspect that recovery is required first to make those patches or there's something that I don't know how to do it. Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
rb1979 said:
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying
《Cutting》
Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
Click to expand...
Click to collapse
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
andreoide said:
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
Click to expand...
Click to collapse
Thanks andreoide for your honest answer :good:
My phone's working, I didn't get far with it, never broke it, just unlocked it. I guess the installation failed during the validation before actually doing any physical changes because my Samsung stock system still runs. The phone is given to me by my company. I just took out the sim card and put it in my private dual-sim phone. So this phone is on the shelf, it's been there for the last few months. I wish I could use it it's higher end than my personal but can't deal with Samsung stock system. I had two phones with lineage (and whatever the name was before) and loved it so I'm hoping I can use it again.
Anyway, it was just explaining my situation, I guess I'll be checking this forum and hoping for more positive news. Meanwhile the phone goes back on the shelf and waits for better times, thanks again for straitening things up for me. :good:
Blocklisted said:
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
Click to expand...
Click to collapse
Well, since you come clear and admit the guide you posted before was pure crap, i have to rise my thumbs up to you.
I think this is a mature respond.
:good: