Database Info

[GUIDE] getting titaniumbackup (and other root apps) temporarly working

first off, big thanks @teamwin for fre3vo!
this guide is for advanced users only, so I will not explain the adb stuff etc.
you will need to do this stuff FAST, as temp root only works for a short amount of time, but it was enough for me to restore some apps and settings
* install titaniumbackup & busybox installer from market (do not start them)
* reboot the phone and DO NOT start any application
* do the fre3vo stuff:
Code:
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo
* install superuser, su and set permissions
Code:
adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb install Superuser.apk
adb push su /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell ln -s /system/xbin/su /system/bin/su
* start busybox installer and install busybox
* start titaniumbackup and do your stuff
again, this has to be done fault free and FAST, like within 2-3 minutes
attached are su & superuser used

Nothing attached

Thank you for this tuto, i try other from 3D Evo and don't work for me, now im not at home, but will try this one once at home.
Thank a lot!!!
Sent from my HTC Sensation Z710e using Tapatalk

<delete please>

Great man!! Thanks
I am guessing that all these files fre3vo, SU, Su.apk should be in the platform-tools folder? where adb is?

We can delete some apks,right?

jerrylzy said:
We can delete some apks,right?
Click to expand...
Click to collapse
No, but you can disable them

prateekgujral said:
I am guessing that all these files fre3vo, SU, Su.apk should be in the platform-tools folder? where adb is?
Click to expand...
Click to collapse
the 3 files have to be in your current working directory (which should not be the platform dir), and adb should be in your ${PATH}
but yes, you can also put the files where adb is located

blubbers said:
the 3 files have to be in your current working directory (which should not be the platform dir), and adb should be in your ${PATH}
but yes, you can also put the files where adb is located
Click to expand...
Click to collapse
I will have to put them where the adb is located as I havent changed the environment variables for accessing adb from anywhere.. i think it should be ok.. as I have been flashing radios and other apps like that only!! (previous Androids!)
I would usually just copy the file on to the platrform directory.. ADBed the thing and deleted the file oonce the job is done!

prateekgujral said:
I will put them where the adb is located as I havent changed the environment variables for accessing adb from anywhere.. i think it should be ok.. as I have been flashing radios and other apps like that only!! (previous Androids!)
I would usually just copy the file on to the platrform directory.. ADBed the thing and deleted the file oonce the job is done!
Click to expand...
Click to collapse
of course it will work, but it's not the proprer way to do things

blubbers said:
of course it will work, but it's not the proprer way to do things
Click to expand...
Click to collapse
Oh well!! as long as it works!!!
Anyway... thanks man!!

Found this!!
Excellent video tut
http://www.youtube.com/watch?v=1t9AXZWcFQU

prateekgujral said:
Found this!!
Excellent video tut
http://www.youtube.com/watch?v=1t9AXZWcFQU
Click to expand...
Click to collapse
might want to put this in the fre3vo thread, as this is thread goes beyond that

Followed your procedure above but just before I installed busybox - I pushed a new hosts file over which was taken from an adblocker program.
adb push hosts /etc/hosts
Edit: - hosts gets overwritten after few minutes
Pity - thought it might have been useful

Awesome worked great!

EddyOS said:
No, but you can disable them
Click to expand...
Click to collapse
I have uninstalled anything related to "stocks"
The widget , the app and one other have been uninstalled and are no longer present on my phone
Sent from my Nokia 3310 using Tapatalk, 2 carrier pigeons on crack and a cab

j2kquest said:
I have uninstalled anything related to "stocks"
The widget , the app and one other have been uninstalled and are no longer present on my phone
Sent from my Nokia 3310 using Tapatalk, 2 carrier pigeons on crack and a cab
Click to expand...
Click to collapse
Reboot and they'll probably come back

I get this
failed to copy 'su' to '/system/xbin/su': Read-only file system
Click to expand...
Click to collapse

I get all the way to Titanium backup saying its restoring an app and it hangs there. It gets superuser and everything it just doesnt seem to want to actually restore anything.

I get this problem
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22 /system
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb server is out of date. killing...
* daemon started successfully *
mount: Operation not permitted
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22/system
adb server is out of date. killing...
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\android\tools>adb install Superuser.apk
adb server is out of date. killing...
* daemon started successfully *
2180 KB/s (196521 bytes in 0.088s)
adb server is out of date. killing...
* daemon started successfully *
pkg: /data/local/tmp/Superuser.apk
Success
adb server is out of date. killing...
* daemon started successfully *
C:\android\tools>adb push su /system/xbin/su
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/xbin/su': Read-only file system
Click to expand...
Click to collapse

