Develop Bugs

[GUIDE] All-in-One Defy Beginner's guide

{
"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"
}
About this guide
In this guide you will find all the information regarding the Motorola Defy. I’ll try to explain as best as I can how this phone works, how to root, install SBFs, and most important: how this stuff actually works so you don’t screw up your phone installing incorrect versions of Roms.
I’ll try to cover the eFuse system found in this phone as well as other Moto phones and how it actually works, this is fundamental to understand why you can’t go back to old stock Roms once updated.
**NOTE** I AM NOT responsible for any kind of damage your phone can suffer**NOTE**​
Index
I just bought a Defy, now what?!
Red, Green, Plus. What can I and can not do
Facts
Custom Recovery
eFuse
SBFs
Fixed SBFs
CG Versions
Official SBFs
RSD Lite
Rooting
How to flash
CM7, MIUI, Various Custom Roms and going back to Stock
Common Problems
I just bought a Defy, now what?!
Congratulations on your new phone! Now you need to know what kind of Defy you have!
If you've got a Defy+ then this part doesn’t apply to you, so you can jump to the next one. If not, keep reading.
If you got a new Defy, you could have a SOC or Bayer Defy, the difference between both Defy's is pretty much only the Camera Module, there is really no other difference.
At first it was easy to determine which Defy model you had by just checking the Lens color, RED color meant Bayer module, Green Lens meant SOC Defy; sadly it's not so easy to know which one you have now, since there are SOC Defys with Red Lenses.
The Camera Module is the responsible for receiving the "information" from the lens and then translating that into machine data.
The Bayer module is capable of 720p video Recording and can take better pictures than the SOC module. At the moment is not known if the SOC module is actually capable of making 720p Recordings or if it is just a Driver issue; but for the time being there is no 720p recording for SOC Module.
Almost all SOC Defys will have a Green lens; therefore you will find almost all ROM threads labeled compatible or not compatible with Green Lens. Usually a different installation or a patch is needed to make these roms work on Green Defys.
The are a few ways to check which Module your Defy has, the best one and more accurate one though, is installing Catlog, starting it up and then start the camera. After starting the camera, go back to Catlog app, pause the logging, and search for "camera". There should be a couple entries, one of them should say either SOC or Bayer.​
Red, Green, Plus. What can I and cannot do
With the 3 versions on the market, there is some extra caution to be taken.
Green Defy users have to be careful when installing custom Roms since it may not be compatible without doing extra steps like patching or installing extra files. Defy+ must be very careful to what they flash on the phone.
As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong.
Most of this Guide is made only for the Defy, either Green or Red lens, and although the Defy+ is pretty much a Red lens Defy, a few things are NOT made for Defy+ users:
CM7, MIUI, Various Custom Roms and going back to Stock***
Common Problems*
Stuff in this list should be read even for Defy+ owners, but they cannot be applied yet to the Defy+s.
*Not all of them apply to the Defy+
**explained later in the Guide.
*** You CAN install CM7 and other Android Versions, the basics explained on this guide just do not apply to Defy+, as well as Downgrade to Stock.​Facts
So, let’s start doing a small sum up of what this phone can do.
At first the Defy was presented as a low /med end phone. With 800 MHz CPU, no GPU, 2 Points hardware limited screen. It is well known nowadays that the Defy actually has a PowerVR 530 GPU, TI OMAP 3630 CPU and a screen supporting 10 Point multitouch.
The Defy+ is basically a rebranded Defy, with Gingerbread, 1700mah Battery (instead of 1540mah) and its default CPU speed is 1GHz. It has the same internals as the original: Same CPU/GPU, Memory, Screen and so on.
Defy+ comes always with a Bayer camera module, and so far there are no Defy+ variations.
LOCKED Bootloader, what does this means?
For some people is hell, for others (normally non advanced users) is a pretty cool insurance for their phone. This locked Bootloader thing means there is no (so far) way to rewrite the Stock Bootloader or the Stock Recovery.
When the phone turns on the Bootloader basically starts all the hardware and make your phone come alive.
Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip files.
At first this became a problem, because with a locked Bootloader there is no way to install a Custom Recovery like ClockworkMod or install a new Rom.
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Thanks to this locked Bootloader, is really, really hard to Brick your Defy. Most of the issues seen on the Forums are NOT Bricks, just incorrectly flashed SBFs (more on this later ). With brick one mean the phone has no access to the Bootloader or can’t initialize its hardware, requiring you to use a JTAG to directly reprogram the phone (which I’m not sure is possible on the Defy).​
Custom Recovery
A custom recovery is a special "App"** that comes in a separate partition in your phone. This "App"** allows Android Phones to do recovery tasks, like deleting data, installing recovery Zips and so on; The tasks you are allowed to do with Stock Recovery are pretty basic. Here is where Clockwork Mod comes into play.
CWM is a Recovery that allows you to not only do basic tasks but also create Nandroid Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff.
Normally a Custom Recovery is installed by flashing the Recovery Partition in your Android Phone with a Custom Image, but since our Defy comes with a Locked Bootloader, this is not possible. Leaving us without many options to proceed.
And that's why we have 2nd Init, this application is what actually installs CWM in the Defy, it does it by installing it in your internal memory and not in your Recovery Partition and then pointing the Android system to it right after the Stock Recovery boots.
**Is not actually an App, is more like a Linux Console with UI so you can recover.​eFuse
Here comes a really important part on how the flashing works and why is problematic for some people, it is not explained anywhere.
It actually took me more than a month before I started modifying my Defy because this information is really scattered around the web and I don’t like to do things I do not understand
So, to the eFuses; this Technology was developed by IBM, is a really cool tech that allows some chips to actually change their internal wiring, and reprogram themselves.
How is this used on the Defy (and the Droid too)?
Well, see this system as a bridge, each time you flash a new update to your phone you burn a bridge, the information went to the other side, but there is no coming back.
Here comes most of the issues we have with the Defy, once you update to a higher version of your Android, there is no way to come back. (There are some tricks, explained later).
This lead us to the next part of the Guide, where I will explain you WHY you can’t go back and how this actually works.​SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.​
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.​
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.5, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
For a full list of Roms and their respective CGs go here​
Official SBFs
Here is a list of all the Defy Official SBFs and Defy+ Official SBFs that means that they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.​
RSD Lite
RSD Lite is an App used by Motorola to Flash Smartphones. It can revive mismatched Nandroid/Fixed SBFs, Black Screens, failed flashes etc.
Even though is really, really hard to completely brick a Defy, it is possible; a corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a Bricked Defy. If you can, always flash your Defy from a laptop so the power is not an issue, use good cables, and be sure the PC doesn’t go to sleep when is not being used.
Also, when flashing SBFs, is normally advised to put your SBF in your PC Root directory (C:/ ) or whatever it is in your PC and rename it to a short name like Defy.sbf, why? Because sometimes the Path name is just too long and RSD Lite throws errors not allowing the phone to be Flashed.​
Rooting
So, what’s rooting and why everyone talks about it.
Phones come “locked” , this means users can only do basic usage of their phones, installing/uninstalling apps, wallpapers and basic stuff. You can see but not touch any System file, or change the actual behavior of Android. Rooting just means you have access to your phone like an Adinistrator, meaning you can access and change system files, delete/create files and folders and so on.
To be able to install Apps like 2nd Init that need to access Android System files your phone needs to be able to write and acess these files.
Thankfully, rooting the Defy is a rather simply and usually harmless task.
How to Root: (NOT for BL7)
Get SuperOneClickRoot
Get and Install Motorola [Drivers ]
Reboot your PC
Turn USB Debugging ON (Settings -> Applications -> Development on your Defy)
Connect your Defy to the PC
Wait for the PC to install any missing Drivers
Click on Root
Let it work, then it will ask if you want to install BusyBox, hit YES
After it finished it will ask to make a test, click cancel and just Reboot your Defy
Done, Defy rooted
How to Root BL7:
Enter Recovery, Wipe Data/Cache
Download this SBF and Flash it
Enter Recovery, Wipe Data/Cache
Download Part1 and Part2 SBF and Flash it
Enter Recovery, Wipe Data/Cache
Recommended ->> New Method to root the Defy: (Thanks TJKV for the tip):
Now there is one method for rooting all Defy and Defy+ devices irrespective of CG signature versions, simply use the Framaroot app to root:
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
​
How to Flash
Ok! Now that we understand how a lot of stuff works, it’s rather easy to get a new Android version installed on your phone.
For any full SBF the same steps must be always done, just be sure to know what SBF are you flashing and keep always in mind your CG Version to keep the possibility to downgrade in case you need your warranty.
Requirements
Get the SBF you want to flash
- Full SBF: No Nandroid backup needed, always keep CG versioning in mind.
- Fixed SBF: You might need a matching Nandroid Backup.
Get and Install RSD Lite v4.9: There are reports of other versions working, but this one is what I have used.
Get and Install Motorola [Drivers ]
Now to Business:
To Flash full SBFs, here is the standard procedure:
Open RSD Lite: Click on [ … ] Button and select your .SBF (Remember to rename to a short name and put it on root of your PC) and click Open.
Boot your phone into Bootloader Mode (check last section if you don’t know how to do it).
Now connect your Defy to your PC
The START button on RSD Lite should be available now, click and wait.
For Fixed SBFs a slightly different method is needed, it's basically the same but you need to Wipe Dalvik Cache and Data before flashing. Then after flashing you need to enter immediately to Recovery and restore the matching Nandroid Backup. I won’t write a specific way to do it here, since most of these versions require different steps (for Example CM7 or MIUI), so is better to check a specific guide for your Custom ROM or Android version.​
CM7, MIUI, Various Custom Roms and going back to Stock.
Now, if you want to go to CM7 or MIUI Roms, there are good tutorials on how to do it. I will just explain here how the procedure works so you know what you are doing and not only follow step 1, 2 and 3, which usually leads to issues if anything goes not exactly as written.
There is no way to flash a full SBF with CM7 or another rom. What is being done in these cases, is just use a base Android, be it CEE, Localized EU, Éclair, whatever.
Quarx recommends using JRDNEM_U3_3.4.3-11_BLUR_SIGN (not anymore, old) 3.4.2-179 CEE Deblur SBF. But this is not NEEDED; I’m running CM7 with German 3.4.2.177-3 and is running perfectly.
Then, restore a Nandroid Backup of a CM7; it will copy all the new stuff into your partitions and won’t remake them, keeping all the signatures, security and stuff intact.
Here is a good Guide to install CM7: How to Flash CM7
To downgrade from any of these Roms all you need to do is install a Full Stock SBF (remember to check CG Versions!) and done, phone back to Stock.
There is another way to install a lower version of Android without using a full SBF, and it is installing a Fixed SBF of a lower Android version, then restoring its matched Nandroid Backup.​
Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Method 1:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup << File is Back, thanks Ichibanme again!>>
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))[
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Download this SBF and Flash it.
Root your phone.
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery.
Reboot to CMW recovery, and wipe Data/Cache.
Install CM7 then install Google Apps.
Reboot an go into Stock Recovery (using the vol- button, not from Bootmenu).
Do a Data/Cache Wipe or you won't have any space when you're done.
Flash this Fixed SBF
Reboot into your nice new rom.
Do not Wipe Data anymore or you will have to start again.
​
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.​
How to Install CM7 after Installing a Full Gingerbread SBF: (!) Ok, first of all do all the steps above on "Installed full Gingerbread SBF and can’t go back to another rom"
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
Thanks jebrew for the info.
I installed a Full SBF/installed CM7/other Android version and need my warranty: (!) Ok, this pretty much depends what have you installed and on which zone you are. Try to keep ALWAYS your phone ability to downgrade to whatever version is supported in your region.
For example I have a German Defy, we have SBF 3.4.2 (Froyo) officially deployed, this means all I need to do to go back to Stock and claim my warranty is download the Stock 3.4.2.177-3 version and Flash the full SBF. If your zone only has Éclair officially deployed then you should never ever flash Full SBFs with anything higher than Éclair, only Fixed SBFs, then in case you need your warranty, just Flash your zone full SBF and done, back to Stock and hi2u Warranty.
Full Stock SBFs will put your phone to the state Motorola sells that Android Version. If you install the same SBF you had, it will be like new.
How do I enter Recovery Mode?!: With the Phone off press VOLUME DOWN then, while still pressed, power up the phone and leave VOL key pressed until you see a Yellow triangle, once you see this you are in Recovery now press Vol Up and Vol Down at the same time (if you are in Froyo) and the menu will appear, if you are on Éclair the menu should appear without having to press anything.
How do I enter Bootloader Mode: With the Phone off press VOLUME UP, then while still pressed power up the phone. Keep the Vol key pressed until a black screen with some white letters appear. This is the Bootloader.
After Upgrading to Froyo my Defy is laggy, slow or reboots: (!) This is a common issue when coming from Eclair to Froyo. If this happens to you, just do a full wipe (Delete Data/Delete Cache on Stock Recovery), after that your phone should work correctly.
Stock Froyo sometimes lags and/or freezes the phone: (!) Its caused by the VM consuming all memory, all you need to do is adjust the amount of MB the VM should leave free.
There are a few ways to do it:
Use a terminal emulator, or use GScript Lite to run this:
Code:
su;
vm.min_free_kbytes=8192;
(Not permanent, need to be ran every time you reboot)
Get Sysctl and change vm.min_free_kbytes to 8192.
Get SetVSel and tap on increase vm.min_free_kbytes to 4096.
How do I make/restore these Nandroid Backups everyone is talking about?: Nandroid backups are made using Clockworkmod (CWM). Enter the Custom Recovery, go to Backup and Restore and create your Backup. To restore use the same method but Restore instead of Backup
I downgraded from CM7 to Stock / Installed a new SBF but I'm having bootlops: (!) If this is happening to you, after flashing the Stock SBF, enter in Stock Recovery and do a full wipe (Data/Cache) and reboot.
I have issues with my Battery Readings / Battery charge suddenly Drops: This issue is caused by a cheap battery reading implementation. If you want to know more about it, and how to get more accurate readings on your Defy, please go to: Defy Battery Drops Explained. Thanks jusid for the detailed explanation!
(!) NOT for Defy+ ​
If you find this Guide useful, please remember to click the Thanks button

Thank you for putting all this useful information together. It should be made sticky .

Wish I would've found this post three days ago. But you learn from trial and error. Made alot of errors but looking good now.
Sent from my MB525 using XDA App

This made a very good read thanks for compiling all this information.
djc

great guide,i agree it should be "sticky".

yeah, it definitely needs to be a sticky, would make a lot of defy newbies' life easier

Thanks!!! (button pressed)
Sticky +1

Great Guide, wish it would have been around when I decided to flash my Defy. Sure it will help those is the future. Thanks for taking the time to put all this information is one place.
I to would say +1 for Sticky

This's the great work,
it's easier for the beginner
Thanks

Nice to see people has found usefull my Guide, would be awesome if it became Sticky ><
If you have suggestions, more important information to add, send me a PM and I'll fit the info in there.
Sorry I didn't post it before hehe, took me like 5 days to write everything and make it as simply and understandeable as possible.

Awesome post man!!
If any post deserves to be a sticky,this is it!!
Cheers..

great work.
cg39.smg version 5 for > Gingerbread 4.5.1-128

walter79 said:
great work.
cg39.smg version 5 for > Gingerbread 4.5.1-128
Click to expand...
Click to collapse
Good thanks, added that and the other 4.5.0 as CG version 5.
Corrected some typos and grammar issues I found.

Zephyrot, you made my life way more easier!
A million thanks to you. (xda lets me thank just a post once )

This is awesome, especially for people like me who are fairly new to Android. After spending some time with this thread I may get the courage to try a new rom.
Thank you!

Here's a Q:
Do the various Android 2.2 versions all have a version number of 4?
(I am asking because I am on Froyo 3.4.2-145, and am wondering if I can flash a full Nordic sbf and will be able to go back to my own official Froyo.)

juried said:
Here's a Q:
Do the various Android 2.2 versions all have a version number of 4?
(I am asking because I am on Froyo 3.4.2-145, and am wondering if I can flash a full Nordic sbf and will be able to go back to my own official Froyo.)
Click to expand...
Click to collapse
Yeah, all SBFs 3.4.2 have the same CG version. The ending number, in this case -145 is just for the zone/language it is released.
What I'm not sure is if the 3.4.3 version has a different CG, I <think> they have the same version, and only changes once updated to Gingerbread, but I don't know how to check it out.
In your case there is no issue, since Nordic is 3.4.2-177 and your base -145, same CG
Edit: Searching around the web I found out all 3.4.X should have the same CG version, if anyone can confirm this to add it to the guide would be awesome

Maybe I can get a confirmation for my answer.
I use JRDNEM_U3_3.4.2_179-002_DEBLUR_CEE official rom for basic (with official update).
Does my Defy lack any part of CM7 if I flash directly the latest nightly on it (leave out rc1v2)????
And if lacks than what part(s) is(are) that(those)????
Kernel is the same in this official and rc1v2 too, so I can't find a part that needs from rc version to be up-to-date with CM7 on Defy. I think official rom above and latest nightly is enough, but if not please someone tell me the missing part(s).
Thanks

Thanks for this info, its very helpful for those who are learning... like me

Really well put together. Invaluable to any Defy owners wanting to flash.

[Q] Question about Customization

Hi am new to this Customization of Android (Gnex is my first android phone)
I know how to root and and install rom, kernels and etc
What i need to know is the following questions:
- What does it mean someone says you need a rooted phone? (is it something that just enables you to Customize your phone, hence installing custom rom and kernels)
- What does rom means? (is it like a OS on computers)
- What does kernels means? (is it like a software that changes the layout of OS to look like Mac OS)
- What does recovery mode do? (does it help to unbrick the bricked phone)
I may have answered my question but i just want to make sure if i am right

can someone confirm this please?

1) Rooted means having root access on the phone. Root is the equivalent of administrator on Windows. It allows access to the restricted areas of the phone. Basically like jailbreaking on ios.
2) A rom is an OS package. They are essentially variations on the same base code but add features, optimizations or other goodies.
3) A kernel is the software that interface between the OS and the hardware. It controls the cpu, ram, wifi, etc.
4) Recovery mode allows you to install zip files (roms, kernels, etc), backup/restore the phone, and other features. It's used to change roms and kernels normally, but also can be used to reinstall a rom if the phone won't boot.

