Develop Bugs

[ROOT] Wont Trip Flash Counter (Bell Canada I747M)

Hey Everyone!
This is my first time doing an official ROM repact by injecting Root into the ROM itself so as to not trip the flash counter!
This is for Bell's Canadian S3 SGH-I747M firmware: I747MVLALE8
I know this has recently already been done by MrRobinson for the Canadian carriers but I have done mine slightly differently.
Most of you im sure know of Chainfire and his amazing work, well I love the work he does and it is my opinon that his Root app SuperSU is better then the Superuser one, this may be very minor or non exisist to some people and it all really boils down to Personal perference but as such I perfer SuperSU and love it and want to support his work!
I have tested this myself on my own S3 works great, counter does not increase, and flash time only took me 6 minutes! (some people were complaining about the other root injected roms taking 10 minutes and upwords to 20 to complete)
IMPORTANT NOTE:
This rom has been injected with Chainfires CF root but it is only his SuperSU root app and does not contain any custom CWM recovery or Manager app. Chainfire custom builds his CWM manager app specific to certain devices and is not compatible with the North American varients.
To get the North American LTE version of CWM Recovery please see team epics website at:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
To install this recovery without tripping the counter you will need to manually copy it over to the memory card block which contains the recovery section of your phone. Once downloaded extract the recovery.img file out of the tar and place it into your sdcard.
Either through ADB shell or using a terminal emulator app on the phone run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Remember to do "su" first to grand root access to the ADB shell or terminal emulator otherwise you will not be given the permissions to do the recovery copy on the 2nd command as mentioned above.
1 final note, like all the other root injected roms for the S3, these root methods currently do have not busybox built into them so it is highly recommended for you to download and install the busybox app off the play store [the one by Stephen (Stericson)] to get even more functionality for your rooted device.
~~Link Removed~~
My apologies in advance for uploading to filefactory as they are known to be slow sometimes on downloads. If anyone is able to host it for faster speeds that would be awesome.
EDIT:
For some reason the cache file doesn't properly install and so you are left with a blank CSC. Currently trying to figure out why this is happening as I havn't done anything to the CSC file to begin with. In the mean time I have taken down the link. I recommend getting the one made by MrRobinson for flashing Bells Rom
View the sticky post for his here:
http://forum.xda-developers.com/showthread.php?t=1739426

There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium

jthrasher47 said:
There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am aware of this, I actually made a point of saying so in my post but I guess you skimmed it and didn't see that part?.
I also explain that mine is a bit different and why.

Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.

dbzgod said:
It took me longer because I had to do it without a Linux box, funny enough I manage to do it using my Rooted S2 phone lol.
Click to expand...
Click to collapse
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?

danny6514 said:
Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.
Click to expand...
Click to collapse
Yeah they can be changed out, but I released this anyways because I had started work on it right away when the firmware was released and even though MrRobinson had put out root injected roms before me I still wanted to complete what I started and not leave it half done.
I would of had this out at about the same time if not before the others but because of time contraints on my part as well as running into a few problems via doing the whole repack and inject a unique way on my rooted S2 Android phone. Instead of a Linux box I figured out how to do almost all of the repacking steps on an Android phone and then I was delayed trying to figure out 1 important step that required a full Linux box, but discovered an alternate means to do so on Windows.
At any rate I just wanted to post my work (even though late coming) and offer people this alternate root injection Rom.
qwer777 said:
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?
Click to expand...
Click to collapse
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.

dbzgod said:
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.
Click to expand...
Click to collapse
Damn! I was really excited! Oh well. I'll need to find me a windows pc.

removing root and resetting back to stock

Hi Everyone,
Sorry if this has been discussed in lengths somewhere, I wasnt able to find full information so I just wanted to make sure I got the right idea before proceeding with removing root. I need to go back to full stock no root or recovery. according to some info on this forum
http://forum.xda-developers.com/showthread.php?t=1739426
I need to use Odin to flash the stock image for my phone (bell). after doing that i need to go in with root explorer or adb shell and delete the superuser and associated binary files, this is where I am not 100% sure does this mean the following 3 files:
1- /System/app/SuperSU.apk
2- /System/xbin/busybox
3-/System/xbin/su
are there any other files that need to be removed?
thank you very much for the help.

You just need to use a nonrooted stock img, then boot into factory recovery and do a factory reset. No need to manually attempt to remove root

