Hi, my developer options do not show oem unlocking. I tried the Exynos root apk, but it says it cannot root my device. I assume my bootloader is unlocked.
I have searched around and not come up with a good solution. Can someone point me in the right direction?
A buddy gave me the tablet, and I am going to give it to someone that needs it when I get home to Thailand, but I would like to get Lineage up and running rather than giving them android 4.
Thanks in advance, JC
PattayaGlock said:
Hi, my developer options do not show oem unlocking.
Click to expand...
Click to collapse
This does not exist on this device and it's not needed.
PattayaGlock said:
A buddy gave me the tablet, and I am going to give it to someone that needs it when I get home to Thailand, but I would like to get Lineage up and running rather than giving them android 4.
Click to expand...
Click to collapse
Than you can directly install TWRP and any ROM.
Just follow my instructions:
Instructions – MHS Solutions
www.mhs-solutions.com
Thanks so much!
Just realized the charger I have is not usb. As soon as I grab a usb charger I will install Lineage and buy you a beer!!
html6405 said:
This does not exist on this device and it's not needed.
Than you can directly install TWRP and any ROM.
Just follow my instructions:
Instructions – MHS Solutions
www.mhs-solutions.com
Click to expand...
Click to collapse
I get this error messsage when using heimdall .:
[email protected]:~/Downloads
$ heimdall flash -twrp-3.5.0_9-0-n8010.img
Missing parameter for argument: -twrp-3.5.0_9-0-n8010.img
Action: flash
Arguments:
[--<partition name> <filename> ...]
[--<partition identifier> <filename> ...]
[--pit <filename>] [--verbose] [--no-reboot] [--resume] [--stdout-errors]
[--usb-log-level <none/error/warning/debug>]
or:
--repartition --pit <filename> [--<partition name> <filename> ...]
[--<partition identifier> <filename> ...] [--verbose] [--no-reboot]
[--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
Note: --no-reboot causes the device to remain in download mode after the action
is completed. If you wish to perform another action whilst remaining in
download mode, then the following action must specify the --resume flag.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
What am I doing wrong?
Further update........I booted into windoes and used Odin to flash twrp. I still end up in the android recovery. Have tried 3 times and gotten "pass" with each.
When I go back to download mode the top left corner says :
Odin mode
product name: gt n8013
custome binary download: yes ( 3 counts)
current binary: samsung offical
system status: official,
PattayaGlock said:
$ heimdall flash -twrp-3.5.0_9-0-n8010.img
Click to expand...
Click to collapse
heimdall flash --RECOVERY twrp-xxxx.img
would have been correct.
PattayaGlock said:
custome binary download: yes ( 3 counts)
Click to expand...
Click to collapse
Because you've flashed 3 times, thats the knox counter.
Is it now working?
THIS is why I am not a prgrammer. I make little mistakes like this.
Unfortunately, no, I am still getting factory recovery. This is the output from heimdall:
$ heimdall flash --RECOVERY twrp-3.5.0_9-0-n8010.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interfac
PattayaGlock said:
Unfortunately, no, I am still getting factory recovery. This is the output from heimdall:
Click to expand...
Click to collapse
Ok the flash process was ok,
you have to boot directly into the recovery mode from there.
If you're not doing this, it will re-write the stock recovery.
But if you did this correct and you still see the stock recovery, it could be that your eMMC is locked and needs to get replaced.
Got it up and running. For some odd reason, after I booted into TWRP I could not read my sd card ( where Lineage was ). Ended up sideloading Lineage and it seems to be working nicely.
Hope beer is as cheap where you are as it is in TEXAS. I bought you 2 rounds!
I spoke too soon
It ran just fine for about an hour. Now it is constantly rebooting into recovery. Did a dirty flash, ran 3 minutes then rebooted.
Oh well, Lineage is on there now.
PattayaGlock said:
I spoke too soon
It ran just fine for about an hour. Now it is constantly rebooting into recovery. Did a dirty flash, ran 3 minutes then rebooted.
Oh well, Lineage is on there now.
Click to expand...
Click to collapse
Wich version are you using and is it working now?
Did you also do a data wipe?
Well, when I got a chance I did a wipe and facotry reset. Lineange loaded right up and has been running without issue for almost 48 hours.
At this point I assume I did something that broke my 1sty install. After my reset I got a totally different welcome screen and set up procedure.....further supprting my theory I did something wrong.
Thanks so much for your time and help.
PattayaGlock said:
Well, when I got a chance I did a wipe and facotry reset. Lineange loaded right up and has been running without issue for almost 48 hours.
At this point I assume I did something that broke my 1sty install. After my reset I got a totally different welcome screen and set up procedure.....further supprting my theory I did something wrong.
Thanks so much for your time and help.
Click to expand...
Click to collapse
Ok and what's now? Still booting into the recovery or is it working?
Related
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
de4dw0lf said:
There is a phone on the left, a warning triangle in the middle, and a computer on the right side.
Click to expand...
Click to collapse
Does it look like the attached pic? Or similar?
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
de4dw0lf said:
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
Click to expand...
Click to collapse
First off, you are in an alternate download mode. Just flash Odin as normal with a stock ROM and all will be good again.
Second off, what ROM did you flash that has an overclocked processor? We don't have a kernel that supports overclocking yet, at least for gb.
As for the SIM card, I've had that problem before. It's from not wiping /data /system /cache before flashing. Once you Odin back to stock, it should work. If not, you will have to contact your service provider to get a new one.
de4dw0lf said:
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
Click to expand...
Click to collapse
That is still download mode. Use Heimdall One Click.
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g?
Click to expand...
Click to collapse
Use Heimdall One Click. The one with bootloaders. It will work. Read the OP to a T.
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
Click to expand...
Click to collapse
Click on the Lightning Zap link in my signature... Then click on the link called Removing the Gremlins in the OP
Read the whole post. The link will give you KG4 and Odin and the necessary drivers...
If you already have odin setup use this http://forum.xda-developers.com/showthread.php?t=1353176 It's the official update to Gingerbread.
alright
Alright. i will try the things you guys sent me, and i will tell you later if it worked.
Thanks a lot!!! i hope it works^^
I'm going through the exact same problem right now! But this happened to me using Heimdall. My phone is still recognized by Heimdall but when I try to reflash it I get this in the command prompt:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DD F\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\mod em.bin]
and this in the Heimdall window:
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: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
i am too stupid
Ok, i am probably just way too stupid, but i can't find the download for heimdall one-click.
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
de4dw0lf said:
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
Click to expand...
Click to collapse
Did you download java?
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
DarsOnMars said:
I'm going through the exact same problem right now! But this happened to me using Heimdall.
Click to expand...
Click to collapse
You may have a bad download. You might try redownloading the file.
java is installed, i might have fixed that problem though. i think my download wasn't quite finished, because when i updated java, it wanted me to close firefox..
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
de4dw0lf said:
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
Click to expand...
Click to collapse
Here is my recommendation...
First used the attached .zip (assuming you are on a 64 bit machine) and uninstall all samsung and android drivers.
Then start over with Heimdall One Click. It will tell you whether you have the drivers you need or not, and if you do not, it will put up directions, send you to zadig and tell you what you need to do.
And you are in download mode.
Heimdall uses different drivers then ODIN.
Go here then and download 32 bit USBDeView.
I recommend restarting your machine after uninstalling drivers.
im on 32 bit
de4dw0lf said:
im on 32 bit
Click to expand...
Click to collapse
By the way... I recommended downloading the bootloader one click in case whatever you previously flashed was not for our device and changed your bootloaders.
"java -jar T959V-UVKJ6-One-Click.jar" --> is not the bootloader download.
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar = bootloader download.
hmm.. so it tells me to select Samsung USB Composite device, but it's not there.. :/
i am downloading the one "Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders" right now.
And after i am done im gonna restart my computer.
Message for Verizon: http://i.imgur.com/2Cmoq.jpg
Important information:
- If you get to a point where you don't want to go any further, or things don't work, you can always flash the stock rom (extract the .tar.md5 from the zip) using Odin in your bootloader. Get that here: http://forum.xda-developers.com/showthread.php?t=1755386
- Do not attempt this hack if you've disabled apps. Re-enable them first or use the stock ruu from above before attempting this. (You'll save yourself a bunch of time)
First off, you'll need some files. This basically flashes a custom system.img.ext4 which has your su binary. You then boot up and flash cwm or twrp
1. USB Drivers: http://tinyw.in/Fdoz
2. Odin: http://samsung-updates.com/Odin307.zip
3. One Rooted system.img tarball:
Root66: A more proper rooted image than what I originally had to work with. http://forum.xda-developers.com/showthread.php?t=1762204
OR
Stripped down (unzip first), more details here on what this one is: http://forum.xda-developers.com/showthread.php?t=1759642
-----http://goo.im/devs/invisiblek/i535/stripped.rooted.system.img.tar.md5.zip (unzip this before trying to flash with odin)
OR
Stock: (although it does seem to have some sprint stuff for some reason)
-----http://goo.im/devs/invisiblek/i535/rooted.system.img.tar.zip (unzip this before trying to flash with odin)
-----mirror: http://tinyurl.com/tytillithz thanks tillithz!!
4. Recovery image:
CWM Recovery 6.0.1.0: http://goo.im/devs/invisiblek/i535/recoveries/cwm-6.0.1.0-d2vzw.zip (unzip the recovery.img out)
Ok, lets get started....
1. Boot into Odin mode on the phone. Do this by powering off and then holding vol down, home and power to power on. Then press vol up to accept the disclaimer. Plug into your computer.
2. Fire up Odin (Heimdeil may work in linux, haven't tested) choose the PDA section and browse to wherever you downloaded rooted.system.img.tar then click flash. This takes awhile, be patient. Took me around 8 minutes to flash this.
3. It will auto reboot. It should boot up and thing should act mostly normal except that you'll be able to adb in and use su to take root
If you don't want a custom recovery, you may stop here. You are rooted.
Continuing on to get custom recovery on your device...
4. You'll need adb installed and working for this. If you don't know how, this isn't the thread for that. Open a command prompt and follow these commands:
<cd to the directory with the files you downloaded earlier>
(if you downloaded twrp8.img, use that instead of recovery.img in the commands)
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
reboot recovery
5. Profit
EXTRA CREDIT: Hate the VZW boot logo and audio as much as I do? Flash this in CWM: http://www.mediafire.com/?m6urrypvx2c156p
Its a stock Samsung Boot animation (pulled from Blazer ROM)
You are welcome to join me in #verizons3 on irc.freenode.net for help
enjoy
Thanks to many people...
Epic 4g Touch Team
Samsung-Updates.com
rizdroid for this: http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1 which i loosely followed to build our rooted system.img
Many others for bits an pieces for this whole thing
FAQ:
Q: It's not working!!! Keeps failing!!!
A: Try again. Turn the phone off (battery pull) and boot into download mode again
Q: Odin doesn't seem to be doing anything!
A: Be patient, it can take awhile sometimes. I've also noticed if you try to flash something, and leave the phone plugged in and try to flash something else it won't work. Unplug, then replug, then try flashing again
Q: Does this trip the flash counter?
A: No
Q: Can we flash custom kernels?
A: Not properly at this time. If we flash to our boot partition, we'll end up with this: http://i.imgur.com/Ci0gY.png We can still recover from this by booting into odin mode and flashing the stock boot.img, found here: http://goo.im/devs/invisiblek/i535/stock.kernel.tar
Awesome work SOOO glad you got this lol
Is This For Real?!?!?!
Yeah buddy ..all I need now is my damn device ..
Sent from my Galaxy Nexus using Tapatalk 2
Ker~Man said:
Is This For Real?!?!?!
Click to expand...
Click to collapse
Very real, the man is a genius!
Bracing for epic.
#f***verizon
Doing This **** RIGHT Now! Got Out Of Bed Because I Literally Couldn't Stop Thinking About How Bad These VZW SGS3 Problems SUCKED, And Within 15 Minutes Here Comes THIS! Yeah Boyyy!!!
can anyone confirm this working? if not im leaving verizon
The large system.img upload isn't finished uploading yet. Fingers crossed, nonetheless. I'm banging the "refresh" button on this page every 10 seconds or so!
Nice work, will try soon as I get my device!! Stick this in your corn verizon!!!
This is fantastic news!
Sent from my Galaxy Nexus
mmmmmm <3
This is brilliant. I can't wait to get my phone now. Hopefully the BL is next.
As somebody that has made it his new goal to do everything Verizon doesn't want me to do for the next two years, I greatly appreciate this. :silly:
I plan on downloading it with my tethered Verizon Android phone. As a thank you to Verizon
K
Does this trip the flash counter? From what I can surmise from other S3 root methods, the system image root method doesn't trip the counter. Is that true for this as well?
Kev13Dd said:
I plan on downloading it with my tethered Verizon Android phone. As a thank you to Verizon
K
Click to expand...
Click to collapse
Lmao, made my night.
akanealw said:
Does this trip the flash counter? From what I can surmise from other S3 root methods, the system image root method doesn't trip the counter. Is that true for this as well?
Click to expand...
Click to collapse
invisiblek just updated the OP- this will NOT trip the flash counter
K
Well this might be difficult to download, it stops downloading randomly and my download speed just continues to drop and then eventually stops completely
Neverendingxsin said:
Well this might be difficult to download, it stops downloading randomly and my download speed just continues to drop and then eventually stops completely
Click to expand...
Click to collapse
i'll throw up a torrent...
give me a couple minutes...
For Those Who Haven't Been Able To Try This Yet, I Have One Word That Says It All -- FLAWLESS! Already Got Exactly What Is Described In OP - Root AND CWM - And It Just Works - PERIOD! Excellent, Excellent Job My Friend! Giving The "Thanks" A Little Tappy-Tap Right Now!~
Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
stedmakr said:
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
Click to expand...
Click to collapse
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Gatsrom said:
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Click to expand...
Click to collapse
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
stedmakr said:
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
Click to expand...
Click to collapse
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right? https://goo.im/devs/OpenRecovery/v1awifi/openrecovery-twrp-2.8.0.0-v1awifi.img.tar
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Gatsrom said:
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right?
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Click to expand...
Click to collapse
Gatstrom, I believe yes to all of the above. I attached a file that shows the Odin screen (didn't take - screen readout below). The successful line says (succeed 1 /0 failed) The recovery file is correct. Odin 3.09 does not say Note pro. I have also tried Odin 3.09 from a different source with the same result. The other thing I can think of is after flashing and I take the usb cord from the phone my steps are to turn off the phone and turn it on to recovery with the three finger steps. Is their anything else I need to do at this point. Should I be in TWRP now? I find myself in stock recovery system and it gives me I think 5 options. I am just rebooting. Should I be using one of the other options.
I unzipped Odin with 7z. I am using an original samsung USB cable connected directly to the computer and I turned off antivirus before flashing. There is no indication that Kies is operating any services in the background. I also downloaded he latest drivers
Pass
02:02
Auto reboot and f.reset time checked
From message block
added
recovery.img
Nand Write Start!
RQT_CLOSE !!
RES OK!!
Removed!!
Remain Port.... 0
All threads completed. (Succeed 1 / failed 0)
Binary size 8.2mb
Thanks,
Keith
I got it to work. On the TWRP thread at original development forum on page 48 or 49 there was someone with the exact same problem. Bigbiff told the user to uncheck auto reboot in odin and then to boot directly into recovery. I did and it worked. I was unaware that you could root directly from TWRP and a quick stop at the play store. I then loaded your debloated rom and I'll see how it goes once everything updates.
I am so F$%^King excited. I have spent scores of hours attempting to get this to work.
Thanks for all of your help (it helped)
Keith
Ya that was my next suggestion to not reboot and go into twrp directly. Let me know how the rom works. If you have any questions/bugs throw them in the rom thread. I'll see it quicker and it keeps problems and solutions centralized.
I would say give the xposed framework a shot. I put a list of the ones I use. They are incredibly useful.
I am using the latest stable nightly build for me, the one released in 04-04 of the LineageOS.
The build is working fine, however, I need to go back to stock firmware.
Last time I tried to do it using newest Odin, I was on latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
Bricked up to the point where a restore using Samsung Switch was the only apparent solution. So I went for it. I have to say it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed me to go into install mode. The installation started anf seemed to be doing fine, but sadly the process has failed at 67%.
I'm afraid that the same thing could happen again.
Could you please help me out?
Thanks.
use Odin
Sent from my SM-G930F using Tapatalk
bustyouup4free said:
use Odin
Click to expand...
Click to collapse
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
hemp_invader said:
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
Click to expand...
Click to collapse
First - Wrong section, this is development not help, https://forum.xda-developers.com/galaxy-s7/help
Second maybe your download is corrupted, or the wrong model, in odin double check sections you know csc, modem, bootloader, and ap, check your drivers and usb cable
Check Your usb cable, don't use an usb hubs, also check is your battery is good
Give log from odin