thanks a lot John
this clears a lot of things
One more question
in order to install custom ROM or KERNEL
Rooted > Recovery > ROM/KERNEL ?

Technically rooting and recovery are independent. Rooting makes flashing the recovery easier, but isn't required - It is possible to flash recovery via fastboot. Any ROM you'll flash should have root built in.

thanks
1 more question
How can i go back to stock rom (one that was right out the box "yakjuux")
let say if i dont like the custom rom's (I couldn't find a factory rom for yakjuux)

HTC Desire 310/320 All Roms,firmwares,recoveries,root,etc

Thread update 15.04.2022, fixed some links, removed others, added RR 5.8.8 and did some formatting.
So since there were many users who had questions for roms,root,firmware and stuff like that which was already available but only in small posts,I finally decided to make a big official thread for the HTC Desire 310 and 320. Why 1 thread for 2 phones? Well,they are practically the same phone but desire 320 is running on stock kitkat and has flash.
Port guys and developers: @MaRtYy01 aka Martin Dimitrov @HTC Desire 310 aka 69techur aka Alija Huskic (Team N3GG3)
@Swoopae (deserves to be here lel) and users in 4PDA Desire 310 and 320 threads
New facebook group (tnx Swoopae) click
1.ROOT​Flashable SuperSU zip: in firmware flashing video
<Moderator Edit>: Files removed due to 15 different antivirus services detecting the APKs as Trojans.
2.RECOVERIES​
Spoiler: For firmware 4.2.2 only
Recommended-CWM 5(you dont need anything else,everything on 4.2.2 can be flashed with it): click
CWM 6 click
TWRP click
Stock recovery(if something messes up with other recovery and you get into bootloop flash it with sp flash tools) click
OTA - for android 4.2.2 click
Steps:
1.Put the OTA (named as update.zip) and the CWM on your SDCard
2.Reboot to Recovery (Volume UP + Power)
3.Select "apply update from sdcard"
4.Choose our update.zip (OTA)
5.It will return an error(if it doesnt then you should flash the stock rom with sp flash tools)(as our device is already updated) and it will let you choose two options. SELECT REBOOT SYSTEM NOW
6.After the phone is fully booted up, proceed to install the recovery as you wish!!!RENAME THE RECOVERY TO RECOVERY.IMG OR YOU WILL END IN BOOTLOOP!!!(You can use Rashr or MobileUncle MTK Tools or whatever you want)
7.After install, reboot to recovery
4.4.2+​These don't work if you are with the jellybean firmware(kernel 3.4.5), only for desire 320 firmware. Required to flash roms with version higher than 4.2.2
- Philz Touch click in this archive you have all stuff required for the rooting and installing the recovery on the d320 kitkat rom. Password is amogus
- Philz Touch mirror link without any other stuff coming with it: click mirror
- Flash the OTA click mirror with the stock recovery and reboot, go to mobile uncle tools and flash the recovery (new recovery.img)
btw OTA for android 4.4.2 is different from the jellybean one
3.ROMS​
Spoiler: 4.2.2
These roms are usually bugless or with minor bugs that dont interrupt the work. All ported from 4PDA users
XPERIA C click (sometimes gives errors while installing apps)
Lenovo(vibe ui) click
MIUI 5 click (one of the best 4.2.2 roms)
Lollifox click
Moonmod click
CyanogenMod 10.1 click (google play doesnt work)
4.4.2/4.4.4​
WARNING:YOU NEED THE DESIRE 320 FIRMWARE TO FLASH ROMS WITH NEWER VERSION THAN 4.2.2
[07.11.2016]MIUI 8 click (bugless) [ported by @Swoopae]
​
Spoiler: 5.1.1
[01.11.2016] AICP 10 click
gapps(for AICP only) click [ported by @MilkyPL]
[26.8.2016]CyanogenMod 12.1 click bugfixed version by @Swoopae
Flyme OS 4.5 link in kk firmware flashing video (google play doesnt work,I will try to fix it soon;gapps built in) [ported by me]
Spoiler: 6.0.1
Not 100% of the roms are well tested, so have a working rom as backup in case the rom you try doesnt work properly, also report back if you experience this.
IMPORTANT-If you own desire 320 flash this patch right after the rom or you will face wifi issue-click
Its made for marshmallow roms,so work for lollipop and kitkat isnt guaranteed. Tbh it doesn't always work on marshmallow too lmao
For mounting the sdcard as internal storage,here is @Swoopae 's patch click
It's made for cm13 but will probably work on other marshmallow roms too.
[14.11.2016]Mokee 3 click (bugless,vpn also works,just 2g switch bugged) [ported by @Swoopae]
[01.11.2016]AICP 11 click (gotta be almost bugless as all new mm based roms) [ported by @MilkyPL ]
[12.10.2016]TemastekPLUS click (improved and tweaked temastek cm13,bugless,vpn also should work) [ported by @Swoopae]
[02.10.2016]SwoopaeOS r01 click (based on slim6,fixed lag and minor bugs plus a sexy theme) [yes its by @Swoopae]
[04.9.2016]Paranoid Android 6.0.3(aospa) click (vpn and audio from headphones doesnt work) [ported by @Swoopae]
[17.8.2016]CyanogenMod 13 click ( very stable, gps, google play work,just fm radio doesnt work) [ported by @Swoopae]
[15.8.2016]Slim Marshmallow click (everything except fm radio works) [ported by @Swoopae]
7.1.2​|27.09.2017| Resurrection Remix N 5.8.4 by Swoopae: click
(should work well,needs some testing)
|15.04.2022| Resurrection Remix N 5.8.8 by me: post download
Steps:
1.Make sure the rom is on the sdcard
2.If you wish you can make a backup of your current rom
3.Wipe cache,data,system;dont mount anything/wipe for a new rom on philz recovery
4.Select update from sdcard/zip from sdcard/whatever is it from sdcard
5.Choose the rom zip and flash it
6.Flash gapps if the rom requires it(pico gapps are strongly recommended)
7.Reboot,first boot takes 3-8 minutes depending on the rom
GAPPS: http://opengapps.org/
Choose arm - whatever android version rom you are flashing - pico are recommended,if you have problems with gapps try with pico,flashing after rom and after 1 boot and then report if still doesnt work
4.Firmwares​
- Have any problems with the gps? Try this: click and this: click
- Desire 310 stock roms:
single sim: click mirror mirror 2
dual sim: click mirror
- Desire 320 stock rom(works for both d310 single and dualsim): click ; When installed on desire 310 bugs of that firmware are little while line on top of the screen and auto rotation(screen flickering too but doesn't happen on 5.0+ roms)
- SP Flash tools: click
- Driver: click
- Fix for driver signature error on windows 8/8.1: click
- Stuff for fixing imei(including toolhero): click mirror
- If you don't want to flash the desire 320 firmware and just want to unbrick this tutorial will be more helpful(also works if you have desire 320 and want to unbrick): click
HTC Desire 310 aka 69techur reported that Lenovo A328 firmware also works without flickering on and white line,but volume buttons,camera,rotation and a lot of other things dont work.
- Instructions for flashing D320 firmware on D310:
1.Backup imei with toolhero on 4.2.2
2.Install the driver on the pc,if it cant install them because they arent signed-disable signature verification(test mode) or try on other pc
3.Run the sp flash tool with compatiblity mode windows 7(only if you are on newer os) and set everything on it like in the video, connect the phone to the pc without battery and holding volume down;da dl with cheksum,high speed,no battery in the options,select firmware upgrade and start to flash
4.Root with the pc software,make sure you have enabled usb debugging in developer settings
5.Flash the OTA with the stock recovery and reboot, go to mobile uncle tools and flash the recovery(new recovery.img)
5.Now you have recovery.Wipe system,data and cache and flash the rom you wanna flash(the 4.2.2 roms dont work anymore) after that flash gapps if the rom requires it and reboot.
KERNEL BUGS:Screen flickering(kitkat roms only),screen rotation,little white line on the top of the screen
5.YOUTUBE​
Kitkat firmware,recovery and roms installation: click
CyanogenMod 13: click
How to fix imei: click
CyanogenMod 12.1: click
CyanogenMod 10.1: click
MIUI 5: click
Galaxy S5 mod: click
The HTC Desire 320 rom: click
AICP 6.0.1: click
CyanPOP 5.1.1: click
CleanKat 4.4.4: click
Wanna port a rom on your own? Here is a video guide for android 5 and 6: click
and written tutorial: click
Credits:​
-The users of 4PDA for all 4.2.2 roms and all recoveries, cm12.1, guides, etc.
-Me for translating the guides, youtube videos and ported roms
-HTC Desire 310 aka 69techur for helping me test stuff, his porting tutorial, ported roms and youtube videos
-Swoopae and Tomi Sudi for ported roms
-other guys that I havent mentioned
If you have questions, reports about bugs, requests or something feel free to ask.
Don't forget to hit thanks

Nice thread
#Proud_To_Be_Team_N33G3!

Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?

Immortel.CZ said:
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Click to expand...
Click to collapse
in 5.x.x roms flash rom, boot, then flash
in 6.0.1 roms flash rom and then flash gapps

Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes

Immortel.CZ said:
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Click to expand...
Click to collapse
Broken os is for the 4.4.2 firmware (kernel 3.4.67),not the stock 4.2.2(kernel 3.4.5) .You need to flash the d320 firmware first,get philz recovery on it then flash the rom and the gapps.
And here my explanation:
7b) I will add that later in the firmware section
9 ''(You can use Rashr or MobileUncle MTK Tools or whatever you want)'' Rashr is in the google play
11.-14. Well,I guess I will have to add instructions how to flash roms
BTW The kitkat firmware installation+installation of recovery and roms video is complete gotta upload today
Edit:video uploaded https://www.youtube.com/watch?v=QRpw5sQA0rs
and thread finished

Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
Last two bugs above (GPS and data) still occuring but not every time. Looks like switch is bugged.
EDIT: Did full wipe, format SD, reflashed G5 mod and now works without those bugs. Probably my fault flash. Yay!
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too

