Develop Bugs

Can I revese back after root so I don't void the garanty ?

Well Can I ? and how is this done.. because I want to download OC program and for that I must have a rooted phone (Want to make it save more power)

i would like to know this too

to revert you would need to flash a "stock rom" to your device.

jackdaniels_lee said:
to revert you would need to flash a "stock rom" to your device.
Click to expand...
Click to collapse
And where does one find this ? And will it "restore" my warranty ?

You can make a backup before flashing/applying anything to your phone, and then flash that backup back to the phone later. Technically, that isn't going to restore your warranty, by meddling with the phone you lost it for good - but if you do it correctly your provider won't be able to tell.
The bigger problem is: If your phone is broken and you want to bring it back, there's probably no way to flash back the original firmware first (what with the phone being broken and all). But I guess you can always send it to an HTC repair center (not for free though).

eh?
you need to "restore" the system files you have modified (you loose your warranty if you modify system files?!? :-| ).
if you have only pushed su and superuser.apk you just need to delete superuser.apk and push the su binary from the wwe version posted in this forum...or if you have a nandroid backup, just restore it

Anywhere to find the Stock Rom online?

Tom_Codon posted one a while back

Ah sorry yes. I saw that but thought it was a ported one for the G1 because he posted it early July before release date. Thanks.
Is the method of flashing back the same as rooting? Just instead of using the rooted rom put the htc rom in its place in the sdk folder?

veejayjameson said:
Ah sorry yes. I saw that but thought it was a ported one for the G1 because he posted it early July before release date. Thanks.
Is the method of flashing back the same as rooting? Just instead of using the rooted rom put the htc rom in its place in the sdk folder?
Click to expand...
Click to collapse
what do you mean by rooted rom? if you followed one of the tutorials in hero forums( if you added only Superuser.apk and su) to go back to "stock" you need to:
- boot with the modified recovery found here http://forum.xda-developers.com/showthread.php?t=543571
- extract the su binary (/system/bin/su ) from the original hero rom here: http://forum.xda-developers.com/showthread.php?t=533808 , and put it on the tools folder of sdk (or wherever you want... if you have set PATH correctly),
then :
* adb shell mount /system
* adb shell rm /system/app/Superuser.apk (if you have it)
* adb push su /system/bin/
* reboot
now you have again the stock rom

Ah thank you.
Still deciding whether to keep my device rooted or not. Seeing as my wifitether doesn't work yet there's not that much else I wanted to do.
Decisions decisions... lol

4.0.4 Stock boot.img with flags to set adb to root

Here you guys go.
Credit goes to imo for helping me with the ramdisk.
http://aospdev.com/rhcp/dev/404boot_root.img

Doesn't work.
Flashed this via fastboot, booted into CWM, flashed su.zip, rebooted phone, still no root.

M Diddy said:
Doesn't work.
Flashed this via fastboot, booted into CWM, flashed su.zip, rebooted phone, still no root.
Click to expand...
Click to collapse
su/superuser wont work. Its not compat with 4.0.4
Thats why you need this modded boot.img so you can have root over adb.
it's tested and it works.

Ah, but still no root in the GUI?

M Diddy said:
Ah, but still no root in the GUI?
Click to expand...
Click to collapse
Correct. Not until Chains fixes superuser or SU.
I pasted the logcat to his git.

Out of curiosity then, how are some managing to get SU to work after upgrading to 4.0.4?
I've seen plenty of posts around of users stating it's fine.

M Diddy said:
Out of curiosity then, how are some managing to get SU to work after upgrading to 4.0.4?
I've seen plenty of posts around of users stating it's fine.
Click to expand...
Click to collapse
Your guess is as good as mine.
Im not sure if they have gui root or adb root.
also, many are getting tricked by the hybrid rom (Like mine) which is 4.0.3 (with 4.0.4 props) and people are saying its true 4.0.4 src built which is 100% lie

rhcp0112345 said:
Your guess is as good as mine.
Im not sure if they have gui root or adb root.
also, many are getting tricked by the hybrid rom (Like mine) which is 4.0.3 (with 4.0.4 props) and people are saying its true 4.0.4 src built which is 100% lie
Click to expand...
Click to collapse
That's what I'm thinking. People are updating radios and bootloader and saying they're on 4.0.4.

M Diddy said:
That's what I'm thinking. People are updating radios and bootloader and saying they're on 4.0.4.
Click to expand...
Click to collapse
Yeps!!!!!!!

In order to fix su.
You can try to flash http://downloads.androidsu.com/super...ghi-signed.zip
If you get an assert failure.
You will need to unzip that. and put the su bin in place via recovery then set perm 04755 to it.
Hope this helps. Comes from chains

rhcp0112345 said:
In order to fix su.
You can try to flash http://downloads.androidsu.com/super...ghi-signed.zip
If you get an assert failure.
You will need to unzip that. and put the su bin in place via recovery then set perm 04755 to it.
Hope this helps. Comes from chains
Click to expand...
Click to collapse
I flashed this from CWM, and it did the trick:
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
Thanks to adrynalyne for the info.

yourfriendmat said:
I flashed this from CWM, and it did the trick:
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
Thanks to adrynalyne for the info.
Click to expand...
Click to collapse
Yep, That also works

I can confirm this works!!!! Great find
thanks

[BOOT] [GSM] Insecure boot image for IMM76I

