Note 4 Developer back to stock? - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

I have been digging through multiple "how tos" about this process but after reading so many different things, I want some clarification. I made the mistake one time of loading the factory retail firmware version and am scared that I could screw something up. I had to send it back to Samsung to fix that. I have some backups of the phone including the aboot back-ups (Followed the below thread for that). I literally want to go back to the basic Dev Edition firmware to sell the phone.
Anyone know of any guides that can simplify this process?
Link I used for back ups:
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911

Related

[Q] Unrevoked 3 with Full nand Questions/Concerns

First off, YES I have read a ton of posts about some of this, and YES I am a complete noob when it comes to rooting, and YES I am prepared to suffer the flames I may get for asking such inane things...that being said:
I have an EVO that I want to fully root. I use a mac (even read the mac root tutorial on another site...), and am now hearing about Unrevoked 3, and how wonderful/horrible it is. Here are my questions:
If I fully root with unrevoked 3, is there a way to go BACK to the original system that came with my phone? The reason I ask is so many threads hint at a "no turning back" kind of vibe.
Two: if I were to root in the classic sense (you know, the one that appears to a noob such as myself to performing brain surgery), would that allow me to go back to the original HTC system?
I have hacked my mac for years, I used to think I was fearless, but after reading so many posts on subjects like this, I have been terrified to even begin. So any of you Gurus out there that can offer any advice, I would be eternally grateful for it.
Thanks...!
1.- Yes, you can reenable S-ON, you'll need to flash a RUU (official EVO FW) afterwards, after this your phone will be back to stock.
2.- ??? You can root the current HTC FW Sense OR switch to another one if you wish. If you need to go back refer to #1
The RUU is the generally accepted method, however, there is an infamous error of the bootloader not responding to it.
The next method, and the one I used, is over in the Android Development section, probably buried under a couple pages. The thread title is "[GUIDE] How to Unroot the EVO in 2 STEPS" and the author is djR3Z.
I guess this account is too new, and the spam control settings are still in place, so I can't, or at least don't know how, to link to it.
Edit: Also can't edit a post unless I wait 5 minutes. Fun.
Thank you both very much. I will be rooting my phone asap, now.
You should be fine, it takes a lot of effort to really brick a phone. As long as you don't flash only stuff meant for the Evo and you don't interrupt it while anything is flashing you should be good. Unless you lose your account information, which most of the time doesn't get touched, it's pretty simple to return it to stock.
Also, if you have a new phone that says it is hardware version 004 Unrevoked 3 wont work for you. You'll need to follow the instruction found here.

[Q] Help Updating Rooted Epic

I have a rooted Epic on Froyo with CWM. No custom mod or kernel.
I got the OTA Update, and it failed.
I downloaded the Zip and tried CWM to install it. And it fails with this message :
Code:
I:Update location: /sdcard/update.zip
Opening update package...
Installing update...
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 775 4090
1: 1023 4089
2: 1053 4088
3: 2879 4087
4: 2894 4086
5: 2944 4085
6: 3446 4084
MountFn : RFS File System, location : system
mount: failed to mount /dev/block/stl9 at /system: Device or resource busy
Verifying current system...
file "/system/bin/recovery" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Do I have to do a full flash and wipe my phone to get to GB? Can I unroot & try?
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.
I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?
infyrno676767 said:
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.
Click to expand...
Click to collapse
Yes, there is a root available. I'm currently rooted & running ACS ICS v4.
Take a look at this video: http://www.youtube.com/watch?v=KesCXPpa3cI
DjFarout said:
I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?
Click to expand...
Click to collapse
Preeeetty sure you cannot get OTA with Root, you need to manually install or flash back to Stock. There are lots of threads about this, with the same answer. Also, Best Buy doesn't know a thiiiing. A friend of mine works there, and she's pretty damn stupid.
Well, since you're rooted.. you should probably invest in Titanium Backup. It can backup your data (contacts, messages, apps. you name it) and restore this all as well. Once you back up all of your data, revert to Stock, upgrade to the OTA, root it, then install Titanium Backup & you'll have it all back.
https://market.android.com/details?id=com.keramidas.TitaniumBackup&hl=en (free)
https://market.android.com/details?...iY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cFBybyJd (paid)
I Odined back to stock, ran the update.zip, Odined a recovery, flashed su and then started flashing roms to test. I save my messages with mms backup & restore, but other than that, most of the things I use save to sd. I like a really clean install so I know where my problems are coming from.
marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
Seriously? You're *****ing at this person because you failed to take the time and research these forums. I spent an entire day reading threads and watching QBKing77's videos to gather all the necessary information and files before doing anything. Also, spare me with any replies to you not having enough time to do so.
Hope you walk away from this with a new found respect for doing research.
Edit: You even posted in the "Everything EI22" thread in the General forum where I gave a typed out how-to for a clean install, or full ODIN to Froyo then the upgrade to Gingerbread. You could've simply scrolled up on page 10 to this post. (Seeing as your post created page 11 of that thread.)
marschmellau said:
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.
Click to expand...
Click to collapse
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
They see me trollin'..
You're obviously an idiot. I used the method to return to stock just last week. It's not my fault that you can't comprehend simple instructions. That is not the wrong picture, btw. ODIN looks like that.
Also, Out of oh.. I don't know, all of the people I've linked this to, you're the only one who had any issue. It's damn near obvious that you were the one who screwed up.
Do some damn research before you even post anything else.
Oh! And, if you actually used the search function you would learn how to get your phone into download mode so you can reflash stock rom.
I think this is pretty hilarious, btw.
Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.
@ThunderOKC,
I live in the OKC area. I imagine you are from here. If you need hand holding help, PM me. I've been around snooping the forums since January. I am now confident enough to answer questions, troubleshooting, and also start producing my own mods. There is always someone willing to help.
I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious
ThunderOKC said:
Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.
Click to expand...
Click to collapse
Well then, the picture itself is wrong. Don't rely on pictures for a guide, half the time they aren't correct. Next time, follow it step by step from the directions, not pictures.
b16flybye said:
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious
Click to expand...
Click to collapse
Lol, Pretty much what has been said.
Also, ThunderOKC. You do realize that to fix the "soft brick" on an epic means returning it to STOCK. So yes, you idiot, you can use that thread to return to stock without it having a soft brick.
like I said, do some more research
ThunderOKC said:
I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol
Click to expand...
Click to collapse
Funny thing is that thread works for everyone but you. No one has cried about it semi-bricking the phone or that they can no longer afford to get the breast implants, or whatever the surgery was you claimed you couldn't get to because you had to buy a new phone. That statement alone showed your mentality and level of competence. The Red fail means your stock cable is a piece of crap and you should spend $2 of your surgery money to get a good cable. If you just red through the thread instead of running your mouth everywhere you would have seen that is common for Odin and stock cables.
---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------
ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
Actually it is funny. Your level of incompetence shows you should not be rooting or messing with your phone. You are very rude and have no gratitude for people trying to help you. Stay out of the love connection chat rooms asking for help with your phone.
I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.
@ ThunderOKC
It's your choice to hack your phone. With that choice comes the responsibility to do proper research beforehand and make educated decisions based upon that research. Otherwise you will likely end up with a paper weight. That is the inherent risk of hacking the phone.
You've been posting all over this forum complaining, and the tone has been down right rude. Welcome to the ignore list.
ThunderOKC said:
I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.
Click to expand...
Click to collapse
This is why your stupid. You rely on a picture, and whatever chat room you have laughing at xda devs, are just as idiotic as you are. Your not welcome here douche. Good luck in the future. I think your dumbass should stick with what sprint gave ya.
Sent from my SPH-D700 using XDA App