Immortel.CZ said:
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Click to expand...
Click to collapse
I would recommend you broken os over cm13,I havent updated it from a month(since I currently dont have the phone to test it) and broken os is super stable and almost bugless.
BTW if you have the 512mb ram version,I highly recommend the s6 mod or cleankat(69techur still hasnt uploaded it tho,lazy bastard XD).Kitkat uses less ram and its faster.I actually think that cleankat must be the fastest rom after all.
For the s5 mod:
-Keyboard works by default,just swipe the status bar and choose aoso keyboard
-Weird,dialer worked fine for me.And its not for s5 after all,the dialer looks like jellybean touchwiz,not kitkat,probably ported from s4/s5 chinese clone.
-The unlock screen looks like that because of the navigation bar,if you remove it(find qemu.hw.mainkeys=0 in the build.prop and change it to qemu.hw.mainkeys=1) and add pie controls instead,it will be fine.
-The pop up about the back cover aoso appears in the original s5,but this isnt real touchwiz rom so I suggest you not to touch it/backup the rom and try to remove it.
-Idk,probably sh1tty touchscreen,I think I faced the same issue when I was with the rom
-I dont know about solution of the last problems,the russians have ported the rom not me,checked the forum and they havent even reported these issues XD
BTW,if you have problem with random reboots put the fingerorint unlock.Its not real fingerprint of course,you just have to swipe down on the finger icon.The russians reported that this fixed the random reboots.
Anyway,thanks for the bugs report

Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.

