[Q] Someone plz help a n00b trying to root... - Verizon Samsung Galaxy S III

Any help or advice here would be GREATLY appreciated --
Q: Is it possible to get root on my S3? SCH-I535 running stock android 4.3 (I535VRUCNC1)
First, I am new to rooting so please refrain from ridicule... I have been online literally since this morning trying to find a way to do this, so needless to say I have searched. Tried Motochopper in OS X, and when that didn't work, went so far as to install Windows in VMware to try saferoot and CF autoroot--still no luck. From what I've read, I am I correct in understanding that this may not be possible? Bottom line: All I want is root in order to mount the internal memory to a volume for recovery of deleted files.
Thanks!

You're gonna have to ODIN back to ML1. NC1 has a Saferoot/Safestrap patch... The is thread on it. XDA search is your friend...
Sent from my SCH-I535 using XDA Premium 4 mobile app

Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html

Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?

messier42 said:
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
Click to expand...
Click to collapse
Try an actual Windows machine before giving up hope bud

Rushead said:
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Click to expand...
Click to collapse
There are links to this guy all over. However, I can't get it to work and neither can anybody else as far as I can see. Don't bother.

Related

Bricked..

My friend asked me to root his phone. When I asked him what phone he had, he told me it was a samsung vibrate.. however I found out that it is actually a sgs4g.. I flashed it with vibrant and now I have a vibrate boot loop / soft brick. I have searched around the forums and tried several jars and tars using heimdall and odin, however they all just fail. I have been trying for several hours now and am not getting any luck, especially since multiupload is dead. Does anyone know of a way to fix this? I am able to get into download mode (I have seen both variations (I.E. Digging droid and the orange triangle)). I believe it was on gingerbread.
Any help would be greatly appreciated.
Thank you.
Use the Heimdall One-Click guide in the second link of my signature. Go ahead and flash with bootloaders to be safe. And yes - that is download mode you see.
Afterwards - you can look at the guide in the first link of my signature for links to stable GB custom ROM's to flash.
I got the error "local and device PIT files don't match and repartition wasn't specified"
I remember trying this method once. However I got the same error after pushing 'ok' and flashing for a second time.
Edit -I flashed with bootloaders anyways (didnt do that step the first time). Thank you so much.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
i bricked my phone installing the wrong rom and used one click unbrick. worked great!

Galaxy Tab 2 P3113 Bricked after trying to root

I found steps to root my gt-p3113 via heimdall as I can't run odin in OS X. Followed instructions to the t but turns out the files used were from april of this year and I think possibly for a previous kernel version. When the tab restarted it just shows the galaxy tab 2 splash screen but nothing else. Clockwork didn't install. I can get into download mode and it shows custom instead of stock. :crying:
How can I fix this? I just need to get back to stock 4.0.4 so I can start back at step one and then get on a win machine and try the odin steps to root. If someone can please direct me it would save me worry and frustration...
Phil Grace said:
I found steps to root my gt-p3113 via heimdall as I can't run odin in OS X. Followed instructions to the t but turns out the files used were from april of this year and I think possibly for a previous kernel version. When the tab restarted it just shows the galaxy tab 2 splash screen but nothing else. Clockwork didn't install. I can get into download mode and it shows custom instead of stock. :crying:
How can I fix this? I just need to get back to stock 4.0.4 so I can start back at step one and then get on a win machine and try the odin steps to root. If someone can please direct me it would save me worry and frustration...
Click to expand...
Click to collapse
Well this has only been explained about a 100 times here. So a little searching would have been a good idea.
Just download the 4.0.4 firmware from http://www.sammobile.com for your model and country and flash it via ODIN.That's it
find a WINDOWS computer and follow this guide http://forum.xda-developers.com/showthread.php?t=2007876&highlight=restore
I'm sorry but I searched for hours. I found the odin restore but I don't have windows... I was looking for a way to restore from my mac via heimdall. But if odin is the only way then I'll have to find a windows machine.
Phil Grace said:
I'm sorry but I searched for hours. I found the odin restore but I don't have windows... I was looking for a way to restore from my mac via heimdall. But if odin is the only way then I'll have to find a windows machine.
Click to expand...
Click to collapse
I've not seen any heimdall method here, so you will need to find a windows computer, in general windows 7 is where you want to be when flashing android related stuff, its the OS everything is built to work with.

[Q] Bricked p6200 using Heimdall on Ubuntu, factoryfs.img stuck at 15%

