{
"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"
}
Android Flasher needs you!
Are you an experienced Android user?
We need people to update the Pro database for each device, this means the radio/bootloader/recovery for each device. PM me for more details.
This also includes HTC Magic, Samsung Galaxy S and S II, Motorola Atrix, and Sony Xperia Play.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
S-OFF is essential with ENG hboot
Features:
Multiple flashes without closing the application.
Deletes all used files leaving you with nothing more than what you had to start with.
Fully automatic, users only need to create a splash image or locate a recovery, hboot, or radio img.
Unified interface.
Coded entirely in C#
Now supports BMP, PNG, and JPEG images. Not just BMP like NBIMG.
Usable on your Desire, Desire Z, Desire HD, EVO 4g, EVO 3D, Desire S, Incredible S, Thunderbolt or Sensation.
The application checks image dimensions and the file sizes of splash images to prevent any errors.
Click to expand...
Click to collapse
Requirements for use:
USB debugging enabled.
HTC and Fastboot/Hboot drivers must be installed.
Windows with .net 4.0
Splash image, recovery img, hboot img or radio img. (not required for donate version)
Click to expand...
Click to collapse
What the application does:
This application flashes the specific parts of your device, ie. Bootloader, Recovery, Splash screen, and Radio.
It has taken many hours and much extensive research and testing on multiple devices to make a straightforward, efficient and reliable program to offer you the freedom in device customisation you are otherwise denied.
The app allows you to quickly customise your device in a way that is simple and alot goes on behind the scenes to guarantee you don't get caught with error messages.
The splash screen is the image before the boot animation, (by default the white HTC logo.) With this application you can change it in under a minute.
Click to expand...
Click to collapse
Credits to SA7039 for assistance and Google for fastboot, adb and dlls.
Android Flasher Splash Database Upload Tool
(like imageshack but just for splash screens)
http://deltaxent.com.au/af/upload.form.php
Search the DB using:
http://deltaxent.com.au/sa7039/Sorter/view.php
Got problems? Want to request features? Submit them here.
Click to expand...
Click to collapse
Changelog:
Code:
2.2.0.5
Donate - Added auto-login.
Donate - Added another "Download Archive" button for convienence.
Donate - Fixed a few exceptions.
Donate - Fixed some downloads.
Donate - Auto sort list by version.
Donate - Bigger image displayed on hover of image/splash.
Reworked flashing selection page.
Reworked about page.
Reduced timers from 7 to 2.
MessageBoxes for errors.
MessageBoxes on detection of S-ON and non-ENG bootloader.
Fixed backgroundworker on the flashing process.
Added "Errors/Requests" menu item under help.
Cleaned up code.
Added news page.
2.2.0.0
Added other devices for ALL other devices.
Added progress bar for initial downloads.
Added Wildfire S support.
All images are now resized for your device :).
Donate - Added download browser, contains an archive of radios, recoveries, hboots and splashes.
Donate - Official release.
2.1.0.5
Added: EVO 3D, Incredible S, Desire S and Thunderbolt.
Added recent device display as the first button.
Updated pictures to be higher quality.
Fixed redo progress bug.
Added WiMax
2.1.0.1
Fixed a device bug that affected everything except for the Desire and Sensation.
2.1
Fixed checkboxes
Added 'Already in fastboot' button
Rewrote logging
Fixed donate button ;)
Added update notifications
Auto downloads data folder
Added path conversion to unicode, should help with localisation.
Added Desire HD and EVO 4g support.
Added Device list pages - moved DHD to second page with EVO 4G.
2.0.5
MsgBox for invalid splash image dimensions
Image displays in the center when selected
When you unselect a checkbox, it says 'No file selected.'
Menu button added in the file menu
Label changed Z/HD
Added 'Donate' button ;)
Now verifies that the splash img file is the correct size for flashing
2.0
Brand new, recoded entirely from the ground up.
Supports multiple devices, and image extensions.
Please consider donating .
New!
With Download Browser for all supported devices:
Click here!
Click to expand...
Click to collapse
How is the bmp supposed to be configured?
BMP should be configured how ever you like. The program converts it from whatever configuration you saved it as. I personally use:
"File format: Windows"
"Depth: 24bit"
Wow...interesting...sounds good
Thanks..with kind regards..Alex
so now we can use our own boot pics right?
dosent work for me, just sits at waiting for device
hmm tried it with an .jpg
saved and renamed it as written to splash1.bmp but it didnt worked.
i have got the android now on a skateboard as bootscreen.
weird haha
you have to save the image as bmp, not jpg.
Cool, one minute before s-off and there is a thread to change the first boot screen ... will try it now ... black boot screen = save batt
WHAT RESOLUTION IS NEEDED? 800x480 or 392x65?
pa.pn2 said:
so now we can use our own boot pics right?
Click to expand...
Click to collapse
Yep, it does. I've got my own .
AndroHero said:
dosent work for me, just sits at waiting for device
Click to expand...
Click to collapse
Have you connected your phone in fastboot mode?
philJ said:
Cool, one minute before s-off and there is a thread to change the first boot screen ... will try it now ... black boot screen = save batt
Click to expand...
Click to collapse
Yeah, will help on reboots.
I'll bring out my next one which puts your device in fastboot flashes and then reboot for you soon.
danward said:
Have you connected your phone in fastboot mode?
Click to expand...
Click to collapse
it says hboot in the op sorry i will try again
i saved a .jpg on my pc from the internet
opened with photoshop and saved it as an .bmp again correct?
renamed it and placed it in the folder...
AndroHero said:
it says hboot in the op sorry i will try again
Click to expand...
Click to collapse
I'm testing the auto reboot version now. It'll be up soon. All you gotta do is have it connected to your comp with debugging on.
danward said:
I'm testing the auto reboot version now. It'll be up soon. All you gotta do is have it connected to your comp with debugging on.
Click to expand...
Click to collapse
Fine ... what res is needed for the pics?
philJ said:
Fine ... what res is needed for the pics?
Click to expand...
Click to collapse
It's up. Umm, it resizes it. But optimal is 480x800.
EDIT: 480x800 is required. Sorry guys.
Doesn't work for me. Created a bmp, renamed it to splash1 and ran the bat while phone was in fastboot mode.
This is essentially same as doing it via cmd using "fastboot flash splash1 *image*" ?
But im a bit confused as to what the image needs to be. Seen .nb's, nb0's, .img's and .rgb565's.
when i flash it, the image looks like its 4 identical images layered ontop of eachother
it changes my splash screen to "three androids playing skateboards", but I don't even know where this image comes from.
Jgruar said:
Doesn't work for me. Created a bmp, renamed it to splash1 and ran the bat while phone was in fastboot mode.
This is essentially same as doing it via cmd using "fastboot flash splash1 *image*" ?
But im a bit confused as to what the image needs to be. Seen .nb's, nb0's, .img's and .rgb565's.
Click to expand...
Click to collapse
Yeah, thats the basic thing. IMG files are what HTC use. I know they are supported. If it doesn't work, try the new one i just uploaded. I know it works on mine and a few others.
AndroHero said:
when i flash it, the image looks like its 4 identical images layered ontop of eachother
Click to expand...
Click to collapse
Check your BMP file. Save it again and reconvert it after. What did you use to make the BMP file?
ive solved my problem, its because it dosent resize it for you, make sure the dimentions of the .bmp are 480x800 and all will be fine
Related
Development stopped
Although this mod had great success with several thousands of different users, just as everything else, it has been surpassed by time. Since it was first introduced, many competent devs made great changes to the Gallery3D's functions. These changes made it hard to keep up with the latest developments without introducing bugs, and due to the lack of time, I might have neglected it sometimes. Luckily, this mod has already been in CyanogenMod for a while, meaning all of it's users got the latest and greatest of this mod, as well as others. So instead of patching the Gallery manually, check out the latest version of CyanogenMod.
If you want to use this in other custom ROMs, either point your devs to this post and ask them to compile in the relevant changes from the github link, or extract the apk from the latest CyanogenMod since it will contain many more fixes and performance improvements that have been added in the last few months.
Thanks to all who contributed to this project!
__________________
UPDATE 12.2.2011.
Well, thanks to user de_MarK, the black borders problem has now been fixed! Should be working on most devices without any problems.
Thanks again!
[Comparison]
Here is a demo of how this will improve your images if you don't touch VMMaxHeapSize. If you do increase the former, expect even better results.
I found an image of a transmitter on top of a building to be best for comparison since it has very high contrast and sharp lines. Screenshots were taken off my Desire using DDMS.
http://img576.imageshack.us/img576/9451/gallery3dpatchdemo.png
Notice how the transmitter and power cables look differently.
The original photo (5mpx) is here:
http://img838.imageshack.us/img838/6189/imag0106z.jpg
[Will it work?]
Reported to work on various devices and various ROMs. If, by any chance, this doesn't work on your phone, report here.
User Airwalker82 reported that even 12MPx images are loaded without problems. Thanks for that!
[Installation]
If your ROM didn't come with Gallery3D preinstalled:
Uninstall any versions of Gallery3D present and install the .apk.
If your ROM came with Gallery3D or the above method fails:
You will need to remove the existing Gallery3D.apk in /system/app. You can use any method you prefer for this, however, those owning a Desire will have to do it from recovery through ADB shell.
Code:
Step by step:
1) Connect the phone to the PC
2) Open a Command Prompt (WinKey+R->type 'cmd'->enter)
3) Using the command 'cd', navigate to the directory where the Android SDK is installed
4) Use 'cd' again to enter the 'tools' directory
5) Type 'adb reboot recovery'
6) The phone should restart
7) Once in recovery, type 'adb shell' to get the shell interface
8) Now type 'rm -rf /system/app/Gallery3D.*'
9) Disconnect and reboot the phone
Now simply install the .apk.
[Source]
All source code (with compiled downloads) is available on github at the following URL:
http://github.com/mrPjer/android_packages_apps_Gallery3D
[Other/Bugs]
Please post here any bugs, errors or words of praise
Gallery3Dr.apk
Only install this one on devices that have problem with rotation (such as the HTC Hero).
Number22 said:
'sup guys!
[You can skip the text, download and demo are below]
I don't know how many of you have noticed, but, although beautiful, Gallery3D doesn't really load images at their full resolution, unlike the default Sense Gallery. Infact, the difference is quite dramatic on my phone. So, today I decided to get the sources and see if something can be done. And indeed it can!
So I present to you my patched version of Gallery 3D!
Although I couldn't manage to get it to load full res images, the difference is quite noticeable (but it isn't anything like Sense )
Anyhow, what's going on here? As some of you may or may not know, Android has a VERY limited amount of memory allocated for bitmaps which are necessary for showing images. For an example, even with the best phones today, you can't load a 5mpx image as a bitmap. That's why Gallery3D downscales images when loading them. The problem is, it doesn't upscale them when zooming in! So, what I did is I downloaded the latest sources from AOSP and changed the downscaling algorithm a bit so the images are downscaled 2x less (which equals to 4x more detail). Now, since I only have my Desire at hand, I couldn't really test this properly, however, this should experience no problems with images that are 5mpx (that's what I was able to test).
I would, however, like you to try and load some larger images (something of a DSLR, like 10mpx) and report on how it works.
[Comparison]
I found an image of a transmitter on top of a building to be best for comparison since it has very high contrast and sharp lines. Screenshots were taken off my Desire using DDMS.
http://img576.imageshack.us/img576/9451/gallery3dpatchdemo.png
Notice how the transmitter and power cables look differently.
The original photo (5mpx) is here:
http://img838.imageshack.us/img838/6189/imag0106z.jpg
[INSTALLATION] Uninstall any previous versions and install the .apk. This was built for Android 2.2 off AOSP
Works on official FroYo. Report how it works on other ROMs.
[OTHER]
Please post here any bugs, errors or words of praise
Oh yeah, I removed some resources that the Desire doesn't use, so it's somewhat smaller in size
Click to expand...
Click to collapse
Good work =)
Number22 said:
[INSTALLATION] Uninstall any previous versions and install the .apk.
Click to expand...
Click to collapse
Yeah! Thanks for that...
we need to uninstall the old gallery via adb i assume?
Works great thx!
x01a4 said:
we need to uninstall the old gallery via adb i assume?
Click to expand...
Click to collapse
Can't say for sure. It wouldn't install for me over the default one I had installed. However, if it came with your ROM, you just might be able to overwrite it. Try it and report back
14.1 mpx images look great in the thumbs! A bit slow on initial load, but seems ok after that.
Does anyone know of a screenshot application that can run on non-rooted devices? I'd like to take a screenshot so I can show how the 14.1 mpx thumbs show up like.
One thing though - It picks up album art, and as a result I have numerout galleries showing that are just an artist/album folder. Is there a way to include options that allow you to select which albums to show/hide?
thanks for the great work!
Works great on defrost 2.6a rom!
Nice dude !
Airwalker82 said:
14.1 mpx images look great in the thumbs! A bit slow on initial load, but seems ok after that.
Click to expand...
Click to collapse
That's good to hear
Airwalker82 said:
Does anyone know of a screenshot application that can run on non-rooted devices? I'd like to take a screenshot so I can show how the 14.1 mpx thumbs show up like.
Click to expand...
Click to collapse
DDMS from the Android SDK should work on non-rooted devices. (Nice guide here: http://www.androidcentral.com/taking-screenshots-without-root) Just remember, if you are on Linux, you need to start it as root.
Airwalker82 said:
One thing though - It picks up album art, and as a result I have numerout galleries showing that are just an artist/album folder. Is there a way to include options that allow you to select which albums to show/hide?
Click to expand...
Click to collapse
Hmm, well, no way of including the show/hide without some serious rewriting. However, if the album art is in it's separate folder, you could try the .nomedia trick (just be careful and make sure the folder is empty before applying .nomedia). If it isn't, the best option might be to just encode art directly into the mp3 tag. Some of my MP3s have album art in their tags so it doesn't show up in Gallery.
This isn't a problem of the app itself, more of the Android Content Provider for media which scans all folders for images, videos and songs.
Airwalker82 said:
thanks for the great work!
Click to expand...
Click to collapse
Np
patachon33 said:
Works great on defrost 2.6a rom!
Click to expand...
Click to collapse
Nice to hear that
i have made a zip file from this so you can install this via the recovery shell, it will overwrite the original "Gallery3D.apk" file in /system/app
tested and confirmed working in OpenDesire 3.1.0
mikel.1969 said:
i have made a zip file from this so you can install this via the recovery shell, it will overwrite the original "Gallery3D.apk" file in /system/app
tested and confirmed working in OpenDesire 3.1.0
Click to expand...
Click to collapse
Thanks, I linked it in the first post.
Thanks for the advice - Glad to finally know how to take screenshots! =)
As promised, here are some screenshots of how some of my pictures from my Canon Ixus 210 show up in the gallery. The last one is just of a few hires pictures I have.
They're pretty clear!
{
"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"
}
i just tried flashing it the zip and it said verification failed.... so how else would i go about installing this now? i tried the apk and that failed too ...
Runnin opendesire 3.1.1
it says...
E:Wrong Digest :
META-INF/com/google/android/update-script
E:Verification Failed
Installation aborted.
Turn off verification in recovery...
Easy as 123
i have no idea how to do that, and didnt even know you could, were about could i find it?
I use the the R5 Desire recovery windows.bat if that makes any difference i dunno lol
360nitrous said:
i have no idea how to do that, and didnt even know you could, were about could i find it?
I use the the R5 Desire recovery windows.bat if that makes any difference i dunno lol
Click to expand...
Click to collapse
you should use the recovery mode in "ROM Manager", this makes it a little easier for you.
http://www.appbrain.com/app/com.koushikdutta.rommanager
Install the apk from market, than install the "update.zip" from inside "ROM Manager", boot into recovery, at the red triangle sign press & hold the UP volume button than press power again, than choose "Apply update.zip from sdcard" press power again and your in the recovery mode as in "R5 Desire" but without the risk of bricking your device.
thx for the great patch
and a request, could you speedup the photo loading speed? i noticed the loading speed is slow even if i open a 800*480 jpeg file (yes, original Gallery3D had such issue too), I use sandisk class2 16G sdhc tf
mikel.1969 said:
you should use the recovery mode in "ROM Manager", this makes it a little easier for you.
http://www.appbrain.com/app/com.koushikdutta.rommanager
Install the apk from market, than install the "update.zip" from inside "ROM Manager", boot into recovery, at the red triangle sign press & hold the UP volume button than press power again, than choose "Apply update.zip from sdcard" press power again and your in the recovery mode as in "R5 Desire" but without the risk of bricking your device.
Click to expand...
Click to collapse
thanks man that worked a treat, i dunno why i never tried usin rom manager before, makes everythin a little more than easy
This mod is really nice too, makes it a lot smoother when zooming in on the photo's an i noticed the loading times is a lil quicker too!
could you speedup the photo loading speed?
Click to expand...
Click to collapse
There's nothing much that can be done since the app uses standard Android APIs for loading images. However, I do beleive that the speed of your SD (class 2 is the slowest) plays a major role in the speed of the loading process.
hello, thanks for this mod!, i have just installed and I have lost my picasa online albums!!!. Can someone help me to fix it?
or at least how to restore the original froyo gallery (i have flashed the .zip file with recovery)
Thanks
Number22 said:
There's nothing much that can be done since the app uses standard Android APIs for loading images. However, I do beleive that the speed of your SD (class 2 is the slowest) plays a major role in the speed of the loading process.
Click to expand...
Click to collapse
i agree class 2 is slowest, but sandisk class 2 sdhc is not slow, i get 18M/s read and 7M/s write speed with card reader.
Check Post #2 for plugins for your device!
Description
RegawMOD Bootloader Customizer is a utility for Windows that allows the
user to create a custom HTC firmware zip containing a custom bootloader image.
Your device has to be S-OFF for this to work!
If you are looking to create a plugin for your device so you can use this program go HERE
With this program, you are able to edit the *** UNLOCKED *** text on the top
to whatever you want it to say, change the S-OFF to S-ON, change the bootloader's version number,
update the bootloader's date and time stamp, and hide/customize the splash screen disclaimer.
Choosing the "Stock" look option automatically sets your banner to *** LOCKED ***,
changes S-OFF to S-ON and hides the HTC Development Splash Screen Disclaimer.
This program will NOT flash the zip for you, but it will allow you to save it to your computer to let you flash the zip yourself.
The process (flashing a new bootloader) is dangerous and may possibly brick your device if done incorrectly. You have been warned.
Just remember, anyone can make a plugin, and not everyone can be trusted.
Make SURE you only flash zips made from plugins by developers you trust!
Featured on the portal (Thanks PoorCollegeGuy!)
Screenshots
Requirements
Windows w/ .NET 4.0 - Get .NET 4.0
HTC Device that is either S-OFF or allows flashing of unsigned hboot
Usage
Download the plugin for your device (See post #2 for list of plugins)
Place the plugin in the same directory as the 'RegawMOD Bootloader Customizer.exe' on your computer
You can have as many plugins in the directory at the same time as you'd like
Run the 'RegawMOD Bootloader Customizer.exe'.
Begin customizing be choosing "Stock", or customize your own look and feel using the text box at the top and options below.
Press "Create Zip" to make the firmware zip
How To Flash A firmware zip (Devices with a removable sdcard)
Place the zip on the root of your external sdcard. (Copy it right onto your sdcard, not in any folder)
Reboot the phone into the bootloader by either:
Powering off your phone completely, then hold Volume-Down and Power until the phone boots into the bootloader
If you have the android sdk set up, type 'adb reboot-bootloader'
Use my RegawMOD Rebooter
Then select the menu option "Bootloader" and press the power button.
If you rebooted the manual way (Volume-Down + Power) You should already be at this menu
It will load the zip from your sdcard and ask you to accept the flash.
Press Volume Up to flash (On most devices, but could be a different button)
Once prompted, press Power to reboot (On most devices, but could be a different button)
Pro-Tip #1 (thanks dsEVOlve): Remove the firmware zip from your sdcard so it doesn't load next time you enter the bootloader.
How To Flash A firmware zip (Devices without a removable sdcard)
Reboot the phone into the bootloader by either:
Powering off your phone completely, then hold Volume-Down and Power until the phone boots into the bootloader
If you have the android sdk set up, type 'adb reboot-bootloader'
Use my RegawMOD Rebooter
Connect your phone to the computer (if it isn't already) and issue the fastboot command
Code:
fastboot oem rebootRUU
To flash the zip, issue the fastboot command
Code:
fastboot flash zip <[SIZE=2]YourZipName>.zip[/SIZE]
The device's progress bar may not be complete, but when the fastboot command says it's complete, issue the fastboot command
Code:
fastboot reboot
Warning
This program/created firmware zip comes with NO WARRANTY (express or implied), and NO GUARANTEE OF FITNESS for any particular task. I have made every effort I can to make this a safe process for users however the author disclaims any liability for damage to your phone or other materials or devices used during this process. The entire risk of flashing the created PJ75IMG.zip lies with you, the user. By creating and/or flashing the firmware zip, you acknowledge and accept that the author is not liable for any loss, material or otherwise howsoever caused.
Changelog
Version 2.1 | 10.09.13
Add Verizon HTC One support
Version 2.2.2 | 06.10.13
Updated to support HTC One varieties
Version 2.2 | 02.18.13
Added support for HTC One series (X, XL, V...) and Droid DNA
Download Latest Release
RegawMOD Bootloader Customizer
Download Info
RegawMOD Bootloader Customizer.exe MD5 - 9d642f7502fe0953b95e9c2ea578e1f1
Source Code
Github
List of user-made plugins:
HTC Evo 4G LTE - regaw_leinad
Hboot 1.12.0000
HTC Evo 4G LTE - liamstears
Stock Hboot 2.09
DirtyRacun Hboot 2.09
HTC One (Sprint) - eg1122
Stock Hboot 1.44.0000
HTC One (AT&T) - eg1122
Stock Hboot 1.44.0000
HTC One XL - liamstears
Hboot 2.14
Hboot 1.14
Hboot 1.09
Droid DNA - liamstears
ENG Hboot 1.39.2000
Stock Hboot 1.33
OTA Hboot 1.33
HTC One S - liamstears
Hboot 2.15
ENG Hboot 1.14.0004
Hboot 1.13
Hboot 1.06
HTC Vivid 4G - cruzin_cruzing
Hboot 1.85.0025
HTC Droid Incredible 4G LTE Thread - junkmail9
PLEASE read the entire OP. I don't want to sit here answering questions that are already answered in the OP.
And be sure to use the 'Thanks' button
So will using this new version/tool to create a new zip put the custom message back on the boot screen that disappeared after the 1.22 update? I have tried re-applying my zips from the original bootloader customizer for LTEvo after 1.22 and I only get the custom message when rebooting into Recovery. Just wondering if you found the fix for that yet.
Sent from my Meanie ICS LTEvo
Stock look option lists bootloader version as 1.12.2222 instead of 0000.
long_tall_texan said:
So will using this new version/tool to create a new zip put the custom message back on the boot screen that disappeared after the 1.22 update? I have tried re-applying my zips from the original bootloader customizer for LTEvo after 1.22 and I only get the custom message when rebooting into Recovery. Just wondering if you found the fix for that yet.
Sent from my Meanie ICS LTEvo
Click to expand...
Click to collapse
I think that change was in the kernel (or something else related to the boot.img), not the bootloader, so no, this won't "fix" that.
Also, great work on getting the purple banner background to display only behind actual banner characters even when there's less than 16 of them. Is it possible to get a post-OTA stock look option and a way to edit the entire HBOOT version number? Got a bit of a cognitive dissonance going between HBOOT 1.12.0000 / old build date and 1.05 radio.
I have my test Unit HTC HD2, is it supported?
i think its not,
ill just try another phone here...
great work man. really hard working
OT:
with your lib i created a drop and drop apk installer
great man
thanks
I made a .dll plugin file for the HTC Sensation with the help of cruzin_cloud. It is for the Sensation, Sensation XE, and Sensation 4g using Hboot 1.27.1100 and it will change the Hboot to 1.27.1111 unless you choose for it not to when making the .zip. I used the Hboot from unlimited.io. If the regaw_leinad updates his tool i will update the .dll file as needed. Thanks to regaw_leinad for this awesome tool. Also if regaw_leinad does not mind I will post a thread in the Sensation Android Development Forum for this.
Edit:
I thought I should also add that you have to have the 1.27.1100 Hboot version to use this. It is do th how the RegawMOD Bootloader Customizer works. I will make more but I will have yo flash different Hboots to my device to text so it might be a day or two befor I have a couple more ready
Thread in the Sensation Development forum.
HTC Sensation Download
Great work going to give it a try
Has anyone been able to create a profle for the HTC Incredible S (Vivo)
small bug found
There is a small bug in this DLL version of the customizer (as opposed to the Evo 4G LTE single EXE version in another thread)... if you pick the "stock" look and generate the PJ75IMG.zip file, you get a MessageBox informing you of the things that will change in the bootloader look. One of them is the hboot version will be set to "0000". However, with the latest LazyPanda hboot 1.12.2222 - this change does not take place when the zip is flashed; it remains 1.12.2222.
I noticed that when you click the stock radio button in the application, it defaults some of the checkboxes in the lower half and at the same time disables that group box. However, if you look closely, the boot "Version #" is not checked. Perhaps this is why the version number is not set. If I go the custom route and make the changes myself, it indeed changes the version number to "0000" when I put that in.
Anyone else noticing this behavior?
PillowMetal said:
Anyone else noticing this behavior?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=29100365&postcount=5
Yeah, I'll get to this in a bit. I am updating the plugin interface for the developers.
Is it trivial to update the first 3 digits of HBOOT version along with the last 4? Now that 1.19 is out, it would be nice to be able to display the latest version number to match the latest radios.
Also, is there a way to update the build date/time to something specific? I see the option in the Customizer menu, but no way to input the date/time.
Kisakuku said:
Is it trivial to update the first 3 digits of HBOOT version along with the last 4? Now that 1.19 is out, it would be nice to be able to display the latest version number to match the latest radios.
Also, is there a way to update the build date/time to something specific? I see the option in the Customizer menu, but no way to input the date/time.
Click to expand...
Click to collapse
If you just want an updated stock-looking HBOOT, I have that, and can post it.
You can update pretty much all that stuff with a simple hex editor.
Captain_Throwback said:
If you just want an updated stock-looking HBOOT, I have that, and can post it.
You can update pretty much all that stuff with a simple hex editor.
Click to expand...
Click to collapse
Fair enough, I just really like the whole concept of this tool, so I was trying to coax Regaw_leinad out of hiding.
If you do have the latest Lazy Panda HBOOT 1.12.2222 (with fastboot flash enabled) edited to look like 1.19 (with correct spacing/purple background for "*** LOCKED ***"), I'd love that. BTW, any recommendations for a bug-free hex editor under Win7? Also, do you have a pic of a stock HBOOT 1.19 bootloader? The perfectionist in me wants to get the correct build date/time.
And the last question: is the displaying of CID when S-OFF the last thing that still needs to be fixed in order to have a completely stock-looking bootloader screen?
Kisakuku said:
Fair enough, I just really like the whole concept of this tool, so I was trying to coax Regaw_leinad out of hiding.
If you do have the latest Lazy Panda HBOOT 1.12.2222 (with fastboot flash enabled) edited to look like 1.19 (with correct spacing/purple background for "*** LOCKED ***"), I'd love that. BTW, any recommendations for a bug-free hex editor under Win7? Also, do you have a pic of a stock HBOOT 1.19 bootloader? The perfectionist in me wants to get the correct build date/time.
And the last question: is the displaying of CID when S-OFF the last thing that still needs to be fixed in order to have a completely stock-looking bootloader screen?
Click to expand...
Click to collapse
Here's a picture of my current bootloader:
{
"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"
}
Of course the date has been updated to match the new version - I am also a perfectionist .
And yes, the only thing keeping this from looking exactly the same as stock is the CID line (which I assume, is by design).
Captain_Throwback said:
Here's a picture of my current bootloader:
Of course the date has been updated to match the new version - I am also a perfectionist .
And yes, the only thing keeping this from looking exactly the same as stock is the CID line (which I assume, is by design).
Click to expand...
Click to collapse
Ah, nice to meet a fellow perfectionist. Thanks for the pic and the clarification, would appreciate a download link and a hex editor recommendation.
Kisakuku said:
Ah, nice to meet a fellow perfectionist. Thanks for the pic and the clarification, would appreciate a download link and a hex editor recommendation.
Click to expand...
Click to collapse
Attached is the fastboot-enabled HBOOT from the LazyPanda site, modded to appear as 1.19.0000, with build date updated, and red dev text removed.
As far as a hex editor goes, I use the Free Hex Editor Neo on Windows, and HexEditor on my device.
Captain_Throwback said:
Attached is the fastboot-enabled HBOOT from the LazyPanda site, modded to appear as 1.19.0000, with build date updated, and red dev text removed.
As far as a hex editor goes, I use the Free Hex Editor Neo on Windows, and HexEditor on my device.
Click to expand...
Click to collapse
Much appreciated and thrice thanked.
I had broken the screen on the Nexus 4 and after a daylong nightmare of pursuading LG and Google that my phone should be repaired in my native USA rather than Australia (the phone I got from Google had a model number for the international market rather than the US market), they finally let me send it in to a US facility to get it repaired. I now received the phone back with the screen repaired (took exactly 14 days and $140).
But when I start the phone it goes into a strange debug screen. After pressing the power button for a some time I get to another, more standard looking screen. But the buttons on the bottom are completely missing (no home, return, or widgets buttons). From there I can only access the settings widget in the top right corner of the screen. When I go into settings I get the following info:
Model Number: Full Jellybean on Mako
Android version: 4.2
Build number:
full_mako-userdebug 4.2 LGEP19
eng.seungju24.choi.20121114.105751 test-keys
Also lots of debug apps seem to be installed, although I have not managed to get to the main screen to actually execute anything.
It seems that LG has replaced the standard OS with another (maybe debug or testing) build that does not work properly on the final consumer
product.
Does anyone have any suggestions? I am concerned that if I try to deal with LG I will be without a phone for another 2 weeks, and based on the
experiences so far I am not convinced that I will not have any further problems.
Thanks!
RWTX
I would suggest you download the factory android 4.2.1 image and flash that. That way you'll have your android os setup like brand new.
1. The firmware(s) can be found on this page :http://forum.xda-developers.com/showthread.php?t=1745781
2. Instructions on how to flash stuff to and on your phone can be found anywhere, but I prefer to use this for it's simplicity and step by step instructions: http://forum.xda-developers.com/showthread.php?t=1766475
On the screenshot posted by the OP, you can also see the option to flash stock. It's pretty easy to do if you follow the instructions. Also make sure you follow the driver installation procedure in the program.
No! Please upload that firmware to the web!
Post some pictures of it. We're all curious to see what it is. This is a Dev forum anyway
Sent from my Nexus 4 using xda app-developers app
Welcome to the forum. Thread moved. Please make sure you post all questions here in Q&A in future.
Thanks
AvRS
Thanks. Can I find instructions somewhere of how to do the firmware upload?
Sent from my Nexus 10 using xda app-developers app
Here some pictures.
First view
{
"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"
}
Then moves to
Phone info screen
Sent from my Nexus 4 using xda app-developers app
upload that baseband!! :laugh: :good:
This's gonna be good ...subbed
Sent from my Nexus 4 using xda premium
daddioj said:
upload that baseband!! :laugh: :good:
Click to expand...
Click to collapse
I am totally new this. What does basedband mean?
How do I do that upload?
RWTX said:
I am totally new this. What does basedband mean?
How do I do that upload?
Click to expand...
Click to collapse
I don't know either, maybe PM one of the Devs here. If its something of value i would assume they should be glad to help.
Sent from my Nexus 4 using xda premium
Holy wow... That's the ICS boot animation! We've got something good going oh here
Subbed
Sent from my Paranoid Nexus 4 using Tapatalk²
RWTX said:
I had broken the screen on the Nexus 4 and after a daylong nightmare of pursuading LG and Google that my phone should be repaired in my native USA rather than Australia (the phone I got from Google had a model number for the international market rather than the US market), they finally let me send it in to a US facility to get it repaired. I now received the phone back with the screen repaired (took exactly 14 days and $140).
But when I start the phone it goes into a strange debug screen. After pressing the power button for a some time I get to another, more standard looking screen. But the buttons on the bottom are completely missing (no home, return, or widgets buttons). From there I can only access the settings widget in the top right corner of the screen. When I go into settings I get the following info:
Model Number: Full Jellybean on Mako
Android version: 4.2
Build number:
full_mako-userdebug 4.2 LGEP19
eng.seungju24.choi.20121114.105751 test-keys
Also lots of debug apps seem to be installed, although I have not managed to get to the main screen to actually execute anything.
It seems that LG has replaced the standard OS with another (maybe debug or testing) build that does not work properly on the final consumer
product.
Does anyone have any suggestions? I am concerned that if I try to deal with LG I will be without a phone for another 2 weeks, and based on the
experiences so far I am not convinced that I will not have any further problems.
Thanks!
RWTX
Click to expand...
Click to collapse
Dude upload this to the web before you flash back to factory. This is gold to the devs...
Edit: Lol I see u all already told him this as I read the rest of the thread. U are right kcls this is the ICS boot animation.
Using Tapatalk 2
Plz upload this we would all love to see what this is
Sent from my Nexus 4 using xda app-developers app
Someone please tell him how to do it?
I fail to see how this is "gold"? Yes it is the ICS boot animation, and possibly a different baseband, but what exactly would this achieve? We already have the easiest phone to bootloader unlock and root, what good does this do? I can see if maybe this was an HTC phone that was S-Off with an ENG hboot it would be valuable for S-Off.. but it's not..
It's a debug rom, it may contain useful debug tools from LG that arnt available in release roms.
That and some of us just like collecting "official" roms, please upload if you can OP
Worse come to worse, I'm sure there is a developer here that would pay shipping both ways, of you could hold out a week
I am curious if the phone is " Rooted" ( of course it is if it's a developer ROM) bit I would like to know what the boot loader lists.
Sent from my Nexus 4 using Tapatalk 2
Bump
Sent from my Nexus 4 using xda app-developers app
RWTX said:
I am totally new this. What does basedband mean?
How do I do that upload?
Click to expand...
Click to collapse
Someone get this man the tools to get the images of this off his phone ASAP!!
Do you have windows or OSX?
---------- Post added at 08:08 PM ---------- Previous post was at 07:56 PM ----------
Not sure if anyone knows if there's a new version of ADBRecovery or if this would still work for him. Download the Android SDK (http://developer.android.com/sdk/index.html and USB Drivers if you're in windows), then do this:
Make a nandroid backup:
1. download ADB Recovery -> ADBrecovery v6-1.zip
2. copy the content of the ZIP to your SDCARD (there should be a "recovery" folder and an "update.zip" file, you need to copy both to the root of your SDCARD)
3. download the Android SDK -> Android SDK | Android Developers
4. extract the Android SDK to a folder of your choice
5. on your phone go to "Settings -> Applications -> Development" and select "USB debugging"
6. turn off your phone and start it by holding the camera and power button (a /!\ sign should appear - if it doesn't you're doing it wrong or you have the newest bootloader and should power up the phone using the "X" key on your physical keyboard together with the power button)
7. after you get the /!\ sign press the volume up and camera button
8. from the menu select "apply update.zip" (you can move around using the d-pad and confirm your selection with the d-pad)
9. after the update.zip loads you should be at a similar screen with a bit of extra info on it
10. connect your phone to your PC using the USB cable
11. open the console on your computer (Start -> Run -> cmd)
12. navigate to where you extracted your Android SDK and then navigate to the "tools" directory inside the Android SDK dir
13. write the following commands
Code:
adb shell
nandroid-mobile.sh --backup
It should then ask you for a name for your backup. You can leave it blank or write something of your choice
14. after the backup is done, you can "exit" the adb shell and restart your phone
NOTE: If you need to restore your nandroid backup, just replace the "backup" from step 13 with "restore" and select the name of your backup.
Click to expand...
Click to collapse
Getting the baseband/radio:
Just a quick guide for those who want to extract/pull radio img file from their Nexus Phone.
So, basically, here is what you need to do.
1, conncet via adb
2, Type "su" without the "", just SU, 2 letters.
3, Allow superuser with it.
4, Type "dd if=/dev/mtd/mtd5 of=/sdcard/radio.img" without the "", just those letters in the "..."
5, It should take a few second to copy the file to your sdcard and it will mention that it is successful.
6, When it mention succesfully copied, go to your sdcard with USB MOUNT to your computer.
7, You will find a file name "radio.img"
Click to expand...
Click to collapse
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
FIRST OF ALL THANKS AND CREDITS GOES TO THE FOLLOWING XDA MEMBERS
@fnoji111 for working on the ENG HBOOT in the Droid DNA forum
@Argumentation for creating the flashable zip that I used for this tuttorial
@daddioj for doing the leap of faith and used the ENG HBOOT on his device which lead me to writing this tutorial
NOTE: I created this tutorial because HTC One has different variants. After reading mike1986. article on HTC One variants I realized why I can't install OTA updates with my model ID (MID). Now since we have S-OFF I wanted to get updates from the UK. But since I have a different MID to the UK version, I can't install OTA updates. And this is the only solution I found to work at this time. So I hope it will help people who wants to change their MID
VIDEO LINK AT THE BOTTOM OF THIS POST
REQUIREMENTS:
1: S-OFF
2: KNOWLEDGE OF ADB COMMANDS
3: PATIENCE
PLEASE MAKE SURE YOU PAY ATTENTION TO EVERY STEP ON THIS TUTORIAL
***** I WILL NOT BE HELD RESPONSIBLE IF YOU BRICK YOUR PHONE*****
STEP 1:
Make sure you don't have HTC Sync Manager installed, if you do uninstall it!! Also make sure you have HTC drivers installed!
Step 2:
Go here http://forum.xda-developers.com/showpost.php?p=38180376&postcount=6 and download the Argumentation's zip file
Step 3:
After downloading the PL83IMG.zip you will need to edit the android-info-txt inside. Please see sample picture below:
{
"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"
}
Step 4:
Now you have to place the zip file in C:\Android SDK\sdk\platform-tools folder. I know some people don't have the same directory as I have so this is just an example. Just make sure you place in the platform-tools folder.
Step 5:
Now connect your HTC One (MAKE SURE YOUR DEVICE HAS PLENTY OF CHARGE) to your PC and start a command prompt in the "platform-tools" folder. The quickest way to do this is (see picture below):
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually
You will not lose S-OFF and still have unlocked bootloader. I suggest that backup all important stuff before doing this I hope it helps.
If the mods feels that this doesn't belong here, please feel free to remove it. Thanks.
Here's a short video that shows how I changed my MID (model ID) on my HTC One
Just a side note: better to edit all kind of text with notepad++.
1) It formats text better (not just one single line)
2) It keeps Unix coding if needed
EDIT 05.12.2013 by the request of user @alray
THIS METHOD WILL NOT WORK USING WINDOWS 8.1
After flashing ENG hboot, Windows 8.1 won't detect the device and fastboot won't work, so you can't change MID and execute the RUU. (win 8.1 drivers issue).
I'll give this a go shortly
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
tyler1234567 said:
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
shadowboy23 said:
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Click to expand...
Click to collapse
Oh ok I got ya. Didn't see that before.
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
If it doesn't belong here then the mods can delete that is fine by me.
EDIT:
Just sent a message to one mod so he can delete this thread if it doesn't belong here.
thank you very much it worked like a charm just changed a tmous mid so far so good waiting to install ota
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
False. How is this not developement. And if this isn't developement then neither is the cid thread, or all the stock rom threads.
shadowboy23 said:
If it doesn't belong here then the mods can delete that is fine by me.
Click to expand...
Click to collapse
No harm, just easier to follow one thread since I am interested in this.
I converted my ATT One to the Dev Edition (hoping that nothing ATT is on m phone now except service), easy since both have the same MID but will be doing this for the PN0710000 soon.
Thank you for the tutorial. :good:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
CheesyNutz said:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
Click to expand...
Click to collapse
Which one? Do you mean the "android-info-txt"? If that's what you meant then you have to put in your current model ID, CID and ROM version..If it's the same as mine then you just copy what is written in the first picture. Just remember that Argumentation's zip file is intended for Droi DNA but all you have to edit id the "android-info-txt" and you don't have to touch the HBOOT.nb0.
A video lesson would be perfect
Tried to do something, but adb is not for me, I guess...
It would be perfect to change from carrier to free uk version..
darenas said:
A video lesson would be perfect
Click to expand...
Click to collapse
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
shadowboy23 said:
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
Click to expand...
Click to collapse
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
Click to expand...
Click to collapse
I see already.
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly..
Click to expand...
Click to collapse
Well my phone has S-OFF and have a unlocked bootloader. S-OFF is a MUST! You will see in the video very clearly what I type in adb/fastboot so I'm pretty sure people can work it out.
Video link is up! It is at the bottom of the OP. I hope it helps people.
Done with OTA :thumbup:
Sent from my HTC One using Tapatalk 2
READ THIS FIRST:After downloading "oxygenos_1.0.0.zip" you will notice that it contains a folder with two files:
oxygenos_1.0.0_flashable.md5
oxygenos_1.0.0_flashable.zip
Extract oxygenos_1.0.0_flashable.zip first, then copy it to the SD card, wipe, flash, etc.
MultiROM works!
Check here and click thanks for MMWolverine.
New touchscreen driver to fix ghost touches:
Click here.
__________________________________________
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
__________________________________________
Download it here:
Official:
https://forums.oneplus.net/threads/oxygen-1-0-2-release-with-stagefright-security-patches.340711/
There is a pre-rooted and de-bloated version by @CraZY_BoY^ right here:
[ROM][MOD] OxygenOS - Rooted | Cleaned | Some apps from CM
Features
Screen-off gestures like double-tap to wake, music controls, and shortcuts for the camera and flashlight
Hardware and software navigation keys
Quick settings feature, tiles can be added, removed, and re-organized
Their own file manager, though it's pretty buggy ATM (see below).
Missing features:
Privacy guard
Double tap to sleep
Display color settings
Theming support
Custom camera app (uses Google camera app)
MaxxAudio and Swiftkey (coming in a future update)
{
"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"
}
Installation steps:
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
If you find yourself wanting to rollback to CM, Make sure you have TWRP or CM recovery on the device. Another factory reset will be needed before flashing unfortunately so make sure you backup all of you data.
Click to expand...
Click to collapse
Source
To revert back to CM11/CM11s:
Flash the latest CM11/CM11s modem from here.
Restore CM11/CM11s from a backup or flash new.
There is no need to reboot between steps 1 & 2.
Rooting Instructions:
Just like CM11s, download SuperSU-v2.xx.zip to your SD card and flash from recovery.
Known issues:
Reported by OnePlus:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Reported here & elsewhere:
4k video is non-functional with Google camera.
Google Play Services wakelocks. Check here for a fix.
Other Stuff
Wallpapers
Boot animation
Modem
Please click thanks for the guys that posted these for you.
CafeKampuchia said:
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
Click to expand...
Click to collapse
Downloadning now! Lets see
very slow..hope for a mirror soon!
CoreGaming said:
very slow..hope for a mirror soon!
Click to expand...
Click to collapse
Its 700 MB
Nice to know, but I'll wait CM12s and then I choose what to do
I'm getting an average 100-150kbs using Firefox and DownloadThemAll. 1 hr 22 minutes left :/
Edit
Mine's shot up to >300kbs - 20 minutes left
Nothing like flashing a new ROM at 1:30AM!
Downloading now - Cant wait to get this thing running!
I am downloading on both my pc and my opo. on my the opo, it's taking 1 hour or so to download. on my pc it took 10 minutes. both on wireless on the same network.
Uploading to mega now, nearly half way, will post a link when finished.
gsmyth said:
Uploading to mega now, nearly half way, will post a link when finished.
Click to expand...
Click to collapse
Send me the link and I'll update the OP ASAP.
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
aravindhramachandran said:
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
Click to expand...
Click to collapse
Bug list in OP already, friend. Good point on the file manager. I'll add that to the OP as well. :good:
vacenzo said:
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
Click to expand...
Click to collapse
Dude, nobody even has it installed yet. And even if they do, it's been <1 hr. We'll know something tomorrow. :highfive:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
saar120 said:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
Click to expand...
Click to collapse
Read the comments.
Transmitted via Bacon
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
this is what happend to me as well. in the middle of the download i switched from wifi to 3g . i thought it was beacuse of that.
zee24 said:
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
Click to expand...
Click to collapse
Did you extract the zip? There is a flashable zip in the zip you downloaded.
There is a zip inside downloaded zip! Flash that.