Related
I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway
would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"
Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.
some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now
THIS WILL WORK ONLY IF YOU CAN GET INTO DOWNLOAD MODE (Odin mode) if you bricked your bootloader try HERE
Who can benefit from this?
Anyone who took the OTA to 4.3 then tried to downgrade resulting in a soft brick
Anyone who took the OTA to 4.3 and somehow lost there recovery or follow restoring stock recovery instructions HERE
Anyone who took the OTA to 4.3 but failed with access to download mode
Anyone who wants 4.3 but for some reason can not OTA
Anyone who took the NC1 update (new 4.3) and wants to revert to ML1 (old 4.3 with saferoot and safestrap support)
Linux and Mac users must follow the Odin method using the correct PIT file (found at the bottom of the op) and substitue Odin with Jodin3 found HERE and spam AdamOutler thanks button for making Jodin3
WARNING! UPDATING TO 4.3 WILL RESULT IN A LOCKED BOOTLOADER FOREVER!!
4.3 with Odin
How to enter Download Mode
Make sure your device is completely off
Hold Volume Down + Home
While holding both of them simultaneously press the Power button until you see the disclaimer on the screen
Then let go of all the buttons and press Volume Up
=====================================================================================
Download and extract Odin <--- New link 1/23/14
Download and extract ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5.7z (official old 4.3 tar ball) or ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low_ship.tar.md5.7z (official new 4.3 tar ball)
Download kies and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Windows Kies Here
Mac Kies Here
Enter Download Mode
Make sure Kies is closed then plug in your phone and wait for drivers to install
Open Odin As administrator
You should see your phone under ID:COM (you should also see it has been added in message)
Make sure only Auto Reboot and F. Reset Time is checked
Check PDA [ ]
Click on [PDA] And select the .tar file you just extracted (Only use PDA Never use the others)
Wait for it to verify the MD5 then click [Start]
From here on out its all automated Odin will Flash SCH-I535_I535VRUCML1 then restart (dont forget first boot takes time)
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
4.3 With Verizon Utility [will always push the most recent firmware atm 4.4.2 and you will not be able to go back to 4.3] (Windows only for now)
How to enter Download Mode
Make sure your device is completely off
Hold Volume Down + Home
While holding both of them simultaneously press the Power button until you see the disclaimer on the screen
Then let go of all the buttons and press Volume Up
=====================================================================================
Download and unzip
Windows SUA_ar.zip <--- New Link
Mac SUA_ar.zip
Open SUA_ar folder
Install SUABnRSetup as administrator (might take some time and may not be nessesary)
Download kies and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Windows Kies Here
Mac Kies Here
Make sure Kies is closed then go into download mode and plug into your pc (hold here until drivers install)
Run SUA.exe as administrator
Click on [Repair Assistant] (on the left)
Click on run [Repair Assistant] (on the bottom)
After repair assistant recognizes your phone click [Repair Galaxy S(R) III] (on the right side)
It will say "Due to the condition of your phone/tablet, all data will need to be erased during the repair."
Click [continue]
From here on out its all automated it will download and install SCH-I535_I535VRUCML1 then restart (dont forget first boot takes time)
If you get stuck at 84% try THIS
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
If you keep failing it might be because you have bad partitions. Download the pit file that matches your phone (16gb S3 use the 16gb pit file or 32gb S3 use the 32gb pit file) Follow the Odin instructions with the addition of your pit file By clicking [PIT] in Odin. Or try this fix Here
SCH-I535_D2VZW_16gb.pit
====================
SCH-I535_D2VZW_32gb.pit
As long as things went smooth you should be back on 4.3 ready to take on the world!
Want root on 4.3? Use saferoot (ML1) HERE or towelroot (ML1/NC1) HERE Remember you are on a locked bootloader. You can not flash insecure bootloader, roms or custom recovery.
awesome. I had given up and was just waiting for the 4.3 tar
I'm really hoping this works since you had the exact same symptoms as me
Thanks in advance!
kangeon said:
awesome. I had given up and was just waiting for the 4.3 tar
I'm really hoping this works since you had the exact same symptoms as me
Thanks in advance!
Click to expand...
Click to collapse
I was waiting as well, But I was about to chuck my Droid x against a wall. Another funny thing is right before I tried this my phone got sudden death syndrome (power button stayed compressed so every time battery is put in it automatically tuns on then off ). Luckily slamming my phone against the table wasn't a internet troll and it got fixed.
ThePagel said:
I was waiting as well, But I was about to chuck my Droid x against a wall. Another funny thing is right before I tried this my phone got sudden death syndrome (power button stayed compressed so every time battery is put in it automatically tuns on then off ). Luckily slamming my phone against the table wasn't a internet troll and it got fixed.
Click to expand...
Click to collapse
Bro I hate my Droid X. I sent my phone out today to have it JTAG to 4.3 and hours later this came out LOL. Good job bro!!!!:good:
I got it working
Thanks so much!
You are a life saver. Thank you!
Good to see that some folks can resurrect their device now. A locked but working phone is certainly better than no phone at all.
Awesome work ThePagel!
Sent from my SCH-I535 using Tapatalk
I signed up just to say thank you. I decided to go for broke and take my phone into Verizon just to see what they said and they suggested I upgrade to a new phone. I'm sure they could have performed this for me, but I'm glad I did it myself. Once again, thank you.
Couple things, when you redo the OP could you make sure to detail what scenario would lead you to using this tool? Maybe make that a little clearer.
Also, we don't have a bootloader to boot directly into like say HTC devices. Samsung let's you boot into recovery or download mode. Download Mode may be an equivalent term to "bootloader" for other devices but it may be confusing to new S3 users down the road. Cheers!
Sent from my SCH-I535 using Tapatalk 4
@ThePagel I PMd you. I will go ahead and post a mirror for the SUA_ar.zip here. You can move this link to the OP. Once everyone wakes up they are gonna shut down your dropbox for excessive traffic.
http://www.androidfilehost.com/?fid=23269279319199403
Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!" moment)
s'pht said:
Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!" moment)
Click to expand...
Click to collapse
Kies should handle that. Not sure but as never used Kies but you should not need that other file. Just repair in Kies.
Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.
harrst1 said:
Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.
Click to expand...
Click to collapse
It seems this method will restore the phone to the factory state thus should repair your recovery also.
SlimSnoopOS said:
Couple things, when you redo the OP could you make sure to detail what scenario would lead you to using this tool? Maybe make that a little clearer.
Also, we don't have a bootloader to boot directly into like say HTC devices. Samsung let's you boot into recovery or download mode. Download Mode may be an equivalent term to "bootloader" for other devices but it may be confusing to new S3 users down the road. Cheers!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I can manage that
prdog1 said:
@ThePagel I PMd you. I will go ahead and post a mirror for the SUA_ar.zip here. You can move this link to the OP. Once everyone wakes up they are gonna shut down your dropbox for excessive traffic.
http://www.androidfilehost.com/?fid=23269279319199403
Click to expand...
Click to collapse
Thankyou!
s'pht said:
Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!"
Click to expand...
Click to collapse
Yes
prdog1 said:
Kies should handle that. Not sure but as never used Kies but you should not need that other file. Just repair in Kies.
Click to expand...
Click to collapse
Because he is on 4.3 kies is no help. Its still giving us 4.1.2
harrst1 said:
Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.
Click to expand...
Click to collapse
Yes this will work just remember you run the risk of a hard brick if things go wrong
ThePagel said:
I think I can manage that
Thankyou!
Yes
Because he is on 4.3 kies is no help. Its still giving us 4.1.2
Yes this will work just remember you run the risk of a hard brick if things go wrong
Click to expand...
Click to collapse
Ok. I see now. You are just using the drivers from Kies.
Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!
eudoxia said:
Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!
Click to expand...
Click to collapse
A lot of original S3s came with that lock. Don't know if we ever figured out why.
eudoxia said:
Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!
Click to expand...
Click to collapse
prdog1 said:
A lot of original S3s came with that lock. Don't know if we ever figured out why.
Click to expand...
Click to collapse
That is weird. Mine did not ship with custom but after the brick it did have it, then after the unbrick it was gone. Is your warranty in download mode 0 or 1?
prdog1 said:
A lot of original S3s came with that lock. Don't know if we ever figured out why.
Click to expand...
Click to collapse
I stand corrected, after pulling the battery for a minute and rebooting the "Custom Lock" screen is gone..
Thanks ...You Rule :good:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Thanks Justin! Works great. Someone should sticky this.
Luckily I had a Windows computer I could use for this, but my main machine is a MacBook Pro. I wish someone would do a nice clear walkthrough like this one for using Heimdall on a Mac.
To start I have rooted many phones but am stumped on this tablet. After getting it to start with holding the volume down and power key it stops on the downloading screen. Once I can get it to reboot I held the volume up and power key and got into system recovery. If I am not mistaken I can boot from here also. Right??
Thanks it was very useful!
Will this trigger the Knox 0x1 problem? I just got this tablet and I want to be able to take it in to Sprint for repairs if I need to.
Thanks!!!
Justin Buser said:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Click to expand...
Click to collapse
Thanks for the help! This is my first root I've done myself and it works like a charm. Now my next step is to flash it to any carrier. Does anyone know how to flash the sprint device to a different carrier? If anyone could help me out, that would be greatly appreciated.
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
colt223 said:
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
Click to expand...
Click to collapse
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
slickdealers said:
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
Click to expand...
Click to collapse
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
colt223 said:
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
Click to expand...
Click to collapse
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
slickdealers said:
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
Click to expand...
Click to collapse
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Just tried it and successfully rooted! I got the same message that you described about Knox. It appears when you go to update SuperSu. Thank you for the help!
For anyone else wondering about going back to stock, I found a thread to the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2512172
I found the answer in another thread. Flashing TWRP will trip Knox.
Didn't work for me
I did the TWRP stuff and all it did was trigger that warranty bit. Still no root.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Yeah, same story here. After flashing TWRP then installing SuperSU first via the TWRP option by booting directly to recovery before OS after flashing TWRP through odin.....then once I clicked the SuperSU app after the OS loaded I chose first the "play" option to update SuperSU then the TWRP option to install the binary update. When it next booted it informed me that Knox was installed and asked whether to disable or not..I said yes and haven't had any problems at all...just trying to find a good ROM now^^
awesome thanxs for the info..... now if we could only get cm11 on this puppy
Root Failure, odd case
I have twins - they are both, identically:
Software Version: T217VPUAMH9
Hardware Version: T217S.04
Model Number: SM-T217S
Android Version: 4.2.2
Baseband Version: T217SVPUAMH9
Kernel Version: 3.4.0-1458241
Build Number: JDQ39.T217SVPUAMH9
Jim Trotter III-style, I-DENTICAL!
I successfully rooted one with:
1: Enable debugging
2: Boot into Download Mode (from poweroff, hold Vol Down+Power)
3: terminal: sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
4: poweroff ; boot to TWRP. From TWRP, wipe [factory reset], then install: ./root/SuperSU-v1.93.zip
With the second (apparently evil) twin, at the heimdall command, I get:
...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
On the device, the blue progress bar grows to about 2% and stops.
I even tried using a different cable in case one had gone wonky, to no avail.
I am at a total loss here.
... and SUCCEED, but via strangeways
...
So, mounting frustration.
I tried instead a slightly different version of TWRP:
$ sudo heimdall flash --RECOVERY recovery/T217S.TWRP.2.7.0.0.recovery/recovery.tar.md5
This time the result is different, but still no success:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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%
... but it stuck at 100% and did not continue. Device also stuck.
^C, hard reboot of device.
Tried again to double check, same result - sticks at 100%, progress bar on device sticks at somewhere around 5%.
Aware of the possible futility, but bored, I tried first one again:
$ sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
SUCCEED.
So, apparently it has to be "knocked loose"?
Dunno. I'm in. Hope this helps someone else.
Root NB8
This won't work with NB8 EDIT: I was wrong this does work on NB8
Apparently had to reinstall the drivers a few times to get it to take on Windows. Still no clue what the issue was with Heimdall.
Here is the sequence of events:
Galaxy tab 2 10.1 with factory rom (wife's tablet)
Wife tells me that she keeps trying to complete the update everytime she gets prompted, but it always fails
Wife also tells me that she can't power off the tablet (she presses the power button, it shuts down, but then it starts up again)
I try the upgrade, get same result as wife
I try to reset the rom: I download what I think is the correct file, download Odin 1.85, and run it.
put tablet into download mode, attempt to use Odin to load new rom ***note, this is probably where I screwed up, as I am not sure i used the correct file. This is the file I used: PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar, which I found in a search on xda forums for my problem.
Odin reported failure. I tried again, same result.
I tried using KIES, using the Firmware upgrade and intitialisation (note that I must have UK version of KIEs, based on the spelling of initialisation--maybe that's a problem??/). I put in the model number, then the serial number if the tablet, get a message that GT-P5113 does not support initializing
tablet displays the message: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I try to put tablet back into download mode, but that doesn't work. Any suggestions on what to do at this point? Appreciate a step-by-step solution, if possible.
Thanks!
kevinkohut said:
Here is the sequence of events:
Galaxy tab 2 10.1 with factory rom (wife's tablet)
Wife tells me that she keeps trying to complete the update everytime she gets prompted, but it always fails
Wife also tells me that she can't power off the tablet (she presses the power button, it shuts down, but then it starts up again)
I try the upgrade, get same result as wife
I try to reset the rom: I download what I think is the correct file, download Odin 1.85, and run it.
put tablet into download mode, attempt to use Odin to load new rom ***note, this is probably where I screwed up, as I am not sure i used the correct file. This is the file I used: PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar, which I found in a search on xda forums for my problem.
Odin reported failure. I tried again, same result.
I tried using KIES, using the Firmware upgrade and intitialisation (note that I must have UK version of KIEs, based on the spelling of initialisation--maybe that's a problem??/). I put in the model number, then the serial number if the tablet, get a message that GT-P5113 does not support initializing
tablet displays the message: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I try to put tablet back into download mode, but that doesn't work. Any suggestions on what to do at this point? Appreciate a step-by-step solution, if possible.
Thanks!
Click to expand...
Click to collapse
Seems you flashed a wrong file.
Download another rom from http://live.samsung-updates.com/
and reflash with odin
Last week i tried to update my tab from 4.1.2 to 4.2.2 it hangup while flashing. Had to reset but then end up with firmware upgrade encountered blablabla. I just reflash within the blind screen without download mode and got it to work again
But don't I need to get the tablet into download mode first?
Rosli59564 said:
Seems you flashed a wrong file.
Download another rom from <<url.....>>
and reflash with odin
Click to expand...
Click to collapse
That makes sense, but how do I get the correct file to the tablet if I can't get the tablet into download mode?
kevinkohut said:
That makes sense, but how do I get the correct file to the tablet if I can't get the tablet into download mode?
Click to expand...
Click to collapse
If it's really a gt-p5113 then find the 1 for your country. If you're not sure your region code/csc then just download for any region.
You will know what i'm talking about if take a look at the given link
Please look at item 10 on my list
Rosli59564 said:
If it's really a gt-p5113 then find the 1 for your country. If you're not sure your region code/csc then just download for any region.
You will know what i'm talking about if take a look at the given link
Click to expand...
Click to collapse
I can't load ANY file to the tablet, as I CANNOT GET IT INTO DOWNLOAD MODE. I need to know how to force the tablet into download mode. Pressing POWER and VOLUME DOWN does not work. NOTHING HAPPENS.
Connect to PC on the screen "firmware upgrade encountered blablabl" Downloadmode on in Background, Odin can get access
If you are working with Odin, please kil ALL Samsung and KIES Programs and Services running in Background.
Hi for go to download mode you have to press power and volume up buttons
Sent from my GT-P5113 using XDA Premium 4 mobile app
Android-Andi said:
Connect to PC on the screen "firmware upgrade encountered blablabl" Downloadmode on in Background, Odin can get access
If you are working with Odin, please kil ALL Samsung and KIES Programs and Services running in Background.
Click to expand...
Click to collapse
I have tried this many times and Odin just fails. TWRP, CWM, Phil's touch all tried and failed. I have tried so many ROMs not sure I could list 'em all. Wanted to try SlimKat. But have this same problem, can't find the handle now, I only get the firmware upgrade encountered blah, blah. I'm just about ready to make confetti out of it! Can I get assistance with this problem, please. I don't care what ROM I have to run, I just need it to work...
Any solution to your problem?
Pp.
PanchoPlanet said:
Any solution to your problem?
Pp.
Click to expand...
Click to collapse
None as yet, I'm running out of real estate to search...
The rom you used in your op was probably for a data tab like sprint, att, Verizon, that is usually a brick result.
If you could factory reset you may have a chance but I doubt it without recovery or download mode.
Pp
You are faceing the "black screen of death" ("Firmware upgrade encountered an issue....").
Uninstall kies and reboot your pc.
Start odin.
Connect the tab running the black screen of death (BSOD).
Download mode running in background of BSOD so odin will detect your device.
Flash the correct firmware now and pray flashing the at&t rom didn't caused a hardbrick.
Send from OnePlus One using Tapatalk
Correct rom
I think that is exactly my problem. Last night I got Odin to run all the way through, it said pass but still no soap. I'm just about to list it for parts and at least minimize my loss.
Hi, I have a Verizon Samsung Note 5. I have attempted to flash every stock rom available for this device. I continues to stay in bootloop. If i try to boot into recovery mode, it just goes into the bootloop anyways. I am at a loss of what to do. I cant use adb on Windows due to the bootloop. This is the first time I have ever posted because I can usually find my solution from other peoples misfortunes. I have tried the following stock roms where most roms passed, and a few failed. I have also tried the ones that failed with multiple versions of Odin. I can access the download mode with no issues. I can also access the Maintence Boot menu from the download mode. Everything I have read says I need to wipe system cache and the odin install would work correctly. Any help would be fantastic. Also, I do not know what build number my phone is since I cant access.
N920VVRU3CQB9 7.0 (Nougat) 04/12/2017 (details)
N920VVRS3BQA1 6.0.1 (Marshmallow) 01/31/2017 (details)
N920VVRS3BPL4 6.0.1 (Marshmallow) 12/28/2016 (details)
N920VVRU3BPJ3 6.0.1 (Marshmallow) 12/02/2016 (details)
N920VVRS3BPI1 6.0.1 (Marshmallow) 09/27/2016 (details)
N920VVRU2BPG5 6.0.1 (Marshmallow) 09/07/2016 (details)
N920VVRS2BPF4 6.0.1 (Marshmallow) 07/19/2016 (details)
N920VVRS2BPF2 6.0.1 (Marshmallow) 06/18/2016 (details)
N920VVRU2BPD4 6.0.1 (Marshmallow) 05/10/2016 (details)
N920VVRU2BPC2 6.0.1 (Marshmallow) 03/4/2016 (details)
N920VVRU2AOJ3 5.1.1 (Lollipop) 12/15/2015 (details)
N920VVRU2AOJ2 5.1.1 (Lollipop) 10/20/2015 (details)
N920VVRU1AOGJ 5.1.1 (Lollipop) 09/25/2015 (details)
What does Odin say after a flash? Pass or Fail? Maybe your PIT file got messed up? Normally you don't want to mess with the PIT but you might need to try something with that. I've never messed with them so you'll need someone else to help you with that. Was this phone ever booting okay ? If this only happened after you flashed something there should be a way to get back to a bootable phone. Did you unlock the OEM lock before flashing - I think that is important (in the developers options) or you may get into a bootloop. If it's on a VZ service plan you could take it back and they might fix it with a box for flashing at a level you can't normally do with Odin on a usb cable. Just don't admit you were flashing anything
droidzer1 said:
What does Odin say after a flash? Pass or Fail? Maybe your PIT file got messed up? Normally you don't want to mess with the PIT but you might need to try something with that. I've never messed with them so you'll need someone else to help you with that. Was this phone ever booting okay ? If this only happened after you flashed something there should be a way to get back to a bootable phone. Did you unlock the OEM lock before flashing - I think that is important (in the developers options) or you may get into a bootloop. If it's on a VZ service plan you could take it back and they might fix it with a box for flashing at a level you can't normally do with Odin on a usb cable. Just don't admit you were flashing anything
Click to expand...
Click to collapse
I have tried the pit file with each as well. Ive tried them all with and all without. It is not on a Verizon plan. I purchased it from someone to use, they said the battery died during an update. I believe they may have told me a lie, because it shows custom on the bootloop screen.
Apd833 said:
I have tried the pit file with each as well. Ive tried them all with and all without. It is not on a Verizon plan. I purchased it from someone to use, they said the battery died during an update. I believe they may have told me a lie, because it shows custom on the bootloop screen.
Click to expand...
Click to collapse
That can be bad having an update during a low battery. Yes they may have bricked it doing something wrong flashing a wrong file. You might want to try flashing the Oscar kernel and look through this message thread for help: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593 Dealing with the Verizon version of the Note 4 is a real pain but I managed to get root following the above link thanks to Tripper511's detailed instructions for this phone. Check his troubleshooting guide also.
Apd833 said:
I have tried the pit file with each as well. Ive tried them all with and all without. It is not on a Verizon plan. I purchased it from someone to use, they said the battery died during an update. I believe they may have told me a lie, because it shows custom on the bootloop screen.
Click to expand...
Click to collapse
When you boot into download mode, what does it say next to "PRODUCT NAME"?
Also can you get into recovery using the power, volume and home buttons? If so can you tell me what it says right underneath "Android System Recovery"?
MrMike2182 said:
When you boot into download mode, what does it say next to "PRODUCT NAME"?
Also can you get into recovery using the power, volume and home buttons? If so can you tell me what it says right underneath "Android System Recovery"?
Click to expand...
Click to collapse
Actually this was a very helpful suggestion by MrMike2182 when my Note 5 was stuck in a bootloop one time: do a factory reset right after it's done flashing. Stop Odin from auto rebooting the phone and after the flash hold the volume down and power button at the same time until the screen turns off and when it comes back on just select factory reset and let it finish. But since Mike's here if that doesn't work he may have some other good suggestions :good:
droidzer1 said:
Actually this was a very helpful suggestion by MrMike2182 when my Note 5 was stuck in a bootloop one time: do a factory reset right after it's done flashing. Stop Odin from auto rebooting the phone and after the flash hold the volume down and power button at the same time until the screen turns off and when it comes back on just select factory reset and let it finish. But since Mike's here if that doesn't work he may have some other good suggestions :good:
Click to expand...
Click to collapse
I tried those exact steps too actually. I found that solution on another thread. Still nothing.
MrMike2182 said:
When you boot into download mode, what does it say next to "PRODUCT NAME"?
Also can you get into recovery using the power, volume and home buttons? If so can you tell me what it says right underneath "Android System Recovery"?
Click to expand...
Click to collapse
I can't get to recovery in anyway at all.
Odin Mode
Download speed: fast
Product name: SM-N920V
Current binary: samsung official
System status: custom
FRP Lock: On
Secure download: enabled
RP SWREV: B:3 K:0 S:1
Apd833 said:
I can't get to recovery in anyway at all.
Odin Mode
Download speed: fast
Product name: SM-N920V
Current binary: samsung official
System status: custom
FRP Lock: On
Secure download: enabled
RP SWREV: B:3 K:0 S:1
Click to expand...
Click to collapse
I suspect the FRP Lock could be some of my issue.
Apd833 said:
I suspect the FRP Lock could be some of my issue.
Click to expand...
Click to collapse
RP SWREV: B:3 K:0 S:1 You're on bootloader 3 and the knox is not tripped on the phone.. What I would suggest you do is flash this firmware version N920VVRS3BPI1 from my Android File Host and before connecting the phone to odin open the settings and disable the auto reboot option and then connect the phone and flash it and after odin displays PASS then disconnect the phone and immediately press and hold the volume down button, the home button and the power button at the same exact time and when the screen turns on select factory reset and let it finish doing that but do not let odin reboot the phone!
And if FRP Lock is on meaning OEM unlock is disabled then you'll need to use one of the adb root only kernels in order to get the FRP reset.
MrMike2182 said:
RP SWREV: B:3 K:0 S:1 You're on bootloader 3 and the knox is not tripped on the phone.. What I would suggest you do is flash this firmware version N920VVRS3BPI1 from my Android File Host and before connecting the phone to odin open the settings and disable the auto reboot option and then connect the phone and flash it and after odin displays PASS then disconnect the phone and immediately press and hold the volume down button, the home button and the power button at the same exact time and when the screen turns on select factory reset and let it finish doing that but do not let odin reboot the phone!
Click to expand...
Click to collapse
I did that firmware version, but it didn't work. I did the exact steps you just stated. I will attempt it again and see if I can get something out of it. I read that Odin v 3.10.6 worked best for the note 5, is this true or does it matter? I have most of them. Haha
Apd833 said:
I did that firmware version, but it didn't work. I did the exact steps you just stated. I will attempt it again and see if I can get something out of it. I read that Odin v 3.10.6 worked best for the note 5, is this true or does it matter? I have most of them. Haha
Click to expand...
Click to collapse
I'll upload something for you to use in a few minutes.
MrMike2182 said:
RP SWREV: B:3 K:0 S:1 You're on bootloader 3 and the knox is not tripped on the phone.. What I would suggest you do is flash this firmware version N920VVRS3BPI1 from my Android File Host and before connecting the phone to odin open the settings and disable the auto reboot option and then connect the phone and flash it and after odin displays PASS then disconnect the phone and immediately press and hold the volume down button, the home button and the power button at the same exact time and when the screen turns on select factory reset and let it finish doing that but do not let odin reboot the phone!
Click to expand...
Click to collapse
I did that firmware version, but it didn't work. I did the exact steps you just stated. I will attempt it again and see if I can get something out of it. I read that Odin v 3.10.6 worked best for the note 5, is this true or does it matter? I have most of them. Haha
Can you give me d/l link for the root only kernels and directions possibly?
MrMike2182 said:
I'll upload something for you to use in a few minutes.
Click to expand...
Click to collapse
Thank you for all of the help.
Apd833 said:
Thank you for all of the help.
Click to expand...
Click to collapse
Download this odin and try it.. The auto reboot is already turned off. Just unzip it. odin-modified
Those root kernels should be posted on the root section but they aren't full root! Only adb terminal root with no write permission to /system..
TRY THIS
Firstly you will need:
About 6gb of data and a stable network
A usb data cable
Patience
After getting all that, follow these steps:
1. Download samsung smart switch and install it to your computer
2. Download samsung usb drivers and install it too
3. Make sure your device is charged and your computer is connected to the Internet (with a stable network and at least 5gb of data because a slight error in the network will send you back to the beginning and you will have to start everything all over again.)
4. Launch smart switch and when prompted to connect your device, don't connect it, just click on "more" at the top right corner
- Then click on "Emergency software recovery and initialization"
- Then click on the "device initialization " tab
- Then enter your model number (your model number is N920V)
- Then click on search
- You'll be asked to enter the S/N (serial number)
- You'll find the serial number at the back of your phone (on the glass)
- Then remaining steps are self-explanatory
*DON'T FORGET TO LET US KNOW HERE.
h.meed said:
Firstly you will need:
About 6gb of data and a stable network
A usb data cable
Patience
After getting all that, follow these steps:
1. Download samsung smart switch and install it to your computer
2. Download samsung usb drivers and install it too
3. Make sure your device is charged and your computer is connected to the Internet (with a stable network and at least 5gb of data because a slight error in the network will send you back to the beginning and you will have to start everything all over again.)
4. Launch smart switch and when prompted to connect your device, don't connect it, just click on "more" at the top right corner
- Then click on "Emergency software recovery and initialization"
- Then click on the "device initialization " tab
- Then enter your model number (your model number is N920V)
- Then click on search
- You'll be asked to enter the S/N (serial number)
- You'll find the serial number at the back of your phone (on the glass)
- Then remaining steps are self-explanatory
*DON'T FORGET TO LET US KNOW HERE.
Click to expand...
Click to collapse
It tells me "The S/N you have entered is incorrect. Please check and re-enter."
MrMike2182 said:
Download this odin and try it.. The auto reboot is already turned off. Just unzip it. odin-modified
Those root kernels should be posted on the root section but they aren't full root! Only adb terminal root with no write permission to /system..
Click to expand...
Click to collapse
I've tried that Odin version and the root kernels I could find. I am still stuck in a bootloop. I have never been at such a loss with a phone. I usually am very good at figuring everything out, but this phone hates me.
Apd833 said:
Thank you for all of the help.
Click to expand...
Click to collapse
Apd833 said:
It tells me "The S/N you have entered is incorrect. Please check and re-enter."
Click to expand...
Click to collapse
Snap the back of the phone and send it to me on whatsapp
+2349020428078
h.meed said:
Snap the back of the phone and send it to me on whatsapp
+2349020428078
Click to expand...
Click to collapse
I can't get whatsapp to add the number you provided. I attached an image to this reply.