Related
Update 10/02/11:
For existing users of the ROM, flash the 2.2GB_NoCG_31_39.sbf (Link below). This will flash the rest of the ROM apart from the part that stops the ROM from being downgradable and system - Don't worry your ROM will be as it was before after flashing - you won't loose any data.
##CAN PEOPLE POST WHETHER THEY ARE HAVING GTALK/MARKET ISSUES PLEASE## Please also post if it is working ok for you
Back up after needing to sort out a few niggles and an issue with the rom including my Titanium backup license key. Now RC2.
Higgsy Modded 3.4.2 GB Froyo for Motorola Defy.
Fully working, no niggles ROM. Everything works. Its a blank canvas, All social networking blur stuff removed, some widgets, some other stuff.
Included:
Launcher Pro
Milestone Overclock
Titanium Backup
Widgetsoid2
Clockworkmod Recovery
Es File Explorer
Also:
Deodexed
Rooted/Busbox (Busybox installed in /system)
Over clock Script included with following freq/vsel 1000/52, 600/36, 300/26. (milestone overclock is not loaded as default - just go in and load module and set to apply on boot then forget about it)
Install process - this must be followed to the last letter - there is no variation so please don't ask.
If you have already followed the process to get onto a downgradable base, (i.e. you already flashed RC1, or, you followed the other thread Here then all you need to do is boot into clockworkmod, wipe data/cache and restore this. It will wipe everything again, sorry about that.
I never flashed a non downgradable .sbf before, such as 2.51 Eclair, or the GB/US Froyo, so can't vouch for whether it will work correctly on peoples devices that have done that, you should however just be able to flash the system/image if you've already got a 3.4.2 froyo base. If you have never either recieved the phone/flashed one of the undowngradable .sbfs, this process will ensure you keep you downgradibility.
Files Needed to complete This:
2.2 Chinese .sbf(Unzip the .sbf from the archive)
Higgsy_Modded_3.4.2_GB_Froyo_RC2 (Unzip and put folder in the sdcard/goapkrev/backup folder)
Superoneclick Root
Clockworkmod Recovery
2.2GB_NoGG_31_39.sbf(Unzip the .sbf from the archive)
1)Make a backup of all your apps with Titanium backup on your current ROM.
2)Boot into Stock recovery (Power On/Vol Down, then press bottom right hand corner of the screen when you see the warning sign) Then perform a data wipe.
3)Using RSD Lite flash the 2.2 Chinese ROM (Guide Here if you need it!)
4)Once the phone has rebooted, skip set up, root via superoneclick and then install clockworkmod recovery/apply.
5)Boot into Clockworkmod Recovery and wipe data/cache
6)Now got to backup/restore and restore the Higgsy_Modded_3.4.2_GB_Froyo.
6)Important! Once the restore is complete pull the battery, as you are reconnecting the battery hold volume up, so that it goes straight into bootloader.
7)Once in bootloader flash the 2.2GB_NoCG_31_39.sbf by RSD Lite
8)Once the above is completed it should reboot and you are done
PLEASE READ:
I don't recommend restoring settings via titanium backup, only apps/app data, in the past I have done this and found it problematic. I suggest to redo your settings manually.
If you want to use setvsel (as it now works fine with froyo) you need to remove the setscaling scripts I put in for overclock and also milestone overclock. Setscaling scripts are located: /system/xbin/setscaling.sh + /system/etc/install-recovery.sh
If you report a bug I need to know what roms /things you have flashed before, there are too many variables, most notably if you been on non downgradable roms
Enjoy!!!
Thanks go to:
Sorensiim - Hosting all my files
mcm_xyz - for the haptics fix
Bizzaboy - for info on updating media profiles, so improving video recording
Authors of all the apps included in here, donate or buy the full versions they are worth it!
Further updates I intend to release as update.zip's, looking at themes, bugfixes (even though there aren't any that I can find) etc etc...... Please don't pester me for these, I do it as a hobby and sometimes don't have time for days to do things.
Change log:
03/02/11
RC2 release
Removed my TI Backup license that I had inadvertently included
Removed various info from the data.img, that I believe could have been cuasing some of the niggly issues people were having.
01/02/11
RC1 Initial Release
fantastic work !!!! will try after i'm gone from work
+1 looking forward to trying after work today
how to edit the overclock script ?
my phone could run on [email protected] , [email protected], [email protected] , [email protected] very stable
008325 said:
how to edit the overclock script ?
my phone could run on [email protected] , [email protected], [email protected] , [email protected] very stable
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=880851
Hey higgsy, i didn't flash your ROM yet but i have a question
At the moment I have a Defy which is on 2.34, and I didn't upgrade yet because i NEED a downgradable ROM (for warranty reasons, the DE version is still at 2.21)
now thanks to your tutorial, i can upgrade to froyo while being able to downgrade to the official 2.21 if needed, but here's my question:
what happens if i nand restore a different ROM based on the 3.42 UK rom (like HandlerExploit's upcoming Vanilla version), will I still be able to downgrade?
(e.g. does restoring a backup WITHOUT flashing a new sbf make your device undowngradable?)
yozgatg said:
Hey higgsy, i didn't flash your ROM yet but i have a question
At the moment I have a Defy which is on 2.34, and I didn't upgrade yet because i NEED a downgradable ROM (for warranty reasons, the DE version is still at 2.21)
now thanks to your tutorial, i can upgrade to froyo while being able to downgrade to the official 2.21 if needed, but here's my question:
what happens if i nand restore a different ROM based on the 3.42 UK rom (like HandlerExploit's upcoming Vanilla version), will I still be able to downgrade?
(e.g. does restoring a backup WITHOUT flashing a new sbf make your device undowngradable?)
Click to expand...
Click to collapse
Its flashing the sbf what locks you out of being undowngradable. simply restoring a system and/or data partition should not cause an issue. Ask the authors of the other ROMs, I can't comment on what effect there releases will have on your phone.
could we have some screens?
fabianowerner said:
could we have some screens?
Click to expand...
Click to collapse
Screens are pointless mate, its a blank canvas there is no theming etc. the screens in my 2.2 CN thread are pretty much the same
Looks nice,
so far running very smooth every thing ive tested and works well as far as i can tell!!
although I cannot got into recovery just get a black screen
Overall very nice cheers!!
Duh! I just flashed the uk rom posted by iaio72. I just realize it is not deodexed and i *must* (must?) replace that statusbar. If i understand correctly, it is not possible to theme odexed roms, right? Do you think i can just flash your system image or may this raise some issues ?
Higgsy, first of all thanks you very much for this rom, but I have a "little" problem. With a clean nandroid and with your, I have problems with gmail notification and "google talk connection problem" (don't know how is exactly writen, I have in another language)
what can be?
Edit: Just say: "Google Talk failed to login. If this is a google Apps account, confirm that Chat service is enabled for this account."
add.thebad said:
I cannot got into recovery just get a black screen.
Click to expand...
Click to collapse
Just a blind guess: you did disable usb debugging before booting into recovery, right? This is mandatory for froyo (don't know why though).
Another, market is not the new.
Edit: Now is up to date, it just didn't want to update, or install app. Removed data and restarted. Somebody know something about the other issue?
If I already followed the safe upgrade to 3.4.2, it should be good enough to simply do a nandroid restore and flash devtree again, right? I so want to get rid of blur
Camera not working!
Everything run smooth but the camera is not working.
if i'm already on 2.51 (it came stock), how do I go about flashing this froyo release?
Can anyone help? thanks.
Hi, Thanks for the good work
I've the same problem with Talk, authentification problem...
I've another problem with the LED from camera doesn't work.
Any idea?
gratias mate, for your work.
I had the blur-UK ROM installed, so I was able to restore your system.img only. Non of my data got lost and it's running smooth on your deblured version
It took me forever to find this in the various threads in the development section so decided to post this for anyone who needs it.
Note: I have not *discovered* this, invented it or just made it work by luck. All
credit goes to the developers and early adopters who share their knowledge and
know how. These are just basic steps that is all.
Excuse the little influence I am picking up from the original thread.
#1 This post assumes the following:
a) You are on Timat 1.1
b) You have CWM installed (no reason you shouldn't have it installed if you are already on Timat)
c) You have downloaded the appropriate update file form this thread -> http://forum.xda-developers.com/showthread.php?t=1165998
d) You have some basic flashing experience
#2 What needs to be done:
a) Download the file to your SDCARD downloaded from the above stated thread and rename it to update.zip (thought I didn't and it worked fine for me).
b) Reboot into recovery
c) Flash wipe / factory defaults
d) Go to advance and also wipe dalvik cache
e) Flash the above zip file
That is all. If you follow the above steps you should fine. I cannot stress this
enough please please do not restore data back ups from Titanium. Apps are fine.
At best its a hit or a miss so I would strongly advise against it.
Optional #1
You can also flash the new Timat Kernel once you finish flashing 3.2. For all the over clock goodness. Follow steps mentioned in the thread: http://forum.xda-developers.com/showthread.php?t=978013
Optional #2
To enable display of all apps in the market you can follow this thread which works perfectly: http://forum.xda-developers.com/showthread.php?t=1168508
All credit goes to original OP's
This post is a mere guideline nothing else.
I hope this thread helps people. Once again I do not take credit for any of this.
PS: One last thing all the steps mentioned above have been tested by me and I have a perfectly working XOOM on 3.2 Rooted and @ 1.2Ghz.
Cheers.
This also works on stock 1.1 running tiamat 1.4. Thanks dude!
Excellent thread. These are the same steps that I followed, and it worked for me, without a hitch. Fwiw : this is the standard protocol that I follow on my Incredible, and Thunderbolt when flashing new roms, or major updates to roms. It always works, without fail. After a while, one gets pretty efficient at restoring everything. TB can create more problems than it solves. Congratulations to OP for a well written post, that's easy to follow.
Thanks bro, great write up.... answered a few of my questions.
thank you bro this is an Excellent thread i followed the steps to update my xoom
Is there any reason that this update process would NOT work if I was on the Tiamat 1.0 ROM (with the 1.4.4 Full_Throttle kernal)? I got sidetracked for the last couple of weeks and as I was getting ready to update to 1.1, I saw that 3.2 had dropped. Seems like it should work as well as it does for 1.1. Any obvious concerns?? TIA.
TBH I don't see any reason why it shouldn't.
Best to do a nandroid back up and have a go at it. Let us know how it goes.
Cheers
3.1 and tiamat 1.4.4
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
Can anyone help?
Thank you
how can i do this with 3g zoom
I've got some questions regarding the install documentation of Simply Honey 5.1 Revolution for SGS ROM
Install Instructions Coming From Froyo OR ECLAIR(CM7/MIUI ODIN TO STOCK FIRST)
First Question regarding CM7 - Does this include CM7.1 as well? The example outside the parenthesis says Froyo or Eclair - CM7 is GB so this is not clear
- 1. Disable any Lagfix.
- 2.Download - xxx LINK REMOVED xxx This is the light version with hardly any apps and only one keyboard and 4 lock screens.
- 3. Flash via ODIN. USE 512PIT FILE.
- 4. Let phone boot. Wait 15 minutes and reboot.
- 5. Enjoy. You may now proceed to the MediumOR Large.
What is the difference between medium and large? Where are these files? I see a Light and Full but nothing else.
[/SIZE]
Install Instructions
Coming from Any Gingerbread Rom (If bootloaders aren't installed or you have trouble follow steps above.)
CM7 issue listed above. Any GB rom sounds like any - including CM7 this adds to the confusion of what will/won't work here.
1. You must first be running a Gingerbread rom (Doesn't matter Lindroid, Rainbows, your cousins top secret GB rom.) If you are not then please follow instructions above.
2. Place SimplyHoney5Beta1.zip on your SD card
Filename is out of date. Please link new file or list correct filename. If the ROM is out of Beta, the filename in the instructsions should reflect this.
3. Use rom manager or flash through recovery.
4. Let phone boot. Wait 15 minutes and reboot.
5. Enjoy
The new script is wipe for who come from SH <3.3 and from Froyo/GB!
It doesn't do wipe if you're running SH 3.5+ ROMs! Very Simple and automatic!
I've called it the "Anti-Noob" Script!
ONLY FOR CWM VERSIONS!! ODIN VERSIONS ALWAYS DO WIPE!!
Downloads CWM Full Roms
Simply Honey 5.1 Final
Light: xxx LINK REMOVED xxx 5 Locks Screens/ Modify Power Control Menu Options
Full: xxx LINK REMOVED xxx 10 Lock Screens
What is the purpose of Update1? Should this be flashed after Full? Is it flashed through CWM recovery? Some additional information here might be helpful. It is linked but no indication of why or when one would use it.
- Update1 - Gallery3D, Polaris Office, SNS Account -
xxx LINK REMOVED xxx
Is this section below a second set of instructions - you seem to list a If you have problems section above; however this one is more comprehensive. I'm not sure which one to follow if I have problems.
HOW TO
The anti-noob install script is a double edge sword so to speak. On one hand it is convinient as it doesn't do a wipe install if already on Simply Honey 3.5 and up. On the other some data needs to occasionally be wiped. That said if you experience ANY problem please follow the steps below.
1. Force Close of certain apps...go to settings/applications/manage applications/all and clear data of the offending app.
If that doesn't work then use Tiatnium backup to wipe data and uninstall the app (as long as it's not a system app such as phone or contacts or settings, you get the picture. Now you are free to re-install the app.)
2. The next step is to try and re-install the rom. Boot into recovery and select install from SD. After it's done and you reboot give it the 15 minutes. Now try again to recreate the original problem.
3. If the problem persists then boot recovery and wipe data factory reset and re-install the rom.
4. Problem still there then ODIN to stock (Stock ROM recommendation?)with repartition, ODIN the Simply3.8 Odin/Heim package. After rebooting boot into recovery and install the latest release of Simply Honey.
If these instructions are still useful, please link to SH 3.8 Odin/Heim package pls.
5. If all else has failed make a backup of everything you want saved to your computer. Boot recovery and go to mounts and storage and select format SD. After it's done reinstall Simply Honey's latest release.
6. If your problem still remains after doing all of this or just the last step then I suggest finding another rom as this one may not be for you.
I made an attempt to convert from CM7.1 this weekend; it wasn't clear what was going wrong but I couldn't get SH 5.1 to load properly. I tried to Odin the SimplyHoney 5.1 light version as per the first group of instructions, however, it was unclear whether I needed to repartition or not. the phone began the robot voice indicating partitions were not correct. I odin'd back to stock and reflashed CM7 with no problems.
Please understand I'm not trying to be critical, and I have rooted/flashed a number of phones over the years. Although I've been a fan of CM in the past, it's absolutely not where it needs to be on the Galaxy S/Vibrant and the Nightlies are not getting there fast enough. After reading the settings/features and positive comments for this ROM I'd really like to try it out, but the vague instructions and lack of links are not making this process easier.
If one of the developers can answer some of these questions, I'd be willing to assist writing documentation for this and future SH releases.
I'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful!
Oh, and pleeease use the Thanks button!
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.
will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it
Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.
tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.
Hey Guys -
After recently messing up the root on my A9, I re-flashed it completely this weekend. Although it's unlocked, has s-off, and has been converted to a DEV phone (originally AT&T), the process is tedious for me since I use Internal Storage. Instead of just applying a ROM, flashing recovery (twrp-3.0.2-0-hiae), then installing SuperSU; I must apply the RUU to the phone normally, do the steps above, backup the boot.img from the rooted phone, inject my verity key and another setting from the extracted RUU, then re-flash the boot image - the whole process takes a couple of hours but it's the only way I can format my SD as Internal Storage without issue.
It took me a lot of trial & error to figure out all steps required, but if anyone's interested, I have the process documented...
This time around, I went to a slightly newer build from Dev 1.57.617.52 to Dev 1.57.617.60. The only difference this time than past rebuilds is that I used the phone / installed apps for a while with internal storage on prior to rooting and when I rooted, I used the latest SuperSU - 2.78-SR1.
The Issue
The root succeeded as well as reflashing the modified boot image. Once the phone was booted, I was able to launch SuperSU and in Settings saw all looked good. The only change to settings I made was the usual changing of "Prompt" to "Grant." Root Checker Pro verified it to all be good to go, too. However - in most of the apps I try which require root, they say that my phone is not rooted. When selecting an app in Lucky Patcher, I only have the option to create a modified APK. I also downloaded a Build Prop editor which required root that said my phone wasn't rooted. I had to try two additional / different Build Prop editors before I found one that would work. I've never had this issue before!
My best guess is that this issue is due to one of the below things...
- That I used a newer version of SuperSU than in the past
- When starting the rebuild, I applied the RUU for 1.57.617.52 then went to 1.57.617.60 via OTA when prompted. When rebuilding my boot.img after rooting, I did get the extracted boot.img from a 1.57.617.60 RUU I later downloaded, though.
- That I formatted my SD as Internal Storage and installed many apps prior to actually rooting the phone (Even though I get the error in apps that were installed prior to root as well as ones installed afterwards)
- When creating my modded boot image, I copied over the verity key file but instead of copying & overwriting fstab.qcom, I just directly edited it and added ",verify" (It was at end of 1st un-commented line - I think after "wait"")
- That I used a newer RUU version (doubt it - not a huge jump by any means)
Anyone seen this behavior before? Any suggestions would be helpful. I'd obviously prefer a fix where I didn't have to invest time rebuilding from scratch again if possible. I do still have the originally rooted boot.img I backed up from TWRP prior to modding if it makes a difference. Thanks!
Phone Specs:
- HTC One A9
- Originally AT&T - Now Converted to DEV (Still use on AT&T network)
- TWRP 3.0.2-0 hiae
- SuperSU 2.78-SR1
- s-off / Unlocked
Try uninstalling superSU and re-installing it, and maybe try different versions. I also have a question for you, I see that you still use AT&Ts network, I do too. My question is while on the sense based roms do you experience slow data, and if so do you know how to fix it?