how to install the topaz androind what am i doing wrong for - Touch Diamond2, Pure Android Development

Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
In preloader
PSR = 600000df
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/AndroidApps/
/conf/
/media/
/STARTUP CONFIG/
/STARTUP.TXT
/haret.exe
/initrd.gz
/rootfs.img
/system.ex2
/zImage
/modules-2.6.27.46-01165-gfc1639f.tar.gz
REMEMBERING THAT THIS CARD SD formatted in FAT32.
SETUP FILE IS THIS DEFAULT.TXT.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "acpuclock.oc_freq_khz=650000 lcd.density=240 msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=528 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,2,3 force_cdma=0 sensor=topaz pm.sleep_mode=3"
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
which the configuration of the startup?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
GRATEFUL FOR THE HELP

Try to use "stock cpu-speed" which means you have to delete the commandline "acpu.oc_frq...". also you need to unzip modules....tar in the root of your sd-card and paste the zImage and module-tar into the root. But I think it's because the overclocking...

Related

unable to install android on topaz someone help me do not know where this error

Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
In preloader
PSR = 600000df
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/AndroidApps/
/conf/
/media/
/STARTUP CONFIG/
/STARTUP.TXT
/haret.exe
/initrd.gz
/rootfs.img
/system.ex2
/zImage
/modules-2.6.27.46-01165-gfc1639f.tar.gz
REMEMBERING THAT THIS CARD SD formatted in FAT32.
MY SD CARD HAVE 2 GB.
SETUP FILE IS THIS STARTUP.TXT
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "acpuclock.oc_freq_khz=650000 lcd.density=240 msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=528 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,2,3 force_cdma=0 sensor=topaz pm.sleep_mode=3"
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
which the configuration of the startup?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
GRATEFUL FOR THE HELP
pauloedusp said:
SETUP FILE IS THIS STARTUP.TXT
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "acpuclock.oc_freq_khz=650000 lcd.density=240 msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=528 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,2,3 force_cdma=0 sensor=topaz pm.sleep_mode=3"
boot
Click to expand...
Click to collapse
I think the problem is, that you're changing the cpu. "acpuclock.oc_freq_khz=650000" try and set it to stock, by deleting this from starup text and run at 528 MHZ. the point is that android cannot handle this. use default setting at initial boot. change this after configuring the phone.
PS: I'd also delete pm.sllep_mode=3, try =2 or better =1, then calls will be displayed although your phone is in sllep mode.
Which phone are you using?
There are different startup.txts for each one
And yeah, taking out the overclock and changing the sleep_mode to =1 are also good
pauloedusp said:
Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
In preloader
PSR = 600000df
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/AndroidApps/
/conf/
/media/
/STARTUP CONFIG/
/STARTUP.TXT
/haret.exe
/initrd.gz
/rootfs.img
/system.ex2
/zImage
/modules-2.6.27.46-01165-gfc1639f.tar.gz
REMEMBERING THAT THIS CARD SD formatted in FAT32.
MY SD CARD HAVE 2 GB.
SETUP FILE IS THIS STARTUP.TXT
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "acpuclock.oc_freq_khz=650000 lcd.density=240 msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=528 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,2,3 force_cdma=0 sensor=topaz pm.sleep_mode=3"
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
which the configuration of the startup?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
GRATEFUL FOR THE HELP
Click to expand...
Click to collapse
Delete 'msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=528'
Also you can try one STARTUP.TXT that was posted in these topics and worked...

Can't get ANdroid to Work

Hi
Im trying to get android working on topaz.
I got the "[03/03/11]XDAndroid - Topaz [2.2.2][FRX05 Final]" and all files indicated by it.
http://forum.xda-developers.com/showthread.php?p=3695364#post3695364
I download haret.exe from somewhere else (no link in that post), but It just locks completely.
Am I doing something wrong? Someone has all the files in a single place?
I used the following default.txt:
set MTYPE 2293 #- MTYPE of Topaz is 2293, that of Rhodium is 2292
set KERNEL zImage
set FBDURINGBOOT 0
set initrd initrd.gz
pwf dm.txt 0x8e0000 0x20000
#
# (every line which begins with a # is a comment line, and isn't read by HaRET)
#
# The following kernel parameters are useful (can be added or changed in the cmdline):
# msmts_calib - The location of the touch-input of your screen (format in hexadecimal: 'x-min.y-min.x-max.y-max')
# - best value for Topaz: 0x395.0x3d5.0x79.0xa0, but isn't necessary anymore because of calibration app on first boot
# lcd.density - Defaults to 250, 240 fits the screen a little better
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# To find your APN settings please look here http://www.androidonhtc.com/wiki/Carrier_network_settings
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# msmsdcc_1bit
# msmsdcc_fmax=14000000
# msmsdcc_nopwrsave - Try to add these last 3 lines in you cmdline (with spaces between) when your SD doesn't want to boot (anymore)
# WiFi.mac=XX:XX:XX:XX:XX:XX - Adding your mac address is needed for best results on WiFi,
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Use 2 for best power savings
#
set cmdline "lcd.density=240 msmvkeyb_toggle=off WiFi.mac=11:22:33:44:55:66 pm.sleep_mode=2"
boot
Click to expand...
Click to collapse
I would appreciate any help on this.
Emerson
try one of the bundles here
http://forum.xda-developers.com/showpost.php?p=12407445&postcount=6110
syrian
what is heppend to your device is lag when you open the haret