Reading this comments makes me feel like my IQ decreasing

Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!

Immortel.CZ said:
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Click to expand...
Click to collapse
Just to start from something,6),thats most likely software fault.And indeed I think the tutorials are fine,since you managed to flash s5 mod you are smart enough and for the videos-they are more to see how it happens,if i wanted I could put a song in the background instead of talking,my english sounds like **** tho(sometimes even I dont know what Im saying XD).So if you look at the instructions carefully,then follow what Im doing in the video you will be fine.Just if you dont know,you need to flash the desire 320 stock rom before s6 mod,broken os or other roms with version newer than 4.2.2 which might seem a bit hard for you(its actually easy tho,try to flash roms on htc one x and you will see what is hard ).The desire 320 rom also has a few issues like the rotation and white line.And dont get me wrong,Id choose broken os every day over s6 mod since its wayy better,s6 mod isnt bugless too.Also,your ram seems to be 1gb which is fine.
If you want the fastest solution-flash miui 5,its the stablest and the awesomest rom so far,ive been using it for a month and really loved it.You dont need to flash the desire 320 rom for it.

In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot

Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?

Aconcerneduser said:
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Click to expand...
Click to collapse
Hey Aconcerneduser.
If you have stock room then no, you cant install/move apps to SD. I´ve tried lot of things (like App2SD, Link2SD) and nothing works.
Try flash Galaxy S5 Mod, it is not hard and then you can move apps to SD!
I can make you noob proof walkthrough (how I flashed it), it takes you 15 minutes tops and it works.
EDIT: Updated my bug report about S5 mod!