XDA user stesmo has compiled an insecure boot image based off the IMM76I source if any one is interested. Completely stock with ro_secure set to 0.
He asked me if I could post it here given that his post count is not high enough to post in the dev section.
You can download it from this post.
This is NOT my work, so if you've found this image useful, thank stesmo in his post.

What is the difference between a normal secure boot and an insecure one?

Theshawty said:
What is the difference between a normal secure boot and an insecure one?
Click to expand...
Click to collapse
An insecure boot image enables root access by default on boot.

efrant said:
An insecure boot image enables root access by default on boot.
Click to expand...
Click to collapse
Root access for what, exactly?

I have already did the same thing here http://forum.xda-developers.com/showthread.php?t=1610854

Theshawty said:
Root access for what, exactly?
Click to expand...
Click to collapse
I enables root access for the shell user. When you start ADB and open a shell, you will have root immediately, whether your device is rooted or not. It also allows you to use "adb remount" to mount your system read-write from ADB.

bigeyes0x0 said:
I have already did the same thing here http://forum.xda-developers.com/showthread.php?t=1610854
Click to expand...
Click to collapse
Woops. I didn't see that. I did search, but I searched for "insecure" not "unsecured" . Maybe you should change the word in the title to insecure.
Mods, I see no reason for two threads. This one can be closed.

Thread closed on OP's request.
Mark.

[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.

Todays OTA security update on rooted stock 4.1.2 w DPI Mod

Hey there,
today my N7100 surprised me by anouncing that there is a firmware update available. Must be that 4.2(.2). [edit: no, unfortunately it's just a security update] In all my years with my i9000 I never OTA updated because I was always on custom ROMs and like lightyears ahead of the official update cycle, but now I'm uncertain.
Of cause I want to keep root / reroot at least for AFWall and especially the 240dpi is very important to me... will OTA override those settings, going along with those as well the Xposed settings? Any experiences yet?
And if, will rooting and Triangle away work like before on the new version as well? I am as the title says on the stock 4.12 with root and counter reset according to this manual: http://forum.xda-developers.com/showthread.php?t=1896696
On my SGS I'd just give it a shot, but the Note is just like a month old (so me still a bit nooby) and at the moment I don't need&want to mess around with it too much - Especially because all this counter stuff is bugging me ^^
Any advices? I know that's probably not really helpful, but probably someone has the same concerns too and just wants to share his thoughts too
Guess unrooting before OTA updating would be the safest way anyway.. wouldn't it be? ... Kinda have a lack of motivation here ^^

I think that is just a security update. There is still no word on 4.2.2 yet
Sent from my GT-N7100 using xda app-developers app

hendog4385 said:
I think that is just a security update. There is still no word on 4.2.2 yet
Click to expand...
Click to collapse
Good point, found this: http://www.sammobile.com/2013/06/18...ty-update-galaxy-note-ii-still-android-4-1-2/
Questions still persist though..
Adjusted the thread title and initial post to reduce confusion.

Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2

dr.ketan said:
Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2
Click to expand...
Click to collapse
Awesome! Thanks! (will give it a shot as soon as I have a bit mroe time and want to reboot into WIndows. A shame that there's no proper - as easy to use as ODIN - alternative for Ubuntu)
Is this usual, that flashing stock with some extra apks like the su stuff doesn't increase the counter? Or is it that just flashing PDA doesn't affect it? Am curious..

Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Sent from my GT-N7100 using xda premium

XXDMF2 is probably the same as XXDME2 except they could only be bothered to work on/release that geographic variation last?

dr.ketan said:
Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Click to expand...
Click to collapse
That's great thanks. So basically I could as well push some more apps with my installation by following your, how I find very clear and nice to follow, Tutorial in your Pre-Rooted-Thread and varying the step where the superuser.apk is being added from:
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
to
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
cp myFavoriteApp.apk temp/app/myFavoriteApp.apk
chmod 0644 temp/app/myFavoriteApp.apk
Right? So this way I could have a Stock ROM that comes with my usual App Setups by default when flashing and still leaves my Counter untouched..That's just wonderful, spares a lot of time after wiping..since in this case there is no wipe that's not needed here I know, but having a clean phone without having to install everything manually again would be nice anyway.
Wondering what weird things would happen if I tried to install apk's that are already installed.. will they be skipped..guess so, I mean, superSU is installed as well here already.. ?
Thanks for teaching me A pleasure to learn

When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Sent from my GT-N7100 using xda premium

dr.ketan said:
When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Click to expand...
Click to collapse
Ah I see, sounds reasonable... thanks for clearing that up!

Hey guys, im on the same state like the op.
i have stock rom, but rooted with odin and on TWRP recovery, busybox, superuser and triangleaway.
can i easily run this update without issues or should i completely go back to stock?
thanks, greetz, hope for a fast answer :|

Done! Without problems. but iam lose root, busybox and su

I updated yesterday, rooted stock 4.1.2 with xposed. Flashed new non-rooted (original) ROM from SAM mobile.
upon flashing, I had to
1) root agiain
2) install SU again from apk,
3) run SU and it updated binary
4) run Triangle away and reset counter
5) run Xposed framework and press "install", reboot
6) run busybox and let it auto-install
Then I was able to manualy change sounds for keypress/press and bootanimation.
All well.
D,

Just flashing stock prerooted ROM, you can skip first 4 steps