About The ROM
Revision is based on I605VRALJB. Also, it's been specifically designed to be the most stable image to fall back on before or after flashing kernels, recoveries or ROMs. It will put your device into the MOST working condition possible currently. The only more possibly stable image would be the one your device came with and we don't have that.
What is Revision?
Revision is a stepping stone. It puts your device into a relatively stock, and known working condition.
Tweaks
I added the following tweaks to the ROM for usability and hackability.
Carrier Unlocked for AT&T network.
Rooted with ERD Chainfire's SuperSU
Bash
Busybox
i2cdetect, i2cdump, i2cget, i2cset
ipctool
strace
tcmpdump
viewmem
PARAMS: UART Logging Increased
PARAMS: UART Root Prompt at battery charging
PARAMS: UART Shell terminal during normal operations
The PARAMS will be available in a future CASUAL application for testing.
Download Revision3 ROM repacked
Troubleshooting
Windows users: First uninstall PDANET drivers, then install Samsung Kies.
Here's some notes I wanted to record:
Uncompressing a Samsung System image
Code:
./ext4_utils/simg2img ./originalsystem.img ./working.img
Compressing a Samsung Image
Code:
sync; sudo ./ext4_utils/make_ext4fs -s -l 1792M -a ./temp ./system.img /path/to/mounted image
Create a tar.md5.gz file from a set of images..
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./Revision1.tar;sync md5sum Revision1.tar >> Revision1.tar; mv Revision1.tar Revision1.tar.md5; sync; gzip Revision1.tar.md5 -c -v >Revision1.tar.md5.gz;
the tools are available on the internet.
Revision1: initial release
Revision2: Fixed Baseband issue. The PARAMS were to blame for this. Removed features to add functionality.
Revision3: Carrier Unlock for AT&T.. needs more work to get rid of Verizon warning. Thanks Joder for the APN info.
Revision3 repacked: apparently there was an issue with the uploaded Revision3. Repacked is a properly repackaged version of Revision3.
thx
downloading now... cant wait for the unlocked bootloader hack to be released!
Great Work!
Nice, can't wait for the bootloader unlock tool to be released!
Thanks Adam for all your hard work. You and Beans are the first devs I ever donated to, and you wont be the last. I really appreciate the all the hard work devs put into this.
So what's the next step? Does this help you understand the bootloader?
So just flash this via Odin?
Sent from my SCH-I605 using Tapatalk 2
Thanks very Much
I really appreciate all you have done
I'll download it and put it in a folder locked with a code.
Sent from my rooted galaxy note 2... U mad?
nnnnr14 said:
I'll download it and put it in a folder locked with a code.
Sent from my rooted galaxy note 2... U mad?
Click to expand...
Click to collapse
Make sure you encript it as well
drumdestroyer said:
Make sure you encript it as well
Click to expand...
Click to collapse
Pshh that's too advanced! I'll probably have to leave a .txt file on the desktop reminding me what the code was!
Sent from my rooted galaxy note 2... U mad?
i flashed in odin and now i have no service nor 4g it is simply stuck at the activation screen in setup wizard......any ideas. thanks in advance.
oh well aint it grand
thunderbread said:
i flashed in odin and now i have no service nor 4g it is simply stuck at the activation screen in setup wizard......any ideas. thanks in advance.
Click to expand...
Click to collapse
Flash back to what u were on before. Seems like a common problem. Beans had that prob with his rom. Before he released it.
mine too
mine is tryn to activate but still stuck at activation screen
nnnnr14 said:
Pshh that's too advanced! I'll probably have to leave a .txt file on the desktop reminding me what the code was!
Sent from my rooted galaxy note 2... U mad?
Click to expand...
Click to collapse
That's me! Lol. I have to write it on my hand next to my grocery list.
welp dont know
welp Adam yours kept saying tryn to activate,so I went back odin the others and now the other 2 does also is saying tryn to activate,sounds like I am gonna have to call and see if my sim card has to be reactivated,but I am gonna let it set overnite just to make sure...........
Yeah mine isnt doing anything. Tried to Odin back and still nothing. Just sits at activation screen. Anybody have any ideas.
Sent from my SCH-I535 using xda app-developers app
thunderbread said:
Yeah mine isnt doing anything. Tried to Odin back and still nothing. Just sits at activation screen. Anybody have any ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you check Settings>About>And status to see if you have an IMEI or any info?
Nope. Won't let me leave activation screen.
Sent from my SCH-I535 using xda app-developers app
Has any one tried the bypass activation like we did on the s3?
on select a language screen, press lower left corner, lower right corner, lower left corner, lower right then volume up
Sent from my SCH-I605 using Tapatalk 2
Mine finally just stopped tryn to activate and gave me a number to call and i have wifi,, but the answer to question on imei is there is no imei number, no baseband, all says unknown
Related
This phone I got to get. Who is getting it
sent using the WWW.psxforums.com app
Please close this.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
This rom looks fantastic! Will it break root? Where's your download link?
From fastboot menu make sure phone is plugged in... Open up a command prompt.. change directory to wherever you have your adb & fastboot ... Make sure your recovery file is there also.. from command prompt type "fastboot flash recovery ********.img" replace the ****** with whatever your recovery is named ... This will flash a new recovery
Sent from my PG86100 using xda premium
i have fastboot and adba drivers installed what do i do text my ipod number please i hate this gay posting crap 14158537142
please help me i dont know what do do in cmd
In cmd change directory to the folder where you have your adb stuff... For example mine are in c:/rootevo3dnew so I type cd rootevo3dnew at command prompt
Sent from my PG86100 using xda premium
what is adb stuff tell me what to do.
do i make a folder in my directory of my phone called rootevo 3d or do i rename the removable media as rootevo 3d i dont know what to do and dont know how to use adb
You said you have adb and fastboot installed... What directory are they in?
Sent from my PG86100 using xda premium
i thought xd devs was a place for help and support i need help and support on what im doing as i donot have a celphone now i need this peace of crap working asap
Watch that video I posted one page back, it shows you exactly how to do it and has files you need to download.
Sent from my PG86100 using xda premium
i need your help
Go to windows folder and copy cmd.exe
Paste cmd.exe where your SDK/ fastboot,adb files are at.
Download a recovery like twrp.
Rename the twrp .IMG file to trwp.img
Copy the img file to the same folder as cmd, adb, and fastboot.
...
Now pull your battery. Re insert battery.
Connect your phone to your computer using a USB cable.
Hold vol down and turn on phone.
Your phone should be in fastboot USB
open the cmd.exe file and type
fastboot boot twrp.img
The command window will display that it sent the info to your phone and reboot your phone into a full unlocked recovery.
From here you want to wipe system, data , and cache.
Then install a 3.6 or 3.0 sense Rom to make sure everything works
Sent from my EVO One 3D using the XDA Premium App.
Well said...
Sent from my PG86100 using xda premium
ICantAffordIt said:
Probably a strange coincidence, but I lost all voice and texting capability about 15 minutes after I went s-off. I was on Meanrom ICS and wanted to avoid having to flash kernel to make it work. I can get sprint data working no problem, but can no longer make/receive calls or text. Tried everything I could think of:
Reflash rom
Wipe/Factory reset
Superwipe
Flash stock unlocked rom
Flash OMJ GB rom
Even called sprint to see if they could reset on their end.
No luck. I'm going to try going back to stock, locked s-on and take the phone in for replacement I guess now.
Click to expand...
Click to collapse
I had the same thing happen to me. I tried to make a call out, and got a recorded voice saying "error 16. please stay on the line while your call is connected to a representative."
30 seconds later a sprint rep was on the line, just verified my personal info to make sure I was authorized to be making changes to my phone (apparently it failed some kind of security test). I told them that I just did a hard reset on my phone and they said it was the most common reason that people got that error. 3 minutes later they fixed my issue. All connectivity restored, phone working 100%.
---------- Post added at 08:04 AM ---------- Previous post was at 07:30 AM ----------
zachdees said:
i need your help
Click to expand...
Click to collapse
LOLing so hard at the guy who is obviously way under-experienced trying to hack his phone.
Here's a link to help you:
http://bit.ly/Lc81Yh
Rooster85 said:
LOLing so hard at the guy who is obviously way under-experienced trying to hack his phone.
Here's a link to help you:
Click to expand...
Click to collapse
That probably won't help since he didn't want to read anything.
Maybe he should stick to Apple products.
ramjet73
I'm happy I can make neato splash screens again.
Sent from my PG86100 using xda premium
zachdees said:
i dont think you where ment to be here if you wherent gonna help im bout to sledgehammer my new evo 3d i dont know what to do
Click to expand...
Click to collapse
Wow, really dude? He linked you to a video and and the proper thread to deal with the recovery YOU installed. Did you even look at them or you sitting here, in this thread, waiting for someone to hold your hand? This isn't your personal tech support. Read up. Tell us what you learned and tried. Then, ask for specific help..not, "I'm a dohdoh and messed up my phone, fix it"..Christ.
My sides hurt XD still a little wary of this but looks much simpler than bricking. Awesome work!
dimebagdan65 said:
My sides hurt XD still a little wary of this but looks much simpler than bricking. Awesome work!
Click to expand...
Click to collapse
It works...took me 5 mins to do
Sent from my PG86100 using xda premium
govno64 said:
I had the same thing happen to me. I tried to make a call out, and got a recorded voice saying "error 16. please stay on the line while your call is connected to a representative."
30 seconds later a sprint rep was on the line, just verified my personal info to make sure I was authorized to be making changes to my phone (apparently it failed some kind of security test). I told them that I just did a hard reset on my phone and they said it was the most common reason that people got that error. 3 minutes later they fixed my issue. All connectivity restored, phone working 100%.
---------- Post added at 08:04 AM ---------- Previous post was at 07:30 AM ----------
Click to expand...
Click to collapse
I wonder if I should call sprint again or just go into the store. Guy gave me an eticket number for a replacement phone. If anyone is interested though, I restored to stock, then used adb to put s-on. Bootloader now shows Locked and S-On with Hboot 1.50. Doesn't appear to be any evidence of my rooting.
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Source for the kernel has been released.just a matter of time untill the devs create something wonderfull you might look on samsungfirmware.com
I havent seen a kernel specific to the att version. Not sure if anyone has made one yet. You might be stuck untill e get one but I dont think it will be to long. Good money says D.G. Is already on it.
sent from my Infuse at Tranquility Base.
My Fault
I knew I should of waited i just wanted to run Titanium Backup
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Yeah International kernels dont support bottom keys since they aren't on the Int' version so if you used one of the kernels you will need to go stock like you said or wait for DG to cook up his genius like another poster said.
This might not be the right place for this question and I know it's still very early but anyone think there'll be a way to unlock the AT&T SGS2 for other carriers? I know the Captivate could be unlocked simply by rooting and downloading an app from the market. I only ask because I'll be getting the phone on release day and I'm heading out of the country for 3 weeks. would love to use it wherever I go.
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Sent from my SAMSUNG-SGH-I897 using XDA App
it's that simple? i was under the impression I had to wait 6 months for that
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
There may be a waiting period that i'm not sure about. I was under the impression you just had to have the phone's imei number and verification you own the phone and they would give you the unlock code on request.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lol. Wondering same thing.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Sent from my I897 using XDA App
Nerz said:
Lol. Wondering same thing.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Yeah, no kidding. I'm glad dg is working on it though! I sent him a PM and he never did respond though.
dayv said:
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Click to expand...
Click to collapse
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
It is that simple. However, a lot of recent new phones had been put on 10-month exclusivity clause by AT&T that includes Captivate which means AT&T won't give you unlock code until 10 months after the phone has been released.
The normal waiting period is 90-day if you purchase on contract. But given GS2 will be on 10-month lock, you won't get your code until next summer.
post a tutorial on how to get it and ill upload it for you.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
First rule about fight club...
alton987 said:
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Click to expand...
Click to collapse
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
keeploading said:
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
Click to expand...
Click to collapse
zImage can't be dumped without a rooted /system.
Do you have root via kernel? If so, get a dump as described above so someone can root their /system and get the stock zImage
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
Stop kidding yourself Entropy. You're getting this phone. You're addicted now.
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Fenny said:
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Click to expand...
Click to collapse
Sweet. FYI, some processing is needed to make a dumped image Odin-flashable for native ext4 phones.
http://forum.xda-developers.com/showthread.php?t=1081239
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.
T-Mobile SM-N900T
Verizon SM-N900V
Sprint SM-N900P
Root de la Vega
By @designgears & @Chainfire
First off, a big huge thanks to Chainfire for his SuperSU app and help getting root setup manually.
Warning: This will wipe your data and internal sdcard, this will show custom system status. I cannot be held responsible for anything you do to your phone, rooting is optional, I am not forcing you to do it.
DO NOTE TAKE OTA UPDATES OR UPDATE WITH STOCK ODIN FILES THAT CONTAIN BOOTLOADER UPDATES!!
How To Enter Download Mode
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
IF YOU HAVE REACTIVATION LOCK ON, TURN IT OFF!
Go to Security Settings and turn the reactivation lock OFF, this is just a precaution.
Rooting Instructions
Remove the external sdcard (if you have one)
Boot into bootloader mode (see methods above)
Load the correct AP file into the AP slot in Odin (find your AP version in post #2)
Load the correct CSC file into the CSC slot in Odin (find your CSC version in post #2)
Click start in Odin, wait for it to fully flash
Let your device fully boot after flashing has completed
Copy the contents of Root_de_la_Vega.zip to the root of the internal storage
/My Computer/[Phone Name]/Phone/
root_de_la_vega.sh
root_files (folder)
Reboot (very important!)
After fully booting delete the files from the internal storage that were added previously
/My Computer/[Phone Name]/Phone/
root_de_la_vega.sh
root_files (folder)
Reboot (extremely important!)
Reinsert the external sdcard (if you have one)
That's all! Enjoy Root!
Bounty Pledges and Donations can be sent via Paypal:
Click Here (please include your xda username in the comments)
Bitcoin: 1F2FfTNnaXzFrGhUaB4iBD7EBegR5gh3qF
If you haven't already, pick up a copy of SuperSU Pro to support @Chainfire! Well worth the $2.49!
Root_de_la_Vega.zip / Odin v3.09
Root_de_la_Vega.7z
Get your version information:
Dial *#1234# (If SuperSU opens, press the back button)
Find your AP version below, Download the tar file
Find your CSC version below, Download the tar file
Find Your AP Version, Download Tar File
--------------------------------------------------------------------------------
Sprint N900PVPUBMI3_VEGA
N9005VJUBMI7_VEGA
N9005VJUBMJ1_VEGA
N9005XXUBMI7_VEGA
N9005XXUBMJ1_VEGA
N9005XXUBMJ3_VEGA
N9005ZHUBMI7_VEGA
N9006ZCUBMJ3_VEGA
N9008ZMUBMJ7_VEGA
N900SKSUBMJ1_VEGA
N900SKSUBMJ5_VEGA
N900W8UBUBMJ1_VEGA
N900W8VLUBMJ1_VEGA
N900W8VLUBMI5_VEGA
--------------------------------------------------------------------------------
DO NOT mix and match AP and CSC files! Doing so will trip KNOX Warranty!
Find Your CSC Version, Download Tar File
REQUEST THE CSC FILE IF YOURS IS NOT LISTED!! Failure to comply will may leave your warranty voided.
Sprint N900PSPTBMI3_CSC.tar.md5
CSC FOLDER <-- get your csc files here
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Question & Answer
"Root de la Vega" What kind of name is that?
It's named after Ralph de la Vega, CEO of AT&T Mobility.
Can I flash custom recovery/kernel without tripping KNOX flags?
No.
Will this set a tripped KNOX flag 0x1 back to 0x0?
No.
Can you help me with the drivers?
No, but you can head over here for help with drivers.
How do I get into download mode?
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
Will rooting or downgrading or flashing stock trip the Knox flags?
No, KNOX flags will not be tripped!
Will root survive a factory reset?
Yes, it does.
Do I need have to fully wipe my phone when rooting?
Yes. If you don't you will get lots of nasty force closes. I have yet to find a way around it.
Does Xposed Framework work?
Yes, it has been updated to work fully with the Note 3.
Will rooting report system as custom and display an unlocked lock on the initial boot screen?
Yes. It can be removed by installing Xposed Framework with Wanam Xposed and enabling Security hacks > Fake system status.
Titanium Backup is giving me problems, how can I fix it?
Check out this thread. If you are still having issues, please take your concerns to the dev, they are not related to rooting.
How do I open a 7z file?
With 7zip or IZArc!
Can I do this on OS X/Linux?
No, not until heimdall is updated to support the Note 3.
Can I unroot?
Yes, use SuperSU full unroot option or flash stock.
I am getting a "Prevention Information" popup after running a root app, how do I disable it?
From terminal emulator or adb shell as root, run; pm disable com.sec.knox.seandroid
Or freeze the Knox apps with Titanium Backup.
I am getting Force Closes after flashing, how can I fix it?
Make sure you are flashing the CSC file! If you are, try flashing AP and CSC separately.
HELP! I flashed N9005XXUBMJ3_N9005OXABMJ1 and now I am stuck in download mode! What do I do?!
You are mostly going to trip the KNOX Warranty at this point.
Flash this AP N9005XXUBMJ3_N9005OXABMJ1_BTU_RECOVER.tar.md5 (2.05 GB) and this CSC N9005OXABMJ3_CSC.tar.md5 (38.0 MB)
Whats stopping this being used for the N9005?
vinokirk said:
Whats stopping this being used for the N9005?
Click to expand...
Click to collapse
The method? Nothing, I am working on it
Don't use these files for it tho.
designgears said:
The method? Nothing, I am working on it
Don't use these files for it tho.
Click to expand...
Click to collapse
Good stuff!
Getting root whilst keepin know at 0x00 would be fantastic
OMG! I didn't believe someone could find a solution to root and maintain Knox on 0x0!
Please do the same for SM-9005 and a donation will arrive
Galaxy Note 3 | SM-9005 | Tapatalk
mouse100 said:
OMG! I didn't believe someone could find a solution to root and maintain Knox on 0x0!
Please do the same for SM-9005 and a donation will arrive
Galaxy Note 3 | SM-9005 | Tapatalk
Click to expand...
Click to collapse
What is your current build number and what carrier is the phone for?
settings > general tab > about phone > build number
JSS15J.N9005XXUBMJ1
I use Vodafone Italy but phone is no brand.
Awesome! That was fast! Thank you for this! sorry I used up all my Thanks for the day :laugh:
designgears said:
What is your current build number and what carrier is the phone for?
settings > general tab > about phone > build number
Click to expand...
Click to collapse
I havewritten on the othertopic but for N900 models i think here is better to write
Hey @designgears i see that you are really so talented developer here on xda. You really made this root quick for the friend who has asked you right now.
My paypal is not active yet but nowadays i want to activate it and send you donation for your hard works. Actually i dont own the at&t or roger version but i am sure that you deserve it and i also hope that maybe i can get your great root support on my device too (N9000Q).
As i said i will donate you as soon as my paypal has been activated because i think that you really deserve it.
And i can also tell you that lots of people from the Turkish forum website are also waiting for a root method like yours. Everyone would be so happy if you can do sth for us.
I also want to send you our firmware link and details:
N9000QXXUBMI5_N9000QTURBMI3_TUR
http://www.hotfile.com/dl/250045625/af09deb/N9000QXXUBMI5_N9000QTURBMI3_TUR.zip.html
Build number:
JSS15J.N9000QXXUBMI5
If you could do sth and help us about rooting our phones with knox 0x0 it would be really so appreciated.
Thank you very much for all you effort for this great community
I read something about CSCs of GN3, and i saw that you can flash any region and it wont trigger know but it doesnt change CSC, maybe its an option to use a single firm to all of them.
Can someone mirror the file? It seems to not be available..
DDRFAN said:
Can someone mirror the file? It seems to not be available..
Click to expand...
Click to collapse
Rebuilding it, tar'd the files wrong. It will be back in a bit.
designgears said:
Rebuilding it, tar'd the files wrong. It will be back in a bit.
Click to expand...
Click to collapse
Thanks for the speedy reply I'll be waiting.
Glad I waited to root! Thanks OP. Maybe you can enlighten us on how this works versus every other method?
Sent from my SM-N9005 using XDA Premium 4 mobile app
jetbruceli said:
Glad I waited to root! Thanks OP. Maybe you can enlighten us on how this works versus every other method?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hex editing the system img to call to a script on the sdcard
designgears said:
Hex editing the system img to call to a script on the sdcard
Click to expand...
Click to collapse
Ok great lol! I am no dev or anything but this is just plainly great news for the note 3 users and for anyone worried Knox.
Also it's an awesome "Haha look what I did Mr. Manufacturer!"
Sent from my SM-N9005 using XDA Premium 4 mobile app
TheRecRuiT89 said:
I havewritten on the othertopic but for N900 models i think here is better to write
Hey @designgears i see that you are really so talented developer here on xda. You really made this root quick for the friend who has asked you right now.
My paypal is not active yet but nowadays i want to activate it and send you donation for your hard works. Actually i dont own the at&t or roger version but i am sure that you deserve it and i also hope that maybe i can get your great root support on my device too (N9000Q).
As i said i will donate you as soon as my paypal has been activated because i think that you really deserve it.
And i can also tell you that lots of people from the Turkish forum website are also waiting for a root method like yours. Everyone would be so happy if you can do sth for us.
I also want to send you our firmware link and details:
N9000QXXUBMI5_N9000QTURBMI3_TUR
http://www.hotfile.com/dl/250045625/af09deb/N9000QXXUBMI5_N9000QTURBMI3_TUR.zip.html
Build number:
JSS15J.N9000QXXUBMI5
If you could do sth and help us about rooting our phones with knox 0x0 it would be really so appreciated.
Thank you very much for all you effort for this great community
Click to expand...
Click to collapse
Uploaded!
Other files are back up to!
Can you please make this work for wind mobile n900w8! I will post the build number when I get home
Sent from my Nexus 4 using XDA Premium 4 mobile app
Please for n9005!!! :thumbup::thumbup::thumbup:
Enviado desde mi SM-N9005 usando Tapatalk 2