So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
mewrius said:
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
Click to expand...
Click to collapse
Did you installed the drivers while you were in download mode? Maybe this would solve your actual issues. Also if you used a different port, you need to reinstall the drivers once again AFAIK.
Recently I have tried to root my Samsung Galaxy 3 7.0 (SM-T210R) WiFi edition. After unsuccessfully attempting to install a custom rom, I believe I have accidentally deleted the stock rom for the device..So now, whenever I turn the device on, it automatically brings me to CWM recovery. I have tried to install a different rom onto the device unsucessfully, giving me an error saying "format() expects 5 args, got 4" It also says (Status 7). I have also tried to connect my device to my computer and hook it up to Odin, but Odin does not recognize the device. If anybody is able to resolve my issue I would greatly appreciate it.
josephdiniso said:
Recently I have tried to root my Samsung Galaxy 3 7.0 (SM-T210R) WiFi edition. After unsuccessfully attempting to install a custom rom, I believe I have accidentally deleted the stock rom for the device..So now, whenever I turn the device on, it automatically brings me to CWM recovery. I have tried to install a different rom onto the device unsucessfully, giving me an error saying "format() expects 5 args, got 4" It also says (Status 7). I have also tried to connect my device to my computer and hook it up to Odin, but Odin does not recognize the device. If anybody is able to resolve my issue I would greatly appreciate it.
Click to expand...
Click to collapse
you have bricked your galaxy tab..
try to flash stock firmware using ODIN or use oneclick unbrick tool
Vaibhav Chauhan said:
you have bricked your galaxy tab..
try to flash stock firmware using ODIN or use oneclick unbrick tool
Click to expand...
Click to collapse
I can not do either of those methods, because my computer no longer recognizes this device when I plug it in.
josephdiniso said:
I can not do either of those methods, because my computer no longer recognizes this device when I plug it in.
Click to expand...
Click to collapse
make sure you have installed device drivers correctly
&
try this thread
http://forum.xda-developers.com/showthread.php?t=2366951
i think you have same problem as in this thread
Hey guys, im newb, so excuse me while i ask for help---
So a few weeks back, i was at whatever update verizon pushed out. (not 5.1)
i decided it was a year of no updates and used your guys' guides to get me into 5.0.2... well........ VZW pushed out 5.1.1 and i'd really like to get the most updated version i can---
with that being said, im trying to roll back to 4.4.4 so i can get the verizon push update because i cant get it with my leaked lollipop version.
when i try to flash back to 4..4.4, i get the errors
"16/036/2016 10:36:40 - ERROR - Error flashing. Aborted
16/036/2016 10:36:41 - ERROR - Drivers need to be installed for connected device.
16/036/2016 10:36:41 - ERROR - You can find them in the drivers folder of Flashtool"
first it makes me choose which to identify my device as, as soon as i open flashtool- ive tried closing it, and choosing z3, with no luck- same errors.....
i go to reset my phone, get the "Upgrading, do not disconnect" screen- but then it cant read the drivers?
thats where i'm at.
giga save me
I went through the same thing last night. I google the drivers for it and then installed them and restarted the phone and made sure it was in flash mode. Once i installed the drivers for the phone manually i was able to flash the 4.4.4 and then i just got the update today and going to try and root the phone now so i can start to use it again. thanks
oh here are the drivers that i used to get mine to work. thanks
www.gizmobolt.com/2014/02/11/downlo...pack-v1-3-windows-drivers-xperia-smartphones/
I got the update all installed and now I have to figure out how to replace KingRoot with supers. But did the driver's works for you. Thanks.
Hello, I need help, I own a Samsung galaxy s8 and I tried to root it, I failed and ****ed up hard :'(
I tried to flash it following multiple tuto and it failed, I had the issue :
sw rev check fail bootloader device 3 binary 2
but now, my phone has a blue screen with :
an error has occurred while updating the device software.
Use the emergency recovery function in the smart switch PC software
The smart switch pc software doesn't recognize my phone.
Please help me i'm out of option :'(
Hi , try to put your phone into Download mode , and use latest Odin version in order to re-flash the latest stock version of OS if you are note sure which one is , just send me 7 and 8 number from imei ...
Thank you for your answer, I managed to fix my phone by flashing the latest firmware. I was downloading it from a website and it turns out it wasn't the last one.
After I looked on different site, I went on sammobile and I downloaded the latest version, It took me one entire day, the download speed was slow AF and my internet connection crashed in the middle of it.
I had to ask a friend to download it at his place and then, bring it to me.
I'm really happy, I managed to fix it.
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!