[GUIDE][SIMPLIFIED]HTC Inspire S-OFF

After the advanced ace hack kit (AAHK) was taken down, it was a bit tough to get an S-Off on our devices. The existing guides never explained anything much.
So , I will be explaining and trying to simplify the S-Off method for HTC Inspire 4g.
Please note: I take absolutely no CREDIT for this. All I have done is simplified it.
The following goes unsaid.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about directions in this method
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please donot ask me what fastboot mode is or how to boot into it or the advantages of an "S-OFF". I have only made this guide a bit simplified , but not noob friendly. This is still for advanced users and in addition for intermediate users.
Requirements
Your device must be rooted and the bootloader must be unlocked
Android sdk tools must be installed
Please make sure you have the Unlock_code.bin that you used to unlock the bootloaders since you will need it.
Most Important : Please follow the instructions exactly, Don't exit from shell unless I ask you to. I will not entertain any PMs or posts if you don't follow them.
Directions
I would prefer using a linux machine for this, but the choice is upto you.
1 . Download and extract this and cd into the directory in your terminal / CMD window and push the following files
Code:
#~adb push misc_version /data/local/tmp
#~adb push goldcard /data/local/tmp
#~adb push gfree /tmp/
2 . Make sure you have the original "boot.img" of your ROM on you PC HDD.
3 . Make a Goldcard in the following way
Code:
#~adb shell
$~su
#~chmod 775 /data/local/tmp/goldcard
#~cat /sys/class/mmc_host/mmc2/mmc2:*/cid
This will generate the CID. Copy the generated CID
Code:
#~/data/local/tmp/goldcard -c <YOUR_CID_HERE> -o /data/local/tmp/goldcard.img
#~dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
This should create the Goldcard.
4. Next to lower the main version
Code:
#~chmod 775 /data/local/tmp/misc_version
#~/data/local/tmp/misc_version -s 1.11.111.1
#~reboot bootloader
5. Next relock the bootloader
Code:
#~fastboot oem lock
6. Flash the firmware.zip in RUU
Code:
#~fastboot oem rebootRUU
#~fastboot flash zip firmware.zip
#~fastboot reboot-bootloader
7. Unlock bootloader with the Unlock_code.bin got from HTC's Developer site
Code:
#~fastboot flash unlocktoken Unlock_code.bin
8. Next flash your ROM's boot.img
Code:
#~fastboot flash boot boot.img
9. Next flash the recovery.img
Code:
#~fastboot flash recovery recovery.img
#~fastboot boot recovery.img
Don't worry : The screen will stay blank. ADB will work.
10. Now to S-OFF...
Code:
#~adb shell
#~chmod 775 /tmp/gfree
#~/tmp/gfree -f
#~reboot bootloader
Now the device will reboot to bootloader. And you will see that your device as been S-Offed.
11. Next step is to enter fastboot mode on the device. (Please keep the device connected to the PC)
Choose the appropriate Hboot_xxxx.zip file for your phone
Code:
#~fastboot oem rebootRUU
#~fastbbot flash zip hboot_xxxxx.zip
#~fastboot reboot
12. Now flash CWM recovery
Download file from here
Pull battery out and reinsert. Boot phone to fastboot mode.
Connect to PC.
Code:
#~fastboot flash recovery recovery-clockwork-touch-5.8.1.5-ace.img
That's it!! Now flash your favourite ROM and reboot.​
CREDITS
The Guy who posted the original method here
Cheers!!

When we start pushing the files should we be in the bootloader, fastboot, or the operating system? This is exactly what I've been looking for going on 2 weeks now thank you for this. I get an error message when trying to push the gfree to tmp ": Is a directory" is what I'm getting. I see we push while booted in the OS.
Edit: I'm S-OFF now! I think that either pushing the gfree to /tmp/ needed to be elsewhere or it just doesn't work with 2.3.5? Not really sure but I followed your every step, even with errors, and came across a thread that used an eng hboot image here I scrolled down to "Gaining Engineering S-OFF:" and went from there. Thank you deathscream for this useful post and thanks to Haroon Q Raja as well for the other findings. Now my phone is Super CID, rooted, and S-Off.

