Database Info

[Q] Accidentally flash vibrant rom... some help? PLEASE.

Well I barely got my phone about 4 days ago, and i couldn't get my mind out of rooting and flashing the device.. and without much research... that's where I think I was being a little stupid.. I had got online and saw this program on wiki for samsung vibrant phones called "heimdall-suite-1.1.1-win32" and I read what it told me to do.. now this wikipedia site said that with heimdall i can flash "Cmenard-overstock-vibrant" I had done that and right away the phone would load up to the galaxy S boot logo and turn black... the only thing after that were the little lights would react to touching them. I got freaked out and started looking for information like crazy.. I honestly can say I started around 11Pm and did not go to bed researching til 7am and sadly still nothing.. I grabbed a better usb cable just today. my other one is kind of torn and kept coming on and off I would have to keep it at a certain angle. But this one works perfect! I don't get the actual charger til monday, the person I bought this phone has an Iphone 4s and didn't want his galaxy anymore so I took the opportunity to buy it for $100. A good deal like that I should of never played with this phone and I regret it... a day later I find out I don't have the vibrant.. I have the galaxy s 4g. I can still boot into download mode however now everytime it boots up it bootloops and has the samsung vibrant logo instead of the standard Samsung Galaxy 4g s logo with T-mobile. I'm finding this to be so complicated I wish I could go back to stock... please someone on here help me.. I'd appreciate it so much. Thank you for reading and I hope to get someone's response soon
**************************************************
12:52Am
I first want to say thank you guys for directing me towards the right area.
This is going to sound a little weird...
I've gotten the stock KC1 rom to flash and I kept getting failed. I thought I was stuck at the samsung screen logo
i waited about 2 minutes later and it booted up! Weird so anyways now what's bugging me now is this phone keeps Vibrating! what's going on? is there another update to a stock rom I can flash that will work? Do I have to be rooted? Can I unroot yet? (because I don't wanna mess with this no more!) lol what can I do to make this phone back to normal?
I'll tell you what I am capable of doing now
Go into stock recovery
Go into download mode
and boot my phone
once again I'd like to thank you all
*************************
UPDATE!!!!!
12:17AM Central
I have fully restored my rom with Mr. bkoon1218 assistance!!!
Here's what I did just in case anyone runs into what I did. I will say what mistakes I had done and then give my resolutions that couldn't have been possible without the assistance of these awesome members!
1. I was curious on flashing a custom recovery to my device, STUPIDLY I did not read or research anything regarding this phone.
2. I flashed Cmenard with heimdall-suite-1.1.1-win32 thinking that it would give me a recovery because I thought that I had the Samsung Galaxy *Vibrant*
3.Two days stressfully googling and googling for corrections and mistakes other may have done like me I had no choice but to ask myself.
I started off in the Vibrant section and a guy helped me out with flashing the rom but still nothing. Given instructions I felt my phone was done. I would get glitches and a nasty pixelated boot.
4. I researched my phone model number on the back of my phone and realized my phone wasn't the Vibrant.. Then it banged my head when another emailed me saying it was weird that my Samsung Vibrant was a 4g device lol.
5. I then moved to Samsung Galaxy S 4g and proceeded to find help along with the research I had done.. I even tried all the Odin updates thinking that could've made the difference.
*Resolution*
1. THANKS TO ALL FOR HELPING FIRST OFF ALL!!! YOU ARE ALL GREATLY APPRECIATED!! Next! A BIG THANKS! to * bkoon1218 *
for providing me with a helpful link where I read and understood what this rom was for. LINK - http://forum.xda-developers.com/show....php?t=1129933
2.Downloading Hawk.zip file I then used Winrar to extract it and there are four files!
-1.SGH-T959V-CSC-TMB.tar.md5
-2.Sgs4g.pit
-3.T959VUVKC1-Phone-CL932707.tar.md5
-4.T959VUVKC1-REV00-ALL-low-CL933594.tar.md5
3. I tried Odin 1.85 and it didn't work for me however I now know the reason why and what's funny is it happend accidentally.
I forgot to uncheck Re-Partition and I thought it would immediately softbrick my phone!! I started to see however it doing it's magic!
I said "ahh might as well let it go through the process I'll just one click unbrick my phone if it doesn't do it again..". By the way I used Odin 1.7.
and poom!!!! I got a pass!!! *This was only with Checking the box Re-Partition!*
4.So I am now fully fresh back to stock and unrooted and I am done. I decided to write this for any others that go through the same problem I did. I don't mean to take anybody's credit or anything I just want other to look this up when they accidentally flash their phone with a different rom and are as lucky as I am.
**MY ENDING RESULTS**
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 is valid.
<OSM> T959VUVKC1-Phone-CL932707.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> factoryfs.rfs
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> modem.bin
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
THANK YOU ALL AND GOOD LUCK TO YOU ALL!!!!!

Read the Bible in the stickies and Odin stock.
Sent from my SGH-T959V using XDA App

can you please provide me a link? I'm new sorry

Here's the Bible: http://forum.xda-developers.com/showthread.php?t=1117554
Read through it before you really brick your phone. You got lucky this time.

http://lmgtfy.com/?q=galaxy+s+4g+stock+odin
There is always a 5 second search on Google too.
Please use the search button to look around xda.... you the 9001st (over 9000!!!!) person to not read up on things before getting in over your head.
Sent from my SGH-T959V using XDA App

I've flashed with these and get all the way to the end and come up with a Fail.
I don't know what to do anymore I just want to go back to stock rom and not flash anything else but I'm a bit tired I've been doing this for almost three days and am starting to lose hope.. I just don't know what else to do

If you want to go back to stock, you might as well do stock GB.
Look for KI3 LEAK (you'll need bootloaders). Odin that in PDA and you'll be fine.

Odin/heimdall fail on Chinese P6200?

Hi I got a tab from China i think originally the baseband said ZCLA1. The default search engine and the chinese market app was annoying me since I couldn't read any of that. I thought I could just flash to a stock Euro firmware like XXKL7. . I've tried a few different versions from the Heimdall thread here and also firmwares I d/led from check fusI attempted many times with both heimdall and Odin. Heimdall got the furthest for me. I
Heimdall v1.3.2 would stop at cache and older versions of heimdall would fail at modem.bin both stopping after 100% and saying it could not confirm end of file transfer. after the heimdall update the language changed to russian i think but all the chinese apps were still there and default search baidu.
Code:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Uploading PIT
PIT upload successful
Uploading KERNEL
0%
1%
100%
KERNEL upload successful
Uploading RECOVERY
0%
100%
RECOVERY upload successful
Uploading CACHE
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
CACHE upload failed!
Ending session...
Rebooting device...
Odin would always fail before starting until I d/led the the new ICS update.
then i got
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> recovery.img
<ID:0/007> Sbl.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Right now it seems bricked and I can not do a recovery. I tried to do a search for zcla1 firmware and I couldn't find anything for the P6200. I saw the tab 10.1 and a few others had zcla1 firmware. But is that the same?
Is there something about the chinese tabs that prevents me from installing other firmware? Is there another way for me to install a non chinese firmware?
Also I've noticed everytime I flash with heimdall theres a counter that keeps going up on the download screen of the tab "Custom Binary Download: Yes (13 counts)" Should I need to worry about that?
Thanks for any suggestions you may have!

Perhaps it is a knock off ???

I'm getting same problem. Please help us!

MrNo said:
Perhaps it is a knock off ???
Click to expand...
Click to collapse
I don't believe it is but I really don't know how to prove or disprove that.
So after d/ling a ton of different firmwares and trying each one, I seem to have been able to install something that allows google apps.
Is it right that the Baseband,kernal and build are all different?
I'm a little afraid of trying to install ICS again because I really dunno how I fixed the problem in the first place. Does anyone else know what I can try to make this work? Or has anyone else know anything about these Chinese P6200s?

Try using Odin 1.85 it should work.

same thing here,
purchased a p6200 from china with no google support, wasn't too affraid at the start, just decided to use odin and push another firmware to it...
I tried ICS, nop same error as the original post here, so i tried a EU version, still not, tried a HK version, and still not.
Looks i can just push the original firmware back into it.
Will try to root and use mobile odin see if it can get better,...
Also there's no VPN option in the wireless settings.
Will let you know more about what i can find

Getting somewhere
ok so,...
I successfully flash a stock rom with heimdall using this post method:
http://forum.xda-developers.com/showthread.php?t=1517934
Thanks oarth
And i'm now running on 3.2 HC
Will now try to get the ICS running
will keep you guys posted

And..... Done
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!

Post link for us
sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
Hello Guys,
I am facing the same problem with my GT-P6200 Chinese version, now I get stucked on download mode or another screen telling me to connect KIES in restore mode. Could you post the link for tar file that you create and finally get ICS on P6200.
I am downloading now the file that you mention on the link (http://forum.xda-developers.com/showthread.php?t=1517934) and try to get live on my tablet again.
Thanks,

sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
sirprize_p6200, could you post your solution? Currently I have a Chinese P6200 keep rebooting at the logo. Bricked? Desperately need a solution.

sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
PLEASE can u upload the files you used i need to ressurect on Tab asap.....

Even with PIT file and Phone Bootloader Update checked...
Odin 1.85 log
<ID:0/082> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6200DXKL3_P6200OLBKK8_P6200DXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/082> Odin v.3 engine (ID:82)..
<ID:0/082> File analysis..
<ID:0/082> SetupConnection..
<ID:0/082> Initialzation..
<ID:0/082> Set PIT file..
<ID:0/082> DO NOT TURN OFF TARGET!!
<ID:0/082> Get PIT for mapping..
<ID:0/082> Firmware update start..
<ID:0/082> boot.bin
<ID:0/082> NAND Write Start!!
<ID:0/082>
<ID:0/082> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone share any Success story with these Chinese ones?
BR
---------- Post added at 05:22 PM ---------- Previous post was at 05:11 PM ----------
And no Codes entered via keypad works ???
e.g. *#06#, *#1234#, *#197328640#, *#9090# etc...
Regardless of SIM in tablet on no... Really "LOCKED" huh....
Phone is factory Simfree...
How about that tutorial.... I dont want to RIFF-it if I don't need to.
BR

And I can't extract PIT file from device with Heimdall 1.31running on XP
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12

Heimdall is a bit glitchy here, sometimes it flashes some partition, sometimes it does not...
I tried lot's of combinations of BOOT.img KERNEL, FactoryFS, SBL1 etc In between Chinese version 4.0.4. GT-P6200_CHN_P6200ZCLPM_P6200OZHLPM_P6200ZCLPG
And Malaysia version 4.0.4. P6200DXKL3_P6200OLBKK8_XME
The goal was not Chinese 4.0.4. Stock Android but it Faled.
I revived tab with odin and stock firmware I had inside in a first place...
Hex editor claims that .pit extracted from my fully working chinese no google and market firmware IS IDENTICAL to serveral here on forum published ones.
So. Since I DO HAVE RIFF JTAG box I am planning to update bootloader even if it bricks device, but cant find any.
Anyone?
BR

Weird... It look's that won't accept different boot even trough Odin...
P6200_APBOOT_P6200XXLQ7_XXXXXXXXX_REV02_user_low_ship.tar.md5
Do I really have to JTAG fully working phone in order to get Google and Market? Hmpfff....
BR

hi :
heimidal not work for me but mobile odin 1.85 work like of charm an recovery installed .
backup and restore work good
also wipe data and cash
i erase all my files and restore all of themes by recovey

[Completed] Note 3 stuck on the mmc_read fail screen after attempting backup....won't do anything

no flash mode...no download mode...nothing

XDA Visitor said:
no flash mode...no download mode...nothing
Click to expand...
Click to collapse
Upps ... sound like a brick.
You can try to unbrick like described here: [GUIDE] Root/Install recovery/Unroot/Unbrick/Flash official stock on Galaxy Note 3 (post #2).
Or like this: How to Unbrick a Hard Brcicked T-Mobile Note 3 SM-N900T.
Or like this: [HARD BRICK Fixed] - N9005-Make your debrick.img and have it on extSdCard by security.
Always keep in mind that there are several different variants available for the Note 3. So you should identify the exact device model name to flash the correct files.
Good luck !

It_ler said:
Upps ... sound like a brick.
You can try to unbrick like described here: [GUIDE] Root/Install recovery/Unroot/Unbrick/Flash official stock on Galaxy Note 3 (post #2).
Or like this: How to Unbrick a Hard Brcicked T-Mobile Note 3 SM-N900T.
Or like this: [HARD BRICK Fixed] - N9005-Make your debrick.img and have it on extSdCard by security.
Always keep in mind that there are several different variants available for the Note 3. So you should identify the exact device model name to flash the correct files.
Good luck !
Click to expand...
Click to collapse
Ok...I somehow have gotten it to finally boot to ODIN, but all PIT files I have found so far....this is what I get on ODIN itself when attempting to flash PIT...
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone says: SECURE CHECK FAIL : PIT
I have also tried the factory OS flash, and it fails as well, is there possibly something that I'm doing wrong, or is it just I have to try file after file until finding the correct one?
Thanks for the help so far!

RT4U2C said:
Ok...I somehow have gotten it to finally boot to ODIN, but all PIT files I have found so far....this is what I get on ODIN itself when attempting to flash PIT...
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone says: SECURE CHECK FAIL : PIT
I have also tried the factory OS flash, and it fails as well, is there possibly something that I'm doing wrong, or is it just I have to try file after file until finding the correct one?
Thanks for the help so far!
Click to expand...
Click to collapse
Please post in one of the threads I linked in my previous answer.
There you will get best help.
Thanks for your understanding. Thread closed.

[Q] New Note Edge Developer, possibly bricked. Please help!

I am really desperate here! I just spent $800 on the Note Edge Developer Edition (SM-N915V):
samsung dot com/us/mobile/cell-phones/SM-N915VMKEVZW
I am really hoping this isnt totally bricked because it was expensive and I only had it two days.
I tried to get root and found posts/pages on the net that said the Note 4 rom/tar file for odin could be used for all the "Note" linn devices. I turned on developer mode, booted into installation mode (home volume power) and followed these instructions
android dot gs/root-verizon-galaxy-note-4-developer-edition-using-odin-and-cf-auto-root/
Loading the tar file: CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
Odin found the phone fine, then when I clicked start here is the log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when it boots up it just shows the error in the attached image "Software update failed". It still says odin in the tiny status text and odin "seems" to see it when I reconnect it, so I am hoping hoping it can be fixed with the right tar file.
Is there anyway to fix this???? I will do almost anything to get this working...

starfoxtj said:
I am really desperate here! I just spent $800 on the Note Edge Developer Edition (SM-N915V):
samsung dot com/us/mobile/cell-phones/SM-N915VMKEVZW
I am really hoping this isnt totally bricked because it was expensive and I only had it two days.
I tried to get root and found posts/pages on the net that said the Note 4 rom/tar file for odin could be used for all the "Note" linn devices. I turned on developer mode, booted into installation mode (home volume power) and followed these instructions
android dot gs/root-verizon-galaxy-note-4-developer-edition-using-odin-and-cf-auto-root/
Loading the tar file: CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
Odin found the phone fine, then when I clicked start here is the log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when it boots up it just shows the error in the attached image "Software update failed". It still says odin in the tiny status text and odin "seems" to see it when I reconnect it, so I am hoping hoping it can be fixed with the right tar file.
Is there anyway to fix this???? I will do almost anything to get this working...
Click to expand...
Click to collapse
Would suggest to flash STOCK 915V(edge)rom. Might fix problem.
Don't flash anything for other models unless you are 100% sure you can recover or it will work. It's a very expensive mistake to make...

I honestly thought it was a compatible rom. Do you have a link to the stock one I cant find anything? Its all for the SM-95F/G/etc and not the V. And will the stock rom blow away the developer/unlocked bootloader and revert it to retail?
And if it does work, is there anyway to get root on this one??

starfoxtj said:
I honestly thought it was a compatible rom. Do you have a link to the stock one I cant find anything? Its all for the SM-95F/G/etc and not the V. And will the stock rom blow away the developer/unlocked bootloader and revert it to retail?
And if it does work, is there anyway to get root on this one??
Click to expand...
Click to collapse
Your issue sounds exactly like what happened to sprint users when we first tried to root. The cf-auto-root root method for us failed every time giving that same message. See this thread: http://forum.xda-developers.com/note-edge/help/n915p-cf-auto-root-fails-t2944539
The issue with xposed will also apply to you (I'm 99.999999% sure of this), so read up on that if you're not already aware.
---------- Post added at 09:14 ---------- Previous post was at 09:12 ----------
Also, the ONLY Note 4 intended root-related tool I know of that's safe to run on the Edge is the Note 4 variant of TWRP. Set brightness all the way down and disable screen lock though. You'll see why if you run it.

use a 915G ROM and all will be well, i myself have went through this pen.

Ok hold on. What are we talking about here? The OP was all about CF auto root. Why are we all talking about flashing different roms now? The issue of CF auto root failing has been seen on both the Tmobile and Sprint variants, and both times it has been solved by flashing TWRP afterwards. I pasted a link to one of the (numerous) related threads above.

Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.

starfoxtj said:
Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.
Click to expand...
Click to collapse
If chain fire autoroot fails simply flash a compatible custom recovery for your device right after the failure. Twrp is an awesome custom recovery with a lot of great features built into it.

starfoxtj said:
Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.
Click to expand...
Click to collapse
TWRP is a custom recovery that replaces the stock recovery. It lets to do MUCH more than the stock recovery, notably making Nandroid backups (full images of your system in its exact state that you can restore to if anything goes wrong). This is what you should do:
Download TWRP. The Note 4 variant is the only option here, but it works fine. Choose "twrp-2.8.6.0-trltevzw.img.tar" from here: http://dl.twrp.me/trltevzw/
You've already run CF auto root so just boot into download mode again, and connect the phone to your computer. Run odin and flash the file you just download in the PDA slot (for odin 3.07) or the AP slot (for odin 3.09).
once you've flashed that, see if you can reboot into recovery (Home, Power, vol UP). Once you're there, make sure you go into settings and turn the brightness all the way down and disable screen lock (the two white bars are because this was intended for the note 4 and will burn in your screen if you leave it on too long at full brightness. Unlocking the screen in TWRP also seems to be broken, but disabling screen lock works around that.).
Now you can reboot into the system, and from there you should be rooted. If SuperSU isn't already downloaded, just download it from the Play store.
If you're not rooted, try flashing CF auto root again, and then go through these steps again afterwards. Although next time, try this one: http://download.chainfire.eu/617/CF-Root/CF-Auto-Root/CF-Auto-Root-tbltespr-tbltespr-smn915p.zip It's for the sprint variant but should work.

jooniloh THAT WORKED!!! THANK YOU SO MUCH!!!!
I have SuperSU and titanium running perfectly!! I was sweating so bad at the thought of losing 1k....dude thank you so much I cannot tell you how happy I am!!!
I read about how I should backup the "aboot" partition incase it gets lost somehow. Do you recommend doing that and is this the guide to use?
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Or will a full backup in titanium backup include that as well? And is there anything else I should do before installing all my apps and loading my data?
Once I do a backup with titanium can I just do a normal factory reset to test that the restore works correctly? If so, how is that done on a rooted phone?

Reflash of the stock rom will 9 times out of ten fix any problem. I would suggest you find a stock rom so if anything does go wrong, you can restock.
Also, DON'T flash any other model; rom (no, a 915G rom is not the answer... you needs a 915V rom)... That will definitely cause bootloops or hanging at the Samsung logo...

starfoxtj said:
jooniloh THAT WORKED!!! THANK YOU SO MUCH!!!!
I have SuperSU and titanium running perfectly!! I was sweating so bad at the thought of losing 1k....dude thank you so much I cannot tell you how happy I am!!!
I read about how I should backup the "aboot" partition incase it gets lost somehow. Do you recommend doing that and is this the guide to use?
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Or will a full backup in titanium backup include that as well? And is there anything else I should do before installing all my apps and loading my data?
Once I do a backup with titanium can I just do a normal factory reset to test that the restore works correctly? If so, how is that done on a rooted phone?
Click to expand...
Click to collapse
What you want to do is make a Nandroid backup in TWRP. With a nandroid backup, if anything goes wrong with anything on your system, 99% of the time, you can restore the backup and your system will revert to EXACTLY how it was when you made the backup (root, apps, settings, EVERYTHING).
What I suggest you do is get a Micro SD card (you need one large enough. The Nandroid will be as large as however much is on your phone (NOT including your internal SD card). Ergo, if you have a 64GB phone filled to 50GB of application data, you'll need something with around 60GB (50GB + system, modem, efs, cache, boot, etc.) of space for the backup.), put the backup on that, and move them to a safe location (like your computer, or an external drive). To make a Nandroid, boot into recovery again, press "Backup", make sure all the partitions are selected, make sure storage is set to "Micro SDcard", then swipe.
Once the backup is done, turn off the phone, take out the SD card, and put it into your computer. Keep a safe copy of your backup (it'll be in TWRP/BACKUPS/<8-digit hex ID>/<your backup name>) somewhere and do this regularly. I suggest you also give your backups detailed names so you remember when you made each one, or what you did right after making that backup (like if you made a backup before flashing a certain file that you don't know if it'll work correctly). That way, if you need to go back to a backup, you can figure out which one to go back to easily.
Once they're on your computer, I wouldn't keep the backups on your Micro SD card because they're large and take a lot of space. IF you had the 128GB Micro SD, maybe keep the latest backup for convenience, but that's about it. Keep the rest on your computer. You can delete backups from your Micro SD by going to "Restore" in TWRP, selecting the backup, then pressing "Delete Backup".
An important thing to keep in mind is that Nandroids do not back up your data on the Internal or External SD cards. You can access both these locations through your computer though so make backups of them manually. Otherwise, you risk loosing downloaded files, photos, etc.
For less serious things, you can make a backup of apps and their corresponding data in Titanium Backup. This wont save you from corrupt systems files or other more serious issues, but if you switch to a new ROM and want to take your apps and data with you, Titanium is your friend. Titanium WON'T back up anything else besides apps and data. If you need a more comprehensive guide on Titanium, give a shout, and I'll see what I can do.
As for backing up aboot. Yes. Definitely do that. I'm reading through the guide posted there now. If you need any clarification or help with the steps, don't hesitate to ask. When in doubt, just ask. Some of the tools used could do some serious damage to your phone with even a slight error. Also, it's always a good idea to read all the instructions through once before doing anything so nothing surprises you as you're doing it.
The closest thing to a factory reset you can do quickly is the "Wipe" option in TWRP. Otherwise, to truly factory reset, you have to flash a stock rom. This will unroot AND remove TWRP.
ultramag69 said:
Reflash of the stock rom will 9 times out of ten fix any problem. I would suggest you find a stock rom so if anything does go wrong, you can restock.
Also, DON'T flash any other model; rom (no, a 915G rom is not the answer... you needs a 915V rom)... That will definitely cause bootloops or hanging at the Samsung logo...
Click to expand...
Click to collapse
Will the 915V ROM work for the dev edition? This was brought up before but never confirmed or denied as I remember.

The retail rom will not work on the dev edition. also for the dev edition you do not need cf autoroot. only flash twrp then use twrp to flash supersu update.zip reboot and done.
Also I have a full backup of full stock dev edition but when you flash it onbdefferent device it becomes super laggy. I'm currently trying to figure out how to make my backup into a flashable rom so that it goes through all the proper install steps instead of being a backup that can be restored on a different device at the cost of a $900 box of lag.
Sent from my SM-N915VMKE using XDA Free mobile app

NekoShinigami said:
The retail rom will not work on the dev edition. also for the dev edition you do not need cf autoroot. only flash twrp then use twrp to flash supersu update.zip reboot and done.
Also I have a full backup of full stock dev edition but when you flash it onbdefferent device it becomes super laggy. I'm currently trying to figure out how to make my backup into a flashable rom so that it goes through all the proper install steps instead of being a backup that can be restored on a different device at the cost of a $900 box of lag.
Sent from my SM-N915VMKE using XDA Free mobile app
Click to expand...
Click to collapse
Could you please post links to the proper tools for the Dev edition?
I don't know what version of Odin I would need, or where to find the proper twrp.zip.
Please help.
Again it's the Verizon Dev edition Note edge.
Thanks in advance.

Vorridor said:
Could you please post links to the proper tools for the Dev edition?
I don't know what version of Odin I would need, or where to find the proper twrp.zip.
Please help.
Again it's the Verizon Dev edition Note edge.
Thanks in advance.
Click to expand...
Click to collapse
I've already posted instructions for everything on the thread. Please read. Odin version doesn't matter; there's only two that are widely circulated anyways.

jooniloh said:
I've already posted instructions for everything on the thread. Please read. Odin version doesn't matter; there's only two that are widely circulated anyways.
Click to expand...
Click to collapse
Okay thank you. Will I need the extsdfix.zip? Also I have Odin 3.07 from working on my galaxy reverb will that work?

Vorridor said:
Okay thank you. Will I need the extsdfix.zip? Also I have Odin 3.07 from working on my galaxy reverb will that work?
Click to expand...
Click to collapse
The SD card fix is optional. Apply it if you want. Make sure you read the other posts before continuing. Use the latest version of TWRP for any Snapdragon Note 4 (TMO/ATT/VZW/SPR) downloaded from the TWRP site as the one in the T-Mobile Root thread is probably outdated. Use whatever version of Odin you already have.

jooniloh said:
The SD card fix is optional. Apply it if you want. Make sure you read the other posts before continuing. Use the latest version of TWRP for any Snapdragon Note 4 (TMO/ATT/VZW/SPR) downloaded from the TWRP site as the one in the T-Mobile Root thread is probably outdated. Use whatever version of Odin you already have.
Click to expand...
Click to collapse
Okay I downloaded the twrp mentioned in the posts on here, and got the Odin 3.09.
Now should I download the kies mini that's linked in the op?
I'm sorry for all the questions, I'm having trouble navigating the posts and links.
I do very much appreciate all your help and time! :good:
Also, can I flash the extsdfix.zip and SU update from twrp or do I need Odin for that also?

Vorridor said:
Okay I downloaded the twrp mentioned in the posts on here, and got the Odin 3.09.
Now should I download the kies mini that's linked in the op?
I'm sorry for all the questions, I'm having trouble navigating the posts and links.
I do very much appreciate all your help and time! :good:
Also, can I flash the extsdfix.zip and SU update from twrp or do I need Odin for that also?
Click to expand...
Click to collapse
Like I said, download the latest TWRP from its site. You don't need Kies unless you don't have Samsung device drivers on your computer. The SD card fix is flashed from TWRP. You don't need the SU update. As I said before, read the rest of my instructions on this thread first before continuing. All the steps after flashing CF-auto-root are listed here.

jooniloh said:
Like I said, download the latest TWRP from its site. You don't need Kies unless you don't have Samsung device drivers on your computer. The SD card fix is flashed from TWRP. You don't need the SU update. As I said before, read the rest of my instructions on this thread first before continuing. All the steps after flashing CF-auto-root are listed here.
Click to expand...
Click to collapse
Sorry again, I'm having trouble finding your post with instructions, so, if I have this right...
1st : open Odin, plug the phone in to pc, let Odin recognize the phone?
2nd : put the twrp in the ap slot then flash?
3rd : reboot phone in twrp, flash the extsdfix.zip?
And finally since it's dev edition, do I need to do the cf autoroot?

Help with rooting!

I have quite the issue with the phone, i can't flash anything with Odin.
Here's what I did that got me into this mess and hopefully you guys can dig me out of this hole.
The phone was running 4.3, I rooted it using Kingo, then flashed CWM Recovery. When I attempted to reboot it it gave me a screen saying "System software not authorized by Verizon Wireless has been found on your phone..." So, I went into the recovery, opened Odin and tried to flash stock.vzw_root66.tar and got this:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So is my phone toast or can I fix this, im still a rooting noob, this is only my third phone ive messed with.
Edit: if i reboot the phone after being in the recovery i get "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again"

Medical Cola said:
I have quite the issue with the phone, i can't flash anything with Odin.
Here's what I did that got me into this mess and hopefully you guys can dig me out of this hole.
The phone was running 4.3, I rooted it using Kingo, then flashed CWM Recovery. When I attempted to reboot it it gave me a screen saying "System software not authorized by Verizon Wireless has been found on your phone..." So, I went into the recovery, opened Odin and tried to flash stock.vzw_root66.tar and got this:
So is my phone toast or can I fix this, im still a rooting noob, this is only my third phone ive messed with.
Edit: if i reboot the phone after being in the recovery i get "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again"
Click to expand...
Click to collapse
You should honestly read through the guides on here. 4.3 is locked and you can't run a custom recovery. Root 66 is a stock rooted 4.1 build. You should be happy it isn't flashing because it would hard brick your phone.
Look in the development section and read the 4.3 sticky, Everything you need to know is there and should know for future reference. You have a soft brick, so follow the soft brick repair guide with a 4.3 rom.

BadUsername said:
You should honestly read through the guides on here. 4.3 is locked and you can't run a custom recovery. Root 66 is a stock rooted 4.1 build. You should be happy it isn't flashing because it would hard brick your phone.
Look in the development section and read the 4.3 sticky, Everything you need to know is there and should know for future reference. You have a soft brick, so follow the soft brick repair guide with a 4.3 rom.
Click to expand...
Click to collapse
Honest mistake, thanks for pointing me in the right direction.