I'm pleased to present my repack of the stock ROM for the HTC Vision! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo stock ROM repacks
Unlike a MCR (MoDaCo Custom ROM) release, a stock ROM repack is as close to the stock ROM as possible. Only root / Superuser and an insecure boot image is added. The benefits of the repack are providing a rollback option in update zip format as well as providing an online kitchen to remove parts that are not required.
A MCR release of this ROM is also available!
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
THIS ROM SHOULD RUN ON BOTH THE G2 AND THE DESIRE Z!
Features
Repack of the 1.22.531.8 (OTA) ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Changelog
Please see the post below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM (unless you are coming from a 'Sense' ROM), however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen - see the post below for details! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
11/Nov r1
Initial Release
Let me know how you get on people!
MCR'd version and Sense stock / MCR for both G2/Z to follow (soon)!
P
OMG
jaws drop
paul you da man
Hah, you ain't seen nothing yet... wait till you see what i'm dropping tomorrow!
P
Need a drink now, long day.
P
yes . Happy day.
Thanks.
Well done Paul, thank you!
So we need clockwork on the Z to make this work? hpw do i install clockwork on Z, only says G2?
got it flashed but keep getting "The process Android.process.media has stopped unexpectedly. please try again any ideas?
Media error hasnt come up in a while but ive been on wifi the whole time and i cant get 3G to pop up at all meaning i have no mobile data and APN's are correct
im in australia on OPTUS
shaunm1989 said:
So we need clockwork on the Z to make this work? hpw do i install clockwork on Z, only says G2?
Click to expand...
Click to collapse
check the EZ-DZ thread:
http://forum.xda-developers.com/showthread.php?t=835777
updated with easy S-OFF and clockwork tips
Radio
Hi.
Rom is fantastic, but where is Radio app ?
THX
How do we install the overclock kernel after flashing this rom?
foxfire235 said:
How do we install the overclock kernel after flashing this rom?
Click to expand...
Click to collapse
To do it with the vision_oc u need to use the file from the G2 Forums
You can actually use bacon bits with this rom. I over clocked to 1.5ghz with this rom and bacon bits, was fast as all hell, but I missed sense too much
JD
Sent from my HTC Desire Z Beast
Sweet. I just flashed bacon bits and it works great!
[ignore]Oops, posted on wrong post![/ignore]
Will this rom work on a North American Desire Z (850/1900/2100 WCDMA)?
Yes, it's working fine on my unlocked Bell D-Z.
I'm pleased to present my MoDaCo Custom ROM for the HTC Vision (this is the version based on the T-Mobile G2 ROM, without HTC Sense)! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
THIS ROM SHOULD RUN ON BOTH THE G2 AND THE DESIRE Z!
Features (these are the features for the currently posted prebake, please check the changelog for any pending changes that are in the kitchen)
Based on the 1.22.531.8 T-Mobile G2 ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Optimised with the MCR build process, which means that the ROM will fit on a G2 without needing to remove any content!
All components updated to the latest versions
ROM is de-odexed
Please note that this is a r1 release, many more changes will be added now via the kitchen and periodically updated prebakes (as per normal MCR builds!)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
Future Updates - READ THIS!
By providing this ROM I am not implying in any way that future updates will follow. Due to limits on my time and the fact that I have a large number of devices for short periods of time, it isn't possible for me to continue providing ROM updates indefinitely. Please do not donate / sign up on the assumption that future releases will be available (I don't want you to be disappointed!).
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
r2 10/Feb
Reoptimised - smaller, faster!
Updated all outdated components
r1 16/Nov
Initial Release
This is the first release of the ROM - I will start dropping in the usual MCR features quickly going forward (via the kitchen first as usual, periodically building prebakes).
P
You say...
"No wipe is explicitly required in order to use this ROM (unless you are coming from a non-'Sense' ROM)"
As this ROM has no Sense, shouldn't that be read ...unless you are coming from a 'Sense' ROM?
Tweaked ta!
P
paulobrien said:
This is the first release of the ROM - I will start dropping in the usual MCR features quickly going forward (via the kitchen first as usual, periodically building prebakes).
P
Click to expand...
Click to collapse
It would be helpful to know what's you've added over your first ROM - aside from scoring 22pts higher on Quadrant
paulobrien said:
Tweaked ta!
P
Click to expand...
Click to collapse
You're more than welcome.
I'm going to putting the with-Sense ROM on, soon. I just need a compelling reason to do it which i haven't yet got...yet!
Hello Wildfire S users !
Here is the guide of the Marvellous Team, the ultimate guide that describes everything you need o play with your phone. There are many tutorials on the web about how to unlock, how to install a recovery or a rom, but none of them explains all these operations. So here, you'll learn first a few things about how Android works, you'll learn a few words of vocabulary, how to unlock, how to choose the best recovery and how to flash it, how to choose the rom you'll prefer and how to ask questions and report errors.
I just say, sorry if this tutorial lacks vocabulary and is not grammatically correct : I'm not English, I'm French, and I'm not really good in English
SUMMARY
Post #1 : Explanations, disclaimer, summary
Post #2 : Unlocking process
Post #3 : Choosing and installing your recovery
Post #4 : Choosing and installing your ROM
Post #5 : Good rules when using the forum, how to help the developer
DISCLAIMER
I am not responsible for anything that can happen to you or your phone. Everything that I say in this tutorial worked for me, and if you do everything as I say, there is no reason for you to brick your phone.
If something happens to your phone, do not even try to blame me, cause I will redirect you to this disclaimer and laugh at you
SOME EXPLANATIONS ABOUT ANDROID
Okay, let' start unlocking your phone. But do you know exactly what unlocking your phone means ?
Here are some explanations about how Android works.
First, when you power on your device, it will start the bootloader. This is like the BIOS for a PC : it checks the processor, the RAM (memory),, and it launches the system. You don't see anything at the screen when it boots, because it is quite fast. You can boot into bootloader without going to the system next by pressing Power + Volume Down (you'll maybe have to remove and replug the battery before doing that).
What's the point of booting into bootloader ? You can go then into fastboot and recovery. Fastboot is a tool that will allow you to flash some things on the unlocked phone, like another recovery, or another kernel.
The recovery is the tool you'll use the most when playing with your phone : it is like a micro-system that can modify the real Android system. For example, it is the tool you'll use when flashing roms : you can't modify the system when you're already into the system ; if you delete all Windows system files to replace them with other files, your system will crash and your PC will not boot
I spoke about the kernel. The kernel is launched by the bootloader ; it will load all the modules that are necessary for Android to work, for example the touchscreen driver, the RAM allocator, and alll. You can see when the kernel is working at boot because you have HTC written in green over a white background.
You'll need to know that for the next steps of the tutorial.
CREDITS
The Marvellous Team : djolivier, thehacka1, Kevinjoa, Mazer.one
simonsimons'34
All the Wildfire S devs, and especially benjamingwynn, dudeman, OliverG96...
And many more I forgot !
This tutorial has taken quite a long time to write, so please press thanks if you think I deserve it
SUPPORT
As you may have heard, the Marvellous Team is about to end. thehacka1 and djolivier already have new devices. Mazer.one, Kevinjoa and I will probably get new devices soon (maybe in few months for me, I still hesitate between Galaxy Note 2 and Galaxy Mega).
I will however still maintain this thread, reading the answers, modifying what needs to be modified, etc. If you see I do not reply, don't worry, I'm certainly overwhelmed by work (I entered the French equivalent of college this year and I must work a lot) I will surely read your question and answer it, even if it isn't immediately. Moreover, other people of the forums will certainly answer you too
So, let's unlock your phone !
Unlocking your phone allows you to bypass the protection on the recovery and system partitions that HTC put. With an unlocked phone, you can use fastboot to flash a recovery (because the original recovery doesn't allow the user to flash anything).
Be careful ! Unlocking doesn't give you access to everything ! You can't modify the bootloader, the radio (part of the system that manages communications with network) and all the important thins of the phone. To modify these, you need to get S-OFF, and that's another problem
WHAT IS YOUR MODEL ?
There are several models of Wildfire S. The most common are marvel and marvelc. To know if you are marvel, just go intoo About phone section, you should find your model name. If it is A510e, it is marvel. If it is A510c, it is marvelc. This part of the guide is made for marvel, do not try to do these steps with a marvelc ! But the part with the choice of your rom and how to report bugs is okay for both models.
If you have a marvel, you maybe have a 2012 model. You can know that with your serial number, that should be also in the about phone section. You should have something that begins with two letters and then you should have a digit. If this is 2, you have a 2012 model and may have some problems with the unlocking process. Go directly to the part HTC Official Unlock.
INSTALL HTC DRIVERS
To unock your phone, you'll need your computer to recognize it. The best way is to install HTC Sync which automatically provides HTC drivers.
You can find HTC Sync here.
You can also download only the drivers, for example the Win7/8 64 bits version with this tutorial.
UNLOCKING WITH SIMON'S HTC UTILITY v4
So, if you have a marvel, AND NOT A 2012 MODEL, I propose you to unlock it using simon's HTC Utility (it should work too with marvelc, but I didn't test). This tool can be found here. This is pretty easy to use, even if you'll need the .NET framework to launch the program. If you do not have a marvelc, use only the unlocking feature !!!
HTC OFFICIAL UNLOCK
If you have a 2012 model, or if HTC Utility doesn't work for you, you can always try HTC Unlock method. It will work 100% but you will lose your warranty AND all your data. So, before doing anything, download SMS Backup & Restore and Super Backup and make a backup of everything.
Then go to this page, select your device and start the procedure.
Here is a guide written by @Uksus17 and translated by @niks255 :
0. Check your bootloader version in fastboot:
- If you have HBOOT 0.90.0000 - start with step 1.1.
- If you have HBOOT 1.09.0000, 1.08.0000 (or 1.03.0000) -
download and flash PG76IMG.zip via fastboot.
- If you have HBOOT 1.09.0099 - start with step 3.
1.1. Download this zip and put it to your SD card. (http://d-h.st/QwN)
1.2. Reboot your phone into bootloader (VolDown+Power) and when the checking is done press VolUp to install. After installation you must remove this file from your SD card before you continue.
2.1. Do steps 1.1 and 1.2 again with this second zip (it has the same name as the previous, but it's a different one) PG76IMG.zip. After all these steps you must have HBOOT 1.08(9).0099, which can be unlocked. (http://d-h.st/kGN)
3. Download and unpack Android.zip to your C:\ drive.
4. Make sure "USB Debugging" is checked. If it is, connect your phone to PC via USB and run Unlock.bat from Android folder on your C:\ drive.
5.1. Your phone will reboot into fastboot.
5.2. Now you will have htcdev.com opened in your browser. Now you need to register there. (Do not close command line!)
5.3. Confirm your email.
5.4. After you done step 5.3, go back to htcdev.com and log in.
6. Then go back to command line and press Enter. You must select the token the way it is selected on the picture below and copy to clipboard. DO NOT CLOSE COMMAND LINE!
{
"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"
}
7. Go back to your browser, scroll to step 10 and paste your token in form, then click submit.
8. After a while you should recieve Unlock_code.bin on your email. Save it to C:\Android.
9. Go back to command line and press Enter.
10. Now choose yes using volume buttons and power button. CAREFUL ! this operation wipes all data on internal memory, for the second time pleaase make sure you made a backup !!! (it doesn't wipe the sd card).
Good. Now, your bootloader should print *UNLOCKED*
Now let's do he real part of the job, what this tutorial has been made for.
CHOOSE YOUR RECOVERY
The choice of the recovery is very important. For the Wildfire S A510e, there are a lot of available recoveries :
ClockWorkMod 5, 6 and 6 Touch Version
TWRP 2.2.2.0 and 2.3.3.0
OWL-mod 0.1.2 (based on ClockWorkMod).
These recoveries usually are also available for non-marvel models, you can find a link to the other versions in the thread. But DO NOT TRY TO FLASH ON YOUR DEVICE A RECOVERY THAT ISN'T MADE FOR IT ! Meaning, if you want to try ClowkWorkMod 6 Touch Version, but you have a marvelc, do not flash the marvel version. Look for the marvelc version of the Internet. You could brick your device doing this
So, every recovery has a lot of advantages and also a lot of drawbacks. I will list them here.
CWM 5
It can be found here.Take the Wildfire S CDMA version for marvelc.
It is a good recovery, usually the one that everybody use. It is not a touch recovery, so you'll need to use it with volume keys and power button.
It doesn't have amazing features, but is official and working.
CWM 6
This is the newest version of ClockWorkMod recovery. It is better than CWM 5 : support of incremental backups, lighter and faster backups, new interface, etc.
You can find it here.
This one is pretty well working too, although it is not a touch recovery and even if it is not official.
CWM 6 Touch version
Like CWM 6, but using the touchscreen : better for the power button which is not made for a huge use.
The problem is that this one isn't very stable : some features do not work, the screen is strangely sized. Use it only if you want to try, but not if you just want stability.
You can find it here.
TWRP 2.2.2.0
It is another touch recovery, open source and absolutely different. It is less used and is perfectly stable. It has many more features than CWM, especially a file manager (very, very handy when you want to mod some system things without your PC).
I love it, but there is just one problem with the backups and restores : they take (for me at least) 5 more time than CWM ones. If you do not often backup/restore, that is OK, else you'll quickly get bored of waiting 30 minutes before flashing your rom.
TWRP 2.2.2.0 can be downloaded here.
TWRP 2.3.3.0
This was the latest version of TWRP available for the Wildfire S. You can download it on this website.
It is better than TWRP 2.2.2.0 but has a major problem : it cannot flash some old files. That's quite annoying when you want to try a rom and you see you can't because the rom zip file is too old :/
TWRP 2.7.0.0
This is the latest version of TWRP, built by @Olivier for our phone. It is definitely pretty cool, has loads of features and nearly no bugs. You can find it here : http://forum.xda-developers.com/showthread.php?t=2692158.
Like TWRP 2.3.3.0, it cannot flash some old files :/
OWL-mod 0.1.2
This recovery has been made especially for the Wildfire S. For now, it is pretty like CWM 6, with a few mods. But the next version looks very interesting
Here is the thread.
PhilZ recovery 6.0.2.8
Here is PhilZ recovery, a recovery which looks very much like CWM 6.0.2.8 but has some nice features. Here is the non-touch version : http://forum.xda-developers.com/showthread.php?t=2605331.
Then, I let you choose, try some of them and see by yourself
FLASH YOUR RECOVERY
That's easy if your bootloader is unlocked.
Download Android SDK here. Extract everything, and open cmd (Start menu - Execute - cmd). Then, in cmd, navigate to the repository you extracted everything (cd path\to\directory). Then, in this directory, go to sdk\plaform-tools.
In this folder, place the recovery file you downloaded.
Now, reboot your device in bootloader mode. Then go into fastboot. If the device is recognized you should see USB Plug on the screen.
You can now type
Code:
fastboot.exe flash recovery your_recovery_file_name.img
and voila ! You should see a loading bar on the screen, and you can reboot into recovery
THE BEST FLASHING TOOL
@Uksus17 made a pretty nice tool to help you install a recovery : just make sure USB debugging is enabled in your phone's settings, then connect it to the computer (of course, with the drivers installed - see before) and just run the .bat
You can find the script here : https://www.dropbox.com/sh/nuf2pq3ay9eu7xk/7gtYOs07EN
WINDOWS 8.1
On Windows 8.1 the fastboot drivers do not work. Thus you have to use another way to install the recovery : PG76IMG. The recovery will be downloaded as a zip file that you will put at the root of your sd card. Then just reboot into bootloader (vol down + Power) and it will flash it automagically @niks255 made PG76IMG for TWRP 2.2, 2.7 and CWM 6.0.4.8. You can find it here : 2.2, 2.7, 6.0.4.8
Now, you have your recovery... Let's speak about ROMs !
WHERE TO FIND YOUR ROMS
All the ROMs for the Wildfire S are here. You'll see, there are loads of ROMs for our phone
HOW TO CHOOSE THEM
Ah, which ROM is the best... An endless debate in XDA forums !
By the way, many "noobs" post threads to know which ROM is the best, and it annoys a lot the Senior users. Here I will list the existing kinds of ROMs and what they are made for, so that you won't have to spam the forum anymore
Stock rom
There are a lot of modded stock roms. The most advanced is by @Kevinjoa, and it can be found here. Moreover, it is a Marvellous rom !!!
Advantages : Very, very fast and an excellent battery life. Easily moddable and themable.
Drawbacks : Old Android version (2.3.5 ).
Sense 3.5 rom
These roms are based on the same Android version as stock rom, but with the latest Sense version (for Android 2.3). The fastest rom for the Wildfire S is EQDKP 5.2. There is also Marvellous Sense 3.5, and many other roms.
Advantages : Very fast, and good battery life. A very beautiful UI.
Drawbacks : one or two bugs. Old Android version (2.3.5).
CyanogenMod 7.2
CyanogenMod (cm) is the ultimate rom for all phones. It is based on pure Android (AOSP) and has a few more good features.
Advantages : very fast and an excellent battery life. Some mods that makes you forget that you have an old Android version : notification swipe-to-clear, flac support. Very themable : a lot of versions exist in the forum, modded to look like Sense 4, and all.
Drawbacks : a few bugs. Old Android version (2.3.7)
CyanogenMod 9.1
This is the Android 4.0.4 version of CyanogenMod. It is an excellent rom.
Advantages : Android 4 ICS. Very themable and moddable.
Drawbacks : it slows down the phone and has some bugs.
CyanogenMod 10
This is the Android 4.1.2 version of CyanogenMod, and is also a very good rom. Many versions exist in the forum, with a lot of mods and some derivated os.
Advantages : Android 4.1 Jelly Bean. Very themable and moddable, with many derivated versions.
Drawbacks : few space in /system, so you can't install full Google apps (see later in the tutorial). It feels slow sometimes. It has some bugs.
CyanogenMod 10.1
The 4.2.2 version of CyanogenMod.
Advantages : supported by OWL team. Android 4.2.2 Jelly Bean. Very themable too.
Drawbacks : very few space in /system. Also it is definitely slow. And it has bugs.
CyanogenMod 10.2
The 4.3.1 version of CyanogenMod.
Advantages : supported by Team Simplicit. Android 4.3.1 Jelly Bean. Very themable too.
Drawbacks : Well, there are very few features compared to CyanogenMod 10.1 And very few space in /system. Also it is definitely slow. And it has bugs, mostly sensors and camera.
CyanogenMod 11
The 4.4.2 version of CyanogenMod.
Advantages : supported by Team Simplicit. Android 4.4.2 KitKat. Very themable and has few bugs. It is faster than than previous versions thanks to Android optimization.
Drawbacks : There is few space in /system, and camera doesn't work.
Paranoid Android
Paranoid Android is a rom based also on pure Android but without cyanogenmod modificactions. We have two versions : Android 4.1 and 4.2. Both have bugs. The interesting features are in the per-app personnalisation feature : you can choose the size of each app, apply some statusbar colors per-ap, etc. Paranoid Android 3+ (Android 4.2) also has Pie feature and Halo.
Advantages : per-app functionnalities. Halo and Pie.
Drawbacks : bugs. Less features than CyanogenMod. few space in /system
MIUI
If you're a nostalgic of Sense, MIUI is for you. We have MIUI based on Android 2.3, 4.0 and 4.1. It is Android modded to be more beautiful.
Advantages : very beautiful UI.
Drawbacks : slow, and only in English.
AOKP
AOKP is based on pure Android and offers some new features like CyanogenMod. We have AOKP 4.0, 4.1 and 4.2.
Advantages : good personnalisation features.
Drawbacks : bugs and few space in /system.
AOSP
AOSP is the very pure Android with no bonus features.
Advantages : The one we have, by @thehacka1, is very fast.
Drawbacks : few space in /system, no CyanogenMod features.
PAC-man
PAC-man is the ultimate rom for people who want loads of features, or basically for those who do not know which to choose between CyanogenMod, AOKP and AOSPA (Paranoid Android). It offers features from all these three roms.
Advantages : so many features ! Android 4.2
Drawbacks : No camera. For me, extremely fast battery drain.
OmniROM
A modded AOSP 4.4.2 KitKat.
Advantages : supported by Team Simplicit. Android 4.4.2 KitKat. Has a lot of nice features. It is faster than than previous versions thanks to Android optimization.
Drawbacks : There is few space in /system, and camera doesn't work.
The best way to choose your rom is to test all of them. But you certainly don't have time for that.
If you want performance, choose Sense 2.1/3.5 or cm7.
If you want a good UI, choose Sense 2.1/3.5 or MIUI.
If yu want the latest Android, choose cm10.1 or AOKP 4.2
If you want a lot of features, choose PAC-man
And remember : you never need to flash any kernel except if the rom developer tells you so ! The rom already contains the good one
GOOGLE APPS
When you've downloaded a rom, you'll also need to download google apps if they are not installed. They are installed in Sense and MIUI roms, but not always in other roms (the hread usuallly says it).
You can find the gapps package for your Android version at goo.im/gapps - only for Android < 4.1. For Android 4.1 use these lite gapps, and Android 4.2 use these ones. Sometimes, a link to gapps is provided in the rom thread. Use this link instead of mine.
HOW TO FLASH
Just put the rom zip and the gapps zip in your sdcard, boot into recovery, make a backup, wipe data, cache, dalvik cache, system and sd-ext (if you can) and select install zip from sdcard then go to your rom zip and flash. After that flash your gapps zip without any wipe.
Yoou can then reboot. Be careful, it can take some time.
INCREASE INTERNAL MEMORY
As you may have seen, the stock rom has very few space for apps. You can increase it with Int2Ext
First you must partition your sd card. You can use a tool like gparted. Reduce the size of the existing fat32 partition and create a new partition in ext4 format. Note : make sure you've done a backup of your sd card data ! This will erase all data on your sd card.
Then you can go to this page and choose the script that is made for you. Flash it right after gapps without any wipe.
In my mind, Int2ExtV2+ is the best. But it needs 150 MB of storage for 500 Mb of ext4 partition. Int2Ext or Int2Ext4 do not need that, but will slow down the phone a lot, even if you have a good sd card.
ABOUT BRICKING YOUR PHONE
A lot of people, when they start playing with their phone, are afraid to brick it, meaning that it doesn't work anymore and can go straight to trash. That is normal, I was thinking that too But the risks are very low. If you are not S-OFF, it is difficult to brick your phone. I flashed more than 150 roms, installed kernels that didn't work, change 10 times of recovery and I never experienced a brick.
There are two kinds of bricks : softbrick and hardbrick. If your phone is softbricked, you can still go into recovery, wipe everything and install a new rom. If your phone is hardbricked, hmmm... there are very few chances of recovery, because it doesn't boot anymore
Let's talk about support now !
WHERE TO POST A QUESTION
It is easy : when you have a problem with a rom, post it right in the rom thread. Do not create a thread in General section with your problem. If you can't post in the rom thread, or if your problem is very specific, or just if nobody answered you in the rom thread, then post in Q&A section. NEVER IN GENERAL ! general sections is for threads that are not about a mod, a rom, a kernel, a recovery, an accessory or a question. For example, this guide
When you have a problem, people will often ask you to give them a logcat. But what is it ?
HOW TO LOGCAT
The logcat is the command that gives you all the informations about the system in real time, errors, warnings, or just debug info. When you have a problem and if you create a post or a thread about it, try to provide a logcat. This is easy !
In cmd, navigate to the repertory where fastboot.exe was. Plug your device to your computer. Usually Android debug is activated by default, you can verify in your phone's parameters. It depends on the Android version, but for Android >= 4.0 it is in Develper tools and for Android < 4.0 it is in the app menu, in the development section.
Now type
Code:
adb logcat
: you should see a lot of text. Don't worry if you understand nothing ! Just give everything to the people who ask you for the logcat. Then follow their instructions
Advice by @csoulr666 :
For a better and cleaner logcat you can do
Code:
adb logcat -v long
And if you want to put it in a text file
Code:
adb logcat -v long >logcat.txt
Then just upload the file It is easier to read and doesn't spam the thread (very difficult to scroll when you're on your phone ). Moreover with that you do not get into troubles with the character limit.
Just a precision about Android >= 4.2. You can't logcat on first boot, because of a new thief-protection feature. You'll need to boot, to plug the phone to the computer, make sure you have the latest adb installed (adb version - it must be 0.1.31 or more) and when you try to connect to the device, a popup will appear and prompt for adb access. Reply yes, and check the remember box, and now here you are, yu can logcat with this rom !
If you still want to logcat on first boot, you can use this guide (thanks to @thehacka1 !).
RESPECT THE DEVELOPER
A rom developer is a human being He has the right to sleep and to work and to have fun ! Do not ask for updates of the rom everytime, and don't bame him if he disappears from the thread for a few days... The more you ask for updates, the less he wants to make them
Do not forget to press thanks button when you think the dev deserves it ! Do not just post "thanks"
As you may have heard, the Marvellous Team is about to end. thehacka1, djolivier and Kevinjoa already have new devices.
Click to expand...
Click to collapse
I haven't got new device yet
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 04:30 PM ---------- Previous post was at 04:30 PM ----------
Good guide btw :good:
Sent from my Nexus 7 using XDA Premium 4 mobile app
I literally thanked every one of your posts :laugh:...........This thread will actually sort out many noobish threads(provided they read this first)
I hope this is stickied or atleast kept on the first page so that your time consuming work doesn't go in vain
I would actually like to contribute a bit.......for a better and cleaner logcat anyone can use the following command
adb logcat -v long
Click to expand...
Click to collapse
And if you want to put it in a text file
adb logcat -v long >logcat.txt
Click to expand...
Click to collapse
csoulr666 said:
I literally thanked every one of your posts :laugh:...........This thread will actually sort out many noobish threads(provided they read this first)
I hope this is stickied or atleast kept on the first page so that your time consuming work doesn't go in vain
I would actually like to contribute a bit.......for a better and cleaner logcat anyone can use the following command
And if you want to put it in a text file
Click to expand...
Click to collapse
Thanks for your feedback
I add your logcat advice !
izi501 said:
Thanks for your feedback
I add your logcat advice !
Click to expand...
Click to collapse
For logcat you also need your device's drivers. And don't forget 4.2.2 can't be logcated.
thehacka1 said:
For logcat you also need your device's drivers. And don't forget 4.2.2 can't be logcated.
Click to expand...
Click to collapse
Device drivers have already been installed if you unlocked your bootloader And 4.2.2 can be logcated, it just cannot be at first boot... But you're right, they may need to logcat on first boot. Could you please give me the link of your tutorial to get ADB working on first boot on 4.2.2 please ?
izi501 said:
Device drivers have already been installed if you unlocked your bootloader And 4.2.2 can be logcated, it just cannot be at first boot... But you're right, they may need to logcat on first boot. Could you please give me the link of your tutorial to get ADB working on first boot on 4.2.2 please ?
Click to expand...
Click to collapse
An alternative to device drivers is HTC Sync but that is a big hassle. Here is the link: http://forum.xda-developers.com/showthread.php?t=2296632
thehacka1 said:
An alternative to device drivers is HTC Sync but that is a big hassle. Here is the link: http://forum.xda-developers.com/showthread.php?t=2296632
Click to expand...
Click to collapse
I provided link to drivers and HTC Sync Thanks for the tutorial ! I add it immediately.
Anybody knows where I can find SIMON'S HTC UTILITY? I cant find working link anywhere!
denis022 said:
Anybody knows where I can find SIMON'S HTC UTILITY? I cant find working link anywhere!
Click to expand...
Click to collapse
Windows - Linux - Post with links
Must admit this is a great tutorial good job
I have unlocked my bootloader but after flashing and going into recovery there is no response by the recovery....cwm and twrp both not responding
I have a 2012 model a310e hboot 1.09 and I have s-off... It was s-off when I got it.
Sent from my HTC Sensation using XDA Premium 4 mobile app
yasir4abbas said:
I have unlocked my bootloader but after flashing and going into recovery there is no response by the recovery....cwm and twrp both not responding
I have a 2012 model a310e hboot 1.09 and I have s-off... It was s-off when I got it.
Sent from my HTC Sensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm... if you have a A310e you're in the wrong forum mate You have a wildfire, not a wildfire s !
But if you have 2012 model, it is possible that you need to try another recovery... you tried all of those I proposed in the guide?
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
izi501 said:
Hmmm... if you have a A310e you're in the wrong forum mate You have a wildfire, not a wildfire s !
But if you have 2012 model, it is possible that you need to try another recovery... you tried all of those I proposed in the guide?
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
Click to expand...
Click to collapse
Sorry it is an A510e...and I gave tried two recoveries twrp 2.2 and cwm nodded for 2012edition non are responding to touch...
Sent from my HTC Sensation using XDA Premium 4 mobile app
yasir4abbas said:
Sorry it is an A510e...and I gave tried two recoveries twrp 2.2 and cwm nodded for 2012edition non are responding to touch...
Sent from my HTC Sensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could try cwm 6, or owl mod... I must say, as I do not own a 2012 model, I don't know which recovery works for them
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
Marvellous CM10 - RELOADED
Thanks man fr yr ROM: Marvellous CM10 - RELOADED(I hit he button).
(Maybe not the right place, but thanks :good::good::good::good::good::good::good:
I use yr rom fr three days, very good battery and very stable. no problems.
Installed like in OP3 from thehacka1 and Installed INT2EXT+ and format /sd-ext.
Made it personal: deleted viper4android / seeder / wallpaper / filemanager and installed: ES file explorer / acalender / ROM Toolbox.
Camera/camcorder could be better.
Woooooow
OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm
Reserved #1
Reserved #2
I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.
thanks
ROM is very smooth and fast. Works much faster than CM11.
Very thanks
@psyke83 omni rom will be used kernel 3.×.× as per source given above.
@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.
Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?
Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.
Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least
Can Someone reupload this?
Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirementsTo run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
DownloadsNo Download as no longer maintained and buggyQR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issuesYou tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06
FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit
I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...
GOOD JOB .....Bro
kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you
Anyone already try this tool? I want download, but size so damn high
zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)
I can´t flash twrp with this toolikt any one have a clue?
Do you have the adb drivers installed? Or is it throwing an error?
Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk
Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.
dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...
Download link is not working. Please re-up. Thanks
godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1
If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.