Immortel.CZ said:
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Click to expand...
Click to collapse
'' 2) Go to recovery and flash 320 rom.'' XDXDXDXDXDXDXDXDXDXDXDXDXDXDXD
Lollll no.You need to flash it with sp flash tools;before that backup imei with toolhero
After that root it with the pc root program,flash the ota with STOCK recovery,do the ''build.prop thing'' and then flash recovery with mobile mtk tools.And new_recovery.img IS philz touch.
The rest is right.
Also,watch my last video for the kitkat firmware.recovery.You dont need to understand what I say,just look what Im doing.

Immortel.CZ said:
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Click to expand...
Click to collapse
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-

HTC Desire 310 said:
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
Click to expand...
Click to collapse
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.

MaRtYy01 said:
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
Click to expand...
Click to collapse
Mine MLG ports are bugless

And that's your problem, HTC DESIRE 310. Not everyone is like you, not everyone have everything like you. And lol you are not speaking fluidly English.
If you don't want contribute this conversation, please step aside.
Thanks MaRtYy01 for advices. Few hours back I've refreshed my bug reports. Data and gps problems are gone, probably faulty flash or cause of not wiping.
And thanks for correcting me, as you can see I'm still little bit confused Will look it up tomorrow, now is bed time.

No longer able to boot my Note 2 into recovery mode

