Related
Original Thread:
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.
Why “Heimdall”?
The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Why use Heimdall when we can use Odin?
Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.
Is Heimdall safe?
No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.
How do Galaxy S phones get bricked when flashing?
Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.
A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.
Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!
What Galaxy S variants has Heimdall been tested with?
We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.
Enough talk, where can we get it?
The latest release is available here. Please read the instructions and README files included in the archives.
I love you, man. Will you have my baby?
No, but I will very gladly accept donations. If you appreciate my work and would like to support future development you can make a donation here. If you think you have something else to offer, then feel free to shoot me a PM or contact me via the contact form on the Glass Echidna website.
Click to expand...
Click to collapse
Source has been pushed to Github. Let me know how it goes for you Galaxy S II folk.
If you're appreciative of the updates don't forget to donate so I can get myself a Galaxy S II
Gr8 news!
Hope this won't increase the flash counter in download mode when it's finished
Swyped from my overclocked GT-I9100 using XDA Premium App
I'm happy with Odin on Windows, but great work nonetheless !
Chainfire said:
I'm happy with Odin on Windows, but great work nonetheless !
Click to expand...
Click to collapse
on windows, yes
but linux... ^^
Swyped from my overclocked GT-I9100 using XDA Premium App
Great, Ive been waiting for this. More linux love. Thanks!
Sent from my GT-I9100 using Tapatalk
Excellent! Though I may not be the first to try it, I'll probably be using this (tomorrow?) to flash my first custom ROM if all goes well
Hey Ben,
Do you think its possible to make backups of firmware using this tool? I think it'd be good for those who wants to have carrier-branded ROMS backed up for warranty purposes.
phunkycow said:
Great, Ive been waiting for this. More linux love. Thanks!
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Nice will give it a shot later.
OT:
Phunkycow u here? Left the dhd behind? Loved ur cm builds on the dhd..
Sent from my GT-I9100 using Tapatalk
Locster126 said:
Nice will give it a shot later.
OT:
Phunkycow u here? Left the dhd behind? Loved ur cm builds on the dhd..
Click to expand...
Click to collapse
<OT>Yeah, sold it finally and i'm a happy panda now lol
Good to see you here too!</OT>
(Apologies for the OT )
Heimdall 1.2.0 command line binaries are now available. Debian 32-bit, Debian 64-bit, Windows and OS X (universal) are all available.
4iedemon said:
Hey Ben,
Do you think its possible to make backups of firmware using this tool? I think it'd be good for those who wants to have carrier-branded ROMS backed up for warranty purposes.
Click to expand...
Click to collapse
Sorry, I missed this post.
Heimdall has theoretically supported dumping of firmware for quite some time. However all the devices I've ever tested it with mostly send back junk data and eventually stop responding altogether (requiring a manual reboot). As far as I can tell this is simply a result of the secondary bootloaders on devices just not supporting the functionality, however it's possible that the functionality has been finished/fixed for the SGS2.
If someone wants to test out dumping when they test out flashing that would be great. If so I recommend you enable the verbose switch so you have a better idea of what is going on.
Benjamin Dobell said:
Heimdall 1.2.0 command line binaries are now available. Debian 32-bit, Debian 64-bit, Windows and OS X (universal) are all available.
Click to expand...
Click to collapse
Nice, thanks! Would this (theoretically) work with the GUI from v1.1?
aussiebum said:
Nice, thanks! Would this (theoretically) work with the GUI from v1.1?
Click to expand...
Click to collapse
Yeah, you obviously won't be able to use any functionality that isn't available from the GUI though. Because the SGS2 has a few different partitions that aren't accessible from Heimdall Frontend you won't be able to flash to them, however you can still flash kernels etc. no problems.
OS X users, you will need to download the latest package again. The binaries are the same but I had forgotten to update the kext so that "the interface could be claimed".
Code:
$ heimdall print-pit
Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Failed to detect compatible device
I installed the latest one in OS X 10.6, restarted, and got the above result. Note that running "adb devices" does show up my SGSII properly.
winst said:
Code:
$ heimdall print-pit
Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Failed to detect compatible device
I installed the latest one in OS X 10.6, restarted, and got the above result. Note that running "adb devices" does show up my SGSII properly.
Click to expand...
Click to collapse
is your phone in download mode?
Sent from my GT-I9100 using XDA App
I tried print-pit and dump and ended up with a bunch of "Error -7 whilst receiving packet." print-pit seemed to work fine but was unable to end the session.
Find verbose logs here:
print-pit
dump
For obvious reasons, I'm a little hesitant to try flashing anything
jps1974 said:
I tried print-pit and dump and ended up with a bunch of "Error -7 whilst receiving packet." print-pit seemed to work fine but was unable to end the session.
Find verbose logs here:
print-pit
dump
Click to expand...
Click to collapse
Thanks for the details, much appreciated.
The dump log doesn't really surprise me, it's actually better than how it fails on Galaxy S. The Galaxy S downloads a heap (megabytes) of junk, I guess that it's good that it fails immediately.
jps1974 said:
For obvious reasons, I'm a little hesitant to try flashing anything
Click to expand...
Click to collapse
Haha, no worries.
A few questions though:
Does your device reboot after the PIT information is displayed?
When you reboot does the phone boot normally or is the connect phone to PC screen displayed?
Does "heimdall close-pc-screen" also fail to end the session?
If your device boots up fine (no connect to PC screen) then that should mean the end session packet was received (and interpreted) by your phone no problems. If that's the case then it's possible Samsung have just changed the protocol so no response is expected. It never really made sense to me that you've essentially told the phone you're done and then you still send it a reboot packet.
Alternatively the syntax to end a session may have changed slightly. Someone mentioned a flash counter, maybe I'm supposed to send a packet to update the counter (although I'd rather not anyway).
Without a SGS2 I'm unable to investigate this myself but if someone is able to get me a detailed USB log of flashing with Odin or Kies then I could sort it out. I literally need the 1s and 0s sent to/from the phone. If not then donations towards getting me a SGS2 would be immensely helpful. Thanks again to those of you who have donated.
EDIT: Doh, I just realised I spelt "successful" wrong when Heimdall downloads a PIT file
Well, I grew some balls and tried a full flash - worked just fine
To answer your questions:
Benjamin Dobell said:
Does your device reboot after the PIT information is displayed
Click to expand...
Click to collapse
Nope
Benjamin Dobell said:
When you reboot does the phone boot normally or is the connect phone to PC screen displayed?
Click to expand...
Click to collapse
Boots up normally
Benjamin Dobell said:
Does "heimdall close-pc-screen" also fail to end the session?
Click to expand...
Click to collapse
Yes, see here
Benjamin Dobell said:
Without a SGS2 I'm unable to investigate this myself but if someone is able to get me detailed USB log of flashing with Odin or Kies then I could sort it out, I literally need the 1s and 0s sent to/from the phone. If not then donations towards getting me a SGS2 would be immensely helpful. Thanks again to those of you who have donated.
Click to expand...
Click to collapse
I made a small donation towards your new device, but I'll be happy to help you out if you give me some instructions
By the way, I have to use sudo, otherwise I get this:
Code:
Failed to access device. Error: -3
Thanks for all your work!
Most of us are messing up our sboot or bungling up other portions of the ROM making CASUAL freak out and fail on you during ODIN flashing. Do the following first and I guarantee casual will work without incident.
Download this http://www.mediafire.com/?z2bd5u4esh73mbv
Put the update.zip into your adb folder commonly known as your platform-tools folder.
Boot your phone into stock recovery
Choose adb side load
Then type "adb sideload update.zip" with no quotes.
This will update you to the latest VRALL release. Once this updates it will fix your corrupt sboot file and you are ready for CASUAL boot loader unlock and root.
Sent from my SCH-I605 using xda premium
You do realize most the time is the ROM messed up? That's why the alternate restore that doesn't write sboot fixes it. However, this is a cool alternate restore method never really thought of. Have you done this when on the new ota yet, I'm wondering if it accepts sboot then?
Sent from the dark on a Note 2
kintwofan said:
You do realize most the time is the ROM messed up? That's why the alternate restore that doesn't write sboot fixes it. However, this is a cool alternate restore method never really thought of. Have you done this when on the new ota yet, I'm wondering if it accepts sboot then?
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Yes I have done on new OTA... works great.
das7982 said:
Yes I have done on new OTA... works great.
Click to expand...
Click to collapse
Good to know.
Sent from the dark on a Note 2
Just a minor addition, I had a second device, plugged into my computer when trying to run casual and it would fail saying unsupported kernel detected. Just throwing this out there.
Sent from my SCH-I605 using Tapatalk 2
This guide is for the select few that need to root their Samsung Galaxy S4 via Mac.
This guide only shows how to swap kernels in order for you to run motochopper then swap back to stock kernel.
Please keep in mind this is technical and involves using manual commands for heimdall in terminal.
If you have anything to add or have any questions, don't hesitate to ask.
I have tested this method using Heimdall on my Windows 7 machine.
I do not own a Mac to fully test this.
I am not an expert nor do I portray myself to be one.
I am not responsible to any problems from this method including bricking any devices, loss of data, or other issues that may arise with your device or computer. (Just to cover my behind.)
Things you need:
1. Heimdall
2. prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6)
3. stock kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769)
4. Motochopper Root Exploit Tool
5. Drivers can be installed by installing Kies
First install Heimdall.
And make sure you have the drivers installed.
Make sure you have the prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6) in an easy place to find and make sure you keep it seperate from the stock kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769).
If you have Kies installed, uninstall it.
Then open the heimdall-frontend application that was installed with heimdall.
Use the heimdall-frontend app to detect the device by going to Utilites > Detect.
Next open a terminal type
Code:
sudo heimdall flash --BOOT <full path to prerelease kernel>
Enter your password.
The prerelease kernel will be flashed and your device will reboot.
Go to Settings > More > About phone
and check to make sure your kernel version is 423399.
Then go into Settings > More > About phone > tap "Build number" about 7 times until it unlocks Developer options
Verify in Developer options setting on your device that you have "USB debugging" checked.
Verify in Developer options setting on your device that you have "Verify apps via USB" unchecked.
Verify in Security setting on your device that you have "Unknown sources" checked.
Verify in Security setting on your device that you have "Verify apps" unchecked.
Extract the motochopper.zip file.
Open terminal, navigate to the motochopper folder and type
Code:
sudo chmod +x run.sh
Then type
Code:
sudo ./run.sh
Follow the on screen prompts.
After you are rooted, make sure you update the su binaries.
Otherwise you will lose root later on.
Next boot your phone into download mode in order to put the stock kernel back.
Open the heimdall-frontend application and detect your device once again. (Utilities > Detect)
Next open a terminal and type
Code:
sudo heimdall flash --BOOT <full path to stock kernel>
Then go to Settings > More > About phone
and make sure the stock 562219 kernel is installed.
Credits go to djrbliss, chainsdd, Samsung, creators of Heimdall, and if I missed anybody please let me know and I will add them to it.
Thanks to Doppletronica for confirming the method.
If you found this guide helpful please hit the thanks button
EDIT: If this thread now belongs somewhere else due to its nature, please move it mods.
Also anybody is free to share this guide, just link them to this thread and please give credit where credit is due.
Thanks.
klabit87 said:
Is there anybody willing to test a root method running a Mac?
I may have found a way but I don't have any way to test it myself otherwise I would.
If interested please pm me.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
does it have an unroot? i'd be willing to try it out. if so
theidoctor said:
does it have an unroot? i'd be willing to try it out. if so
Click to expand...
Click to collapse
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
theidoctor said:
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
Click to expand...
Click to collapse
Pm sent.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
I will finish my write-up and get it to you as soon as I can.
I'm not around a computer at work so it may be later this evening possibly.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
Pm has been sent. Let me know if you have any questions or concerns.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
You can unroot it the same way you root. Use Heimdall.
DarkMenace said:
You can unroot it the same way you root. Use Heimdall.
Click to expand...
Click to collapse
Thanks. I knew I was making it harder than it was supposed to be.
I was really only interested in the root guide since a good few people were asking about it.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I was wondering if someone can help me. I keep getting this error message:
patxp:desktop ArmandoOrona$ sudo heimdall detect
Password:
Device detected
patxp:desktop ArmandoOrona$ sudo heimdall flash --BOOT boot.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
patxp:desktop ArmandoOrona$
I uninstalled kies and android file transfer and restarted mac. Any help would be greatly appreciated.
Has anyone else tested this? Just curious.
anothamexican said:
I was wondering if someone can help me. I keep getting this error message:
Initialising connection...
Detecting device...
Claiming interface...
libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
patxp:desktop ArmandoOrona$
I uninstalled kies and android file transfer and restarted mac. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Doppletronica said:
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Click to expand...
Click to collapse
So just to clarify, are you saying the whole process worked for you?
Whereas you successfully rooted your phone?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
So just to clarify, are you saying the whole process worked for you?
Whereas you successfully rooted your phone?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Doppletronica said:
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Click to expand...
Click to collapse
Great! Thanks for your confirmation.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Man.....I wish I saw this yesterday. I spent 2 hours getting my old imac up and running with bootcamp to install windows.....another hour looking for my old XP disc to actually install it on the iMac, another half hour to install XP, then a good 45 minutes or so trying and failing to gett all the samsung drivers to wok (too several installs and unistalls til it finally worked). After all that, I downloaded the all in one root kit and install recovery as well.
Doppletronica said:
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
Click to expand...
Click to collapse
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
anothamexican said:
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
Click to expand...
Click to collapse
The guide has been updated.
You need to continue the process in terminal.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
hexitnow said:
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
Click to expand...
Click to collapse
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
vafangool said:
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
Click to expand...
Click to collapse
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
Further info on what @Surge1223 said:
Go to this thread and follow the directions in the first post.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
vafangool said:
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
Click to expand...
Click to collapse
You have got to be pretty careful, since there's lots of variants of these models. For example, there's at least 6 incompatible models of the Samsung Galaxy S4 (AT&T, Sprint, T-Mobile, Verizon, International (a couple of models as far as I can tell) the "L" variant, etc.
Following directions for a "Galaxy S4" without knowing if it's the same variant as yours can lead to bricks.
People have successfully used Saferoot to root Note 2 with the MK7 build. Then you'll have to research if Safestrap works - it's likely if you're running 4.3, but I have no idea. Do the research before you flash.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed.. I also dont have that padlock unlock when I restart the phone....
vafangool said:
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed, My device status says official...is that where its suppsed to say custom?
Click to expand...
Click to collapse
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
k1mu said:
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Click to expand...
Click to collapse
I may try and reroot it and see what happens...its hard to explain but it was at the part where it was telling me my phone was going to reboot and to unlock it and press any key when it does..I waited and the phone didnt reboot
... I just did it again and it looked like it worked...I kept seeing the popup that ADB shell has been granted superuser permissions....it said all done and the command prompt closed..
Surge1223 said:
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
vafangool said:
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
Click to expand...
Click to collapse
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome..Thanks alot for all the help...
My apologies if I've missed instructions somewhere. I've got a brand new 3840, but all the instructions I can find for rooting are for the 3830. Does anyone know how to root the 3840? I can provide files/etc from the device if needed.
khuey said:
My apologies if I've missed instructions somewhere. I've got a brand new 3840, but all the instructions I can find for rooting are for the 3830. Does anyone know how to root the 3840? I can provide files/etc from the device if needed.
Click to expand...
Click to collapse
perhaps you can pm @social-design-concepts
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
social-design-concepts said:
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
Click to expand...
Click to collapse
Thanks social-design-concepts, that's really cool. I can't wait to root mine and remove the dell cast, Maxx Audio stuff off it. And to install Xposed for customization.
BTW, is there a general walk through (/approach) about how to go about finding a root for a device? I see most of the popular devices have root procedure that can be followed for rooting. It would be nice if I can poke around myself and try to come up with a rooting method if not too tricky. (I know the very first step would be install drivers and get into fastboot, right? but what to do next...) Beats simply following others' path, and could be beneficial for others too.
Thanks
social-design-concepts said:
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
Click to expand...
Click to collapse
Cant wait till you get that done I have been looking everywhere on how to root this device and no resolution. Thanks.
a couple testers needed to test a new root method , sorry it took so long but i do believe i have it figured out :
[TOOL KIT] myKIT_BATCHV1.1.x :
Follow the instructions for setting up myKIT_BATCHV1.1.x use this root downloadable in that same post .
SDC_INTEL_ROOTKIT.7z
Let me know if it works . . .
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Santin said:
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Click to expand...
Click to collapse
Not at this time I'll investigate though thanks for the info. Can you post a pic of the device screen at that point?
Sent from my XT907 using XDA Free mobile app
Hi social-design-concepts
I was so confused, I do the following in order to organize.
1. I did again Unbricking Process.
2. I made a setting up a terminal minimal and OS updates(for kitkat 4.4.4).
3. And I setup ADB driver. (path is E:\myKIT_BATCHv1.1.x\mykits\driverKIT\ADB\usb_driver\android_winusb.inf)
http://forum.xda-developers.com/attachment.php?attachmentid=2963891&stc=1&d=1412770552
4. run run-me.bat.
http://forum.xda-developers.com/attachment.php?attachmentid=2963902&stc=1&d=1412771006
5. rootkit issues an error as follows.
http://forum.xda-developers.com/attachment.php?attachmentid=2963904&stc=1&d=1412771253
Whether there will be information necessary something else?
Here's where mine failed
It failed at the very first step of flashing ADBD (screen capture attached):
writing '/sbin/adbd'...
FAILED (remote: flash cmds error!)
4ge6 said:
It failed at the very first step of flashing ADBD (screen capture attached):
writing '/sbin/adbd'...
FAILED (remote: flash cmds error!)
Click to expand...
Click to collapse
As i said it was a trial it looks as if the fixed it in 4.4.4, when I get home I'll remove it from the list. I need to try to get the 4.4.2 on dells open source site booting on my fake hardware and try to capture the 4.4.4 ota sorry.
Sent from my XT907 using XDA Free mobile app
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Santin said:
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Click to expand...
Click to collapse
Maybe you would wanna roll back to the 4.4.2 and try to root and capture the ota should be able to make a prerooted system.img for 4.4.4
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
Maybe you would wanna roll back to the 4.4.2 and try to root and capture the ota should be able to make a prerooted system.img for 4.4.4
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Downgrade to 4.4.2 before root might be a viable route.
But how can I downgrade to 4.4.2?
(Would only downgrading the boot partition be OK? No need to downgrade the system partition right?)
(will be looking, and report back if I can figure it out)
Although I tried various ...
I write below the work that I've tried.
*Working with non-TOOL KIT depends on the opensource.dell.com.
1. I gave a Unbricking Process again. (roll back to the 4.4.2)
Fastboot mode is not valid in this state.
Also in process of restarting at TOOL KIT, it does not take into fastboot mode even Reboot the tablet and press power + volumn down button.
2. I have enabled the fastboot mode of opensource.dell.com the "Enable fastboot mode" process in 4.4.2 above.
Therefore, I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display came out with.
3. I gave a Unbricking Process again. (roll back to the 4.4.2)
Apply OTA update for first time. (update 4.4.4)
(Fastboot mode is enabled this update later)
I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display again.
4. Apply OTA update for the second time. (update 4.4.4)
Run run-me.bat. The same error is displayed, rooting failed.
It is regrettable, but I tried writing to '/sbin/adbd' has become an error.
to social-design-concepts
And I tried to donate to you, but could not pay for you from my PayPal account(in Japan). I'm sorry.
Santin said:
I write below the work that I've tried.
*Working with non-TOOL KIT depends on the opensource.dell.com.
1. I gave a Unbricking Process again. (roll back to the 4.4.2)
Fastboot mode is not valid in this state.
Also in process of restarting at TOOL KIT, it does not take into fastboot mode even Reboot the tablet and press power + volumn down button.
2. I have enabled the fastboot mode of opensource.dell.com the "Enable fastboot mode" process in 4.4.2 above.
Therefore, I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display came out with.
3. I gave a Unbricking Process again. (roll back to the 4.4.2)
Apply OTA update for first time. (update 4.4.4)
(Fastboot mode is enabled this update later)
I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display again.
4. Apply OTA update for the second time. (update 4.4.4)
Run run-me.bat. The same error is displayed, rooting failed.
It is regrettable, but I tried writing to '/sbin/adbd' has become an error.
to social-design-concepts
And I tried to donate to you, but could not pay for you from my PayPal account(in Japan). I'm sorry.
Click to expand...
Click to collapse
Could you upload the ota some where?
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
Could you upload the ota some where?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I Uploaded to google drive the OTA package, I sent a PM who wrote the url.
Santin said:
I Uploaded to google drive the OTA package, I sent a PM who wrote the url.
Click to expand...
Click to collapse
I finally received my new Dell 3840 today and was able to capture some details about the OTA update using Wireshark.
http://mobileupdate.dell.com/?version=YTP802A119530 will bring you to a webpage where you can download the OTA package: YTP802A125330-i-YTP802A119530-2014-08-23-38.pkg
Alternatively, you can just download this:
http://mobileupdate.dell.com/Packag...P802A125330-i-YTP802A119530-2014-08-23-38.pkg
The .pkg file is just a regular update.zip. If you rename it to YTP802A125330-i-YTP802A119530-2014-08-23-38.pkg.zip, you can unzip it.
It looks like the Android updater also pulls down a couple other files from Google:
http://www.gstatic.com/android/config_update/07172013-sms-metadata.txt
http://www.gstatic.com/android/config_update/07172013-sms-blacklist.txt
-Howard
Is there a 4.4.4 image, available for download, would like to see if it can be modified to run on 3830.
sent from my kingSing T1 via taptalk
vampirefo said:
Is there a 4.4.4 image, available for download, would like to see if it can be modified to run on 3830.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
There still no root for them yet, so I don't think you'll find one.
Sent from my XT907 using XDA Free mobile app
And another OTA update after 4.4.4:
http://mobileupdate.dell.com/?version=YTP802A125330
hharte said:
And another OTA update after 4.4.4:
Click to expand...
Click to collapse
How to install it properly?
Thanks.