Database Info

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!

[Q] Problem during rooting help

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

[GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]

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:

Questions about 1st time root SM-J700P w/7.1.1

Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.

J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !

Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!

Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.

I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?

J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !

Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.

I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?

Verification failed error on my Galaxy S8+

So I decided to manually update my galaxy s8+ since samsung oficially stopped suporting it for future feature updates and my phone started to get too slow, so my idea was to put the lighter lineage os on it.
To do that, first, I first had to get root.
To do that, I followed an step by step guide and I finished it (im new so i cant put the link to the guide, but it's form androidinfotech/.com and the title is "Root Samsung Galaxy S8 Plus SM-G955F Pie 9.0 using TWRP"). Then I finally rebooted my phone to see if I had root installed, and an error popped up: Verification failed, unable to restart your device, that after a little of research I realized it was quite a common error on samsung devices.
After that I checked threads of people that this had happened to and it said to reboot in twrp, which of course, I installed before rooting my phone, and wipe the data and some other steps.
But the problem is that after hitting reset and inmediately hitting the button combination for recovery mode, it just launched recovery mode for a few seconds and then the screen goes black inmediately after, and sends me back to the verification failed error. So basically I can't initiate in recovery mode.
I've tried other keys combinations and they either don't work or aren't of any use. Also, I can acces download mode, if that is of any use.
Does anyone know what to do here or something?

Figured it out
turns out i hadn't wipe the data properly. from that verification failed screen i turned my phone off like you normally do it, with the power button. then accessed the recovery mode after the phone was off. that was why i couldn't access the recovery mode before. after that, i found a fix for the error that showed while wiping data and then i re installed everything i had installed before and rebooted and now everything works. hope this helps someone...?

Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance

Abdul-Hanan. B. Jonathan said:
Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance
Click to expand...
Click to collapse
homie, youre best off posting up an entirely new thread with your issue as most folks will likely miss a post like this on a year old thread. the 1gb of storage is usually fixed with a factory reset done in recovery. If not, youre going to have to flash the stock FW on it again via Odin to tell its storage table how much storage it actually has