1. I started with fully working Samsung Galaxy Note 2 GT-N7100 (Rooted)
2. I'm a newbie to flashing ROM, and read numerous articles to build awareness (and have never used a forum before - so please be gentle!)
3. Installed ClockworkMod Recovery using "ROM Manager"
4. Flashed Slim6 (Slim-6.0.1.alpha.0.1-UNOFFICIAL-20160522-1030) ROM, then Gapps, then re-booted and all OK (Note2 seemed to work fine)
5. Kernel is now3.0.101-Haxynox
6. Spotted (and surprised) that Note 2 no longer rooted (and in particular, want to use Titanium Backup)
7. So, flashed CWM6-root-note2.tar using ODIN, resulting in "Pass"
8. Note2 still not Rooted, and suspect that I should have flashed SuperSu after Slim6 ROM and before Gapps
9. So, tried to reboot to ClockworkMod reccovery using "ROM Manager" but hangs. Tried using VOL+ and HOME and POWER (many times, and for different intervals) but see Samsung logo followed by some "stripes" on the screen (rather like the horizontal hold needs to be adjusted for those that are old enough to remember such things!), but it will not boot into recovery mode.
10. In addition, Odin no longer appears to see the Note2
11. Note2 will boot conventionally, but I'm extremely keen not to have to live without rooting and flashing capability
12. I've searched hard for hints for this particular issue, but would really appreciate some advice, at least so that I don't make my beautiful Note2 any worse (and hope I've not missed any posts that I should have spotted!).
13. Please let me know if I've missed any key information.
Thanks in advance.

Flash the tar version of TWRP for your phone using Odin. You can root by flashing supersu from TWRP.
CWM is very outdated and cannot be used to flash current custom ROMSs.

Many thanks, I've moved over to TWRP and it seems much better.
I also tried to find a more "suitable" (reliable) ROM and chose Resolution Remix, especially as services kept stopping on Slim6.
So now I can get to recovery mode, but still I have issues. Mainly...
a) I've so far failed to flash a compatible Gapps file
b) I've flashed supersu and busybox (Root_SuperSU.0.98-Busybox.1.20.2-signed.zip) but root is still not available. Sometimes I see a "Grant" prompt but it hangs for ages when I grant. The SuperSU app can be seen, but is not responsive. Titanium Backup responds eventually to confirm that Root is not available.
c) Downloading from the Playstore is problematic (sometime very slow to download, usually extremely slow to install - go for a walk type of slow!)
d) Typically the pre-installed applications "stop" shortly/immediately after trying to start them (for example, "Browser", "Clock",...), but then appear after "OK"ing the Close infor box
e) Is my choice of ROM reasonable? And/or is there a ROM which has ROOT "baked in"? (Or, should I go back to JellyBean as being more suitable for a Note2?)
f) Is there some "fine tuning" to the flash process that I need to learn about?
Any hints/tips would be welcome, and many thanks for your initial suggestion to move to TWRP

