---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Battery charging!=-
-=clockwork nandroid restore=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=battery status (charging status, temperature and charge level) display=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Touch screen scrolling on some devices=-
-=Davlik bytecode verification disable/enable=-
---------------------------------
Background
---------------------------------
Last year I made RZRecovery for the original droid. It was a huge success, since then I have been asked to port to other devices. So here, about 1 year later, I have done just that. This will bring all the features of the old RZR plus a few new ones including the epic rom.tgz install format from the days of yore to any device. I have built this recovery specifically to handle all devices without the need for a recompile (except for Tegra2-based devices, they have to be recompiled because of some libc bugs). I have made img files for a few devices to start with:
---------------------------------
CONFIRMED
---------------------------------
HTC Thunderbolt
Samsung Nexus S
Samsung Nexus S 4G
Motorola Droid
HTC Incredible/Incredible S/ Incredible 2
HTC EVO 4G
---------------------------------
EXPERIMENTAL
---------------------------------
HTC MyTouch 4G/Slide
HTC Leo
HTC Dream/Sapphire/Magic
HTC Click/Tattoo
HTC Aria
HTC Wildfire
HTC Legend
HTC Desire/Desire CDMA/Desire S/ Desire HD
HTC Hero/Hero CDMA
Samsung Fascinate (need to find out where recovery is stored for mtd)
LG Optimus S
LG Optimus 1
LG Optimus V
LG Optimus 2X
Huawei Ideos
Huawei u8220/u8150
Motorola Cliq/ Cliq XT
Motorola Backflip
Motorola Atrix
PLEASE: IF ANY OF THSE EXPERIMENTAL BUILDS WORK, PLEASE POST AND LET ME KNOW SO THAT I MAY MOVE THEM TO THE CONFIRMED SECTION
In order to port RZR to anything, I need to know the base kernel address, the boot command line, the page size and the partition layout.
---------------------------------
SCREENSHOTS
---------------------------------
{
"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"
}
View all (in case forums limit the amount of images shown): http://rzdroid.com/ftp/recovery/screenshots/2.1.0/view.html
---------------------------------
CREDITS
---------------------------------
(without any of these individuals/organizations none of this could be possible)
CyanogenMod - for being completely open and having a huge database of device information
koush - for clockworkmod, where I got support for other partition types and filesystems
rbox - for repeat scroll and touch screen scrolling
cvpcs - for helping with anything I have ever asked
slayher - for showing me how to enable capacitive buttons on HTC devices
bekit - for showing me the bionic commits to get recovery built for tegra2's
trevorj - for the original battery charge knowledge
my wife - for giving me all the time I needed to get this done
all the testers for testing and encouragement!
---------------------------------
DOWNLOADS
---------------------------------
I will link img files for use with fastboot or flash_image and any applicable zips.
DISCLAIMER: Not that this needs to be said, but by downloading any of the files below, you take full responsibility for what happens with them. Make sure you have a way out if something goes wrong. The devices above are in the experimental section for a reason
EVO 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-supersonic-update.zip
SAMSUNG FASCINATE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-fascinate-update.zip
MYTOUCH 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-glacier-update.zip
HTC THUNDERBOLT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-mecha-update.zip
SAMSUNG NEXUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-nexusS-update.zip
SAMSUNG NEXUS S 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ns4g-update.zip
HTC INCREDIBLE 2: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivow-update.zip
HTC INCREDIBLE S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivo-update.zip
LG OPTIMUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderc-update.zip
LG OPTIMUS 1: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderg-update.zip
LG OPTIMUS 2X: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-p990-update.zip
MOTOROLA DROID: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-sholes-update.zip
HTC LEO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
HTC MAGIC: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
HTC DREAM: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC MARVEL: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC ACE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ace-update.zip
HTC DESIRE http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravo-update.zip
HTC DESIRE (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravoc-update.zip
HTC WILDFIRE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-buzz-update.zip
HTC CLICK: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-click-update.zip
MyTouch Slide: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-espresso-update.zip
HTC HERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-hero-update.zip
HTC HERO (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-heroc-update.zip
HTC LEGEND: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-legend-update.zip
HTC ARIA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-liberty-update.zip
MOTO CLIQ: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-morrison-update.zip
MOTO BACKFLIP: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-motus-update.zip
MOTO ATRIX: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-olympus-update.zip
HTC SAGA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-saga-update.zip
HUAWEI U8150: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8150-update.zip
HUAWEI U8220: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8220-update.zip
HTC VISION: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vision-update.zip
MOTO CLIQ XT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zeppelin-update.zip
HTC ZERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zero-update.zip
---------------------------------
SOURCE
---------------------------------
https://github.com/raidzero/RZrecovery/tree/gingerbread
---------------------------------
WALKTHROUGH
---------------------------------
Volume up/down - scroll (can hold down to repeat scroll)
HTC - touch screen - scroll
Home - select
Back/Power - back
Code:
Main screen
Reboot android
Reboot recovery
Reboot bootloader
Power off
Wipe menu
Wipe all - wipe everything on the device except recovery
Wipe system (the ROM)
Wipe data (your applications and settings)
Wipe .android-secure (other applications and settings on sdcard)
Wipe boot (the main android kernel)
Wipe cache
Wipe battery stats
Wipe dalvik cache (cache of optimized dalvik executables)
Mount menu
Mount/unmount system (the ROM)
Mount/unmount data (apps and settings)
Mount/unmount sdcard
Enable/Disable USB Mass storage
Nandroid menu
Nandroid Backup
Perform backup
choose boot,data,android-secure,system to back up
Nandroid restore
Choose backup
choose boot,data,android-secure,system to restore
Clockwork nandroid restore
choose backup and immediately restore the whole thing
Install from sdcard
choose item to install:
APK, ZIP, IMG, (must end in rec.img or boot.img) .TAR, .TGZ
Preinstall Menu
Abort Install
Backup before install (make a quick backup of the device naming it preinstall-date-time)
Wipe data
Perform install
if(APK)
Abort APK install
Install to system
Install to data
Extras menu
Custom Colors
Random - randomly generated color, will save to sdcard
Any other color - will save to sdcard
Rave mode - a totally random color each time the screen is redrawn (every key press)
Show battery status - will show charge status, level, temperature if available
Recovery overclocking
Kernel will report the available CPU slots, pick one and it will set the max to your selection. Saves to sdcard
ROM tweaks
Disable OTA update downloads in ROM - will prevent android from downloading updates OTA
Activate Root access in ROM
Yes - roots the current ROM (still requires the superuser.apk from chainsdd)
No - does nothing
Dalvik bytecode tweaks
Disable bytecode verification
Enable bytecode verificaion
this deserves some explaining. saved the best for last :) In android, when executables are loaded, the dalvik VM will go
through each line of instructions and make sure it is valid, if it isn't (poorly written application) it will fix it to the best of its ability. This verification process takes time. Disabling this will speed up all the operations on the phone and might even save some RAM. If it doesn't work for you or causes apps to crash, re-enable the verifier here.
So please, if you want this for your device just post here and I will try to get it done for you
POSSIBLE CAVEATS
Update.zip status 2: this means the update.zip you re trying to flash has an outdated update-binary (META-INF/com/google/android/update-binary). Please replace this file in your zip with my version (from gingerbread) here: http://rzdroid.com/ftp/recovery/gingerbread/APIlevel3-update-binary
Update.zip status 7: This means the script is not compatible with the update-binary. This will most likely happen after you replace the update-binary in an outdated update.zip. The most common errors are that the mount and format commands now take extra arguments. you must pass the filesystem type like so:
OLD:
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
NEW:
Code:
format("MTD", "yaffs2", "system");
mount ("MTD", "yaffs2", "system", "/system");
I have changed the API level to 2, to help alleviate some of these issues. It is still evel 3 but all level 2 update.zips should work fine.
Not the addition of the filesystem type. No idea why they changed this, seems like since it now uses recovery.fstab that this info could simply be figured out. or maybe I will implement a method of checking for status 7 and possibly telling it the filesystem information myself. Either way, this info will get you rolling now.
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
eoghan2t7 said:
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
raidzero said:
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
Click to expand...
Click to collapse
There is kernel source would that help? Thanks
Edit: no cm repo but heres the kernel source:
https://github.com/wingrime/android_kernel_swift_lg/
Sent from my LG GT540 Swift using xda premium
About to try this
nobody calls my EVO a fizzle and gets away with it!!
Well mate any luck?
Sent from my LG GT540 Swift using xda premium
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
raidzero said:
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
Click to expand...
Click to collapse
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
For wildfire s??
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
HD2
i like what u have here...if u can i hope i can use it on HD2
THX
Can it be made for Dell streak 5 PLease PLease..................
anyone try this on NS4G yet?
TheBurgh said:
anyone try this on NS4G yet?
Click to expand...
Click to collapse
ns4g is the phone I have. it works great
Would you mind making this available to HTC G1 please?
Thanks in advance.
ahmadns said:
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
Click to expand...
Click to collapse
marvel? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-marvel-update.zip
BeenAndroidized said:
Would you mind making this available to HTC G1 please?
Thanks in advance.
Click to expand...
Click to collapse
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
raidzero said:
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
Click to expand...
Click to collapse
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
BeenAndroidized said:
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
Click to expand...
Click to collapse
that is correct. flash it like any other update.zip please let me know if it boots and how it works!
eoghan2t7 said:
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
try this: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-swift-update.zip
let me know if it boots and how it runs
seaman2k said:
i like what u have here...if u can i hope i can use it on HD2
THX
Click to expand...
Click to collapse
htc leo, right? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
same story as the rest...
Related
[Official] HSG (X5A/X6) & Pandawill G11 rooting/dev thread (SetCPU & Root working!)
Chinese-manufactured devices, with Korean cpu.. The midX5a / midx6 are both Telechips-based tablets. They're very similar to the Augen device, except they have the actual HDMI port, 300M /data, correct /cache size and a 3.5" headphone jack
The Pandawill G11 seems to be a rebranded version of this hardware using the same firmware(s).
Note: There are older versions of this hardware with no HOME/MENU/BACK buttons, running WinCE. These cannot be upgraded to Android as far as we know right now.
TODO / What's not working: (Updated 24/8/2010)
- Add more languages (like Dutch!)
- Cleanup included languages (Georg77cz is working on cz/cs translation.)
- Find out how to increase /data to the full 3.3GB that's available on internal NAND (hexedit LK.ROM?)
- SetCPU (fc's after moving slider) Working! See attachment![/strike]
- Can't seem to enter recovery by hardware buttons Working, connect USB and use Rom Manager to reboot into recovery!
- Unpack tcc_8900mtd files Naobsd figured it out, thanks!
- Unpack system.img Naobsd figured out to patch unyaffs!
- Repack system.img Naobsd released tools for this.
- Unpack boot IMG, figure out base & pagesizes (4096 page size, base 0x40000000)
- Custom recovery - We have Clockworkmod working as of 20-8!
- Can't boot into recovery from ADB - (From firmware #348 this is fixed..)
- Factory defaults (Works in #348 and wipes properly using the recovery reboot.)
What's working: (As of firmware release #348)
- Custom recovery (Clockworkmod)
- Calibration (You must hold the stylus at the spot for some time.)
- Rooted!
- Telechips FWDN firmware recovery (via WinXP/2K)
- Telechips USB host booting method with empty(!) nand
- Rotation with 'RotateD' from market
- YouTube HD (Just push the Evo4G Youtube.apk)
Note there are similar models. Visit the HSG website and note the right side button spacing/placement.
Link: HSG Website
The model this topic is about, has the buttons spaced across the right side.
The other model that is not from HSG appears to be non-available from China sellers right now, or not in production yet for unknown reason. (sensor rumours)
Another third model has popped up, it's basically the same hardware in APAD casing with metal back plate.
I moved this thread over here from Slatedroid since it got filled with non-dev talk, and thier hosting keeps going offline. I hate it when i can't backtrack to my own findings
{
"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"
}
Specs/Facts:
- MIDX6 has on-board rotation sensor, but it's apparently not working in the firmware yet.
- MIDX6 has optional 3G / GPS inside
- MIDX5A is the basic model with no sensor/3G/GPS. (The rest is the same.)
- CPU Runs at 720Mhz stock
- Has HDMI port
- Has a normal 3.5" jack for headphones
- One speaker, and one microphone inside.
- Runs Android 2.1 eclair-update1
- No GPS/3G/Orientation sensor inside
- Linpack score around 4.9 with no mods / clean os.
- Metal top body, plastic bottom
- Mine came with 2x 1300mA battery inside!
- Battery lasts really long, i can run for ~6-7 hours at work with wifi on.
Quick review
I've used the device for about 3 days now with firmware #297, and it's very fast to use & works like a charm. It has a very solid build quality with a metal top on a thick plastic bottom, making it feel like a quality product. Market worked out-of-the-box with no fuss or hacks. Touchscreen is responsive, but resistive. If you want to slide, push down your finger first, then slide (don't hit-and-run or do a driveby with you finger on the screen).
Battery life is pretty damn good. I've been using it for at least 6-7 hours in one go, with wifi while debugging and ADB and such. The screen is nice & bright, and even if it's a resistive screen it works OK. The main reason for an initial slow reaction from the screen, is that the CPU is downclocked to 36Mhz when you are not doing anything. Edit: This is sorted with SetCPU 2.01! After the first wipe/slide it goes up to 720Mhz.(Yes, that's 120 Mhz more than the Augen!)
Note to posters: Please keep this thread clean. If it's not about rooting or dev, do not post it here please. Thank you!
Post reserved for updates:
Root updated (20-11-2010)
Updated One-click root for #348 and lower.
Download here
This also works with the newer revisions of this tablet with g-sensor
Recovery now working! (20-8-2010, requires #348)
See This Topic for working recovery files.
Steps for flashing with FWDN in USB mode (16-08-2010) (Thanks @fun_ & GeorgCZ for testing!)
(more details will follow)
- Figure out your device serial number and /data/softmac. Store it. (easiest to do, is flash same firmware, FWDN shows it)
- Option #1: You are on V7 (@205, #270, #297, #320) ? Use FWDN mode, and just flash it, format entire nand between different versions!
- Option #2: You are on V6 (WINCE) firmware ? Use use the internal switch to set USB host mode. Place tcBoot.rom in fwdnv7 folder
- When going from V6 to V7 firmware, you will need to erase the entire flash with the dropdown box.
- Plug in when asked, the device will boot with the USB boot mode. Then flash your firmware.
- It's almost impossible to kill the device. The CPU will boot in USB host boot mode if you erase the nand completely!
(In)Compatible USB devices (13-08-2010)
- Keyboards
- Mice
- Wifi USB/Keyboard (as long as they are USB HID devices with no drivers)
- CSR Bluetooth: Not working (no driver in kernel)
- UVC webcams: Not working (no driver in kernel)
SAFE MODE boot (12-08-2010)
This is a special mode if you screwed up something and can't get in the OS because of force-closes in an bad-behaving app that you installed..
- Ensure no power is plugged in
- Press the centre of the touchscreen, & keep it pressed.
- Power on the device as normal. Don't let go of the touchscreen..
- You're now in Safe mode! (a message should be in the bottom left corner stating so.)
Exact steps for flashing with FWDN (12-08-2010) (Thanks @fun_!)
- Power off the unit
- Unplug USB
- Plug in the AC adapter
- Firmly touch the touchscreen
- Power on the unit
After a while you'll notice it stays at the boot splash screen, then you can plug in the USB cable and fire up FWDN.
Google maps update failure fix (11-08-2010)
Connect using ADB and issue the following commands:
Code:
adb remount
busybox rm /system/app/Maps.apk
cd /system/bin
sh pm uninstall com.google.android.apps.maps
sync
Now you can install the new Google Maps version from the Market.
(If not, just reboot the device & try again.)
Extract kernel from boot.img (11-08-2010) (Thanks @geoRG77!)
You can extract the contents using split_bootimg.pl (needs linux+perl installation.)
http://android-dls.com/files/linux/split_bootimg.zip
This also works on tcc8900_mtd.img, since boot.img is near the start of this file. Need to DD of some bytes
(Note that system.img and others are also inside this MTD dump, it's for flashing the whole nand area in one go in the FWDN software.)
Modified INF file for ADB driver:
]usb_inf_X5A.zip
How to:
- Enable USB debugging
- Install the driver from my usb_inf_X5A.zip (2k/xp/32 bits)
- Unzip root_setcpu_X5A.zip into C:\rootfiles
- Start a command prompt and do cd /rootfiles, then root.bat
- You should get no errors, and after the reboot, your X5A should be rooted.
- Note, SetCPU does not seem to work properly.
Firmware layout #297 7-10-2010
Here's /proc/mtd output from #297 rom:
Code:
dev: size erasesize name
mtd0: 80000000 00080000 "bootloader"
mtd1: 00a00000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 01400000 00080000 "cache"
mtd5: 13b00000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00a00000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"
mtd9: 00100000 00080000 "tcc"
Firmware layout #348 7-10-2010
Code:
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 12300000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00100000 00080000 "misc"
mtd8: 00100000 00080000 "tcc"
Firmware layout #205 18-10-2010
Code:
mtd0: 80000000 00080000 "bootloader"
mtd1: 00500000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 03200000 00080000 "cache"
mtd5: 12800000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00500000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"
Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Firmwares
Below you'll find a fast mirror for the current firmwares:
(Do a Right-click, save as.. these are 7zip compressed, get it at www.7zip.com)
Firmware #205 (0730) - No market, pretty bland rom.
Firmware #297 (0803) - Works stable, has market.
Firmware #348 (0816) - First rom with recovery booting, but no keys work to select options
We don't know how to repack or unpack them yet. LK.rom seems to hold the MTD layout inside. If anyone figures out how to unpack/repack these files, please let us know.
19-8-2010: User fun_ figured out, we need to flash lk.rom as a single file, and then reboot to have new partitions used
Firmware Updating
There are two modes in which you can update the firmware.
The first mode is basic FWDN mode. The second mode with a blank nand is a factory USB host mode boot, that works even if the nand was completely erased by accident, or empty at the production line.
Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Basic FWDN is also outlined in the Chinese document:
http://www.zonko.nl/files/tcc/CBS7001 Android Instructions v1.01.pdf
Use it a basis for upgrading in this mode.
Basic FWDN mode
This is triggered by the following procedure, and the standard way to upgrade these devices:
Tablet side:
- Unplug tablet from the PC!
- Power off the tablet. Insert the power plug (required!)
- Press & hold finger on the touch screen, and then press & hold the powerbutton.
- The tablet powers up, and remains on the splash screen.
PC Side:
- Install the VTC drivers on your PC (tested OK on Win7 & WinXP 32 bit)
- Set up FWDN before plugging in the tablet
- Optional: Browse & add LK.ROM as a single file when coming from another partition layout, flash and reboot the tablet afterwards, then do the steps below. (You can skip this step, if you are staying on the same MTD layout i.e. flashing the same firmware revision you are on.)
- Browse & add the LK.ROM file.
- Browse & add the tcc8900_mtd.img file.
- Ensure no options are selected in the Tools - Options menu or you loose the mac/serial!
- Plug the tablet into USB
- Click the Nand area map and create a FAT partition for the remaining space.
- Yes, thats 'click on the square below the text' where it shows the block See this picture.
- If you're going to a different MTD layout, choose 'low format' in the dropdown.
- Click Start, and patiently wait.
USB Host boot mode
19-8-2010: No longer needed!
Fun_ figured out the LK.ROM holds the partition info. So if you're coming from another layout, simply flash LK.ROM first. The below procedure remains as a service for those that accidently bricked the device.
This mode is triggered when you erase the entire flash by accident, or when you put the switch on the mainboard inside your tablet to the other position.
You will need to add a bootrom to the FWDN folder where the .exe for FWDN resides. You can get that bootrom from here.
In this mode, the tablet will boot when connected by USB to the PC and init the cpu. After that, it can be flashed the same way as above. In this case you'll need to fiddle with the settings under 'Tools - Options' to set back the serial to what it was before the 'accident'.
If you desire, WinCE can be flashed in this way, if you kill the nand using flash_eraseall under Android..
Uninstall Chinese apps (18-08-2010) (thanks to Asure)
Code:
adb pull /system/app/ ./app
adb shell rm /system/app/91pandaspace_v2.3.apk
adb shell rm /system/app/himarket.apk
adb shell rm -r /data/dalvik*
adb shell sync
adb shell reboot
Official Firmware Download Link:
http://www.huashiguang.com/service.html
* * *
naobsd teardown:
http://twitpic.com/2do3a6
* **
I can open up a forum for you at:
Androidtablets.net
For now, it's a thread here
If a couple of you are up for it, that is. XDA is alright for dev talk though.
* * *
I repacked recovery.img earlier before:
http://www.multiupload.com/3N9VPWXS53
I unpacked Asure's boot.img using instructions from here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Then took the Augen Gentouch recovery, unpacked that as well to replace the ramdisk
The stock 297 recovery image is really large (10mb? Augen is 3mb with clockwork) and has a bunch of useless stuff in it.
So Asure, your recovery image didn't boot? I got all excited...
Edit: repacking doesn't work apparently.
I need to get myself one
I tried to repack the recovery.img using all the methods outlined here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
They all produce an image that looks fine in a hex editor at first glance, but fails to boot on a real device (After flashing it with flash_image recovery /sdcard/recovery.img for example)
I'm pretty sure there's a TTL serial port in the device, but i'll need some time to sort that out. I asked Koush for help, perhaps he can see what is wrong with the image.
Root Holding...
I have the model similar to the Apad with the hardware buttons. The Augen root method worked fine and looks to be holding so far, no stability issues or lockups using SetCPU with 120/720 scaling . I can provide some assistance from the "third" model with direction as needed.
My device is actually showing #320. My partition layout is similar to #297.
Latest Firmware update failure
I tried to flash the new firmware from HSG (16-8-2010)
but everytime it failed with this error
[ERROR] The old version(=0x07000002) device can't support 'MTD' fwdn area image.
i followed the same steps when i did the 13-8 update.
Anybody tried to flash it with succes ?
What am i doing wrong this time?
Please read & follow the steps in the second post. Low-format to get the new MTD layout.
Also, please keep this a dev topic. This is not HSG customer support
First, credits to Koush for his amazing recovery, the Android scene would be completely different if it wasn't for you!
Second, i wonder who @google thought it would be a great idea to force a huge download of 4.5GB + apps needed to compile a 13kb mkbootimg.
Anyway, with some files from someone else's kitchen (only 15mb download) i managed to compile mkbootimg with the new --pagesize parameter from Koush.
(This recovery's kernel --base 40000000 and requires --pagesize 1000 to work properly.)
I've updated the second post with the working recovery.
Also the one-click root.bat is back.
Enjoy your weekend!
Recovery is now working thanks to Georg77cz who provided unmissable help with testing this!
Check http://twitter.com/Asure007 for some pics. I'll upload the recovery tomorrow. For now, only confirmed to work on #348 roms! (older roms don't honour adb shell reboot)
So, now that we can do custom roms/updates/zips, does anyone have Dutch strings.xml for Settings.apk and SettingsProvider.apk from a Android 2.1 release ? HSG did not include this language as an option in any of the stuff on the tablet..
Edit: Never mind, i've pulled them off the emulator and added the sections that were missing (HDMI Output selection and such.)
Accessing Flash Mode MID701
I am not sure if you want to track here or in another thread, but I was able to find the right combo to access safe-mode/flashing mode on the 3rd device, MID701 with the #320 firmware.
To access the flashing mode for a MID701 device. After you have prepped your Telechips VTC driver and have FWDN running, do the following in order:
1) Flip the ON/OFF switch to the OFF Position
2) Connect the AC Adapter
3) Connect the USB Cable
4) Press and Hold the Home+Back buttons on the top of the device (both sides of the "rocker" must be depressed)
5) Flip the ON/OFF switch to the ON Position
In a matter of seconds you should get driver/telechips prompts and FWDN will light up. The screen WILL NOT come on in this mode.
After making a few backups and records, I may attempt to install the #348 firmware tomorrow.
I would suggest to ensure you have a working flash to go back to. From tests we did with #320 on HSG x5a the video is not working (white screen). ADB still works and we could flash_image back a #297 kernel(boot.img) into it to get video back & working.
If you really want to try something, try Clockwork Recovery for #320 tablets: http://bit.ly/aA06cY and let me know if it works
I can flash it but it doesn't escape the fact that I can't get to recovery from #320 lol. I will probably wait until the supplier releases the firmware Monday, so I have an absolute recovery path. Will post back with any success.
You can use ADB to get into recovery: adb shell reboot recovery
Or, if you're a windows user, install Droid Explorer, and use the option in the menu.
Or, if you want, install Rom manager from market, or reboot control widget. Plenty of options
Edit: Also, no need to wait for your supplier, i've put #320 here:
http://www.zonko.nl/files/tcc/Haina.android.320.7z
Few new things to report.
- I located a firmware that is #330 from Pandawill that works on my device. The market works, and it appears to have native support for playing xvid files in the gallery which my #320 build could not do, and I am unsure if the #348 builds have the ability.
-It feels a bit snappier than my #320 build.
-The #330 build also responds to the reboot recovery, which results in the Triangle Android update screen we have all seen before.
-Clockwork recovery also works on my device. I can scroll the recovery menu with the "Home" side of the rocker button. Clockwork reports that the back button is enabled, so it should work as well. The problem is the device is programed with the front button as a Sleep button, so it turns the screen on and off at the recovery menu. If I could remap the buttons, I should be in business.
I may dump the MTD image into one of my linux boxes and try to modify the partitioning a bit. Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.
LCD Density
For those who want a bit more screen real estate, you can modify the lcd density in the build.prop. I switched to 161 and it really scales well in some applications like the browser. Other places like the the status bar menus, and some applications, so no honor the new density and will not render scaled. From some translated notes 161, 162, and 180 seem to be the best values for higher density over the default of 240
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 161
adb pull /system/build.prop /directory/to/store/build.prop
edit your build.prop
adb push /directory/to/new/build.prop /system/build.prop
adb reboot
No sleep?
I've got the X5A yesterday and it came loaded with firmware #348. Rooted it last night and it's quite a brilliant little device!
I surfed the net for a bit and left it idle for the entire night last night, and it promptly ate around 40% of the battery. Spare Parts shows that it hasn't been sleeping properly (just like my old Samsung Galaxy) and that Wifi was running the entire time.
I looked on logcat and this line keeps popping up, not sure if it's causing the issue?
V/BatteryService( 937): lwgmUsbOnline
Googled it but nothing seemed to come up...
helfrez said:
Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.
Click to expand...
Click to collapse
As far as i know, the MTD partitioning is done inside LK.ROM.
You can try to change it in a hex editor, and see if that works. I'm not sure if the CRC changes, and it we can even raw hex edit it.. (200+mb for /data is already pretty good..)
Suggested steps:
- Using a hexeditor on lk.rom you can do a search for 'BMPG'
- Around 0x4d350 you should find the mtd table.
- You can see the partition names, and sizes.
- For example, in '#297' LK.ROM, this is at 350Mbytes (00 00 00 D1 00 00 00)
- Try to change to 00 00 00 FF 00 00 00, see what happens
(If this works it's for all TCC related devices, and we can get an even huger /data partition hehehe.)
This Thread will be for information for the Huawei Ascend M860.
The "Official" Thread has become cluttered with pointless questions and non high quality posts. Over the week I will be trying to scrape as much information as possible from the thread and post it here. If you would like to include information or correct information please PM me and I will add it to the relevant section.
The original mess of a thread is: http://forum.xda-developers.com/showthread.php?t=872608
Please don't post questions here if you have not searched the forums. They will be ignored.
If you are looking to flash back to stock or repair your phone:
http://forum.xda-developers.com/showthread.php?t=909243
General Ascend Notes
SPECIFICATIONS
Release Date: October, 2010
Dimensions (width x height x depth): 62.5 x 116 x 14 millimetres 2.5 x 4.6 x 0.6 inches
BoundingVolume:101.5 cubecentimetres
Mass: 130 grams (battery included)
Released Embedded Operating System: Google Android 2.1
Released Operating System_Kernel: Linux 2.6.29
CPU Clock: 600 MHz
CPU: Qualcomm MSM7627
Width of Machine Word: 32 bit
CPU+Core: ARM1136EJ-S
Level+1-cache: 16KiB data cache / 16 KiB instruction cache
Instruction-Set: ARMv6
RAM-type: SDRAM
RAM capacity: 256 MiB
ROM type: Flash EEPROM
ROM_capacity: 512 MiB
Display Type: color transflective TFT display
Display Color_Depth: 18 bit/pixel (262144 scales)
Display Diagonal: 3.5 " (89 millimetres)
Display_Resolution: 320 x 480 (153600 pixels)
Viewable Display Size: 1.94 " x 2.92 " (49.37 x 74.05 millimetres)
Pixel_density (dot pitch): 164.6 pixel/inch (0.15428 millimetre/pixel)
Audio_Channel(s): stereo sound
Microphone(s): mono sound
Loudspeaker(s): mono sound
Audio:Output: 2.5mm plug
Cellular-Networks: CDMA800, CDMA1900
Cellular-Data_Links: cdmaOne, CDMA2000 1xRTT, CDMA2000 1xEV-DO Rel. 0, CDMA2000 1xEV-DO Rev A
Cellular_Antenna: Internal antenna
Call_Alert: 40 -chord melody (polyphonic)
Vibrating_Alert: Supported
Speakerphone-: Supported
Positioning Device: Multi-touch screen & TouchPad/TrackPad
Expansion-Interfaces: microSD, microSDHC, TransFlash Supports High Capacity (SD 2.0/HC) memory cards with capacity of up to 32GB
USB: USB 2.0 client, Hi-Speed (480Mbit/s) USB Series Micro-B (Micro-USB) connector
Bluetooth+(802.15): Bluetooth 2.0, Internal antenna
Wireless-LAN/Wi-Fi802.11) IEEE 802.11b, IEEE 802.11g, 54 Mbit/s Internal antenna
Built-in-accelerometer: Supported
Battery Technology: Lithium-ion polymer battery
Battery Build: removable
Battery Capacity: 1500 mAh
Camera Sensor Type: CMOS sensor
Camera Resolution: 2048 x1536 pixels (3.15MP)
Camera Autofocus-(AF): Not supported
Camera Optical Zoom: 1 x
Camcorder: 352x288 pixels
File System Layout:
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0aa00000 00020000 "system"
mtd5: 04600000 00020000 "cache"
mtd6: 0bda0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
"Hidden" Menus:
Gtalk Diagnostics:
*#*#8255#*#*
NAM Programming:
##626*
Testing:
*#*#2846579#*#*
Display IMEI:
*#06#
Available Custom ROMS + Themes
The following ROMs are known to be in development or currently available
ICARUS MOD:
http://myascend.org/forums/index.php?/topic/175-rom-icarusmod-based-on-android-21/
ShadownavMOD:
http://myascend.org/forums/index.php?/topic/185-rom-shadownavmod-03-beta/
Bean Bag (Froyo) Testing:
http://myascend.org/forums/index.php?/topic/306-update-froyo-for-huawei-ascend-testing/page__pid__2904#entry2904
The Following Themes are reported to be working
MetaMorph:
http://forum.xda-developers.com/showthread.php?t=700173
rEVOlution(MetaMorph)
http://myascend.org/forums/index.php?/topic/242-revolutionmetamorph-blue/
HTC Sense theme for the Ascend:
http://myascend.org/forums/index.php?/topic/11-htc-sense-theme-for-the-ascend/
Development Related Files
KERNEL AND BOOT IMAGE
Eclair Kernel Released By Huawei
kernel-2.6.29-M860-Eclair.zip
b0904496c759787cdd201eef2839a5dd
Unpack Boot Image
unpack-bootimg.zip
97ad796c22155bd7358a156d16e5db02
Split Boot Image
split_bootimg.zip
c8e511e06a2bc1ab862e33e6f12c140a
Re-Pack Boot Image
repack-bootimg.zip
22e98c0993bfaa1048352efb85b78ba2
Huawei Specific Boot Image Format
--kernel kernel --kernel_addr 0x00208000
--ramdisk ramdisk.gz --ramdisk_addr 0x01200000
--second_addr 0x01100000
--tags_addr 0x00200100
--pagesize 2048
--align 2
--cmdline 'mem=211M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0'
-o $OUT.img
one more
One more reserve post
I dont know if this is chatter or not but
I have installed The custom rom ShadownavMOD
and I Have flashed but can any1 tell me how to install APPS2SD?
And i believe the answer to this question will help other ascend users.
Rooting your Huawei Ascend and Bloat removale list
Want to make your Huawei run a little faster and regain some lost memory from running apps in the background? This guide will help guide you root and remove the loaded bloat on the phone which should boost your available memory and help your phone run a little smoother.
There is no advantage or " speed boost " by rooting your phone unless you want to customize your phone using apps which require root or you want to improve the performance of your phone by removing unnecessary pre-installed apps (bloatware) that came on your phone that you can not delete any other way. The extra performance you see is that of free'ed up memory that is no longer being used by useless apps.
I've personally used this method and it works great but, do this at your own risk as it will void your warranty. I am on Cricket. You can always unroot your phone and delete your Z4 app if you need warranty work, but, like I stated, this is your risk to take.
ROOTING with Z4 Root.
Z4 is a one click up to root your phone giving apps and user access to hidden files or locked by the manufacture. Z4 Root is usually a market app but gets removed and reloaded with time ( reasons I don't know why ).
1. Enable USB Debugging on your phone.
( Settings> Applications>Development, make sure the there is a check in the USB debugging box. )
2. Using your web on your phone, go here and download the Z4 apk file.
( Because it's not available on the market, user's have made it easy to obtain, XDA ftw! )
3. Save it to your phone's SD Card.
4. The app does not usually appear in your app drawer so go to file manager and find it on the root of your SD Card. You may need to download Astro File manager from the market (free) to help you find it if you are having trouble. Astro is just an easy file manager to use. Z4 Root should be in your download file.
5. Once installed, open the Z4 app, and continue to the Permanent or Temporary Root screen.
6. Tap on Permanent. It will start the process and when finsished, it will restart your phone.
7. To make sure it worked, you will the the app Superuser in your app drawer and you can go back in to Z4 Root and you wil see the " unroot " button.
8. You are rooted!
Download Titanium Backup to start removing bloat. It also allows to backup all your apps. It's free and in my opionion, the best on the market.
Next, we will remove the bloat that came with the phone. I have persoanlly removed these files from my Ascend. Please make a backup of these apps just in case you have issues but, first and for most, to be on the safe side, you can freeze these apps first with Titanium backup to make sure your phone won't free. If your phone doesn't react bad towards the freeze, you are clear to remove.
Open Titanium Backup and click on Backup/restore and start the clean up process. Again, I stress being careful. Don't remove anything you are not comfortable removing. DO NOT remove anything that has to do with Google or has the word Google in it. These apps should be the same for Metro PCS but I would cross reference it.
1. UNO
2. Midnight Bowling 2
3. Documents 2 Go
4. Swype ( this will also alter the way your keyboard works and looks, please make sure you back this up so you can revert back to it if you don't like how the keyboard works and looks after removing )
5. MyAccount
6. K Mobile Web
7. Photobucket
8. Storefront
9. Poynt
Using SetCPU from the market will set your phone's processor to the maxinum stock running speed, which is 600Mhz. This is optional but almost a must as you will notice your phone running smoothly all the time and not just on demand. SetCPU is a free app on the market, download it and set it. It's super easy. Overclocking is not an option yet as there is no custom kernal for out phones and the stock kernal is locked.
You have now taken the first steps to making your phone run smoother and having some extra memory. If you used the Set CPU option, your golden!
Hope this helps move your Ascend along and stay posted to this thread for future development!
Can you post links to the bloat app apks just in case anyone does forget to back them up
DarkLG said:
Can you post links to the bloat app apks just in case anyone does forget to back them up
Click to expand...
Click to collapse
To my knowledge, there are not any APK files yet made for Ascend apps. There is however a general gTalk apk that you can download here just in case. Just use caution when deleting apps and don't delete anything you are not familiar with.
Ben's said:
To my knowledge, there are not any APK files yet made for Ascend apps. There is however a general gTalk apk that you can download here just in case. Just use caution when deleting apps and don't delete anything you are not familiar with.
Click to expand...
Click to collapse
Alright thanks I really need those cricket pre-installed apps lol guess I got to recover=/
so, there's no option for a nandroid backup on this yet, right?
what about doing a nandroid backup via PC/adb?
Clockworkmod for the Huawei Ascend has been officially released
{
"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"
}
I've just been informed by Koush that the Clockwork recovery mod for the Huawei Ascend is now available in the ROM Manager, go download it now! If you've already tried to apply the Clockworkmod from the ROM Manger make sure to press menu and clear your download cache. Happy ROM flashing and Nandroid backups!!!!
rEVOlution(MetaMorph) Blue Port of EVO theme made by Manup456 from XDA
I used to love the rEVOlution theme for EVO when I had it. Now that I have (and love) my Ascend, I had to have this theme again. So I found a mdpi port of the theme made by lilwing. I am currently tweaking it for our Ascends.
The original theme made by manup can be found here http://forum.xda-developers.com/showthread.php?t=736487.
I will release other versions as I work on it.
Instructions on how to install:
Make sure MetaMorph is installed
Unzip rEVOlution.zip
apply theme
** Edit build.prop under /system/ **
ro.config.hw_new_double_signal=0
ro.config.hw_customizeType=02
MetaMorph theme contains a xml file to make your progress bar, volume, etc **EDIT** blue
Home replacement used in screen shots is LauncherPro
Clockwork mod. Good news. Downloaded and installed. Any news on the icarus front yet.
Sent from my M860 using XDA App
Do u know where I can get the gtalk app for free? I was freezing apps using titanium back up and accidentally un-installed gtalk.
Sent from my M860 using XDA App
Phenom10 said:
Do u know where I can get the gtalk app for free? I was freezing apps using titanium back up and accidentally un-installed gtalk.
Sent from my M860 using XDA App
Click to expand...
Click to collapse
This has already been addressed in post #9.
Please search threads for questions already answered. The original thread has been now closed due to post clutter and we would like to keep this thread clean. Thanks
joenathane said:
I've just been informed by Koush that the Clockwork recovery mod for the Huawei Ascend is now available in the ROM Manager, go download it now! If you've already tried to apply the Clockworkmod from the ROM Manger make sure to press menu and clear your download cache. Happy ROM flashing and Nandroid backups!!!!
Click to expand...
Click to collapse
wow, awesome news thanks!
Ben's said:
This has already been addressed in post #9.
Please search threads for questions already answered. The original thread has been now closed due to post clutter and we would like to keep this thread clean. Thanks
Click to expand...
Click to collapse
Its safe to assume nobody really cares about this thread. Most of the people that care are using myascend.org, and having an admin close our other thread which was like our general discussion, I'm sure its safe to assume its better off over there
Anyway, for new-comers using the Huawei Ascend, visit http://www.myascend.org for extensive tips and guides made strictly for our little beast!
Sent from my Droid
takenone said:
Its safe to assume nobody really cares about this thread. Most of the people that care are using myascend.org, and having an admin close our other thread which was like our general discussion, I'm sure its safe to assume its better off over there
Anyway, for new-comers using the Huawei Ascend, visit http://www.myascend.org for extensive tips and guides made strictly for our little beast!
Sent from my Droid
Click to expand...
Click to collapse
No, that isn't true!!!!!!!!!!!!! Please, just let us use this thread without it being locked again!
joenathane said:
I've just been informed by Koush that the Clockwork recovery mod for the Huawei Ascend is now available in the ROM Manager, go download it now! If you've already tried to apply the Clockworkmod from the ROM Manger make sure to press menu and clear your download cache. Happy ROM flashing and Nandroid backups!!!!
Click to expand...
Click to collapse
Ok so i flashed the clockwork recovery and when i try to boot into recovery i just get the huawei splash screen that never goes away. Any ideas?
Ok if you have this problem after using the amon ra you will need to go into settings and check the box that says erase recovery before flash, then reflash the latest recovery again. After this you should be able to boot into recovery. Sorry to post a question in this thread but i felt it could be relevant to others.
S.I. 77
this is a work-in-progress development project for porting CyanogenMod 7 (gingerbread/2.3.7) and ClockworkMod Recovery 5 to Telechips TCC8902 and TCC8803 tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* DO NOT USE FwTool APP. IT WILL BRICK TOUCHSCREEN!
* project page
http://androtab.info/telechips/cyanogenmod/
* supported tablets (TCC8902 with atheros wifi)
a-rival PAD NAV-PA80/83 capacitive (a.k.a. ViewQuest Slate 8")
a-rival PAD NAV-PA81 resistive
Cherrypal CherryPad America (a.k.a. NanoPad)
COBY Kyros MID7015(4K)/7016(8K) GB ROM (a.k.a. Emdoor EM71 singletouch, Optimist Gpad701)
ConCorde tab 7.1 GB ROM (a.k.a. DWCO UM700)
Dropad D10 (a.k.a. GOCLEVER TAB T73)
Emdoor EM51
Emdoor EM71 multitouch (a.k.a. Herotab G701, Lonpad D7)
Haipad M1001 GB ROM 4K(non-HY) and 8K(HY) (a.k.a. Musican U10, Telepad 10.1)
Haipad M701 GB ROM 4K(non-HY) and 8K(HY) (a.k.a. Musican U70, Pandawill G10 1st/3rd model)
HSG X5A (a.k.a. Herotab RK7, Pandawill G11 1st model)
HSG X5A-G (a.k.a. COBY Kyros MID7005, Herotab X5A, Pandawill G11 2nd model)
HSG X6D
HSG X6 GB ROM
inet S1008
Optimist Gpad802 GB ROM
Phecda P7 4K(non-HY) and 8K(HY) (a.k.a. TMARSS P7)
Phecda P7S GB ROM
Storage Options miScroll GB ROM
Storage Options Scroll 7" capacitive GB ROM
Storage Options Scroll 7" resistive 4K(non-S) and 8K(S)
Storage Options Scroll 8"
* supported tablets (TCC8902 with realtek wifi)
Haipad M701 512MB
RoverPad 3W T71
Yarvik TAB211 (a.k.a. EKEN MT705)
* supported tablets (TCC8803 with atheros wifi)
COBY Kyros MID7022 (a.k.a. ConCorde tab 7020, Emdoor EM73 capacitive HY30, Joyplus M778 capacitive HY30, Optimist Gpad702 HY30)
Emdoor EM73 capacitive GC2M 4K and 8K (a.k.a. mivvy MIDroid H23, Joyplus M778 capacitive GC2M, Kogan Agora, Optimist Gpad702 GC2M, Telepad 7C)
Emdoor EM73 resistive AK GC2M, HY30 and SX HY2M (a.k.a. DFP7002A8, Joyplus M778 resistive)
inet 11A3 resistive and 11A4 capacitive
LY-F521 with 1024x600 LCD (a.k.a. Diel Flick 7", Sense V7, Suli MY-7)
LY-F521 with 800x480 LCD
* supported tablets (TCC8803 with realtek wifi)
inet 11A5 capacitive
* current status (2011/10/29)
not work:
3G, bluetooth, camera, hardware accelerated video, GPS, HDMI, and many things which you expect to work
work:
accelerometer, audio, gapps, internal NAND flash, SD card, touchscreen with calibration app, USB host/device, wlan
* changelog
refer git log
* resources
http://www.cyanogenmod.com/ (What is CyanogenMod?)
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps (Google Apps)
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
http://source.android.com/source/
http://review.cyanogenmod.com/#q,status:merged,n,z (CyanogenMod merged changes)
https://github.com/naobsd/cm_device_telechips_common
https://github.com/naobsd/cm_device_telechips_tcc8803
https://github.com/naobsd/cm_device_telechips_tcc8803rt (for realtek wifi models)
https://github.com/naobsd/cm_device_telechips_tcc8902gb (for TCC8902 with GB ROM)
https://github.com/naobsd/cm_device_telechips_tcc8902rt (for TCC8902 with realtek wifi models)
https://github.com/naobsd/cm_device_telechips_tcc8902 (for TCC8902 with Eclair ROM)
https://github.com/naobsd/cm_external_yaffs2/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
https://github.com/naobsd/cm_frameworks_base/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
https://github.com/naobsd/cm_packages_apps_TSCalibration
https://github.com/naobsd/cm_system_core/compare/gingerbread-naobsd (placeholder for patches to cherry-pick)
http://www.bernhard-ehlers.de/projects/unyaffs.html
* users' forum
http://scrolltabletforum.co.uk/site/viewtopic.php?f=15&t=1390 (Scroll)
* How to make backup of stock recovery
1. download dump-recovery-signed.zip and put it as update.zip on root of SD card (e.g. /sdcard/update.zip) *1 *2
2. install update.zip from stock recovery *3
stock recovery will be dumped as dumped_recovery.img and /proc/mtd will be copied as dumped_proc_mtd.txt on root of SD card. keep them in safe place.
* How to install ClockworkMod Recovery 5
1. make backup of stock recovery
2. download recovery.zip and put it as update.zip on root of SD card (e.g. /sdcard/update.zip) *1 *2
3. install update.zip from stock recovery *3
clockworkmod will be booted on next reboot recovery.
how to operate: MENU/VOL- = next(down), SEARCH/VOL+ prev(up), HOME/POWER = select, BACK = back
*1 if recovery is 3e, you can put it with any name on any directory in SD card
*2 some tablets/roms mount internal storage as /sdcard. confirm update.zip exists on root of SD card.
*3 some tablets/roms have system update function in Settings to install update.zip
* How to install ClockworkMod Recovery 5 (alternative)
a. flash recovery.img in recovery.zip by fastboot (if your tablet has fastboot mode)
b. flash recovery.img in recovery.zip by flash_image command on root shell
c. flash tcc_mtd.img with clockworkmod recovery.img by FWDN
you may need to delete /system/etc/install-recovery.sh before install (if it exists on your tablet)
* How to install CyanogenMod 7
1. install ClockworkMod Recovery 5
2. reboot recovery
3. make backup of stock ROM
4. wipe data/factory reset *4
5. install cyanogen.zip
6. reboot
7. touchscreen calibration *4 *5
*4 only if you are upgrading from non-CM7 ROM (CM7 1st install)
*5 only if you are using resistive touchscreen or misaligned capacitive touchscreen. if calibration is not needed, press BACK to cancel calibration.
* How to flash FWDN image (Windows PC is required)
i) prepare
1. download FWDN_V7_v2.13.exe
2. download & install VTC Driver v5.xx for your Windows PC
3. download lk.rom and tcc_mtd.img for your tablet (DO NOT USE FILES FOR OTHER TABLETS!)
4. connect power cable (do not use USB power for safety)
ii) flash bootloader(lk.rom) you can skip this step if you already flashed proper lk.rom or you don't have proper lk.rom for your tablet
1. start FWDN on PC
2. drag & drop lk.rom into FWDN window
3. (re)boot tablet into FWDN mode
4. connect PC and tablet (window popped and size of "NAND Data" is displayed in Area Map in FWDN window)
5. confirm checkbox of lk.rom is checked
6. click "Start" & wait complete
7. disconnect & reboot tablet into FWDN mode to use new(just flashed) bootloader
8. uncheck checkbox of lk.rom (it's ok if checked but no reason to flash again in next step)
iii) flash Android image and initialize internal NAND(FAT) partition
1. drag & drop tcc_mtd.img into FWDN window
2. (re)boot tablet into FWDN mode (if you forgot it in 7. in previous step)
3. connect PC and tablet
4. click "NAND Data" in Area Map in FWDN window *6 *7
5. fill "Image File Path" (use [...] button) *8
6. click "Create Image" (NAND Data.fai will be added in main FWDN window)
7. confirm checkbox of tcc_mtd.img and NAND Data.fai are checked
8. click "Start" & wait complete (take several minutes)
9. disconnect & reboot tablet
*6 creating new NAND Data.fai is required when size of NAND Data(FAT partition) is changed by flashing new lk.rom in previous step. you can use same NAND Data.fai if you are using same lk.rom. don't use NAND Data.fai from other people.
*7 if size of NAND Data is not changed, you can skip flashing NAND Data.fai to keep your files in NAND(FAT) partition.
*8 you can make non-empty NAND Data.fai in this window
* issues
no mic input with stock apps
USB host on Scroll 7" resistive and 8"
USB mass storage mode (mount from PC) under some condition
some USB mouse
suspend/resume on Emdoor's tablet with Eclair ROM (a-rival PADs, EM51, and EM71 multitouch)
* tips
- what is lk_androtab.rom? / how to increase size of /data?
use lk_androtab.rom in FWDN.zip. in lk_androtab.rom, size of partitions are modified to get more /data. in addition to this, lk.rom/lk_androtab.rom for COBY Kyros MID7015/7016/7022 and EM73 capacitives have +512MB for MTD(assigned to /data) and -512MB for NAND.
- how to use internal NAND flash as SD card?
Settings -> CyanogenMod settings -> Application -> Use internal storage -> On -> reboot
if enabled, internal NAND flash is mounted on /mnt/sdcard and SD card is mounted on /mnt/nand.
in clockworkmod, internal NAND flash is mounted on /emmc. it will be used by "install zip from sdcard -> choose zip from internal sdcard".
- I like portrait / my favorite portrait apps are upside down / accelerometer axes are wrong on some apps
make /data/local.prop with following 3 lines, then reboot.
Code:
accelerometer.hwrotation=270
input.hwrotation=270
ro.sf.hwrotation=270
* FAQ
- what is GB ROM?
old TCC8902 tablets were shipped with Eclair ROM, but there is GingerBread ROM for some tablets. bootloader(lk.rom) and kernel in GingerBread ROM are not compatible with bootloader/kernel in Eclair ROM. CM7 for GB ROMs only work with bootloader in GB ROM, so you need to install GB ROM before installing CM7. (you can use CM7 FWDN image as alternative)
- what is 4K/8K?
there is 2(or more) variants for some tablets. they have different NAND, pagesize are 8192 or 4096, and it may need specific kernel for each.
HY means Hynix, and S means Samsung.
- touchscreen doesn't work (EM71/73)
there is many variants for EM71 and EM73. check your tablet carefully and use proper file.
- touchscreen calibration doesn't run on 1st boot
try run manually
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
- I want to do calibration again
delete following files if exist, reboot, run calibration app, then reboot again
Code:
/data/misc/pointercal
/data/misc/idc/*
- I can't push any file under /system/
Code:
adb remount
- install failed on some apps (e.g. Angry Birds)
remove SD card before install
- no HQ video on youtube app/web
yes, certainly
- no HDMI output
yes, certainly
here is clockworkmod recovery for Kyros7015/Gpad701 users who installed GB ROM(lk.rom)
http://androtab.info/files/tcc8902/cwm/KYROS7015-GB/
ALL FILES UNDER KYROS7015-GB DIRECTORY ARE JUST FOR TEST. DO NOT USE THEM FOR DAILY USE UNTILL TEST IS DONE.
I can't test it at all. if it can be booted, please check /proc/mtd at first
Code:
dev: size erasesize name
mtd0: 00a00000 00100000 "boot"
mtd1: 00500000 00100000 "kpanic"
mtd2: 0b400000 00100000 "system"
mtd3: 00400000 00100000 "splash"
mtd4: 02800000 00100000 "cache"
mtd5: 10500000 00100000 "userdata"
mtd6: 00a00000 00100000 "recovery"
mtd7: 00100000 00100000 "misc"
mtd8: 00100000 00100000 "tcc"
then try to make backup.
Just flashed Clockworkmod on my GB 7015A. Will try it tomorrow. Thanks for the work
by the way, is fastboot mode(not FWDN mode) exist on GB ROM for Gpad701/Kyros7015?
if yes, flashing recovery.img is easy on GB ROM, right?
if no, should I make tcc8900_mtd.img with clockworkmod recovery for easy install?
(no need talk about rooting here. it's meaningless for us because we can modify any files in .img directly)
Fast boot is present
Hey Fun,
Yes fast boot is present in the OEM version.
Cheers
jschill31 said:
Yes fast boot is present in the OEM version.
Click to expand...
Click to collapse
thank you. then, you can flash recovery.img with fastboot easily, right?
20110529 for Kyros 7015(non-GB ROM)/EM71/EM51 are uploaded.
I'm thinking better way to make zips/imgs to support many tablets...
You r da man!
Fun,
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Cheers
jschill31 said:
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Click to expand...
Click to collapse
here is dev thread, and I don't have that tablet, so if you tried clockworkmod recovery on Kyros 7015 with GB ROM, I want to hear detail what works and what not.
reboot recovery ok? /proc/mtd ok? backup ok? restore ok?
EDIT: oops I read wrongly. "has made a nandroid" == "backup ok", right?
CM7 for it is already uploaded on my site, but I don't know it boot or not. even if everything works as I except, touch screen will not work because there is no calibration yet.
please don't think "I uploaded" is "it boots". please don't consider "it boots" is "it works without problem". test is required but I can't do it on real device.
EDIT:
here is open forum. anyone can join/leave here.
(I'm not owner/admin. I just started this thread)
jschill31 said:
Fun,
I am excited to say that your Clockwork recovery has made a nandroid of the new OEM 2.3.1 for the Coby 7015. I can't wait to see how your CM version progresses. Is it ok with you to direct some other users to your thread?
Cheers
Click to expand...
Click to collapse
me to iam excited. I will wait. Good work
fabricioemmerick said:
me to iam excited. I will wait. Good work
Click to expand...
Click to collapse
I don't have Kyros 7015. someone need to go further away.
fun_ said:
thank you. then, you can flash recovery.img with fastboot easily, right?
Click to expand...
Click to collapse
yep, just did it in fastboot. Really the easiest method to flash recovery. ClockwordMod 3.2.0.0 also made a successfully backup of my GB 7015A tablet. Did it try to restore though but I guess if the mtd is correct for the backup it will be with the restore.
Thanks a lot for that fun
thank you for your cooperation.
here is next test file for Kyros 7015 GB ROM users.
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/cyanogen_kyros7015-ota-eng.fun.zip
it's CM7 for Kyros 7015 GB ROM.
there is no support for touch screen calibration (I think no calc_table on GB ROM, but please confirm), so it will be only for test purpose. please try if you have enough free time
I want to know it boots or not. if not boot, what happen e.g. "a n d r o i d" yes/no, boot anim yes/no, adb yes/no, etc... if adb works, I want to see logcat.
--
I noticed EM71 is usable for this work... touchscreen doesn't work on kernel for Kyros 7015, but it can be usable for initial porting work.
anyway, to get Kyros 7015/EM71 in Japan, cost performance isn't good
I installed the rom for GB and installed your CM7 it gets to chinese 1st boot screen
Then my screen goes black and doesn't do anything ADb doesnt recognize it.
hankm24 said:
I installed the rom for GB and installed your CM7 it gets to chinese 1st boot screen
Then my screen goes black and doesn't do anything ADb doesnt recognize it.
Click to expand...
Click to collapse
oops. thanks. probably insmod lines in init.rc is wrong (I forgot some args)
I'll make next test image, but if you can, please remove all insmod lines from init.rc. I think at least adb will work... (but will not boot without mali.ko. just for testing)
--
try this boot.img
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/boot.img
20110529 cyanogen.zip is also replaced just now.
Trying
Okay will try your boot.img in a while my tablet is completely dead ATM. When it's charged i'll flash it and report back
hankm24 said:
Okay will try your boot.img in a while my tablet is completely dead ATM. When it's charged i'll flash it and report back
Click to expand...
Click to collapse
Any luck?
And also, how are you guys able to make cm7 now? For a while everyone said there was almost no way, then it randomly showed up =o
fun_ said:
thank you for your cooperation.
here is next test file for Kyros 7015 GB ROM users.
http://androtab.info/files/tcc8902/cm7/20110529/KYROS7015-GB/cyanogen_kyros7015-ota-eng.fun.zip
it's CM7 for Kyros 7015 GB ROM.
there is no support for touch screen calibration (I think no calc_table on GB ROM, but please confirm), so it will be only for test purpose. please try if you have enough free time
I want to know it boots or not. if not boot, what happen e.g. "a n d r o i d" yes/no, boot anim yes/no, adb yes/no, etc... if adb works, I want to see logcat.
--
I noticed EM71 is usable for this work... touchscreen doesn't work on kernel for Kyros 7015, but it can be usable for initial porting work.
anyway, to get Kyros 7015/EM71 in Japan, cost performance isn't good
Click to expand...
Click to collapse
Here's the logcat with the black screen after flashing...
ps: I'm now about to flash the boot.img you created. Will post my feedfack once done
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v4 - win8 x64 support
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
yuweng said:
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
Click to expand...
Click to collapse
glad to hear smth like that :victory:
hope it`ll helps to make some things easily
but TWRP is much better for me for a while
and I`ve my own kitchen to work around with apks and jars and all firmware at all - odex and deodex them, but I didn`t translate it to english yet http://forum.china-iphone.ru/viewtopic.php?f=31&t=19708
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
yuweng said:
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
Click to expand...
Click to collapse
i`m just modest user of chineese phone - and while I`ve making it better - I`ve made some scripts - a lot of things i`ve got from this forum
wow... I`m really sorry - yesterday I forgot to attach STD bat files in archive - so please - reload files!
Thanks for the tool, it's compact and fast to work with.
Now at my first attempt to decompile it doesn't find some file and the ramdisk folder inside boot remains empty:
Code:
[total hits/matching patterns/non-matching patterns]
[298/1/0] bin\off2.txt
1 files checked, 1 changed.
- pagesize - 2048
- size of image - 7232000 byte
- ram_disk offset - 3272704
- split kernel...
3268608 bytes copied.
- extract ram_disk.gz...
3959296 bytes copied.
- unpack ram_disk.gz...
- unpack ram_disk.cpio...
[B]The system cannot find the file specified.[/B]
- copy source F:\Porting\ALL_phones_Boot_Recovery_repack_util_for_WINDOWS\boot.img to unpacked folder (to keep source image)...
Press any key to continue . . .
Smth. went wrong... can You give me your boot?
I have to say one thing - not ALL boot can be unpacked - some phones have they own boot structure - it is not correspond to this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images - so my utility cannot process them.
For example it is Samsung Note (1) Samsung Galaxy Tab (1)... maybe other.
ps _polimorph_ - by the way... I have an interesting idea.
after unpacking gz archive - You should receive a file without extension in /boot folder - usually it is named "ram_disk" - and after that, my script uses it as source cpio archive to extract.
BUT! if in your boot this file was named "rmdisk" for example - script will stop after gz extraction - because were is no right-named cpio file to decompress.
this is easy to check
Works on I9001, but not on I9003.
Alex93917
the structure of stock ROM for i9003 is:
and (!) my utility works fine with normalboot.img - but not (!) with boot.bin - it`s different part of ROM
Now Allowed to Post
michfood said:
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v2 - fixed some bags with STD unpack/pack
Click to expand...
Click to collapse
Hi michfood!
A massive thanks for this fantastic recovery and for all your help getting it to work on my MTK6575 GB v2.3.6 device :angel:
I was not allowed to post here earlier because I was a noob but i am sure you have helped many people without knowing it. Please Please keep up the great work us noob's would be toltally lost without you. :good:
Regards bigrammy.
uboot & nvram backup mtd is it possible?
Hi michfood,
Could I call upon you for help once again
TWRP is without any doubt the best most user friendly recovery :good:
It works flawlessly on my Zopo zp300+ MT6577 Android 4.0.4 (ICS) :good:
With the help you provided me already TWRP also works great on my HDC A9300 MT6575 Android v2.3.6 (GB)
I was wondering if I we could get TWRP to backup uboot & nvram on the mtd version like it does on emmc version
I am unsure of the difficulty in doing this or is it a matter of simply editing a few lines of text.
Could you please advice once again which file's script's I need to edit etc
Here are the mtd partitions again from my device for your info.
adb shell
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvram"
mtd3: 00020000 00020000 "seccnfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00500000 00020000 "boot"
mtd6: 00500000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 12700000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 07f20000 00020000 "userdata"
Hope you can help :fingers-crossed:
Thanks. bigrammy
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
michfood said:
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
Click to expand...
Click to collapse
Thanks for your reply :good:
So not quite so easy then I thought it maybe a bit more complicated but I had to ask :laugh:
I will post the question over on the TWRP thread as you suggest to see if anyone there can help :fingers-crossed:
Thanks again michfood for your help & hard work on this tool :angel:
Regards. bigrammy
bigrammy said:
but I had to ask
Click to expand...
Click to collapse
- no question, no answer
U understand that I mean... in Russia there`s a good saying - "follow to Kiev by tongue" - means do not shy to ask - it`s much better to be "know-hothing"
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Sent from my MT11i using xda premium
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
cmoegele said:
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
Click to expand...
Click to collapse
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Ghostfreak NB said:
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Click to expand...
Click to collapse
I haven`t, have You?
I`ve no answer because I never repacked Xperia boots. To do so, at first I need a Xperia boot.img
michfood said:
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Click to expand...
Click to collapse
Windows 7 locks the rmdisk folder so the script will fail.
Exec: %~dp0bin\chmod og=xr rmdisk
Then Cd rmdisk will give:
Access is denied.
- pack rmdisk to cpio...
/usr/bin/find: `./rmdisk': Permission denied
28482 blocks
The system cannot find the file specified.
- pack rmdisk.cpio to gzip...
- make new image...
The system cannot find the file ../pagesize.txt
- pagesize
error: unsupported page size 0
The system cannot find the file specified.
- done.
Press any key to continue . . .
Hi,
I have an unknown tab working under android 4.2.2 , how can i install TWRP or CWM on it? the apps on playstore don't help me ..
help me please
Thank you
saywow said:
Hi,
I have an unknown tab working under android 4.2.2 , how can i install TWRP or CWM on it? the apps on playstore don't help me ..
help me please
Thank you
Click to expand...
Click to collapse
is it rootable? if you dont know any information of the device you probably have to build a custom recovery yourself.
Yes it's rooted , all the information that i have aren't similar to these of the others android device (all of them start with ATLAS10 (the device name)) , what kind of information you need ? how can i creat my own recovery mod? am wondering if there is any way to backup my frimeware and creat a custom rom for it? because the stock rom is using 4xx\1024 Mo of memory (when boot) and there is no custom rom for my device
saywow said:
Yes it's rooted , all the information that i have aren't similar to these of the others android device (all of them start with ATLAS10 (the device name)) , what kind of information you need ? how can i creat my own recovery mod? am wondering if there is any way to backup my frimeware and creat a custom rom for it? because the stock rom is using 4xx\1024 Mo of memory (when boot) and there is no custom rom for my device
Click to expand...
Click to collapse
There are a few ways to make your own recovery, you would just have to look at guides, does it have a mediatek CPU? If so I don't know if you can, I could be wrong but still.
Trozzul said:
There are a few ways to make your own recovery, you would just have to look at guides, does it have a mediatek CPU? If so I don't know if you can, I could be wrong but still.
Click to expand...
Click to collapse
How can i know if i have mediatek CPU or not ?!
saywow said:
How can i know if i have mediatek CPU or not ?!
Click to expand...
Click to collapse
There are a few apps on the playstore that can tell your device information. Most Chinese tablets are mediatek
Trozzul said:
There are a few apps on the playstore that can tell your device information. Most Chinese tablets are mediatek
Click to expand...
Click to collapse
i have processor = ARMv7 Processor rev0 (v7l)
Cpu max/min clock : 1608/312 MHZ
MEMTOtAL = 1GB
is that good ?
saywow said:
i have processor = ARMv7 Processor rev0 (v7l)
Cpu max/min clock : 1608/312 MHZ
MEMTOtAL = 1GB
is that good ?
Click to expand...
Click to collapse
At least its clocked kinda high, still need to find out what CPU version is it
how can i ?!
saywow said:
how can i ?!
Click to expand...
Click to collapse
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Trozzul said:
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Click to expand...
Click to collapse
do you mean antutu benchmark ?!
saywow said:
do you mean antutu benchmark ?!
Click to expand...
Click to collapse
yes benchmark, sorry meant what CPU it has not CPU version. at the end of the test it shoudl tell you your device specs.
Ok thank you , once i will connect to wifi i will re download it and i will answer you because i don't have it anymore , by the way i have already benchmarked it and the result was better then s3's result (+20.000Points)
saywow said:
Ok thank you , once i will connect to wifi i will re download it and i will answer you because i don't have it anymore , by the way i have already benchmarked it and the result was better then s3's result (+20.000Points)
Click to expand...
Click to collapse
haha my moto x is 22k how many cores?
Trozzul said:
haha my moto x is 22k how many cores?
Click to expand...
Click to collapse
Quad if my memory is good
and the results was before i "optimize it" with any thing
saywow said:
do you mean antutu benchmark ?!
Click to expand...
Click to collapse
my cpu is rk3188
saywow said:
my cpu is rk3188
Click to expand...
Click to collapse
Crap rockchip, i dont know about their partitions, you said its rooted? type this in the terminal app (you can get it off the play store) type in SU first
Code:
cat /proc/mtd
tell me the outcome.
also see here http://androtab.info/clockworkmod/rockchip/ im not positive on it
Trozzul said:
Crap rockchip, i dont know about their partitions, you said its rooted? type this in the terminal app (you can get it off the play store) type in SU first
Code:
cat /proc/mtd
tell me the outcome.
also see here http://androtab.info/clockworkmod/rockchip/ im not positive on it
Click to expand...
Click to collapse
That's hurt my feelings
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 01000000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 22800000 00004000 "backup"
mtd5: 18000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 33b800000 00004000 "user"
saywow said:
That's hurt my feelings
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 01000000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 22800000 00004000 "backup"
mtd5: 18000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 33b800000 00004000 "user"
Click to expand...
Click to collapse
Alright cool it has a mtd partition, so that's a good thing. You SHOULD be able to follow any guide with making a cwm port, some people will direct you to make cyanogenmod along with it because it follows along side it. I can't direct you to a guide but there should be lots you can check out, did you look at that link I showed you?
Trozzul said:
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Click to expand...
Click to collapse
I didn't really understand, what should i do after downloading the file for my cpu?! (i'm talking about the link that u gave to me)