extract and pack initramfs from kernel tutorial

What you need:
1. Linux
2. Git (recomended)
3. Internet
4. GCC toolchain from google (size is realy BIGG)
git clone _ttps://android.googlesource.com/platform/prebuilt_
or good one
_ttps://github.com/STS-Dev-Team/arm-eabi-4.4.3_
4. Pack and repack tools from xiaolu
_ttps://github.com/xiaolu/galaxys2_kernel_repack_
5. Now working tools but good include
_ttps://github.com/project-voodoo/kernel_repack_utils_
I modify xiaolu tools for p1000 see attachment (base adress and include)
Command are (ag is a directory):
./unpack.sh zImage ag
./gen_initramfs.sh -o output.cpio -u 0 -g 0 ag
./repack.sh zImage output.cpio new_zImage
I modify init.rc to swap sdcard int and ext (internal sdcard now broken by mmc cap erase).

swap on jb

OK I got swap to work on my bionic, first make a swap file:
dd if=/dev/zero of=/data/cache bs=1024 count=568924
Or how ever many bytes you want it 568924 is over 500mb then with busybox use mkswap
busybox mkswap /cache/swap
Now copy the uuid that busy box has generated from mkswap and paste that uuid in /etc/fstab like below with none swap defaults 0 0
UUID-dhd53bg-75fhvf-this-is-the-uuid none swap defaults 0 0
Now try swapon /cache/swap.
If that fails you will need to download a custom ubuntu.IMG from here: http://www.4shared.com/zip/NKq5ucvZ/ubuntu.html
And a mounting script from zip below copy contents of zip to system/xbin/linux and system/xbin/linux.sh
chmod 755 /system/xbin/linux
chmod 755 /system/xbin/linux.sh
Then if you have the Ubuntu.IMG on sdcard-ext run in your terminal
linux
you should then be at [email protected] host of your Linux chroot try the procedure from above inside your [email protected] host and copy the uuid into the chrooted /etc/fstab and in your system/etc/fstab then try swapon /cache/swap. fstab should be 0644 permissions
If you get the Ubuntu.IMG and the scripts from below you now have a full Ubuntu desktop you can vnc into just type in the terminal :
[email protected]#./root/init.sh
the root/init.sh will start vncserver and gdm gnome will have flash 10.1 and Firefox Ubuntu app center all of which work great
Vncserver is
localhost
User is
localhost
Domain is localdomain
password is ubuntu
vnc port is
5901
http://www.4shared.com/zip/SGolTsWZ/linuxmount.html
Here isthe link http://sourceforge.net/projects/droidbionic.motorola/files/droidbionic/9.8.2O-72_VZW-22/ to the bionic jellybean kernel source if someone wants to build it from source and add swap/zram support or overclocking to add swap edit the config.gz CONFIG_SWAP=y
CONFIG_SWAP_PREFETCH=y
You don't need to add prefetch just supposed to help speed like readahead on sdcard.
If you get and use the ubuntu.img the scripts provided mount rw and kexec your kernel so if you know what your doing you could modify the kernel from inside your chrooted ubuntu or create and use modules for that kernel. You would have to build from source and have the jellybean kernel compiled but it is possible to do all of that from inside your chroot you would also probably need a 64GB sdcard and formatted to ext3 and modify the mount script to mount the ext3 not the .IMG if you want help with this I will provide the mounting script to change from .IMG to ext3 partition just message me