Is the ROM pre-rooted? If yes, don't flash supersu.
You performed a full wipe, including data, before flashing the ROM?
Phone is running these latest bootloader and modem?
Various versions of gapps are here and flash there version that matches your ROM and processor: http://opengapps.org

Many thanks for your further questions/prompts...
a) Yes, I believe I had done a full wipe before flashing, but haven't touched bootloader and modem so they may well be "old"
b) More reading suggests that Cyanogenmod 13 is a very popular ROM, so flashed this with TWRP
c) Found that with this ROM there were no issues when flahsing openGapps
d) Eventually discovered/realised that CM13 is pre-rooted (but has to be enabled in Settings) and that flashing supersu was causing problems
So, with the benefit of hindsight, if I'd used TWRP/CM13/OpenGapps without flashing supersu, it would have been straightforward! I've certainly learned a lot and you supporting questions have led me to what seems to be a nice, stable implementation of Marshmallow - thanks again.
I'm still looking for a quick/easy way to take a screenshot (just used a palm-swipe before), and a free "real" FM radio, but pretty much everything else works.
Great!!!

Glad you got the phone working on CM. We're all here to help and learn from each other.
Last time I looked, which was a while ago, there was no custom AOSP or CM rom that supported radio functions. If you want the FM radio, look into custom ROMs based on a stock Samsung kernel.