[ROOT] For all you that don't know what and how

Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.

someone755 said:
Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.
Click to expand...
Click to collapse
A Simple question, how can i get recovery, if for get it, i need first a root phone?

SteBanVe said:
A Simple question, how can i get recovery, if for get it, i need first a root phone?
Click to expand...
Click to collapse
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app

bluechelsea said:
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
i have Xperia S 2.55, and bin4ry method doest work. To apply this method, i repeat my question how can i get recovery, if for get it, i need first a rooted phone?

someone755 said:
1. You need a phone with a recovery...
Click to expand...
Click to collapse
How do you suppose we get a custom recovery without using different tools or unlocking bootloader?

Yes great guide, but only for UB ... for LB you need root BEFORE you install CWM...
al with .55 FW i recomend - flash any older rootable FW, root it, install CWM ... via CWM flash stockbased rom ( KA, XTX ) and thats all... or you an flash prerooted .55 FW ....

Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!

someone755 said:
Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!
Click to expand...
Click to collapse
I installed the app now how do i install recovery and boot into it?
Sent from my LT26i using xda app-developers app

Return to stock with a broken USB connector

Hi all
My USB connector does not work, I would send him assistance, but unfortunately my device has the bootloader unlocked, with root and rom Mincov6.
I tried to use Mobile Odin, I downloaded directly from the phone the factory image of 4.2.2 and tried to open the file .tgz, however, tells me: "Partition could not be found in file."
What can I do? I'm desperate, I await your response
Thanks in advance.
Sorry for english, but i'm italian :crying:

http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128

bodh said:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
Click to expand...
Click to collapse
My device is GSM, not Verizon

It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.

bodh said:
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
Click to expand...
Click to collapse
From what I understand, who used the Verizon tar in GSM, brock the device.
Now, I can not find anywhere the. Tar for GSM..

This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..

bodh said:
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
Click to expand...
Click to collapse
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?

Try this
ciccionicosia said:
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Click to expand...
Click to collapse
You should've replaced the stock recovery before locking the bootloader. You can try finding a flashable .zip of the stock recovery, but it'd probably have to be made. Has the device ever gotten an OTA update? I'm thinking you could use the following OTA script and patch to reflash the stock recovery in a very minimal sort of way.
First, you'll have to re-root by installing supersu.zip from sdcard download via custom recovery(which youll need to remove later).
Install Root Browser Lite by jrummy, and say no to installing the additional features (you may have to remove some binaries from your sdcard later after unrooting).
Unzip the attachment.
Place the install-recovery.sh in /system/etc/ with r-xr--r-- permissions and root root ownership and group ownership (via long pressing the file once it is in place, first permissions, then ownership).
Place the recovery-from-boot.p in /system/ with rw------- permissions and root root ownership and group ownership (same way as above).
Now power down.
Boot into recovery from fastboot (vol up+down+power, scroll with volume keys until the top says recovery, then press power).
Does it say android recovery on top, or is it still your custom?
If it's stock, let it sit until it boots on its own.
Remove the supersu.apk and su binary via root browser.
Remove rootbrowser and its binaries on the sd.
You should now be in business.
P.S. You could also look for an odin flashable .tar for your device, and flash it to return, but i think that'd be more complicated for you. Those files I provided are put in place during every ota update, and I believe this should work for you.

[Q] T-Mobile S4 Will Not Root (Initial Device Update Issue)

I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?

re: rooting
mrjetpacks said:
I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?
Click to expand...
Click to collapse
Next time don't rely on any Youtube videos
Returning your phone will not help you at all, it still will need to be rooted whether you allow the
OTA update of the firmware or not.
Here is what you need for rooting your phone:
Download ODIN which is a windows application: http://k0nane.info/rom/odin-307.zip
Download the Odin flash TAR file TWRP custom recovery here: http://downloadandroidrom.com/file/...y/TWRP/openrecovery-twrp-2.5.0.0-jfltetmo.tar
Download the M919 MDL Rooter Odin flash TAR file here: http://batakang.com/ftp/SGH-M919/ROOT_M919UVUAMDL.zip
After you downloaded all 3 files create a new folder on your
computer's desktop and copy all three of the files into it.
Open ODIN to flash these two TAR files in the PDA slot in Odin after you put your phone into download mode.
Flash the TWRP custom recovery TAR file first and then flash the M919 MDL Rooter TAR file with Odin.
After doing that you shall be rooted.
If you want or need more specific information about using Odin and rooting here is a good link for you: http://forum.xda-developers.com/showthread.php?t=2268880
Good luck!

