Related
I am very new to the android parralel scene (and the android and smartphones in general) so please excuse me if I have missed obvious things.
I am trying to do a custom android kernel on a CyanogenMod stable in order to activate SCTP support on a HTC Magic (sapphire) PVT 32B (google branded).
I have followed the this tutorial : wiki.cyanogenmod.com/index.php/Building_from_source to make the kernel (2.6.29-cm42) and this tutorial wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port for the packing.
My base is update-cm-4.2.14.1-signed.zip
I have tried with my new package as a module (and also redone modules.sqf) and also in-kernel.
I have tried the full update, and I've also tried to patch the kernel on a clean Cyanogen install.
Everytime I get stuck on the spash screen (google io09 developer conference).
Thanks for having read that post!
NB: Before the manipulation I had made a nandroid backup so I can get back without problem.
I use cm-recovery-1.4.img as recovery image with fastboot, and I noticed that I can't use adb to push data on the sdcard and then install it with the recovery. In fact the commands seem to work, but behind the scene it is the old sdcard.zip that is installed. I have to use my backup, fullboot, put my test update on the sdcard, rebootfastmode recover and then install.
Ah also, I would be really happy if you could tell me how to diagnostise errors on the bootphase. I'm currently totally helpless (and that's why I am posting here ^^).
I am now trying to build a new complete cyanogenmod from source with my custom kernel and modules. I don't think it will resolve my problem but I hope it will help me in understanding the problem.
While waiting for my repo sync (that won't end before tomorrow :/) I have made a new attempt at a CyanogenMod mod.
So i recompiled my kernel
Regenerated the modules
generated the modules.dep
Remade modules.sqf using update-cm-4.2.14.1-signed.zip as a base
Inserted wlan.ko and my new boot.img (made with unpack repack) into update-cm-4.2.14.1-signed.zip
Signed with the testkeys from the tutorial
Fastboot
update
Stuck...
I zipped some file if it could be of any help
my .config, zImage, boot.img, wlan.ko and modules.sqf
Thanks for reading
After some irc chat session I discovered it would be possible that my problem come from a bad boot.img generation.
I use old unpack / repack scripts (with whose you can't use the --base parameter).
I will try to fix this now, and retest!
Updated 2011-05-09 (New version aim3)
So now that Vodafone Spain finally released a Froyo OTA upgrade for HTC Magic, I've built a cooked ROM from the official OTA upgrade. The ROM tries to ressemble the stock ROM, but including the following extras:
Version aim1:
/system/etc/install-recovery.sh is removed, so it won't overwrite your recovery on every boot, as the stock ROM does
This ROM is rooted. Superuser.apk is installed on system.
Included apns-conf.xml from Cyanogen, so APNs from all operators are available, not just from Vodafone.
Google applications updated to the latest release: Maps, StreetView, Gmail, Market and Youtube
Replaced keyboard with Gingerbread (Android 2.3) newer keyboard.
Removed the Vodafone Live application and shortcut
Version aim2:
Removed Gingerbread keyboard, better install as separate package if you want it (see link)
Updated Google Maps and Market to latest versions.
Include busybox, it's needed for some root applications
Deodexed (takes some time on first boot, saves space on /system)
Re-signed (needed to include STK)
Included STK (Sim-Toolkit) application ("Servicios SIM" in Spanish). Required for some virtual operatos to work in Roaming
Added Sound Recorder icon in Launcher (application was there, but only accessible from MMS when adding a sound)
Added support for scripts in /system/etc/init.d (useful for adding compcache, swap, etc).
Version aim3:
Removed the "assert shappire" line on installation script. Should allow installation on Dream/G1
Revert some re-signed packages to allow Google applications updated via Market
Load ipv6 module to have Google Goggles working
Replace stock kernel with a custom kernel for better performance and memory tweaks
Enable compcache (compressed in-RAM swap memory) on boot by default, to get some extra free MB on magic 32B, which makes the system much more usable (applications and launcher are not killed all the time). Tweaks can be customized using setprop (see later)
Overclock CPU on boot. Can be tweaked using setprop (see later)
Include support for Live Wallpapers
Please note that this ROM is only for HTC Magic 32B (not for 32A or Dream). You'll need to use the System-Only ROM and a different kernel and/or SPL for 32A or for HTC Dream.
This latest update (version aim3) includes:
Android 2.2.1 (FRG83D)
SPL (HBOOT) version 1.33.0013
Radio 2.22.28.25
Kernel 2.6.35.13 from Farmatito (http://forum.xda-developers.com/showthread.php?t=1010932)
About the SPL and Radio: This is a perfect SPL, so it won't allow you to flash unsigned images from fastboot. Please make sure you have a custom recovery image. The new 2.22.28 radio won't work with other older SPLs, but it's worth the additional RAM (15MB). Also, if you want to install another kernel, it must be compatible with this radio version.
Requeriments and pre-installation
You'll need a custom recovery that allows you to flash the update.zip file. Clockworkmod recovery or AmonRA should do the job.
Make sure you have a good battery level, and make a full backup before installing.
Disclaimer: I won't take any responsibility if this bricks or damages your device.
Upgrading
Due to resigning, you can't update from previous version. A full wipe is required, sorry. However, if you backup your data and apps with Titanium Backup, and then restore them, it should work if coming from a previous version of this ROM, or if coming from the stock versions. There are no guarantees if coming from other non-official ROMs
Installation (Two-step)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
1. SPL Update. First download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim1/vf_magic_frg83d_hboot_0013.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_hboot_0013.zip?dl=1) and apply update from recovery (copy to the SD Card, then choose Apply .zip from SDCard, and choose the zip file). It will reboot a few times during the upgrade. Finally it should boot the system with the previous version, but the SPL will be upgraded.
2. System+Radio+Kernel update. Download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim3/vf_magic_frg83d_aim3_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_nohboot_s.zip?dl=1) and from recovery wipe Data and Cache. Apply update from recovery, the same way. It should reboot a few times and finally boot the system, updated to Froyo.
Installation (System-only installation)
If you already have SPL 1.33.0013 or 1.33.0013d, and radio 2.22.27.08 or 2.22.28.25, and want to install only the system files, then download http://dl.dropbox.com/u/3658919/and...m3/vf_magic_frg83d_aim3_noradio_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_noradio_nohboot_s.zip?dl=1), and apply update from Recovery.
If you have an 32A, you should be able to use the System-only installation, and when finished, flash an appropiate kernel (the included kernel is for Magic 32B).
Tweak configuration
Latest version includes some performance tweaks which are applied on boot. There's no GUI for changing these settings, but they can be easily changed using a command line (for example adb shell).
First, get a root shell (adb shell, then su). Then you can use the command:
getprop propertyname
Click to expand...
Click to collapse
to get the current value of a setting, and the command:
setprop propertyname newvalue
Click to expand...
Click to collapse
to set a new value. The available setting parameters (Replace propertyname are:
persist.tweaks.ramzenabled: Enabled (if 1) or disabled (if 0) the compressed RAM swap. If not set, it defaults to 1 (enabled).
persist.tweaks.ramzsize: The size of the compressed in RAM swap memory, in KB. If not set, it defaults to 32768 (32MB). Don't try anything higher than the amount of memory in your system. I wouldn't recommend more than 65536 (64M).
persist.tweaks.swappiness: The swappiness parameter. A avlue between 0 and 100, defaults to 10. Tells the system how agressively try to move memory pages to the swap. I keep it to a low value, so pages are not swapped until more free RAM is needed.
persist.tweaks.cpuminfreq: The minimum CPU frequency. If not set, it defaults to 245760 (245Mhz). See the list of available frequencies with command:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Click to expand...
Click to collapse
persist.tweaks.cpumaxfreq: The maximumCPU frequency. If not set, it defaults to 595200 (595Mhz). That's a bit overclocking, but I find it perfectly stable. With higher frequencies (614Mhz) I get random reboots.
persist.tweaks.cpugovernor: The CPU frequency governor. Defaults to interactive, but you can try ondemand too.
Any change will require rebooting the system. If you get stuck with a change (phone can't boot), try using adb shell from recovery, mount /data partition, and remove the offending setting file from /data/property/persist.tweaks.xxxx
Add-ons
Gingerbread keyboard is not included anymore. You can install Gingerbread keyboard along with the Froyo keyboard. See this post.
Alternative kernels: For 32A or HTC/Dream you can try with other non-stock kernels. I would recommend trying Farmatito Kernel or the latest Magic 32B kernel from ezterry, search in Doid Basement. Here is the direct link to the latest ezterry version for Magic 32B/32A
Versions and updates
aim1 - 2010/12/25 (Christmas gift) - Initial release
2010/12/27 - Added "Revert to Froyo keyboard" add-on
2010/12/27 - Added mirrors for files
2011/01/09 - Removed one-step install, seems it's not working
aim2 - 2011/05/01 - New version
aim3 - 2011/05/09 - New version
Hmm,sounds good,how about some screenshots?
But i'm a bit skeptical about the SPL and Radio flash-ing,cuz i almost once bricked my phone
Bad First Try
airadier said:
Installation (Two-step version)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
Click to expand...
Click to collapse
So after many attempts of trying to get my phone back to "factory" for OTA updates, I gave up very very late in the night and decided I'd just try this new ROM. I know I'm crazy since no one else has written of their attempts to try it - meaning I'm probably the first - and I'm a little worried at what I'm seeing. I followed your instructions for the 2-step version using Clockworkmod recovery and my right now my phone is stuck in the black loading screen that says "ANDROID". Its been on this screen for over half an hour. I'm pretty sure it shouldn't take that long so I thought I'd go ahead and ask for tips now so I can work in it tomorrow. My T-Mobile myTouch 3G original (HTC Magic 32 B) phone was on CM6 (Froyo 2.2) before I revered it to factory 1.6 because of frustrations with Cyanogen's slow mod. T-Mobile's OTA updates weren't working because of recovery image issues so I figured I'd give you version a go. Yes, I realize this is the Vodafone version. Hablo español.
So should I try to reset my phone? Take the battery out? Am I bricked?
I don't think it's bricked, it just seems to be failing to boot the system. A logcat (adb logcat command) would help to diagnose the problem.
You should be able to boot to recovery. Did you wipe data and cache partitions?
Did the previous version boot after flashing first step? You can check the SPL on this step was correctly flashed by entering fastboot (vol down + power) and checking if Hboot version is 1.33.0013
I've tried the 2 step version successfuly in 2 htc magic by now.
Let me know about any progress.
Greets.
Sent from my HTC Magic using XDA App
I can't download any chance. Can you post them in another way?
I can't download from phone neither.
Sent from my HTC Magic using XDA App
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
It works!
It works! Here's how...
It had been 6 hours and it was still stuck on the loading screen, so I pulled the battery.
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
W/PackageManager(30347): Permission com.noshufou.android.su.RESPOND from package com.noshufou.android.su ignored: no gro
up null
I/PackageManager(30347): /system/app/TelephonyProvider.apk changed; collecting certs
D/dalvikvm(30347): GC_FOR_MALLOC freed 5701 objects / 392080 bytes in 124ms
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad3a8 android.uid.phone/1001}
E/PackageManager(30347): Package com.android.providers.telephony has no signatures that match those in shared user andro
id.uid.phone; ignoring!
I/PackageManager(30347): /system/app/UserDictionaryProvider.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435f7a48 android.uid.shared/10010}
E/PackageManager(30347): Package com.android.providers.userdictionary has no signatures that match those in shared user
android.uid.shared; ignoring!
W/PackageManager(30347): Permission com.android.vending.CHECK_LICENSE from package com.android.vending ignored: no group
null
W/PackageManager(30347): Permission com.android.vending.BILLING from package com.android.vending ignored: no group null
I/PackageManager(30347): /system/app/VpnServices.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad158 android.uid.system/1000}
E/PackageManager(30347): Package com.android.server.vpn has no signatures that match those in shared user android.uid.sy
stem; ignoring!
Anyway, after restarting twice the phone loaded! Froyo who-hoo! And I love the Gingerbread keyboard addition! This ROM is elegant - almost official OTA with just a touch of fixes. Cyangen's ROMs are over the top for me.
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Thanks for the great work and cool simple ROM.
waffleguy4 said:
It works! Here's how...
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
Click to expand...
Click to collapse
Strange. I'm quite sure a Data + Cache wipe is needed except if you're coming from stock 1.6. The errors in the logcat seem to confirm this.
waffleguy4 said:
It works! Here's how...
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Click to expand...
Click to collapse
I think you should get the updates anyways. The only difference is, instead of having Maps 4.6 in SYSTEM partition, you have 5.0. The day Maps 5.x is out, it should show an update is available. I think showing it in the market as "Installed" is the normal behavior since the google apps were extracted in Froyo, or Eclair, I can't remember
I might be adding some optional packages (as updates.zip) soon. For example, I'm thinking of adding a patched version of Google Maps to force using Vector and 3D graphics instead of bitmap tiles. Also, maybe an update to revert to the standard Froyo keyboard.
I hope you enjoy it.
jvmonjo said:
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
Click to expand...
Click to collapse
The update script is checking that the installed ROM device or product is "sapphire", and it's failing. Maybe the ROM you're using right now uses another device identifier?
I could remove the check, but it was included in the original updater, and I think it's safer this way. You could try flashing cyanogenmod or the stock vodafone 1.6 first, then updating.
Greets.
maverickcri said:
I can't download any chance. Can you post them in another way?
Click to expand...
Click to collapse
I've added a mirror for all files.
Greets.
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
kurjak said:
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
Click to expand...
Click to collapse
How are you booting recovery? Are you using "adb reboot recovery" command? If so, it looks like the perfect SPL won't allow you to run that command.
You must enter recovery by powering the phone off, and then pressing Home + Power On button. Keep pressing them until you're on recovery.
Greets.
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
kurjak said:
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
Click to expand...
Click to collapse
Ok, don't panic, the fix is easy. The exclamation mark screen is the stock recovery, that allows you to flash only HTC signed update.zip file. As this update is not signed by HTC, it throws the "verification fails" error.
So, how to fix it? You need to flash a custom recovery (ClockworkMod or AmonRA, for example), because the SPL won't allow you to boot the recovery from fastboot.
You need to have your current ROM rooted, if it's not already. If not rooted, check SuperOneClick Root in here: http://forum.xda-developers.com/showthread.php?t=803682
Once rooted, you can flash the recovery using flash_image command from an adb shell, or easier, install RomManager from the market and install recovery from there.
Just make sure the recovery is for Magic 32B or Dream. I think last time I used ROM Manager I choose "HTC Magic", and a recovery for Magic 32A was installed, so the recovery wouldn't boot. I discovered I had to choose "HTC Dream" instead, as the recovery for Dream works for HTC Magic 32B too.
Once installed, using the "Home + PowerOn" you should boot into the new recovery (clockwork or AmonRA), and it should allow you to flash the update. If you get "verification failed" error, check that "signature verification" is toggled off (there's an option in the recovery to enable/disable it).
I hope it hellps. Greets.
Radio Installation didnt work
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
maxpower_303 said:
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Click to expand...
Click to collapse
What was the error when the installation aborted?
Puddux said:
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
Click to expand...
Click to collapse
1. I don't know, as I haven't checked the UK ROM, but probably they are both the same. In the spanish vodafone update there's support for english too.
2. SPL 1.33.0013d should work too. It's a modified version of 0013 to allow some additional operations. No need to install 0013. Radio 2.22.27.08 works too, but latest version, the one shipped with the vodafone update, is 2.22.28.25.
Greets.
For those who don't want to upgrade to a perfected spl (Want to stick to engineering spl) and are willing to accept the lower ram count I added ezterry's biffmod kernel/wifi module (oh and also added News and Weather app).
You can download it @ http://dl.dropbox.com/u/7812800/Android/vf_magic_frg83d_eng-signed.zip
Also if you want to use it without sim flash this after the main zip.. http://dl.dropbox.com/u/7812800/Android/Froyo_Provision.zip
Hope this helps anyone.
Btw.. Tested on Google Ion (Yes i got one lol)
Hi!
On behalf of the unrevoked team, we're proud to announce the new release of unrevoked -- version 3.3. This version adds support for HBOOT 2.02 and 2.10, and also adds support for the new OTA, 3.70.651.1.
You can get it at our site, http://www.unrevoked.com/recovery/ .
New in this release is ClockworkMod 3.0.0.2. We and Koush have been working hard on getting ClockworkMod all set and safe on EVO 4G; ClockworkMod is now using the latest EVO 4G kernel, for one, and now has nandroid options to back up your WiMAX keys. It also encodes your phone's serial number in the WiMAX backup, which greatly reduces the risk of restoring the wrong WiMAX image to the wrong phone. Please try it out!
We'll be watching this thread off and on. There are a few known glitches; carefully read the frequently asked questions in the "More Info" section, linked from the page above.
Thanks for everyone's support and assistance -- and have a happy new year!
joshua
unrevoked
UPDATE:
I just pushed out 3.31, which fixes a bunch of small issues that people were having, and backs down to Clockwork 2.6.0.1. This adds support for Amend scripting back in, but keeps all the good changes from 3.0.0.2 -- WiMAX backup, and the new kernel with support for new hboot partitions. I tested this pretty thoroughly -- I fully erased my WiMAX partition with erase_image wimax (don't try this at home!), and then restored it from a backup I took with Clockwork 2.6.0.1. My keys were intact, and my 4G still works. More detail about the changes can be found in the changelog. Thanks!
You guys are the best!!!!!!!!
so im guessing you fixed the recovery. because in my testing with the new version of cw...on older hardware with the new hboot it wouldnt back up squat...and there have been reports of people noting being able to flash things with the new version on new hardware or not being able to boot.
thanks for the hardwork
Sweet! will be trying this on my new EVO tonight... will update how it goes.
Thanks guys for the hard work!
This is great news.
I'm going to hold off on doing anything for now until the flashing issues are completely figured out and there is a solid 3.2 build out.
Thanks for all of your hard work guys.
Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.
bkrodgers said:
Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.
Click to expand...
Click to collapse
didnt work in my testing...but i am just one person. all though i got the same results across 3 evo's two old 0003 and one newer 0003 (with the new camera)
Soooooo stoked for this!!!
VERY NICE!!!!
Quick question, I don't have 4g in my area yet so I haven't gotten 4g connected yet. So should I flash the new wimax radio and start my new restorations from there or just leave it as is and keep my old backups along with whichever new ones I create?
Sent from my PC36100 using XDA App
did this and it worked use it guys make sure you follow everything. Unrevoked team cwr gave me some problems while rebooting it gave me lines on my screen it looks scary but it works so i just switch to amon recovery anyways thanks
First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.
revel1973 said:
First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.
Click to expand...
Click to collapse
sno leopard only. sorry...
running on Ubuntu, ran it in terminal as "sudo ./reflash" as to give it root permssions and it pushed the recovery in no time but has been stuck on "installing unrevoked3 service" for about 10 minutes now....afraid to unplug/close it. any help/clues?
no workie on mac
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022
just did my wife phone on a mac with snow leopard and it worked just fine. the trick was that i had debugging already enabled when i loaded unrevoked so i disabled it then enabled it while still on unrevoked and it worked.
jorge.l.diaz said:
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022
Click to expand...
Click to collapse
same error i got on leopard. you need snow leopard.
How would I go about upgrading my hboot so that I can use the new cmw, and root with this method.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
I Can Backup My Original Evo Rom But I Can't Flash Any. I Get The Lines Too. Should I Just Flash An Older Clockworkmod Or Just Go To Amon's ?
&& I'm On A Old Recovery ( 2.5.0.1 ) . It Looks Like 3.0.0.2 Doesn't Work . Or Am I Wrong ?
I'm A Rookie . -_-
Btw , I'm Trying To Flash Salvage-Mod .9.3 Gingerbread .
I cannot flash a new rom either, it cannot access my SD card.......?
UPDATE: Posted more info in the Misc Android Development section - here.
Hi all, sorry if this is the wrong place to post but hopefully someone else with a rooted Sharp ADS1 can test this out, or even find this usefull - its been working for me for a few days so far and I'd like to share for testing.
I extracted the stock recovery image, used the clockworkmod builder site and have a (mostly) fully working CWM 6 for that device. I've been using it for about a few days, and it works nicely. It wont mount the USB storage on mines, the device was rooted with SuperOneClick.
Started when I saw a youtube video on how to get it into the stock recovery screen (hold Power and Sym while booting).
I was able to make a nandroid backup of my image, I already removed some bloatware from the device. I'm working on a CWM flashable zip of what I have, maybe someone else can do a fully stock image (mines is missing a few bits for a factory-reset).
I also extracted images of the all partitions on the device. I'm working on getting CyanogenMod (working with CM7 at the moment) running on this thing, still trying to figure what to compile it as lol. I managed to get the Kernel to compile, but I'm working on getting a Gingerbread ROM to use with this device.
Specs I noticed on this:
MSM7227/MSM7x27 cpu
Adreno 200 GPU
512MB RAM, 512MB ROM (200-ish accessible by user)
Hardware Keyboard
WiFI/Bluetooth/etc..
Wondering if theres a similar device I can try using their ROM and testing the zImage I compiled.
QUICK N DIRTY INSTRUCTIONS:
-Device must be rooted (use SuperOneClick 2.3.3)
-Copy the flash_image and CWM recovery image for the ADS1 onto the root of your SDCARD (to make things easy for now)
-Using ADB I remounted the sdcard by running the following (otherwise, you'll get permission denied even with/as root)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
-I used flash_image from my sdcard (pushed it with ADB in Ubuntu), I took the CWM recovery.img file and also pushed that to the sdcard.
Code:
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
-As the phone reboots, hold Power and Sym and it should take you to the CWM Recovery screen after it blinks once.
Now you can do backups/restore images, clear dalvik, battery stats. Only thing that didnt work for me was mounting USB mass storage via Advanced menu. Once you get it installed, do a nandroid backup asap!
LINK TO CWM FILE (contains stock recovery.img, flash_image and clockworkmod in the CWM folder).
here
file is packed with 7zip.
I have more info on my findings on this lil device incase anyone is interested including partition mounting, etc.. root info recovery and system dump info also some random notes on the kernel.
I'm using this as a learning experience/hobby, and I'd like to share incase anyone was wondering what makes this thing tick lol. Have a nice day all!
EDIT:
heres a pic of mines booting into CWM for inspiration
{
"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"
}
system and nandroid backups
Didnt wanna wait to edit, but heres img files for all partitions on froyo - and here's a nandroid backup (should boot, but do a factory reset/wipe data/cache and dalvik in CWM and you''re like new).
Also, the new boot.img and splash,img flash when I put em in a CWM zip however no boot with a "quick" ported GB CM7 rom (still waiting for repo sync to finish ) - flashed a zte v9 as the hardware was similar (even running the grab proprietary files grabbed almost EVERYTHING - there were a few that were off). Hopefully someone can find this interesting for the device. There's a few others that looked promising, I'm taking a break for now tho lol
UPDATE:
Tried using a ROM kitchen to play with the stock rom, didn't work too well lol. I managed to restore a nandroid, but WiFi keeps showing as an error (think it may have had something to do with an option for tethering/wifi that I thought I said No to in the Kitchen's menu...). Also , the signed ROM from the Kitchen seemed to BJork the SuperUser/Root - gonna try flashing a SuperUser CMW zip (3.x)
Also, even with experimenting different roms - CWM is typically accessible via Power + Sym combo. No luck with ro.secure=0 in the stock boot.img - hopefully someone with more experience can help get something running on this lil thing. I'll keep moving forward anyways, have a few ideas of things to try out - albeiit somewhat limited, it's a start . Hope this is usefull to anyone trying to mod this sucker.
UPDATE:
Wifi's back, typing from the device. Restored to a old backup using CWM, on reboot toggled airplane mode and was able to see and join my SSID.
(another) UPDATE:
Looking at other models that seem to have similar hardware, Commtiva Z71, Spice MI300 and ZTE v9 (they have the MSM7227 600MHz/Adreno 200 GPU combo - other specs are very similar). Not sure what they have for sensors, etc.. but I found the ones on the ADS1
Code:
Sensors:
BMA150 Acceleration Sensor: 0.2mA by Bosch Sensortech
MS-3C (YAS529) Magnetic SEnsor: 4.0 mA by Yamaha Corp
MS-x Orientation Sensor: 0.0 mA by Yamaha Corp
ISL29011 Light Sensor: 0.0 mA by INTERSIL
ISL29011 Proximity Sensor: 0.0 mA By INTERSIL
random info from the "features" of the phone (build.prop related?)
Code:
Features:
android.hardware.location.network
android.hardware..wifi
android.hardware..telephony
android.hardware..location
android.hardware..touchscreen.multitouch
android.hardware..sensor.compass
android.hardware..camera
android.hardware..bluetooth
android.hardware..sensor.proximity
android.hardware..microphone
android.hardware..sensor.light
android.hardware..location.gps
android.hardware..camera.autofocus
android.hardware..telephony.gsm
android.hardware..sensor.accelerometer
android.software.live_wallpaper
android.hardware..hardware.touchscreen
glEsVers=2.0
Build Info/Kernel Config from Device.
I've attatched the system.info.gz and config.gz for the stock kernel dumped from my own device.
As far as some ROM testing I did earlier, CyanogenMod 6 for the Z71 (using the Sharp ADS1 boot.img) actually makes it past the Sharp logo and goes to the CyanogenMod boot animation, it stays there but its trying to load something lol. (Luckily I have a few nandroid backups, so flashing back to my previously rooted setup seems to work).
Maybe if I can find something that can work with this setup, then I can look at that device for something to base off to work with CM7. Fun learning experience so far. Going to try a ZTE V9 rom with the Sharp boot image and see what results from that (just trying to see what makes it past the initial boot logo). Might try swapping the build.prop in and see if that does anything lol (using the CM6 keys in their build.prop).
I'm guessing for the CM7 source (or AOSP), I'd have to find a device/manufacturer/device that I can base off for a working sharp/ads1 folder grabbing the needed proprietary files and libs.
Sharp fx plus no clockworkmod
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
rrkevon said:
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
Click to expand...
Click to collapse
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
AmauryRR said:
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
Click to expand...
Click to collapse
Thanks. I'll see if i can
rrkevon said:
Thanks. I'll see if i can
Click to expand...
Click to collapse
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
AmauryRR said:
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
Click to expand...
Click to collapse
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
rrkevon said:
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
Click to expand...
Click to collapse
From what I remember, the recovery itself had to be modified to allow unsigned roms to work - Signing it yourself, I'm not sure if it'll give the recovery the "signature" its expecting.
nstewart said:
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
Click to expand...
Click to collapse
Yeah, I had to drop my site for a while - I host it myself as a hobby with whatever I have to spare, and unfortunately funds weren't right. Just started a new job, so hopefully I'll be able to get my old site back up.
If you're running linux, IIRC you have to make sure the udev(?) permissions are correct for the device/user. Been a while, so bear with me lol (haven't had this phone in a while, since sharp wasn't helping with the source) - alternately, I think you can try running adb as root (sudo adb kill-server, then sudo adb) and it should recognize the device in terminal.
I can host the stuff for you if you want.
Sent from my SHARP-ADS1 using xda app-developers app
Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts
The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.
Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk
Error. More than one device and emulator
what am i doing wrong?
LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
I did enable usb debugging
LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait
marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.