Database Info

[HOWTO] Manually Flash Koush's ClockworkMod Recovery (If You Are Already Rooted)

1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).
2. Write down the filename of the recovery image EXACTLY as it is written (i.e. recovery-clockwork-2.5.0.1-heroc.img).
3. Put the recovery image file on the SD card (not in any folders).
4. Download Terminal from the Market if you don't already have it and install it (there are a few different terminals in the Market some have an onscreen keyboard and some don't experiment till you get one, also hold down Menu in some of them to bring up the onscreen keyboard if you don't see it).
5. Open the Terminal program and type the following (with hitting enter at the end of each line).
su
flash_image recovery /sdcard/name-of-recovery.img
6. In the above text, replace name-of-recovery.img with the name of your recovery image (make sure the .img is on the end).
7. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM Manager and Clockwork Recovery Image
Superuser Black Screen, Lockup Solution's
Code:
[B][COLOR="Red"]Enable USB Debugging:[/COLOR][/B]
Press the Home button.
Press the Menu button.
Select Settings > Applications > Development.
Make sure that USB Debugging is checked. If not, check it.
[B][COLOR="red"]Clear Superuser data:[/COLOR][/B]
Press the Home button.
Press the Menu button.
Select Settings > Applications > Manage applications.
Find Superuser Permissions on the list. Tap it.
Tap “Clear data” and “Clear cache” if they’re enabled.

Thanks for that!!

forget what i said....found it lol

silverxj said:
Thanks for that!!
Click to expand...
Click to collapse
your welcome i know that not everyone is gonna have access to adb or want's to play with command prompt's
this method is a really simple quick way around using adb that get's the job done

first post updated with link's

ARoiD said:
your welcome i know that not everyone is gonna have access to adb or want's to play with command prompt's
this method is a really simple quick way around using adb that get's the job done
Click to expand...
Click to collapse
is there anyway to do this not using the command prompt? my SU request does not work anymore apparently...

DrededStar87 said:
is there anyway to do this not using the command prompt? my SU request does not work anymore apparently...
Click to expand...
Click to collapse
your phone is not rooted are you running the stock os or a custom rom?

ARoiD said:
your phone is not rooted are you running the stock os or a custom rom?
Click to expand...
Click to collapse
im running fresh 2.0d

DrededStar87 said:
im running fresh 2.0d
Click to expand...
Click to collapse
did you get prompted by Superuser after you entered su?

ARoiD said:
did you get prompted by Superuser after you entered su?
Click to expand...
Click to collapse
my screen just goes black, not the full thing, but i get an error message that says it stopped unexpectedly and must force close

DrededStar87 said:
my screen just goes black, not the full thing, but i get an error message that says it stopped unexpectedly and must force close
Click to expand...
Click to collapse
restart your phone and try again when you get prompted select always allow

ARoiD said:
restart your phone and try again when you get prompted select always allow
Click to expand...
Click to collapse
i still get the black screen after restarting

DrededStar87 said:
i still get the black screen after restarting
Click to expand...
Click to collapse
go into manage applications and clear the cache of Superuser then try again

Superuser solution's added to first post

Re: How To: Flash a New Recovery Image (If You Are Already Rooted) | The Unlockr
thanks for all the help guys, I have the green recovery screen now
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

DrededStar87 said:
thanks for all the help guys, I have the green recovery screen now
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
glad it worked out for ya

YES it worked(yay) i have super fast 728 one btw can i delete the recovery img off sd card now that it worked?

rulyskull said:
YES it worked(yay) i have super fast 728 one btw can i delete the recovery img off sd card now that it worked?
Click to expand...
Click to collapse
it's safe to remove the recovery image from your sdcard after you know it successfully flashed

I'm getting a huge number of read/write errors on this via Terminal - Attempting to flash Amon_RA 1.7 over CM 1.4 on Cyanogen 5.0.7...

