Database Develop

[Q] Root with Stock ROM and Recovery

Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks

leo.sutton said:
Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks
Click to expand...
Click to collapse
Yes its possible. In fact, last time I used to install binary and apk on top of stock ROM. I flash it from here:
http://androidsu.com/superuser/

petalyaa said:
Yes its possible. In fact, last time I used to install binary and apk on top of stock ROM. I flash it from here:
http://androidsu.com/superuser/
Click to expand...
Click to collapse
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.

leo.sutton said:
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.
Click to expand...
Click to collapse
You need root to install SU afaik

leo.sutton said:
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.
Click to expand...
Click to collapse
Follow these steps :
1) Download SU binary+APK and put it in the sdcard. The downloaded file is a flashable zip.
2) Unlock bootloader (Can be done using HTCDev)
3) Flash custom recovery
4) Enter recovery then flash the zip file you just put in step 1.
5) Wait till it finish flashing, then reboot, you should be rooted now.

petalyaa said:
Follow these steps :
1) Download SU binary+APK and put it in the sdcard. The downloaded file is a flashable zip.
2) Unlock bootloader (Can be done using HTCDev)
3) Flash custom recovery
4) Enter recovery then flash the zip file you just put in step 1.
5) Wait till it finish flashing, then reboot, you should be rooted now.
Click to expand...
Click to collapse
Okay, thanks, but its not possible with stock recovery? I thought your first answer indicated it was.

leo.sutton said:
Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks
Click to expand...
Click to collapse
As far as I know, you just have to flash your stock recovery whenever you want to do ota updates. I converted my one to a developers edition a while back and whenever an ota update came out, i would flash my recovery, update, then put twrp back on. It never gave me any trouble because of my root.

an0ther said:
As far as I know, you just have to flash your stock recovery whenever you want to do ota updates. I converted my one to a developers edition a while back and whenever an ota update came out, i would flash my recovery, update, then put twrp back on. It never gave me any trouble because of my root.
Click to expand...
Click to collapse
Aaah, sorry for the confusion, i mean on stock ROM and not recovery. I'm not really sure if its possible to flash the superuser zip in stock recovery or not. I think its not possible. If you want official OTA, if im not mistaken, it doesnt really matter which recovery you're on. Just use twrp and flash the superuser zip and you're good to go..

petalyaa said:
Aaah, sorry for the confusion, i mean on stock ROM and not recovery. I'm not really sure if its possible to flash the superuser zip in stock recovery or not. I think its not possible. If you want official OTA, if im not mistaken, it doesnt really matter which recovery you're on. Just use twrp and flash the superuser zip and you're good to go..
Click to expand...
Click to collapse
You have to have stock recovery to get a true ota update. That is how it updates. If you download an ota update, first thing it does is go into recovery to flash it. It will end up going into your custom recovery and just sitting there. Your phone firmware and hboot must match the one of the current rom, but it has to have stock recovery to do the actual update. First time it boots after ota, you may loose your su, but just put custom recovery back on and flash it real quick and you should be good to go then you can flash back to stock recovery and twrp should fix your root if it has a problem. I hope this helps. You know you can just download the updates and flash them yourself too. Btw, newest 3.22 rom sucks! It has many problems that are all over the forums. Proximity sensor has gone to hell, and your messages contact pictures disappear every time you get a new text.

an0ther said:
You have to have stock recovery to get a true ota update. That is how it updates. If you download an ota update, first thing it does is go into recovery to flash it. It will end up going into your custom recovery and just sitting there. Your phone firmware and hboot must match the one of the current rom, but it has to have stock recovery to do the actual update. First time it boots after ota, you may loose your su, but just put custom recovery back on and flash it real quick and you should be good to go then you can flash back to stock recovery and twrp should fix your root if it has a problem. I hope this helps. You know you can just download the updates and flash them yourself too. Btw, newest 3.22 rom sucks! It has many problems that are all over the forums. Proximity sensor has gone to hell, and your messages contact pictures disappear every time you get a new text.
Click to expand...
Click to collapse
Okay, thats new for me, never know that we need to be on stock recovery for official update.
That's why I never wait for OTA.. I used ROM in this forum and so far I never have any issue that U mention above..