mrjetpacks said:
I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?
Click to expand...
Click to collapse
From experience trust me make sure u use oudhs cwm recovery first... yes others work but I had alot of issues flashing roms after I got mine.
This is clean and simple method if you havent got it yet.
Download Odin.3.07
Dload MDB-SETuidoff .zip NOT MDL Thats just my opinion, do as you want though.
Dload and Use superuser by koush or chainfire.
NEXT.....
Odin the oudhs cwm tar file
Then boot into recovery
Do a full reset first.
Flash MDB-SETuidoff .zip
"QUOTE" THIS SEEMS TO WORK BETTER THEN MDL ROOT ZIP.
And works on new may 7th ota and stock shipped firmware.
Continue to wipe cache
Then flash super user . zip
Then reboot Phone
Without doing it this way I had reboot freezes with the MDLroot .zip
The MDB-SETuidoff .zip gets it all squared away... its on google and in xda ...it is real important it bypasses samsungs new restricted kernel that messes with rooting.
Before I figured that out I had root with MDL zip,but couldn't reboot after a flash and kept loosing superuser after attempting to reboot.
Sent from my SGH-M919 using xda app-developers app

Misterjunky said:
Next time don't rely on any Youtube videos
Returning your phone will not help you at all, it still will need to be rooted whether you allow the
OTA update of the firmware or not.
Here is what you need for rooting your phone:
Download ODIN which is a windows application: http://k0nane.info/rom/odin-307.zip
Download the Odin flash TAR file TWRP custom recovery here: http://downloadandroidrom.com/file/...y/TWRP/openrecovery-twrp-2.5.0.0-jfltetmo.tar
Download the M919 MDL Rooter Odin flash TAR file here: http://batakang.com/ftp/SGH-M919/ROOT_M919UVUAMDL.zip
After you downloaded all 3 files create a new folder on your
computer's desktop and copy all three of the files into it.
Open ODIN to flash these two TAR files in the PDA slot in Odin after you put your phone into download mode.
Flash the TWRP custom recovery TAR file first and then flash the M919 MDL Rooter TAR file with Odin.
After doing that you shall be rooted.
If you want or need more specific information about using Odin and rooting here is a good link for you: http://forum.xda-developers.com/showthread.php?t=2268880
Good luck!
Click to expand...
Click to collapse
**
When I click on the 2nd link, the page I go to is download for "Zip Opener"... Is that correct?

mrjetpacks said:
**
When I click on the 2nd link, the page I go to is download for "Zip Opener"... Is that correct?
Click to expand...
Click to collapse
**
I was able to retrieve the file from the 2nd link. I have flashed the file [from the third link] to my device via ODIN. ODIN says everything "PASS"ed, but my device still is on the download mode screen with a full downloaded blue bar on the bottom, and I have not flashed that other file "ROOT_M919 etc etc.", yet [because I cannot find anything in the file after unzipping it that will go with ODIN].

abcdefg1234567 said:
From experience trust me make sure u use oudhs cwm recovery first... yes others work but I had alot of issues flashing roms after I got mine.
This is clean and simple method if you havent got it yet.
Download Odin.3.07
Dload MDB-SETuidoff .zip NOT MDL Thats just my opinion, do as you want though.
Dload and Use superuser by koush or chainfire.
NEXT.....
Odin the oudhs cwm tar file
Then boot into recovery
Do a full reset first.
Flash MDB-SETuidoff .zip
"QUOTE" THIS SEEMS TO WORK BETTER THEN MDL ROOT ZIP.
And works on new may 7th ota and stock shipped firmware.
Continue to wipe cache
Then flash super user . zip
Then reboot Phone
Without doing it this way I had reboot freezes with the MDLroot .zip
The MDB-SETuidoff .zip gets it all squared away... its on google and in xda ...it is real important it bypasses samsungs new restricted kernel that messes with rooting.
Before I figured that out I had root with MDL zip,but couldn't reboot after a flash and kept loosing superuser after attempting to reboot.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This looks like a great guide. It actually makes sense. Problem is, I am on Mint and I'm trying to use Heimdall and I absolutely CANNOT get it to successfully flash the recovery tar.