kidblue said:
I'm getting a huge number of read/write errors on this via Terminal - Attempting to flash Amon_RA 1.7 over CM 1.4 on Cyanogen 5.0.7...
Click to expand...
Click to collapse
This is for the Sprint CDMA Hero only.

[PC-APP] SGN3 Mod Tool

DOES IT WORK? I am yet to receive my SGN3, so I haven't been able to test.
I made this tool originally for SonyEricsson Xperia X10, but have now modified it to work for our Samsung Galaxy Note 3. I hope it will make life a little easier when modifying files on the device. It uses ADB to pull and push files, change file permissions and much more - so users don't need to remember long command prompt/terminal emulator commands! It also has a nifty little application manager, which allows for quick installation, backup, and removal of both pre and self -installed software. It has a LogCat function to read and save logs on the go when investigating errors, as well as functionality to decompile/recompile APK, JAR and ODEX files, sign and zipalign APKs, and decompile System images. Finally, straight ADB shell access is integrated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
1. Download.
2. Extract archive.
3. * Install LinuxReader to GalaxyS3ModTool\tools\LinuxReader.
4. Run SGN3ModTool.jar!
*This step is only needed for the Decompile System function in the ROM Manager.
Note: Make sure your phone is connected in debug mode, you have root privileges, and unsecured your device's shell. The application will try to unsecure your shell if you haven't already, but worst case scenario you might have to do this manually.
Also, the manage ROMs functionality is still experimental, and the Recompile System function is disabled. If you know how these processes can be automated, let me know and I will incorporate the functionality.
If you have problems, let me know and I will try to sort them out with you. Keep in mind that often when a modification goes wrong, you can simply push back the original files and reboot. So keep backups handy!

Reserved in case of future expansion.

Very interesting, will test when i get back home. Thanks!

Sound good mate. I'll give it a go I reckon

Wow sounds awesome thank you very much

Does it backup app data as well? This looks very promising. As it is java based, would it work on other platforms?
Sent from my Nexus 4 using Tapatalk

Post Removed

Breach said:
1. Download.
2. Extract archive to C:\cellphone\SGN3ModTool
3. * Install LinuxReader to C:\cellphone\SGN3ModTool\tools\LinuxReader.
4. ** Install the Java Runtime Enviroment from.. http://www.java.com/en/download/windows_xpi.jsp?locale=en
5. Make sure your Note 3 is plugged in and the screen is unlocked.
6. Run SGN3ModTool.jar
* This step is only needed for the Decompile System function in the ROM Manager.
** This step is only needed if you do not already have the JRE installed.
------------
It is telling me the device is offline. For example.. Roboot, Refresh Content, etc.. do not nothing.
Make Dir says "Directory Created" but does this...
adb shell mount -o remount,rw /system
adb shell mkdir "/test"
error: device offline
Click to expand...
Click to collapse
you have to allow ADB to acces your device..
when you try to do anything with ADB, look at your phone screen, it will give you a popup that will enable you to 'allow ADB connections'

karoolus said:
you have to allow ADB to acces your device..
when you try to do anything with ADB, look at your phone screen, it will give you a popup that will enable you to 'allow ADB connections'
Click to expand...
Click to collapse
I watched my screen. I got no popups other than the original "usb connected" popup when I plugged in the usb cable.
Edit: Deleted the app. No Support from Dev.

Breach said:
I watched my screen. I got no popups other than the original "usb connected" popup when I plugged in the usb cable.
Edit: Deleted the app. No Support from Dev.
Click to expand...
Click to collapse
this actually does work!
if somone still wants to use it for whatever reason you can:
get a kernel that is not SElinux enforcing (permissive).*
get adb insecure by chainfire and switch to insecure mode.
be sure that in the app it says:
Binary: Insecure
USB debugging: Enabled
should work, at least for me it did.
not sure if every custom kernel(permissive) works.
*lastest wanam exposed module has an experimental feature to set the selinux to permissive.
i havent tried it but maybe you can do the above with stock kernel and just setting permissive mode in wanam.
edit: does not work with stock kernel, at least for me.
i have not tested every function of this tool but connecting, pushing, pulling and so on work.
there are other tools that can do that, i wrote this just for information.

