Related
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
hi guys I just found 2 old wave s8500 that I had forgot about for a few years :laugh: anyways whats the best way forward as for android install, I am confused with all the development
1) dual boot , any advice on this!
2) android which works the best at the min?
3) any complete guides for a complete setup ?
hope some kind person can take the time to help me out :angel:
whatabody said:
hi guys I just found 2 old wave s8500 that I had forgot about for a few years :laugh: anyways whats the best way forward as for android install, I am confused with all the development
1) dual boot , any advice on this!
2) android which works the best at the min?
3) any complete guides for a complete setup ?
hope some kind person can take the time to help me out :angel:
Click to expand...
Click to collapse
Dual (triple boot) -> see my Fota/Fboot thread in android dev on bada section, it has some explaination about waht is fota and how it's work.
On this project we only have : -a kernel (called zImage, boot.img or whatever), a Fota to load the kernel (all Fota are compatible with all kernels) and of course a ROM.
You'll see several version of installation (Nand, SD, Loop), and several rom (omni, cm11, Paranoid Android).
About ROM (omni, cm11...) your choice.
About installation :
Nand is installed on internal memory (erase bada), SD is installed on SD (doesn't erase bada), Loop is installed next to bada on internal memory (doesn't erase bada). Loop is slower than Nand. Speed of SD rom depend of SD speed.
Don't go to ROM older than Badadroid 4.4, it's outdated.
Any complete guide ? each rom have a little guide in its thread, often clear enough.
Requirement :
Bada 2.0 (it's important, find a bada 2.0 firmware here (like Turko CFW or Firefly) if you have bada 1.2)
Android-friendly bootfiles (common to ALL android rom, if you find one in a thread it will work with ALL rom----
A FOTA (there is a lot of FOTA, all compatible with all ROM as soon as this is an android Fota). It decide which system boot first, what key combination does, and what kernel must be named. Needlessly to say, i like my Fota
Flash all these thing with Multiloader v5.65.
If you have any question, read some threads first (at least first posts), read this again, and then ask
About CM12
Please Post all your Feedback, Fixes or Discovery of new Bugs and Discussion about Mike's CM12 here.
Its compiled by me and released here for some public testing. It was and is Mike's CM !! its his Hardwork !
Thanks to Mikeionniia for his Hardwork and ROM , Langes for helping in the Guide and @Men_in_black007 for helping me in compiling.
Downloads and Build's History
1. 4 Jan 2015 (Initial Build) http://d-h.st/vMXg
*Calls not Going Through but Calls are being Received
*Internet/Data Plan Not Working
*Camera is Working
*Video camera is not 100% stable, sometimes it restart phone. 480p recording work mostly without problems
2. 22 Jan 2015 (Wifi Started Working) http://d-h.st/4Ii
*Wifi Working
*Bluetooth Working
*SMS Working
*Randomly Reboots alot
3. 5 Feb 2015 (Calls/Data work randomly) http://d-h.st/34om
4. 12 Feb 2015 (Calls/Data much Stable. Less Random Reboots Much Stable) Kernel not working so Not uploading this.
5. 17 Feb 2015 (Many Changes inside the Settings. Overclock Built in the Settings and many minor changes. Smoother/Stable) [B]http://d-h.st/AcDk[/B]
6. 7 March (Stable than any other build. Smoother/Faster. Loving it. Some changes in Settings) [B]http://d-h.st/2KHx[/B]
FOR ALL LATEST AND NEW BUILDS PLEASE GO TO THE OFFICIAL THREADS HERE !! Plz hold your Q&A and Discussion in their respective Discussion Threads only !! Don't spam the Dev Threads !!
CM12 For all LegacyXperia Devices http://forum.xda-developers.com/xperia-arc/development/dev-2011-unofficial-cyanogenmod-12-0-t3053950
AOSP Lollipop For all LegacyXperia Devices http://forum.xda-developers.com/xpe...v-2011-android-source-project-builds-t3053170
Gapps
DOwnload Pico,Nano or Micro Gapps Only.. no Bigger than this. !!
from here http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Install Instructions
You should have an Ext4 Partition on your sd card to install properly. I have a 4gb Ext4 Partition on my 32gb card.
Be Warned the process of creating an Ext4 Partition can/maybe wipe your SD card.. So Back Up appropriately
1. Flash .79 FTF in Flash tool
2. Flash Boot.img from Fastboot.
3. Staying in fastboot, erase system and userdata
fastboot erase system
fastboot erase userdata
4. Boot Device, Enter Recovery and (Factory Reset) and then (Wipe Cache)
5. Go to Apply Update, Scroll to the Location of you Zip file of the ROM and Install the ROM !
6. Boot ROM.
Detailed Installation Instructions here for Newbies
http://forum.xda-developers.com/showpost.php?p=58830270&postcount=110
How to Root The ROM or Activate Root on the ROM ?
Go to Settings / About Phone / Build Number and (Press this Continuously for 7+ times until it shows u
that Development Options is Activated.
Go Back to Settings, Click on Development Options and Enable Root Access For Apps/ADB or Both.
Review Video
Installation Video
Thank you for this. From the quick testing I did the D-Pad and buttons work fine but the D-Pad has incorrect directions like it's been rotated anti clockwise up is right, left is up, down is left, right is down. Although you probably know that already directions for installing are slightly incorrect. There is no CWM with this boot.img its CyanogenRecovery so we can't mount /system to wipe it, but it still seems to install and boot fine. System is erased with Fastboot in a previous step anyway
Camera is upside down, but again obvious one you probably know about Well done to everyone involved in getting this device on the cutting edge! Performance is really really good, its like lollipop was made for this
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Phone (Calls u mean) - Not Working
Wifi - Not Working
GPS - I didn't Test
Prox. Sensor - I didn't Test
Light Sensor - I didn't Test
Auto Rotate - Was working I think so, I don't remember
Sound - Working
BT - Working
Camera - Working
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Owriço Winchester said:
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
Click to expand...
Click to collapse
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
saqibkhan said:
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
Click to expand...
Click to collapse
need to flash stock MT25i (Neo L) ftf
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
all I can say is.. I have a 32gb memory card.. a Ext4 4 gb Partition.. and when I installed the ROM .. it showed me everything as One large 1gb Partition.. not 1gb.. something 900mb ..
So make a partition and then Install the ROm !! it should work like it did work for me.. I Wiped everything from ADB .. and Installed from the Recovery by Cyanogen only.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
DocMAX said:
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
Click to expand...
Click to collapse
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
hello !! I wonder if you could help me to port for xperia neo v
What would it take?
There is cm12 for neo v. Just look for it on Yours phone forum
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Bakisha said:
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Click to expand...
Click to collapse
Hi that's nice that you compiled again.. cuz Mike might have made some changes and some bugs might be done with..
yes system was 900mb+ etc.. and I had a 4gb partition on my card for Link2SD .. its Ext4 !! as far as i remember.
Step 1...i flashed the .79 FTF for Xperia Play..
Step 2...then i Wiped System and userdata by fastboot as listen in Mikes CM11 OP !
Step 3...Then i flashed Kernel.. (or you can switch these steps 2 or 3)
Step 4... Install ROM by Using Cyanogen Recovery. i can we need to go to Install Update.zip option ..
Edit : i think 210/700mb is more than enough.. values are already calculated by you so thanks for that.. its always nice to have some space in system else it keeps showing (System Low on Memory Error)
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
saqibkhan said:
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
Click to expand...
Click to collapse
To be honest, i don't know. My guess is that you need to delete cm12 source, then from ~android/system folder do the repo init for cm7
There is a guide for building CM here but use
Code:
repo init -u https://github.com/CyanogenMod/android.git -b gingerbread
instead of ics
Editing partition should be easy, as you only need to edit file semc_zeus_defconfig (it should be in ~android/system/kernel/arch/arm/configs/ folder or just search where is that file when you download source)
Then build as a guide say.
I am not 100% sure about building CM from source, so i'm only guessing, maybe someone else with better knowledge about compiling could say
As for CM12, i'll compile it again in few days, and hopefully i'll have time to test it for weekend
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
DocMAX said:
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
Click to expand...
Click to collapse
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Does the second partition have to be 4GB in order to install CM12 or what size?
P.S. Tested Dead Space on CM7.3, Touchpads not working. I have found Doom Kernel + ICS, without heavy apps, to deliver the best overall performance for the Xplay. Overclocking to 1.8GHz makes even Reicast playable.
saqibkhan said:
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Click to expand...
Click to collapse
i dont see light sensor working?
Hi, this is United Oxygen team.
We were specially working for MultiROM for a long while, and finally, it is almost finished, so we are proud to show up this project to you.
- DOWNLOAD -
@ MultiROM TWRP
- For F220K (Optimus GK)
http://drive.google.com/file/d/0BwF2VxTC-s7_RG10ZTMxWDBMVFk/view?usp=sharing
- For F240 (Korea Optimus G Pro)
http://drive.google.com/file/d/0BwF2VxTC-s7_U1Y1SDUxX09KMms/view?usp=sharing
- For E980 (Intl Optimus G Pro)
http://drive.google.com/file/d/0BwF2VxTC-s7_SE5Fc0VpN0dTYU0/view?usp=sharing
@ MultiROM
http://copy.com/7eCxh7k6f8x7o6LG
Please download all 3 files!
- Caution -
1. YOU SHOULD USE kexec-hardboot SUPPORTED KERNEL IN PRIMARY(STOCK) SLOT! United Oxygen will support kexec in Oxygen Kernel 2.0. Otherwise, you should check whether that kernel supports kexec.
2. In Secondary slots (MultiROM slots), you can install any ROMs, even if it doesn't support kexec-hardboot. It means, you have to install kexec-supported ROM in Original System Partition, and after that, you are free to install any ROM in MultiROM.
-How to install MultiROM-
0.Reboot to custom recovery, and install kexec supported ROM or Kernel like our Oxygen Kernel 2.0. We've already shown our ROMs in other threads.)
1. Install MultiROM TWRP in other recoveries.
2. Reboot recovery, and you will be in MultiROM TWRP.
3. Flash 'MultiROM-~~~-e980.zip'.
4. (Recommended) Reboot recovery once again.
5. Go to Advanced - MultiROM -Add ROM - Install your favorite ROMs to Secondary slots.
6. Reboot system, and you can choose ROMs that you want to boot in bootmenu.
- Must-Know about MultiROM -
Q. Bootmenu does not appear. What should I do?
A. I think you upgraded or changed the kernel. If you upgraded the kernel, please flash 'MultiROM-injectboot.zip' in MultiROM TWRP.
Or, if you deleted MultiROM data, please flash 'MultiROM-~~~-e980.zip' once again.
Q. I want to delete MultiROM.
A. Flash 'MultiROM-uninstaller.zip'.
Q. ADB Sideload not works in TWRP Recovery.
A. It is a bug...We will try to fix it soon.
Oh, it's there already. Thanks.
Oh God, can't believe it! Thanks A LOT Oxygen Team! This will save a loooot of time for flashing
This is a very great addition to the G PRO community. Anyone test this then report?
This thread is keep being written. Please don't follow this yet.
victor19 said:
Oh God, can't believe it! Thanks A LOT Oxygen Team! This will save a loooot of time for flashing
Click to expand...
Click to collapse
MitoTakatori said:
This is a very great addition to the G PRO community. Anyone test this then report?
Click to expand...
Click to collapse
I'm writting again, please wait.
======Finished!======
Genie's said:
I'm writting again, please wait.
======Finished!======
Click to expand...
Click to collapse
I am so excited to try this and I have some questions!
So, there is a kexec kernel for CM 12.1 and for Blisspop 3.2, so to be able to use this MultiROM I am going to need to flash either CM 12.1 or Blisspop 3.2 and their respective kexec kernel right? And that would be my primary ROM, then after that I can flash my stock ROM(or any ROM of my liking) and serve as my secondary ROM. Did I get that right?
[email protected] said:
I am so excited to try this and I have some questions!
So, there is a kexec kernel for CM 12.1 and for Blisspop 3.2, so to be able to use this MultiROM I am going to need to flash either CM 12.1 or Blisspop 3.2 and their respective kexec kernel right? And that would be my primary ROM, then after that I can flash my stock ROM(or any ROM of my liking) and serve as my secondary ROM. Did I get that right?
Click to expand...
Click to collapse
1. Yeah. You just need to install our Oxygen Kernel 2.0-contained ROMs or ROM with other custom kernels that supports kexec.
2. Yeah...maybe? We didn't test stock in secondary slot, but I think it may work.
I recommend these to E980 users:
Install our Oxygen Kernel 2.0-contained ROMs based on F240 in E980's primary slot. Some functions will not work maybe, but you can use MultiROM. (Tested.)
Any one test Twrp recovery for e980
On Adding a secondary ROM, there are details on that part, can you detail what to choose? I am trying to flash a secondary ROM, but I don't know what to do on that part.
There are options there whether the ROM is android or multirom (.rmm)?, then where to install, whether internal, or on the other 2 options. Can you please elaborate on those parts?
Thanks.
@Genie's
MitoTakatori said:
On Adding a secondary ROM, there are details on that part, can you detail what to choose? I am trying to flash a secondary ROM, but I don't know what to do on that part.
There are options there whether the ROM is android or multirom (.rmm)?, then where to install, whether internal, or on the other 2 options. Can you please elaborate on those parts?
Thanks.
@Genie's
Click to expand...
Click to collapse
There's no limits in installing ROMs in Secondary slots. Just install anything you just want to flash.
But you should install kexec-supported ROM or Kernel in just Primary Slot.
We are now tring to support E980.
Please go to my threads that contains ROM with Oxygen Kernel V2.0, download E980 version and test ROM and whether MultiROM is supported or not.
If you install this ROM in Primary Slot, please enter this adb command to know us what E980's kexec code is. :
adb shell
su
dmesg | grep -i hardboot
Genie's said:
There's no limits in installing ROMs in Secondary slots. Just install anything you just want to flash.
But you should install kexec-supported ROM or Kernel in just Primary Slot.
Click to expand...
Click to collapse
Currently I have BP 3.2 installed on Internal slot, then I want to install another ROM for the secondary slot, where to install it? There are 3 options on the multirom menu
Use 'Add ROM' Menu to install in secondary slot.
Genie's said:
Use 'Add ROM' Menu to install in secondary slot.
Click to expand...
Click to collapse
So, I will install on the second slot? Not on the Internal slot?
I will explain shortly :
Primary Slot, means Original System Partition : Kexec-Supported ROMs, like our Oxygen Kernel 2.0 contained ROM.
Secondary Slot, means Internal Memory : Any ROM you want. (But our testers said Stock ROM would not work, maybe.)
@saxsymbol succeeded installing MultiROM in E980 with our Oxygen Kernel 2.0 ROMs for E980!
E980 users should use our ROMs in Primary Slot if you are having trouble in installing MultiROM.
Genie's said:
I will explain shortly :
Primary Slot, means Original System Partition : Kexec-Supported ROMs, like our Oxygen Kernel 2.0 contained ROM.
Secondary Slot, means Internal Memory : Any ROM you want. (But our testers said Stock ROM would not work, maybe.)
Click to expand...
Click to collapse
I am still a bit confused. Sorry. If you can post SS of the MultiROM menu, and step by step guide, maybe I will understand it. Thanks by the way.
Hi guys . I made this build for myself. And now i want to propose it for all. It made for unlocked bootloader only .
It based on original Z rom from HERE .
4pda forum team did fix for adapt ZL and 228kernel with 302TWRP. I only compiled all to this build.
Requirements
Unlocked bootloader
Current backup
How to install:
Go to TWRP .
Do full wipe (system , data, cache and dalvik)
Install rom
Reboot
Long wait ..and be happy!
After successffully start you can install v.1.1 without wipes and Zombie kernell original
or install modify version with Faux sound support modify
Faux sound Faux
Download:
v.1.0 https://www.androidfilehost.com/?fid=24591020540824843
Update v.1.2 http://forum.xda-developers.com/showpost.php?p=68514241&postcount=186
Thanks :
@Kuciak for original rom
@olegusoshin for his fix for ZL
@David_76 for his modified kernels
@Tommy-Geenexus for Zombie kernel
[/COLOR]can i install this on C6502???
nandhul30 said:
[/COLOR]can i install this on C6502???
Click to expand...
Click to collapse
I think that you can.
now i am using this rom....x theme is awesome...thx for the rom...but i cant see any other changes....
Update 1.2
Hi , dev released an update http://forum.xda-developers.com/showpost.php?p=68514241&postcount=186 .
Flash without wipes via recovery.
How long does the first boot take?