Problem installing Clockworkmod

hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418

Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.

sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test

thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....

devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?

jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.

devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.

skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems

[Q] Lollipop 5.0.2 update root access?

I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?

egwktm said:
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
Click to expand...
Click to collapse
You have to "Full unroot" in SuperSU settings and restore the stock recovery. Otherwise OTA will fail. After the OTA is installed, You can easily return to TWRP and flash SuperSU.

okay thanks! also instead of twrp could I use chainfire again?

Unfortunately, i tried to install OTA and now every time i turn on my phone it reboots and tries to install 5.02 only to get an error and it stays at twrp menu. So what can i do now?

lol after many reboots phone decided to tell me that update was unsuccessful so it works again.

more details pls for a beginner
I made the same mistake trying to flash OTA 5.02 over rooted device 4.4.4 . I got out of the loop by moving the download zip from system/cache to external sd...
just wanting to make sure I do all the right things and in order:
so in Super SU I go the FULL UNROOT
how do I then restore stock recovery?
Once I I have restored it what are the steps for the zip and install via stock recovery?
sorry about the boring questions - it's still a bit of a jungle for a beginner

egwktm said:
okay thanks! also instead of twrp could I use chainfire again?
Click to expand...
Click to collapse
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.

Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?

dpdp73 said:
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
Click to expand...
Click to collapse
No

doppelhelix said:
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Click to expand...
Click to collapse
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone? Some people therefore recommend the Chainfire CF-Auto-Root instead.
So after unlocking bootloader can I flash TWRP in fastboot mode and superSU afterwards without those kind of problems?

Wolfcity said:
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone?
Click to expand...
Click to collapse
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.

doppelhelix said:
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
Click to expand...
Click to collapse
Thx a lot for your explantion.
This was one of the things that irritated me right from the start when I was checking out the possibilities of custom recovery/root within 5.0.
I heard about the file-renaming thing but didn´t realize that superSu will do the job too and that it is a Nexus "feature" at all.
Helped me very much!

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

[HELP] How to Install TWRP without PC.

Hello everyone,
I'm in a little trouble. I need to install custom recovery on my Xperia SP C5302 but I have no PC.
How can I install TWRP ( preferred ) / CWM/Philz on my device ? Is there any way ?
Thank You.
Note : There's a cyber cafe beside my house. But all their computers are running Windows XP.
If there's no way to install without PC then can I be able to install custom recovery on my device with Win XP ?
Thanks again.

Do you have root?

TechnoSparks said:
Do you have root?
Click to expand...
Click to collapse
Yes I'm rooted and my bootloader is unlocked.

Are you ready to bear any risks?

TechnoSparks said:
Are you ready to bear any risks?
Click to expand...
Click to collapse
Yes I'm. but what kinda risk ? soft brick ? or something else ?

rhrokib said:
Yes I'm. but what kinda risk ? soft brick ? or something else ?
Click to expand...
Click to collapse
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.

TechnoSparks said:
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.
Click to expand...
Click to collapse
okay. Is there any way to install TWRP without PC then ?

or any custom recovery. philz, CWM anything

Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Code:
dd if=/storage/emulated/0/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel bs=4096
Reboot to check if recovery is accessible after hitting volume up when LED lights up

TechnoSparks said:
Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Reboot to check if recovery is accessible after hitting volume up when LED lights up
Click to expand...
Click to collapse
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.

rhrokib said:
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.
Click to expand...
Click to collapse
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup

TechnoSparks said:
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup
Click to expand...
Click to collapse
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?

rhrokib said:
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?
Click to expand...
Click to collapse
What ROM are you using? You need a ROM that can boot a FOTAKernel recovery, and not all of them can (especially stock based ones, since stock by default doesn't allow this).

Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.

TechnoSparks said:
Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.
Click to expand...
Click to collapse
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?

rhrokib said:
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?
Click to expand...
Click to collapse
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.

TechnoSparks said:
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.
Click to expand...
Click to collapse
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.

rhrokib said:
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.
Click to expand...
Click to collapse
Alright, good to know you finally installed the recoveries. 4.3 Stock ROM does not support my method explained in my recent post. And no problem!