works well here! well done

cant get it to work on mac

thanks MrRusch for your great work!
I am a newbie about these stuff so forgive me if these are questions are stupid~
I was trying to use it to deodex the SamsungChineseIME apk and I got 2 questions want to ask.
1. when it asks for "Install Framework?", I choose the framework-res.apk extracted from my rom. But I also notice there is a twframeworkres.apk in the rom, do I need to include that also?
2. I came to a prompt asking me for "Select framework directory to reference" (as attached screen), I was hold back since I don't know what to choose for this.
Thank you again for your effort and this great tool!

[TUTORIAL][UNLOCKED BOOTLOADER][STOCK] Apply root-level mods without root

Hi, I'm not fairly new to this forum but I silent read from a long time ago and now I decided to share something I found.
Let's say you're tired with rooting and xposed as some apps refuses to run upon detection of either or both of those, and custom ROMs out there didn't float your boat, you decided to return to the stock. No recoveries, just a plain stock. But you need that SystemUI with netmeter, or you're too lazy to re-log in 6 different Twitter accounts onto the Twitter app you've previously backed up using TitaniumBackup or similar.
Without any words let me start:
What you need:
Obviously an unlocked bootloader since we will flash a recovery, and locked ones can't do so.
Any custom recovery, either CWM or TWRP that's fine. Don't worry about its compatibility with the stock, as it'll be wiped again (if you want)
Flashtool, it already includes fastboot for flashing stuffs, otherwise why is this called Flashtool?
Your current FTF file
OPTIONAL : AromaFM if your mods isn't a flashable zip
For TWRP you can also use its built-in file manager
Steps:
Download and set up Flashtool
After installation there will be some folders like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Install the drivers located in the Drivers folder, place your current firmware's FTF file to the firmwares folder, and for convenience, place your recovery in the x10flasher_lib folder, and rename it to something short and easy, like rec.img or similar.
Put your mods in the phone's storage/sdcard (and also your aromafm if you choose to use it).
Turn off your phone.
Open up Command Prompt (or console window of your choice, if you're not on Windows), and navigate to the flashtool/x10flasher_lib folder.
Run this on your console:
Code:
fastboot flash boot rec.img
change rec.img to your recovery's filename.
Plug in your phone with a USB cable while holding volume + button.
When done, plug it out and boot to your recovery by powering it on and pressing volume - button when the illumination bar lights up (depends on your recovery).
Apply your mods (flash mods, replace system files, remove bloatware etc.).
You may skip steps below if you change your mind to having a (compatible) custom recovery
When done turn off your phone again.
Open up your Flashtool, if asked for admin rights just say yes.
Click the bolt icon above the window, leave the Flashmode selected, and click OK
find your firmware, select it but don't flash it yet. Uncheck/check these options, you don't want to wipe your data, right?
Click to expand...
Click to collapse
Now press the flash button, located on the bottom-right of the window. When a window pops out (instructions to connect your phone while holding the back button), connect your phone with the Volume - pressed.
Wait the flash to finish, and unplug your phone.
Now you have your mods back and your app datas restored 'without root'~!
NOTE: I've done this on my Xperia E, for other phones I can't yet verify if this method works, so if anyone is interested to try this out go ahead and don't forget to report it back to me whether it's worked or not~

[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow

There's a hidden feature in Android 6.0, multi window. It has its warnings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So decide if this is actually for you before following these steps
It's not shown in user builds, so we have to do some messing. You'll either need root or a custom recovery to do this, but as not everyone wants root, here's how you do it with TWRP, a USB cable, and a PC with ADB:
1. Boot your device into recovery
2. Mount your system by going to Mounts > Tick System
3. On your PC open a command line, somewhere like your desktop is useful
4. Type the following command:
HTML:
adb pull /system/build.prop
5. Open the build.prop file with your favourite (decent) editor, I recommend using Notepad++ on Windows
6. Find the "ro.build.type" line
7. Change the text after = to "userdebug" from "user"
BONUS: If you want a nicer DPI here, change the line "ro.sf.lcd_density" to your preferred DPI
8. Save the file
9. Go back to the command line and enter the following command:
HTML:
adb push build.prop /system/
10. Now open a shell doing:
HTML:
adb shell
11. Now a adb shell will open, enter these commands:
HTML:
cd system
chmod 644 build.prop
12. Reboot the device as normal
13. When the device has booted, go to the developer options
14. Scroll down to the bottom of the "Drawing" category
15. Enable multi-window and have some fun!
If you're rooted...
1. Download "Build.prop editor"
2. Find "ro.build.type"
3. Edit it to have the value "userdebug" from "user"
4. Reboot when prompted
5. When the device has booted, go to the developer options
6. Scroll down to the bottom of the "Drawing" category
7. Enable multi-window and have some fun!

Worked ! Thanks
Such a shame the Keynote didn't introduce such feature, it's stable enough. Just think of the use of the feature on a 10" tablet.

works perfect thank you !

How do you use it after enabling?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
Go recent menu, on the apps beside the x there's a button to choose the top half or second half.
Multirom users can go /data/media/multirom/roms/ and edit the build prop directly there, no need to use adb. I did it without using a PC

I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
I get how to use it, but how do you consistently pick the two apps that you want to appear?
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
elreydenj said:
I get how to use it, but how do you consistently pick the two apps that you want to appear?
Click to expand...
Click to collapse
It seems to be all over the place. I cant figure out how to always get the two apps that i want in multiwindow to show....

prwnd said:
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Click to expand...
Click to collapse
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards

is it possible to do that with Wugfresh Nexus Root Toolkit?

jonathanxx1 said:
is it possible to do that with Wugfresh Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.

drgonzo712 said:
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
Click to expand...
Click to collapse
I tried also ,,and it doesn't work.

Adr990 said:
I got this message from ADB:
Anything?
Click to expand...
Click to collapse
Open terminal, type
su
cd system
chmod 644 build.prop
exit
and do stages again

Adr990 said:
When I do that, in adb shell:
Click to expand...
Click to collapse
Ow, i forgot ,my mistake sorry can you try this ?
cd system
chmod 777 build.prop
exit

damn.. is there a way to do it if it is a secondary rom on multiboot?

Adr990 said:
Oh and I also tried this:
Kinda wierd how it is not working for some, while we all flashed according to Google's adb flashing method.
Click to expand...
Click to collapse
Can you send your build.prop to me via pm. I can make a flashable zip for you

Hello people, I have multirom installed on my nexus 5, the primary rom is 5.1.1 (LMY48B), and my secondary rom is the developer preview MPZ44Q. I want to know if it's possible to enable multi-window mode since the M preview is installed as secondary rom.

I did it. Reboot into recovery. Swap the Roms. Don't reboot . reboot into recovery again from the reboot tab. Select multiboot tab just to ensure you are OK and the M ROM is the internal.. Mount system and do what the op says. Reboot into recovery again swap Roms again . reboot system and you should be OK. Takes like a half an hour to do though
PS. NEVER FIX SU. ALWAYS SKIP

I understood that if i try to install su on the M rom, it will result in bootloop. And my internal rom is stock ROOTED. So do you think it will work ?
When i will swap the roms, the fact that my primary rom is rooted, will it cause any problem ? Thanks in advance.

Nope my primary is still rooted. And I an typing this from my secondary M ROM with multi window enabled. All you have to do is never fix su for either ROM and never boot the system with M as your primary ROM and you are ok

Help me too
hsay said:
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
Click to expand...
Click to collapse
This is the worst thing to do here but could u please guide me too to the recovery as i searched all i could but still got no answer. Even the Guys in the Discussion group had no answer. Please Help ME,.

Enable Unknown Sources on Android 12

I have ran into a problem, using my Pixel 6 pro this morning. When I drop off an order at the customers location. Most drop off's prompted you to take a picture. When I went to take the picture, I got a toast that read "No Camera app on device". I took a picture with the default camera, and then tried using the second option, of uploading a picture to the Dasher app. That didn't work either.
After posting on the doordash reddit. It seems to be a problem with Pixel devices, and the Dasher app.
My pixel 4XL never updated the dasher app. So I backed up the app. And I'm trying to sideload it onto my Pixel 6 Pro. But I can't find, or figure out how to Enable Unknown Sources on Android 12.

I'm having the same issue on my Pixel 6! It's frustrating

Google_is_the_Higgs_Boson said:
I have ran into a problem, using my Pixel 6 pro this morning. When I drop off an order at the customers location. Most drop off's prompted you to take a picture. When I went to take the picture, I got a toast that read "No Camera app on device". I took a picture with the default camera, and then tried using the second option, of uploading a picture to the Dasher app. That didn't work either.
After posting on the doordash reddit. It seems to be a problem with Pixel devices, and the Dasher app.
My pixel 4XL never updated the dasher app. So I backed up the app. And I'm trying to sideload it onto my Pixel 6 Pro. But I can't find, or figure out how to Enable Unknown Sources on Android 12.
Click to expand...
Click to collapse
Nickdroid86 said:
I'm having the same issue on my Pixel 6! It's frustrating
Click to expand...
Click to collapse
This is for Pixel 5, but its for android 12 so should be roughly the same.
Or, if the device is rooted you could try just using adb push commands to push the app directly to your system/app or data/app folder.
Or even try putting the app in your internal storage somewhere then open your file manager on your device and navigate to the folder where you stored the app and install it from there, it should give you pop up prompts to enable the proper permissions, just follow the prompts until it let's you install the apk.

Droidriven said:
This is for Pixel 5, but its for android 12 so should be roughly the same.
Or, if the device is rooted you could try just using adb push commands to push the app directly to your system/app or data/app folder.
Or even try putting the app in your internal storage somewhere then open your file manager on your device and navigate to the folder where you stored the app and install it from there, it should give you pop up prompts to enable the proper permissions, just follow the prompts until it let's you install the apk.
Click to expand...
Click to collapse
I can't seem to get any thing to sideload on my Pixel 6 Pro. Can't seem to get anything to sideload even on my wifes Pixel 6 Pro. I backed up a few other apps, to make sure it wasn't something wrong with the dasher app itself. Can't sideload any apk files.
This is what I get, when I try to sideload it from Google drive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Droidriven said:
This is for Pixel 5, but its for android 12 so should be roughly the same.
Or, if the device is rooted you could try just using adb push commands to push the app directly to your system/app or data/app folder.
Or even try putting the app in your internal storage somewhere then open your file manager on your device and navigate to the folder where you stored the app and install it from there, it should give you pop up prompts to enable the proper permissions, just follow the prompts until it let's you install the apk.
Click to expand...
Click to collapse
When I try to sideload it from the files app, from my internal storage.

At the bottom, it looks like it's loading, to install. But after hitting install, the toast pops up saying the app didn't install...

Google_is_the_Higgs_Boson said:
At the bottom, it looks like it's loading, to install. But after hitting install, the toast pops up saying the app didn't install...
View attachment 5451591
Click to expand...
Click to collapse
Maybe you have some conflicting data left over from an update or leftovers from deleting the app before trying to reinstall it or just a bug. In this case, booting into recovery and choosing the option to "wipe cache partition"(DO NOT CHOOSE FACTORY RESET) could potentially help solve this issue. Or, if you already have the app installed and you are trying to reinstall the app over the existing app, you can go to system settings>apps then find and select the app on the list then on its app info screen select storage then choose the option to wipe cache for that specific app, then power off and reboot the device then try to reinstall the app.