[HD+ only][Beta] U-Boot v2014.07 + Graphical boot menu

Hello everyone!
Here's a little gift for you.
This is a port of a recent U-Boot (currently v2014.07) for the BN Ovation.
YouTube video: http://youtu.be/LN2bcjdnWnQ
Thanks to bauwks, fattire, Barnes & Noble (although their code is horrible), Wolfgang Denk and the U-Boot contributors, and everyone else that helped with cracking the Nook's bootloader.
Playing with bootloaders can be dangerous. Although I tested this software, I can't guarantee that it won't harm your device.​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this software
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Why?:
I got bored, so I started working on a Debian port for the HD+. I then realized that I'll need to change the boot params to make things work without ugly hacks. I looked around, and all I could find was the same bootloader with hacks for menus and different boot params. So, I thought I'd do a fresh and (hopefully) clean port of the latest U-Boot, and enable boot scripts, so that we can use one bootloader for all the ROMs and kernels.
Do you guys think this would be accepted upstream? No point in doing that without replacing the first U-Boot, I think.
What works:
My board's revision (PVT according to original U-Boot, EVT1B according to kernel. Novatek panel.)
Console over USB (usbtty)
Console over LCD (vga)
Display
Booting from SD
Booting from eMMC
Boot scripting (SD, eMMC)
You tell me
What doesn't work (only in bootloader):
Display backlight control
Gas Gauge (battery meter)
Charging control
You tell me
Sources:
From my GitHub: https://github.com/Ar2000jp/u-boot.git
Based on (upstream): http://git.denx.de/u-boot.git
BN sources: http://www.barnesandnoble.com/u/Terms-of-Service-NOOK-HD-HD-Plus/379003804
Binaries:
Attached to this post.
Copy the file named "uImage" to your SD card's boot partition. To create an SD card with the required boot partition and files, follow the procedure for creating an external recovery SD card. Check out this thread for more information: https://forum.xda-developers.com/showthread.php?t=2600572
To do:
Lots of testing
You tell me
How to compile:
I used Code Sourcery's arm-2014.05-28-arm-none-eabi-i686-pc-linux-gnu release.
Code:
ARCH="arm" CROSS_COMPILE="/opt/codesourcery/arm-2014.05/bin/arm-none-eabi-" make distclean
ARCH="arm" CROSS_COMPILE="/opt/codesourcery/arm-2014.05/bin/arm-none-eabi-" make omap4_ovation_eng_config
ARCH="arm" CROSS_COMPILE="/opt/codesourcery/arm-2014.05/bin/arm-none-eabi-" make -j3 u-boot.bin
ARCH="arm" CROSS_COMPILE="/opt/codesourcery/arm-2014.05/bin/arm-none-eabi-" make clean
gzip --best -vk u-boot.bin
mkimage -A arm -O linux -T kernel -C gzip -a 0x88000000 -e 0x88000000 -n "2nd Bootloader" -d u-boot.bin.gz uImage
For the Engineering build (more command line features), use:
Code:
make omap4_ovation_eng_config
And for the normal build, use:
Code:
make omap4_ovation_config
Changelog:
See GitHub commit log.

Boot scripting
By using U-Boot's boot scripts and boot menu support, we can unify the bootloaders to one bootloader, but use different boot scripts.
Boot scripts can execute any U-Boot commands automatically on boot, which means we can change bootargs, and use whatever other features we want easily.
The current version of this U-Boot port looks for a U-Boot script (boot.scr) on the SD card's first partition (mmc 0:1, which must be fat), and if it doesn't find one, it'll look for one on the bootdata partition (mmc 1:6) on the eMMC.
Please be aware that some U-Boot commands can permanently brick your device.
Please only use trusted boot scripts.​
To make a boot script, use:
Code:
mkimage -A arm -O u-boot -T script -C none -n "Boot Script" -d bootscript.txt boot.scr
Graphical boot menu:
Using the scripting capabilities in U-Boot, I was able to make a graphical boot menu. ROMs can be easily added to the menu by adding a few lines to the script.
I have a favor to ask of developers: please keep the script clean. Let's try to make a standard form for it.
I think the script is simple and self-describing. Adding a new ROM only needs a line for boot arguments, a line for the boot command, and a BMP image for the ROMs entry in a folder with the entry's name on the SD card's boot partition.
To keep the display clean (no artifacts/leftovers), please use graphics with the same dimensions as the entry files in the provided attachment.
BMPs must be in a format supported by U-Boot. I use 24-bit uncompressed BMPs, and then I gzip them.
Code:
gzip --best -k entry.bmp
Attached is the script I wrote, with some (crude) graphics, and support for booting eMMC CM11 and recovery.
To use the script, copy the contents of the "SD Files" folder to the boot partition on your SD card.
Testing, better graphics, scripts, and feedback is most welcome.