[V2][Update][Root][G955U]PartCyborgRom - SamFail Rooted/Debloated/Audio/More

SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G955U/W, Bootloader Revisions 1, 2, 3​
Updates
NOW Supporting Bootloader V3!
I am happy to announce that BL version 3 phones are now supported by PartCyborgRom!
Just download the Version 3 BL further down in this post (after reading everything in between!) and use it in place of the normal BL Part2 file.
NOTICE: Rooting Process Steps Updated!
Enough people are coming from later bootloader revisions that have some extra protections that I updated the process to use an additional step. Many of you have used this step already at my suggestion when your AP flash was failing with Auth Error without a reboot to Upload.
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G955USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G955UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G955U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G955UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4A) Open Comsy Odin and Reboot into Download mode. Add Only the BL Part2.tar.md5 file. Go to the options tab and remove the checkbox next to "Auto-Reboot". Do not check any additional checkboxes and leave the other ones alone. Connect your phone and Start. Odin will flash the BL file to your device and will say PASS, but will just sit in download mode (because we turned off auto-reboot!). This makes the next part a little easier...
4B) Reset Comsy Odin and use the "three button salute" on your device to Reboot back Download mode. This time only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device stays in Download Mode:
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have likely suffered from the usb3 corruption
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and once again add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Do not change any of the options checkboxes, thus leaving the checkboxes checked for "F Reset Time" and "Auto Reboot". Click "Start" and flash the BL (part 2) to your device.
Note: Flashing BL twice is necessary as some newer stock BLs have patched the Root method we use, but the Combo Factory firmware is still vulnerable. In other words, the SamFail nickname continues to be prolific :good: :good:
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.​
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10

Downloads
BQL1 (G955U and G955W)
AP_PartCyborgRom_G955U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G955U_BQL1.Part2.zip
[Alternate Mirror]
NEW: Bootloader V3 Support!
BL_PartCyborgRom_G955U_U3BQL1_R5.zip
[Alternate Mirror]
Other Downloads
Do Not install any of these unless you are running an older version.
BQL1 has all of these mods already!
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
​

Previous Versions
SM-G955USQU2BQK5
AP and BL Parts 1 & 2
AP_PartCyborgRom-G955USQU2BQK5_Part1.zip
BL_PartCyborgRom-G955USQU2BQK5_Part2.zip
SM-G955USQU1AQK3
AP and BL Parts 1 & 2
AP_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part2.zip
​

One more

@partcyborg , nice work and thank you for posting your PCB ROM for S8+!

Thank you @partcyborg!

You ARE the f'ing man!!!!! THANK YOU!!!
And to the peeps whining, over the past 5+ months that there wasn't a custom ROM available for this phone, I would hope to see you hitting the 'Thanks' button.

You said you would do it, and you did it! Thanks for doing this for us! Very excited to give this a try.

Can't wait to get home and try this out!!!!!!

Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?

ok so i have wiped everything before install and then followed install instructions all the way....
scratch that a reboot fixed the rotation issue

Wow ! I watched you actually say you wouldn't mind doing a rom for us and you did do it. AMAZING. I gotta try this when i get home ! time to back everything up lolol. Do you know if xposed works for this ? and also can we change the font with iFont now since you managed to? Once again thanks for port !

Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Sent from my SM-G955U using Tapatalk

matthewd769 said:
Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?
Click to expand...
Click to collapse
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work

partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
Any ideas?
Sent from my SM-G955U using Tapatalk

partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
thanks dog ... appreciate the hard work and answer .... i might start coughing and leave early

Goddly said:
Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Click to expand...
Click to collapse
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people

Stovall Family said:
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people
Click to expand...
Click to collapse
Factory restore?
Sent from my SM-G955U using Tapatalk

Goddly said:
Factory restore?
Click to expand...
Click to collapse
Factory restore through stock recovery.

Goddly said:
Any ideas?
Click to expand...
Click to collapse
Can you fire up PreConfig and try and set your csc?
Also try flashing 1 more time. If you have a usb2 port absolutely use that. Several people have had major issues with flashing on usb3.0 ports and every one whose had a usb2 port to try it's worked flawless after. This rom will fail when stock doesn't because of its size. In order for samfail to work we have to use a raw image not a sparse one like in the stock AP. This means the image is the full size of the partition despite not being completely full