[Q] Rooting help neaded for note2

hey guys im new 2 android community... ive a galaxy note 2 GT-N7100 International version bought in India. Recently ive been thinkin 2 root my device for various mods like copyin/ installing games on memory card etc... so i wanna know wat software should i use 2 mod my device?? Also i wanna know if its safe??? Ive heard that rooted devices leads to void of warranty... is that true???
thanks in advance....
You should use the wonderful Note2 ToolKit, found here: http://forum.xda-developers.com/showthread.php?t=1923956
Yes, rooting it voids your warranty. But you can flash back a stock ROM and unroot if you need to take your phone in for service.
All modifications have risks. Though rooting probably won't break your phone, an user error on your part just might, or malicious code might. You can never know that! You have to be careful and use your best judgment. Rooting is basically like logging in to a computer with an administrator account, you can change all the system settings and as a result you can really screw up your system if you are not careful.
I'm just saying all that to clarify that if you do root your device and mod it, have an accident and screw something up, it's your own fault. You need to always keep that in mind.
When you download the toolkit, the first thing you need to do is:
1) EFS backup
2) Full Nandroid backup
Do those two things first, then do whatever you want. If you have EFS and Nandroid backups you have a safety net in case something goes wrong later on.
Also: read, read, read. Read every single Note II guide and FAQ you can find here on XDA.
Read post #2 and 3 of this thread (though 1-9 all posts are informative for newbies)
http://forum.xda-developers.com/showthread.php?t=1896696

some guidance, direction or links please...

i want to to be safe. i have a tmobile variant and i would like to flash a stock unlocked and/or international rom or developer edition rom. i am guessing this will work but i will have to use gpe or tmobile radios. i haven't seen a clear path to this and i wish it was as easy as fastbooting or just flashing the proper stock nandroid. i am confused, between all the FUU's RUU's, different firmwares etc etc. is there a guide i overlooked to do this?
btw, i've converted to gpe but i went back for various reasons. the gpe just didn't have all the proper drivers to make it the premium phone the m8 is and be stock android, because i much preferred stock but sense is not too bad. helluva lot better than touchwiz. i am just concerned and don't want to brick. i had problems going back to sense. flashing my nandroid after the RUU just failed and failed. i thought i was gonna have to change underwear and get kleenex. ended up flashing my nandroid without md5 check and have had no problems since. i am aware of the CID situation and understand that. i assume i can do this with all 1's or a EU or unlocked cid. i think i understand the MID thing but would appreciate it if somebody clarified it for me. i assume that whatever i end up flashing i need to change my MID to the appropriate MID or change it in android-info.txt or is there where i'm wrong?
anyways, hoping somebody would give some magical link to a thread i overlooked. i am backing up my latest nandroid to my laptop right now and when that is done i am going all the way stock to tmobile version. hopefully in the next hour or so i'll get my answer or direction to the appropriate thread and can just convert to dev or unlocked edition. tmobile variant just has way too much bloat and things i changed like a dozen files for carrier iq block. changing to htc edition firmware will minimize the things i need to do when it's time to ota. anyways, if you made it this far thanks. and even more thanks if you're that person that gets me going in the right direction. i am almost proficient at adb/fastboot so i don't need to be handheld on that.
nevermind. went off without a hitch. was worried because previous restores from nandroids didn't go so well. i'm flashed and tmobile splash didn't show so i am pretty sure i am eu now.

You people writing these rooting and unlocking guides are completely insane.

I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.

Categories

Resources