bootloop

In an effort to access more storage space for apps I used a text editor to change "dev_mount sdcard/mnt/sdcard" to "dev_mount sdcard /mnt/extsd" and "dev mount extsd /mnt/extsd" to "dev_mount extsd /mnt/sdcard" in system/ect.
which resulted in a bootloop. Attempts to use ADB give this result:
[email protected]:~$ sudo adb shell
[sudo] password for daryl:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
probably because usb debugging is not enabled.
this android is not CWM or TWRP compatible either.
Any suggestions or pointers to get out of this loop would be greatly appreciated.
TIA Daryl

[RECOVERY][UNOFFICIAL][3.7.0][Perseus] TWRP for Xiaomi Mi Mix 3

Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working :
Basic twrp features (boot, format data, etc, etc)
Decryption data up to android 13
Vibration
otg
Issues / Notes :
really messed fstab
/system is missing from wipeui, and i have no idea what happened (but flashing should works fine)
miui is partially support (due to using /cust as /system_ext)
Download : Link
Thanks :
aidan for sending me money to buy motherboard
Source :
device tree
kernel

reserved

Hey, thanks for sharing it.
I had some problems with installing custom ROM, because lack of appearing /system partition in format step and installed ROM went started to bootloop.
Fortunately I was able to pass this step by mounting system partition, entering into terminal and executing following command: " cd /system_root && rm -Rf * " -without quotes.
Please make sure to execute whole command at once or just ensure you will not delete files outside of proper system partition by executing part of command (for example when /system mounts in other location than /system_root). If you are not sure, execute "df" command and see last entry which should show you where system partition is mounted and adjust the command.
For some of you, who want to proceed with my advice. Please note, that I am not responsible for any problems you can cause on your device using my advice. It will surely not break your phone if done properly. if you don't understand what you do, please don't do it

Fiqusny said:
Hey, thanks for sharing it.
I had some problems with installing custom ROM, because lack of appearing /system partition in format step and installed ROM went started to bootloop.
Fortunately I was able to pass this step by mounting system partition, entering into terminal and executing following command: " cd /system_root && rm -Rf * " -without quotes.
Please make sure to execute whole command at once or just ensure you will not delete files outside of proper system partition by executing part of command (for example when /system mounts in other location than /system_root). If you are not sure, execute "df" command and see last entry which should show you where system partition is mounted and adjust the command.
For some of you, who want to proceed with my advice. Please note, that I am not responsible for any problems you can cause on your device using my advice. It will surely not break your phone if done properly. if you don't understand what you do, please don't do it
Click to expand...
Click to collapse
or fastboot erase system can help, if someone lack knowledge
i still finding the root cause for this, if i can fix it i'll release new one asap

loipuru said:
or fastboot erase system can help, if someone lack knowledge
i still finding the root cause for this, if i can fix it i'll release new one asap
Click to expand...
Click to collapse
I never would have thought about such obvious solution. Thanks

so, can i still use this to flash older MIUI versions like MIUI 12?
i should just use fastboot erase system after wiping via twrp. right?

bluviper said:
so, can i still use this to flash older MIUI versions like MIUI 12?
i should just use fastboot erase system after wiping via twrp. right?
Click to expand...
Click to collapse
yeah,
i don't have time to rebase tree yet. so it'll preferred method for now

yea. i just tried. and it worked.
did a full wipe and reinstalled miui-globe ROM.
thanks

new update out:
changelog: fix /system missing

loipuru said:
new update out:
changelog: fix /system missing
Click to expand...
Click to collapse
Flashed but upon rebooting into recovery it lost access to storage and sdcard directories.

tlxxxsracer said:
Flashed but upon rebooting into recovery it lost access to storage and sdcard directories.
Click to expand...
Click to collapse
known issues, but it only happened on some roms, no problem on sparks and los as i tried
it's source issues which is really tricky to fix