[RECOVERY][sprout] TWRP 2.8.0.0 touch recovery [2014-09-26]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
DOWNLOAD:
You can download the image here
INSTRUCTIONS:
Same as CWM
XDA:DevDB Information
Team Win Recovery Project, a Recovery for Android One devices
Contributors
varun.chitre15
Version Information
Status: Testing
Created 2014-09-26
Last Updated 2014-09-26
Thanks...!!
Really looking forward to twrp, love twrp more than cwm though
Sent from my Micromax AQ4501 using XDA Free mobile app
Thank You!
Flashed twrp, looks good now.
Can I backup my stock ROM now? @varun.chitre15
Sent from my Micromax AQ4501 using XDA Free mobile app
I am unable to backup my current rom using twrp.it works only a few times.sometimes the backup file is about 10 MB which is corrupted.
Other than that its rocking
official twrp 2.8.1.0 is out now..
official twrp is out now version 2.8.1.0 .. chk it out
problems after backuping stock unrooted and bootloader locked rom
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader and got 13 files some with .tar extension some with .tar.a and 1 with .tar.b extension and 2 files with .img extension
now the problem is.
1. if i try to open any file using winrar i get a error the archive is ither in unknown format or is damaged.
2. if i use 7zip to open .tar files i get error there are no trailing 0filled records if i open .tar.a files the files open properly but when i go to extract the contents i get error unable to open output file when i open data.ext4.tar.a i get error unexpected end of archive.tar and if i click on ok i can see the files in the archive but if i go to extract it again the same error unable to open output file comes if i open data.ext4.tar.b i get error 7zip cannot open data.ext4.tar.b as archive what is the problem?
how can i extract the files?
hear is my recovery.log file.
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Nov 8 14:38:30 2014
No /etc/extra.fstab
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot 0
1 /recovery emmc /dev/block/platform/mtk-msdc.0/by-name/recovery 0
2 /system ext4 /dev/block/platform/mtk-msdc.0/by-name/system 0
3 /data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata 0
4 /cache ext4 /dev/block/platform/mtk-msdc.0/by-name/cache 0
5 /external_sd auto /dev/block/mmcblk1p1 0
6 /tmp ramdisk ramdisk 0
I:Connected to Vold..
I:200 0 Volumes listed.
I:skiping get_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Checking arguments.
stage is []
can't open /dev/tty0: No such file or directory
framebuffer: fd 5 (480 x 854)
PhilZ Touch 6.57.9
ClockworkMod v6.0.5.1
Ievice target: sprout
I:Touch GUI revision: 1.41
I:device_recovery_start()
I:auto_restore_settings set to default (true)
I:check_root_and_recovery set to default (true)
I:compression_value set to default (low)
I:twrp_backup_mode set to default (false)
I:enable_md5sum set to default (1)
I:show_nandroid_size_progress set to default (1)
I:use_nandroid_simple_logging set to default (1)
I:nand_prompt_on_low_space set to default (1)
I:signature_check_enabled set to default (0)
I:install_zip_verify_md5 set to default (0)
I:brightness_user_path=/sys/class/leds/lcd-backlight/brightness
I:set_brightness set to default (160)
I:menu_height_increase set to default (24)
I:show_virtual_keys set to default (true)
I:min_log_rows set to default (3)
I:background_image set to default (default)
I:background_image set to default
Iefault stitch background loaded.
I:show_background_icon set to default (false)
I:show_battery set to default (true)
I:show_clock set to default (true)
I:menu_text_color set to default (8)
I:menu_background_color set to default (1)
I:menu_highlight_color set to default (7)
I:normal_text_color set to default (0)
I:menu_separator_color set to default (6)
I:header_text_color set to default (8)
I:batt_clock_color set to default (2)
I:menu_background_transparency set to default (102)
I:menu_highlight_transparency set to default (102)
I:menu_separator_transparency set to default (102)
I:show_menu_separation set to default (true)
I:dim_timeout set to default (60)
I:blank_timeout set to default (180)
I:scroll_sensitivity set to default (48)
I:touch_accuracy set to default (7)
I:touch_to_validate set to default (true)
I:enable_vibrator set to default (true)
I:boardEnableKeyRepeat set to default (true)
I:wait_after_install set to default (true)
I:slide_left_action set to default (5)
I:slide_right_action set to default (3)
I:double_tap_action set to default (2)
Iress_lift_action set to default (4)
Iress_move_action set to default (1)
I:t_zone set to default (0)
I:t_zone_offset set to default (0)
I:use_dst_time set to default (false)
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Current time: 2014-11-08 14:38:32 (UTC 0:00)
I:use_qcom_time_daemon set to default (0)
I:use_qcom_time_data_files set to default (0)
I:use_qcom_time_offset set to default (0)
Command: "/sbin/recovery"
ro.cm.device=sprout
ro.cm.display.version=11-20140925-UNOFFICIAL-sprout
ro.cm.version=11-20140925-UNOFFICIAL-sprout
ro.cm.releasetype=UNOFFICIAL
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.hardware=sprout
ro.boot.serialno=Mi498HA14090035
ro.boot.bootloader=0.5.17
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=mt6582
ro.build.id=KTU84Q
ro.build.date=Thu Sep 25 13:18:39 EDT 2014
ro.build.date.utc=0
ro.build.host=ketan
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.product=sprout
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=b75c7a7c94
ro.build.description=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.fingerprint=Micromax/cm_sprout/sprout:4.4.4/KTU84Q/b75c7a7c94:userdebug/test-keys
ro.build.characteristics=default
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=cm_sprout
ro.product.board=
ro.product.brand=Micromax
ro.product.model=A1
ro.product.device=sprout
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=Micromax
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=sprout
ro.revision=0
ro.serialno=Mi498HA14090035
ro.bootloader=0.5.17
ro.debuggable=1
ro.modversion=11-20140925-UNOFFICIAL-sprout
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.sys.dun.override=0
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
service.adb.root=1
keyguard.no_require_sim=true
I:Checking for extendedcommand & OpenRecoveryScript...
I:Ignoring 'extendedcommand' boot-script: file not found
I:Ignoring 'openrecoveryscript' boot-script: file not found
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:blank_timeout was set to 300
I:blank_timeout was set to 600
I:blank_timeout was set to 900
I:blank_timeout was set to 1800
I:blank_timeout was set to 0
I:dim_timeout was set to 120
I:dim_timeout was set to 180
I:dim_timeout was set to 240
I:dim_timeout was set to 300
I:dim_timeout was set to 0
I:skiping set_bootloader_message: no /misc
No files found.
I:ro.modversion set to default (noname)
I:ro.romversion set to default (noname)
I:ro.build.display.id=KPW53
I:Checking needed space for backup '/external_sd/clockworkmod/backup/2014-11-08.14.40.12_KPW53'
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/recovery' -> '/dev/block/mmcblk0p8'
I:/recovery backup size (/proc)=10Mb
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/boot' -> '/dev/block/mmcblk0p7'
I:/boot backup size (/proc)=10Mb
I:/system backup size (stat)=692Mb
I:/cache backup size (stat)=4Mb
I:/data: tot size=2322Mb, free=730Mb, backup size=1538Mb, used=1538Mb, media=0Mb
I:/external_sd/.android_secure backup size=5Mb
>> Free space: 6875Mb (90%)
>> Needed space: 2260Mb
>> Backing up /boot...
Backing up boot image...
Backup of boot image completed.
>> Backing up /recovery...
Backing up recovery image...
Backup of recovery image completed.
>> Backing up /system...
Press Back to cancel.
Backup of system completed.
>> Backing up /data...
Press Back to cancel.
Backup of data completed.
>> Backing up /external_sd/.android_secure...
Press Back to cancel.
Backup of .android_secure completed.
>> Backing up /cache...
Press Back to cancel.
Backup of cache completed.
I:No sd-ext found. Skipping backup of sd-ext.
>> Generating md5 sum...
> .android_secure.vfat.tar.a
> .android_secure.vfat.tar
> boot.img
> cache.ext4.tar
> cache.ext4.tar.a
> data.ext4.tar.a
> data.ext4.tar.b
> data.ext4.tar
> recovery.img
> system.ext4.tar.a
> system.ext4.tar
austinpinto said:
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader...............
Click to expand...
Click to collapse
you have to root and unlock the bootloader first.
Swapnil Solanki said:
you have to root and unlock the bootloader first.
Click to expand...
Click to collapse
hi.
i read somewhare that you can backup the entire rom without unlocking the bootloader and without rooting the phone by downloading the recovery.img file.
putting it into the platform tools folder opening the command prompt booting your phone into fast boot mode and typing fastboot boot recovery then once the recovery boots i can use the backup to sd card feature is this right? can i do this? the entire size of the backup folder is about 2.6gb but the only problem is i cannot open some tar files and tar.b files and extract data from all files is not working
:good:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
try installing using fastboot...
Twrp 2.8.4.0
terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
Try the stable build twrp 2.8.4.0 from the official website.
Not working yet
really awesome recovery for android one....:good::good::good:
Please help I'm not able to use touch with twrp
terroboy k9 said:
Please help I'm not able to use touch with twrp
Click to expand...
Click to collapse
Use Flashify to flash the recovery img. I did just that and it worked in the first trial.
Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!
alfavictor said:
Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!
Click to expand...
Click to collapse
Is the recovery meant for your device or you're using some other device's recovery?

Categories

Resources