Hi guys, i'm new hear, and a bit of a noob.
I've tried my best to see if existing threads would answer my query, but i'm not really sure if there's anything specific that would do the job.
First off, i have a p6200 galaxy tab plus, which was bought from Singapore.
This is an unlocked version.
Last month, i decided to flash the ATO (Austria ICS official update) via odin 1.85, which worked flawlessly.
Then last friday, i tried to install AOKP Milestone 1 custom rom.
This resulted into a bootloop.
I tried to do a data wipe, but i think this further damaged the software, as the formatting never really finished, and the unit simply rebooted back into the bootloop.
So i tried to reflash the ATO ICS rom onto the unit using Odin 1.85.
This too was a failure, as the flashing gets stuck at Nand Write Start!! factoryfs
So i tried a newer version of odin, 3.07, and that too got stuck at writing factoryfs.
Now i tried heimdall (still on a Windows machine).
That had an error "failled to access device, error: -12"
So i switched to my Ubuntu PC, and had better luck there by installing LibUSB, and opening Heimdall frontend with sudo permission.
But again, i'm stuck at uploading factoryfs.img 15%.
I'm kind of lost at this point, am i doing something wrong here?
i'm using the xxkl7 package from this forum: http://forum.xda-developers.com/showthread.php?t=1517934
then i got another set of patched .pit files from here: http://forum.xda-developers.com/showthread.php?t=1441350
i'm already up to pit with factoryfs moved by 03840 patched, and all have had the same result where i get stuck at 15% :|
i've got a lot more to try, yes, but i feel a bit hopeless here... anybody else have an idea?
all i can do is get to download mode, so i can't access recovery or anything else...
hoping for your help guys... thanks
Alex Genato
solved
posting xda-threads that helped:
http://forum.xda-developers.com/showthread.php?t=1667886&nocache=1
http://forum.xda-developers.com/showthread.php?t=1823918&nocache=1
http://forum.xda-developers.com/showthread.php?t=1900612&nocache=1
man that was a pain
but many thanks to the devs that made this unbrick possible...
Never wipe factory at stock recovery or it will brick your tab. Thats what they said.
Sent from my GT-I9300 using xda app-developers app

[Q] NAND Write Start Fail in Odin

Hi all,
for the last three days I've been carrying around a paper weight that looks remarkably like my Galaxy S3...
Anyway, I'm at a point where I don't know what else I could (or should) try. Today I thought I had a winner when I came across this thread: http://forum.xda-developers.com/showthread.php?t=1840030
I thought wrong. Flashing the bootchains works but then when I try flashing the root66.tar in Odin it always fails during NAND Write Start. I have seen people in the above thread with the same problem and then "never mind, I fixed it"-posts without explanations what they actually did... So, if you managed to fix it or know how to fix it, how does it work?
(I can't post in the same thread because I have less than 10 posts..)
Any input would be highly appreciated!
Thanks a lot and happy new year!
Cheers
In detail what did you do before this problem.
ThePagel said:
In detail what did you do before this problem.
Click to expand...
Click to collapse
Hm... a lot of (probably not very wise) things... Let's see...
It all started when I updated CM10.2 to a nightly release. Something went wrong, not sure what. I was talking to someone and when I checked my phone again it was just sitting there in TWPR and wouldn't boot up anymore (stuck in Cyanogen splash screen). I was still able to boot back into recovery and then tried flashing the stable CM10.2, which it didn't do. I factory reset the phone, tried flashing again, to no avail. The error message was that E: data something was missing or not accessible. From then on it's kind of a blur what I actually did, the list includes:
- trying to flash back to stock in Odin
- trying to flash new recovery in Odin
- trying to flash a pit file
- trying to install new firmware in Kies (after downloading the firmware Kies would just quit (PC), or not even download it and tell me that it's not posfible with my phone (Mac))
- trying the method described in the linked thread
At some point I wasn't even able anymore to boot into recovery (I think that was when I tried to flash a new recovery).
Thanks
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
joeinternet said:
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
Click to expand...
Click to collapse
Interesting. I am indeed running Windows in a VM... Need to try that later today. I'll report back later in the pm. Thanks!
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Mungo Park said:
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Click to expand...
Click to collapse
Be careful using kies in the future. If they start pushing 4.3 you will be screwed.
Haven't thought about that. It was still 4.1.2 and I'm back on CM10.2.
Thanks!

[Completed] Samsung Galaxy S4 Google Edition GT-i9505G stuck in recovery mode boot loop

Hello. I need some help ASAP. My phone has been rooted (and running CyanogenMod 11) for a LONG while and lately I've been getting into network penetration. Long story short, I unlocked the bootloader of my GT-i9505G, but when it automatically rebooted, it was stuck in a recovery mood boot loop. I've tried reflashing stock Android (got failures), then CyanogenMod (some more failures), and then GApps (want some fail with that failure?). I've also tried to re-flash my firmware again using Odin 1.85, but it failed (surprise, surprise!) as well! It spit out the attached image in the end.
I'm very skilled with computers but lacking in the mobile phone department. I do know my way around them, but getting into THIS level (firmware flashing) on them is beyond me. I honestly don't know how my phone ended up like this, as I read through the guide to get an idea of what would happen and then went through the guide actually doing the work, and I followed it step by step. I REALLY need to fix this ASAP as I'm a high-school student and I take online classes. I'm sorry if this is on a really noob level, but that's exactly what I am and I'm panicking. I don't have a job and my life is on this device.
Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!
jd1639 said:
Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!
Click to expand...
Click to collapse
I got farther in the process this time, but it still failed. This time at the write operation. What should I do? I also tried it in Odin 3.09 but got the same results as in 1.85.
Hi, sorry for the late response. Are you still having problems? There is a forum for your device where others with your specific device may be able to help. It's located here, http://forum.xda-developers.com/galaxy-s4

Categories

Resources