ArchiDroid Q&A/T - Galaxy S III Q&A, Help & Troubleshooting

[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting
Specific to:
And it's components:
{
"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"
}
[/SIZE]
[SIZE=+1]
ArchiDroid 2.X Development Thread
ArchiDroid 1.X Development Thread
Please feel free to share issues, questions and offer help
If you get an answer to your question, don't forget to hit
[/SIZE]​

1. Questions/Issues without ArchiDroid version number may/will be ignored. Don't forget to tell us which ArchiDroid (1.X or 2.X) and which version you're using, otherwise don't expect an answer.
2. All battery questions/tips are allowed ONLY with a full BetterBatteryStats log or screenshot from all it's pages AT LEAST after 5 hours of full deep sleep. We're not magicians and we can't help you without proper information.
3. Respect all users.
Helpful users may be rewarded
From Zero To Hero: Complete Installation/Flashing Guide
This guide covers everything you need to do, to unleash full power of your SGS3 with ArchiDroid.
You've obviously heard about "rooting" "flashing" or other strange things. But these tutorials are quite old and it's already much easier to achieve our goals. Instead of flashing old firmwares, using old methods I'll guide you through complete flashing of ArchiDroid.
First of all you obviously need:
- Working Samsung Galaxy S3 GT-I9300 International Version
- Working computer with Windows OS
1) Connect your phone to your pc and give it some time for installing drivers. When it's finished reboot your pc. It's important. After reboot check if windows can "detect" your phone, for example by entering "My Computer" section. It should be available as portable device.
2) Download newest ArchiDroid .zip file and put it on your phone, I strongly suggest your internal memory.
3) Disconnect your phone from the pc.
4) Download attached Odin3 Software and unpack it's content on your pc: View attachment 1879375
5) Click with your right mouse button on Odin3 executable and select "Run as administrator"
6) Download latest PhilZ Touch Recoveryhttp://forum.xda-developers.com/showthread.php?t=2002953 in .tar.md5 format and put it in the odin's folder or somewhere nearby. DON'T UNPACK IT! File should look like this: philz_touch_4.92.8-i9300.tar.md5
7) Click on the "PDA" button in odin and select your recovery in .tar.md5 format. Also untick "Auto Reboot" option. DO NOT TOUCH ANY OTHER BUTTONS OR CHECKBOXES!
8) Turn off your phone
9) Hold Volume Down + Home + Power buttons to enter Download mode. It should say "Downloading, do not turn off target"
10) Connect your phone to your pc. It should be shown in Odin's message log as f.e. "<ID:0/003> Added!!".
11) Hit "Start" button and be patient. It shouldn't take longer than a few seconds. Your phone won't automatically reboot, wait for progress bar to reach the end and move to the next point.
12) Reboot into recovery by holding combination: Vol-Up + Home + Power. Hold it until you see "Samsung Galaxy S3" logo (about 7 seconds).
13) Click on Wipe Data/Factory Reset => Clean to install a new rom. WARNING! From this point you'll be unable to load your current system as it wipes everything available (your internal/external card will remain untouched). Please make sure that you're ready for this step and that you have right .zip file available.
14) After cleaning hit Install zip => Choose zip from sdcard. Then navigate to your location of archidroid.zip file and open it. Now you'll be able to set various options in AROMA "Setup Wizard", just follow the steps and ArchiDroid should properly flash and reboot your system after installation.
15) First boot takes quite longer than usual, I'd say maximum of 5 minutes.
Notice: This procedure is required ONLY for first flash of ArchiDroid. If you want to update ArchiDroid then simply download latest zip, copy it to your phone, reboot into recovery (or by holding combination above) and select "Install zip". Don't forget to select "ArchiDroid Update" mode to avoid wiping of data. No full wipes are required in order to update ArchiDroid.
In case of any weird rare problems, or if you want to start from scratch...
1) Download latest Samsung firmware for i9300, it doesn't have to match your region. Latest = Highest changelist. You can try unofficial Samsung repo for i9300 (with changelist number) or official, without changelist number. It doesn't have to be exactly the newest one but preferably one of the newest (some regions still have firmwares from more than one year ago...). Also try to use XX(EMG4) PDA instead of f.e. UB(EMI1) because XX are international.
2) Unpack .zip file you've got, extract .tar.md5 file from that, ignore kies file.
3) Enter recovery and wipe /data. It can also be done through stock recovery (Factory reset) but it's important to turn off your phone after cleaning instead of rebooting it.
4) Enter download mode after wiping/formatting /data
5) Connect your phone to your PC and load your .tar.md5 file as PDA in Odin, then start flashing. It can take up to 5-10 minutes because it's a big file.
6) Let it boot properly, when you're sure everything works repeat custom recovery & ArchiDroid flashing.
Above steps update low-level parts of your phone, f.e. bootloader, params partition, tz partition and hidden partition. While it's highly unlikely that any of these components would cause problem it's highly proposed to update low-level parts of your phone from time to time, just to ensure everything works properly. Custom roms don't update these partitions, as they're only being flashed during flashing original Samsung firmware via Odin, flashing custom stock roms won't work here. Also you get "maximum" cleaning, because literally you're overwriting everything on your phone.
If you have any further problems or questions feel free to ask them in this thread.
[SIZE=+1]ArchiDroid Core[/SIZE]
Q: When I want to use "Freedom", "AdAway" or other similar app which edits /system/etc/hosts file, it always fails, what's the reason?
A: ArchiDroid uses it's own built-in AdBlock, which is widely described in development thread. Therefore to prevent issues and slowing down the network, hosts file are permanently blocked from any modifications. This has been implemented to ensure that you know what you're doing before you mess with hosts file. In most common situations, you can point your favourite hosts editor (such as AdAway) to ArchiDroid's hosts file - /system/archidroid/etc/hosts, as THIS file should be edited INSTEAD of original hosts file. However if you really know what you're doing, you know that adding rules to original hosts file slows down the network dramatically and your app can't be set to use other hosts file, then you can unlock original hosts file through ArchiDroid app bundled with ArchiDroid. However keep in mind that I don't support this method, as it's deprecated, obsolete, dirty and ineffective method of setting rules. If you want to do it in proper way, use ArchiDroid's enhanced hosts mentioned above.
Q: I get "set_perm_rescursive some changes failed" error during flashing ArchiDroid. What's going on?
A: Simply update your recovery to latest version. Latest CWM, TWRP or PhilZ Touch Recovery work properly. Initial support for this function was added in ClockWorkMod 6.0.4.4.
Q: Whoa! What happened to colors in ArchiDroid, why they're "blacked out", "dimmed"? I want my stock colors back!
A: ArchiDroid in default configuration applies custom MDNIE settings, which change displayed colors. Samsung (and AOSP) uses over-satured, plastic, vivid colors, while ArchiDroid uses balanced and natural colors for our super amoled. It's up to you if you like it or not but if you decide to flash ArchiDroid it will come with natural balanced colors. You can change them very easily in Display Options (ArchiDroid 1.X) or in Advanced Settings (ArchiDroid 2.X).
Q: How to use delta upgrades provided by ArchiDroid?
A: Simply open any terminal, for example Android Terminal Emulator, type "su" and then "adflash" command. You'll be able to set various options and get exactly what you want. Remember that only "git" mode provides delta upgrades.
Q: My ROM reboots instantly after finishing first boot! What is going on?!
A: As you may know ArchiDroid contains two parts. Android (ROM) and ArchiDroid Backend (init.d scripts written from scratch by me), which works "next to" Android itself. ArchiDroid backend applies some good settings for you and if it decides that a hot (or even hard) reboot is required, it performs it. Hot reboot is always required during first boot from full wipe and sometimes it may be needed also after update mode. You don't need to worry about that, it happens only once after flashing and is totally intended. If you want to learn more please read more about "ArchiDroid Backend" in development thread.
Q: Why this ROM doesn't work with dual boot feature, found in Googy Max, Devil and Siyah kernels?
A: It does, but only as 1st ROM. ArchiDroid includes AROMA wizard, which is compatible only with flashing as 1st rom. Luckily you can swap it to the 2nd rom after flashing but you always must flash it as 1st. This is known issue with dual boot, as it doesn't work properly with aroma-based roms. ArchiDroid is not faulty here.
Q: I have a suggestion! Could you please implement it?
A: ArchiDroid focuses on stability, performance, battery life and out-of-box solution. It gives you literally out-of-box well tweaked and ready-to-go system with nearly everything you'd ever need. However I've already implemented many suggestions proposed by a community, so feel free to let me know if you have a nice idea, I'll tell you what I think and if I'm able to implement it.
Q: How can I use my own settings for Yank555 Kernel?
A: You should download full Yank's kernel from his thread and flash it after flashing ArchiDroid. If you select Yank's kernel in aroma then it comes with a preset chosen by me, so you should reflash it on your own.
Q: Which settings are best?
A: ArchiDroid offers you a power of flexibility and respects your choice. All default settings are proposed by me, according to my taste and what I think is "the best" for you. In most scenarios you'll be very satisfied with my settings, even if you won't touch anything during flashing in aroma. However you have a freedom of choice, bunch of options to choose from and even a few presets, which give you full choice between performance and battery. For now I can assure you that default settings are already well tweaked and optimized, so I highly suggest staying with them, unless you know what you want . The same goes with various "magic tweaks" and third-party modifications. I suggest to avoid them or mention them in development thread so I'll tell you what I think about them. Unfortunately most of these "magic tweaks" cause more harm than good.
Q: I have excessive battery drain! What to do?
A: ArchiDroid in default installation gives you BetterBatteryStats app, which is extremely useful for finding out what causes such high battery drain. You should launch BBS app at least one time (to initialize cache) and then reboot your whole OS right before going sleep. After boot enter your pin of course and let your phone literally "sleep" as deep as it can, of course with network turned on, because we want to get as close score as possible but without any useless apps running in the background. After night or at least a few hours in such total deep sleep unlock your phone, launch BBS and save log in .txt format. Attach this log to your post and hope for the best, we'll try to help you. All posts regarding battery drain WITHOUT BBS log will be ignored. If you won't provide at least BBS log then don't expect any help at all. ROM itself does not cause any additional battery drain. It literally loses from 0.1% up to 0.3%/hour in deep sleep, with 2G turned on and Wi-Fi turned off. It's your phone and your ArchiDroid. While I can prepare best rom for you I can't control what you do with it. If you kindly ask for finding battery drain culprit - I'll help. If you blame ArchiDroid for battery drain, I'll tell you to change the rom.
Q: Okay, let me fix it by myself. I can see really big values under RILJ, multipdp and sec.fd.wakelock wakelocks. What to do?
A: In general these wakelocks are attached to 3G connection. ArchiDroid supports "fast dormancy" function, which improves your signal and battery life during 2G/3G connection BUT it also needs to be supported on your provider's side. Basicly you have a few scenarios:
1. Your provider supports FD, and you have FD enabled. That's great, you will get better signal and less battery drain compared to non-FD.
2. Your provider supports FD, but you don't have FD enabled. Expect slightly worse signal and more battery drain compared to above option, but that's not a big problem.
3. Your provider doesn't support FD and you don't have FD enabled. Same as above, however in this situation it's great that you disabled FD, as you're avoiding excessive battery drain.
4. Your provider doesn't support FD but you have FD enabled. This is the worst case because you're wasting battery on FD requests, which are never accepted on the provider's side.
There is no general answer if you should have FD enabled or not. We don't know where you live, we don't know architecture of your city, and we don't know your provider. If you think that 3 wakelocks described above in fact appear in your BBS log then you can try to disable FD and see if situation improved. To disable FD open /system/build.prop through any root explorer and find this part:
# Fast Dormancy toggle. If your provider doesn't support it then it may be better for you to uncomment this line
#ro.config.hw_fast_dormancy=0
Click to expand...
Click to collapse
And then remove bolded # from second line, as showed above. If you'd like to enable fast dormancy once again simply comment it out. Reboot is required after these changes. WARNING! These wakelocks are pretty NORMAL if your phone uses 3G. They won't magically disappear, we're talking about excessive battery drain here. If you use 3G often then obviously it will require much more battery than 2G.
And once again. There's no right answer if you either should or should not have FD enabled. You need to find it out youself.
Q: This rom is awesome! Can I gain access to any beta versions? Weekly build is too old for me!
A: Please read GitHub section in development thread. You'll be more than satisfied.
Q: I see that you have many languages in aroma, could you add my own?
A: Personally I make only two translations - English and Polish. All other languages are available thanks to appropriate contributors. If you want to contribute to ArchiDroid project and implement your own language then I'm very happy to hear that and I'm looking forward to merge your strings . You should start with reading dummy.lang, I've attached proper instructions there. It's really easy job but it requires some patience and free time. If you're familiar with github or you want to learn how to use it then I'd be very happy to see a pull request with your language.lang. Otherwise everything you need to do is register at github and edit above dummy.lang file. This will automatically send pull request, which I can merge.
Q: How can I disable these cpu stats on the top?
A: This app is called "Cool Tool", you had an option to disable it in aroma. You can also delete/freeze it with Titanium Backup, or change it's behaviour in app settings.
[SIZE=+1]ArchiDroid 2.X[/SIZE]
Q: When I switch to ART runtime, it automatically switches back to dalvik after reboot, why is that?
A: If you have xposed installed then it forces dalvik. You need either to uninstall xposed or stay with dalvik.
Q: My bluetooth headset doesn't work! I can hear only weird noise or can't hear anything!
A: ArchiDroid 2.X is based on open-source Android sources. It doesn't have many closed-source drivers, while only a few have been reverse-engineered to provide you with functionality of your device. ArchiDroid 2.X will work only with a few BT headsets and it won't change until Samsung releases proper drivers, what is very unlikely to happen in near future. Either deal with it, or stick with a stock-based rom, for example ArchiDroid 1.X.
Q: I think that I found a bug. Could you fix it?
A: First of all, please notice that ArchiDroid 2.X is based on AOSP. Some things may be unfixable, while other are hard to reproduce. If you want to have your issue resolved then you must provide as much information as possible, because if you won't expect answers like "works fine here".
Some things to consider:
a) Have you tried full wipe and clean ArchiDroid installation?
b) Have you tried "Bare Bones" preset during flashing, which gives you clean AOSP installation?
c) Have you tried to reproduce this issue on latest OmniROM nightly build?
If bug exists in nightly then it's global bug and either it's unfixable or will be fixed soon (next release). If bug exists in normal installation but doesn't exist on bare bones preset then it may be possible that third-party ArchiDroid function causes issue. In this case I'd be very happy if you could make some basic tests and try to find root of this issue. If bug exists also on bare bones preset but doesn't exist on latest nightly then it's ArchiDroid-specific bug and should be fixed in sources. It's ultra important to provide at least answers to following three questions. If you're advanced user it'd be also cool if you can provide a logcat (if possible) and more specific information f.e. how to reproduce a bug. 99% of the ROM problems are caused by the base, therefore I can't directly fix them and you should forward them directly to the OmniROM. Especially if you can reproduce bug in b) and c) steps.
[SIZE=+1]ArchiDroid 1.X[/SIZE]
Q: Camera or Wi-Fi doesn't work right after flashing with custom kernel. What's the reason?
A: In some rare scenarios it looks like flashing custom kernel in aroma may cause such issues. Users say that flashing stock kernel, first boot & loading camera, and then flashing custom kernel helps, however I couldn't reproduce camera/wi-fi issue, so it's not global bug.

Call recording 1.7.5
Hi,
is there a way to enable automatic call recording (i.e. set the automatic recording of all incoming and outgoing calls)?
Thanks!

Hi JustArchi;
Um using ur omnirom v2.3.2 and i have problem with change to my Runtime dalvik to ART i wanna try ART and im choosing it in developer settings and after i chose my phone reboot but when i checked it is still dalvik. Why İ cannot change my Runtime? Pls help me. How can i use ART?
puHu

bazsoczi said:
Hi,
is there a way to enable automatic call recording (i.e. set the automatic recording of all incoming and outgoing calls)?
Thanks!
Click to expand...
Click to collapse
I'm afraid that you need a third-party app for that or heavily modified stock dialer.

puhu said:
Hi JustArchi;
Um using ur omnirom v2.3.2 and i have problem with change to my Runtime dalvik to ART i wanna try ART and im choosing it in developer settings and after i chose my phone reboot but when i checked it is still dalvik. Why İ cannot change my Runtime? Pls help me. How can i use ART?
puHu
Click to expand...
Click to collapse
If you have installed xposed then it forces dalvik. Either uninstall xposed and use ART or keep xposed and use dalvik.

Can you help me with my DPI issue?
Sent from my GT-I9300 using xda app-developers app

Ahad Ejaz said:
Can you help me with my DPI issue?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Wait for 1.7.5.1 hotfix.

JustArchi said:
If you have installed xposed then it forces dalvik. Either uninstall xposed and use ART or keep xposed and use dalvik.
Click to expand...
Click to collapse
Thats mean xposed doesnot work with art right?
puHu

puhu said:
Thats mean xposed doesnot work with art right?
puHu
Click to expand...
Click to collapse
Yup.

How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3
How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3
I open Terminal Emulator, type in
Code:
su - root
change directory to ArchiDroid/Scripts folder, and run
Code:
./ArchiDroid_FstrimAll.sh
I get a Permission Denied error. I can't seem to upload my screenshot now, but my original post has a screenshot at http://forum.xda-developers.com/showthread.php?p=49336985#post49336985
Thanks

mvariyawa said:
How do I run ArchiDroid_FstrimAll.sh on ArchiDroid V2.3.3 (running OmniROM).
I open Terminal Emulator, type in
Code:
su - root
, change directory to ArchiDroid/Scripts folder, and run
Code:
./ArchiDroid_FstrimAll.sh
I get a Permission Denied error. I can't seem to upload my screenshot now, but my original post has a screenshot at http://forum.xda-developers.com/showthread.php?p=49336985#post49336985
Thanks
Click to expand...
Click to collapse
You have two ways for that.
1. Use any script manager, for example root browser included with ArchiDroid. Navigate to proper folder and execute script as root.
2. Use Android Terminal Emulator. Type "su" and then "sh /data/media/0/ArchiDroid/Scripts/ArchiDroid_FstrimAll.sh"
Eventually you can also chmod this script to 755.
I'll add 755 chmod to updater-script, as it should be 755 from start.

Whats the best Recovery now,, CWM? TWRP? or Phils Recovery and can u post the link thanks,, :good: oh i have Philz Touch 5 at the moe,,, cwm base 6.0.4.4

The King Tyrone said:
Whats the best Recovery now,, CWM? TWRP? or Phils Recovery and can u post the link thanks,, :good:
Click to expand...
Click to collapse
I'm using PhilZ Touch Recovery but any recovery, which you mentioned will work properly, as long as it's the latest version.

JustArchi said:
Yup.
Click to expand...
Click to collapse
I uninstalled xposed and tried many times for change to ART but after i reboot it is still dalvik it doesnot change :'(
puHu

puhu said:
I uninstalled xposed and tried many times for change to ART but after i reboot it is still dalvik it doesnot change :'(
puHu
Click to expand...
Click to collapse
Did you uninstall it completely? I can assure you that it works with no-xposed right after flashing.

Genius
JustArchi said:
You have two ways for that.
1. Use any script manager, for example root browser included with ArchiDroid. Navigate to proper folder and execute script as root.
2. Use Android Terminal Emulator. Type "su" and then "sh /data/media/0/ArchiDroid/Scripts/ArchiDroid_FstrimAll.sh"
Eventually you can also chmod this script to 755.
I'll add 755 chmod to updater-script, as it should be 755 from start.
Click to expand...
Click to collapse
You are a genius. Method 1 worked perfectly. Thanks

JustArchi said:
Did you uninstall it completely? I can assure you that it works with no-xposed right after flashing.
Click to expand...
Click to collapse
Yes i uninstalled it competely with Titanium backup and reboot and i changed Runtime to ART and reboot but after reboot i checked it still dalvik :'(
puHu

puhu said:
Yes i uninstalled it competely with Titanium backup and reboot and i changed Runtime to ART and reboot but after reboot i checked it still dalvik :'(
puHu
Click to expand...
Click to collapse
You should try with full wipe and unticking xposed in aroma then. Sorry, can't help much.

HELP!!!
its happend again!!!! everytime i install or update archy rom, it always boots in to Recovery! why dos it do that?? any other roms dont,, its just this one,,,,,, how to fix thanks UPDATE!!!!!!!!!!!!!!!!!!!!!!! i found the problem!!! i unticked Xposed Framework and flashed again and now i have boot screen! PHONE IS ALIVE!!! :d

Related

[GUIDE] Everything you need to know about your Vibrant. - Rooting/Unlocking/Flashing

Welcome to your device. The Samsung Galaxy S Vibrant T-959 is a great device! Why don't we learn about it before we go any further?
{
"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"
}
Other names associated with this device:
Samsung Vibrant ✓
Galaxy S Vibrant ✓
T-959 ✓
Click to expand...
Click to collapse
This device is NOT a:
Samsung Galaxy S ✗
i9000 ✗
i9000m ✗
Samsung Galaxy S 4G ✗
SGS4G ✗
Click to expand...
Click to collapse
Device Specs:
2G Network: GSM 850 / 900 / 1800 / 1900
3G Network: HSDPA 1700 / 1900 / 2100
Dimensions: 122.4 x 64.5 x 9.9 mm
Display: Super AMOLED capacitive touchscreen, 16M colors
Size: 480 x 800 pixels, 4.0 inches (~233 ppi pixel density)
SD Card: microSD, up to 32GB
Internal: 16GB storage,
RAM: 512 MB RAM
Chipset: Hummingbird
CPU: 1 GHz Cortex-A8
GPU: PowerVR SGX540
Click to expand...
Click to collapse
Great! What Android versions can be ran on this phone?
Froyo - It's been out for a long time so it is optimized to the max. Working GPS, long battery life, quick and snappy. (Recommended for n00bies.)
Gingerbread - Since we had no "official" build, there are problems with battery, GPS and small memory leaks here and there. Plus you will have to install Gingerbread bootloaders. (If you screw this up, it is the one sure fire way to hard-brick this device-so tread lightly) Almost all GB ROM do NOT have e911/911. There is CM7/7.2, Simply Honey, MIUI.
Ice Cream Sandwich - Make sure you choose anything 4.0.4 based, as it has updated code from Google. There is Slim, CM9 and a few others. GPS sucks for the most part and maybe/maybe not e911/911.
JellyBean - All are experimental but run pretty well, may be glitch at times. CM10, HellyBean and SlimBean are the front runners.
Click to expand...
Click to collapse
Cool, but I'm a noob, what should I start off with?
My suggestion to you is for you to run some Froyo ROMs to get you comfortable with the flashing, nandroiding, tweaking processes and then move on to something else.
Above all read and search. This phone is 2 years old, so chances are you won't have done anything that someone else already has.
Nearly all the issues are solved, so you should be able to use the search and find something out about said problem, as opposed to opening a thread about it.
Click to expand...
Click to collapse
Okay, I see.. but I don't quite understand what flashing, nandroiding, tweaking, etc. mean?
* - anything and everything possible. A good example would be "All my friends live at 10* Croxley Street." This is saying that they are all live at 100, 101, 102, 103, 104, 105, 106, 107, 108 and 109.
Dev - See developer.
Developer - A man or woman who has created (developed) software.
ROM - 1. A modified version of the Android operating system operating system. 2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free (see open-source)
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
CM - See cyanogenmod
Cyanogenmod - A free open-source project based on the AOSP. It is a modded (see modded) version of the Android firmware
Firmware - see ROM (1)
Stock - An unchanged version of something. Example: I just flashed stock sense
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
FOTA - "Firmware over the air" this normally refers to ROM's but can refer to radio firmware (see OTA)
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM (1)
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
Radio Firmware - (see firmware) a type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Overclock - (not to be confused with underclock) to exced the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Underclock - to change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
Modding - To perform a mod
Modded - to have included mods
Modification - see mod
Governor - a system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop bellow the (just as eaisly configurable) minimum frequency.
Library's/Libs - a set of instructions for applications to use to function. A functioning camera lib would allow the camera to be used.
WFS - "Wildfire S" an armv6 device made by HTC in 2011.
Logcat - A logging system built into the ADB
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
SDK - "Software Development Kit" a set of tools used for software development.
WIP - "Work In Progress"
JDK - "Java Development Kit" an SDK for the java platform. It is needed to run the Android SDK.
JRE - "Java Runtime Environment" a collection of binarys and files to allow java software to execute.
Execute - To "run" or "start" a binary
Binarys - (sometimes called bin's) a group of executable files.
RAM - Could be one of three meanings: 1. Memory for the CPU to process processes. 2. Random Access Memory, a place where information can be used, executed from, modified, or deleted. 3. A type of sheep.
SD - Short term for MicroSD
Marvel - A gsm version of the phone
Marvelc - The cdma version of the phone
Marvelct - A rare Easten CDMA version of the phone.
Marvel* - all versions of the HTC Wildfire S (see *)
GB - Could mean one of two things. 1. Gingerbread or 2. Great Britain
Gingerbread - Android 2.3
Froyo - Android 2.2
Honeycomb - Android 3.x. it was never released or ported to the wildfire s because it was built for tablets.
Ice cream sandwich/ICS - Android 4.0. The latest version of Android.
CM9 - Cyanogenmod 9. A modified version of ICS. (see cm)
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT
HBOOT - The bootloader for all modern HTC Android phones.
Custom recovery - A o version of the stock HTC recovery to install unoffical ROMs.
AFAIK - "As far as I know"
KANG - The process of creating a code based of someone else's code.
Zipalligned - This is something that makes a ROM faster. If you can improve this please contact me!
Deodexed - Where ODEX files are moved into the actual applications
APK - "Android Package" an Android application
Click to expand...
Click to collapse
This was written by benjamingwynn and brought over to the Vibrant section by Woodrube, so thanks goes out to them!
Okay, I think I'm ready to begin! Where do I start?
You have a couple of choices, click on the one that best suites what you want to do with your device!
#1. I want to root my phone.
- Dowload this update.zip file.
- Plug your phone into the computer and mount your phone.
- Transfer the update.zip you just downloaded to the root of your internal memory. (sdcard/)
- Unmount your phone, unplug the USB and power it down.
- Hold Volume Up + Volume Down + Power button until you see the Vibrant screen.
- This will get you to a recovery menu (blue/purple text) after some yellow text.
- In this (the stock recovery menu) select 'Reinstall Packages' (Use the volume keys to navigate and the power button to select.)
- It should reboot and now you have root!
* If you want to flash ClockWorkMod Recovery, continue to #2, if you want to keep it as stock as possible, stop here.
* If you want to know what you can do now that you have root, scroll down and read the section titled 'What can I do now that I have root?'
#2. I want to install a custom recovery.
- Dowload this update.zip file.
- Plug your phone into the computer and mount your phone.
- Transfer the update.zip you just downloaded to the root of your internal memory, replacing the zip you used to root. DO NOT KEEP BOTH FILES. (sdcard/)
- Unmount your phone, unplug the USB and power it down.
- Hold Volume Up + Volume Down + Power button until you see the Vibrant screen.
- This will get you to a recovery menu (blue/purple text) after some yellow text.
- In this (the stock recovery menu) select 'Reinstall Packages' (Use the volume keys to navigate and the power button to select.)
- It will cycle a bit, you will see that yellow text again, then it will return to the stock recovery.
- Select Reinstall packages again.
- You are now in ClockWorkMod recovery.
* If you want to flash a custom ROM, continue below, if you want to save that for later, stop here and select 'Reboot System Now'
* If you want to know what you can do now that you have a custom recovery, scroll down and read the section titled 'What can I do now that I have a custom recovery?'
So, you're ready to flash a ROM, eh?
Select the class of ROM you want to install below.
Note: (Make sure you're certain of what you want as the instructions are different for each.)
#3. I want to flash a Froyo based custom ROM!
- Download the Froyo ROM of your choice to your PC. (ROMs are typically 140-190+MB’s. So yeah, it’s a big file.)
- Plug your phone into the computer and mount your phone.
- Drag ROM to root of internal memory. (Should appear as: sdcard/TheRomName.zip) (You DO NOT need to rename the ROM)
- Unmount your phone, unplug the USB and power it down.
- Reboot into ClockWorkMod Recovery.
There's two ways of doing this:
1. Using Rom Manager (Downloadable via Google Play.) - You do not need to power down your device for this one.
2. Hold Volume Up + Volume Down + Power button until you see the Vibrant screen.
Use whichever you feel most comfortable with.
- This will get you to a ClockWorkMod Recovery menu.
- It is encouraged that you do a Wipe Data/Factory Reset and Wipe Dalvik Cache (Advanced menu)
- Go to 'Install zip from sdcard'
- Select zip from sd, choose your ROM and flash it. (Use the volume keys to navigate and the power button to select.)
- After it's down, go back and select 'Reboot System Now.
- Your new ROM is going to boot. Note: Initial boot will take a LONG time ( Up to 10 minutes, maybe)
* You may hear a lady's voice (Linda) converting your file system – this is normal if your ROM has the Voodoo lagfix. No worries.
* If you want to know what Voodoo lagfix is, scroll down and read the section titled 'What is a lagfix?'
#4. I want to flash a Gingerbread based custom ROM!
Note: Please select an option
Samsung/Touchwiz based ROM
CyanogenMod/AOSP/AOPK based ROM
#5. I want to flash an Ice Cream Sandwich based custom ROM!
#6. I want to flash a JellyBean based custom ROM!
Click to expand...
Click to collapse
What can I do now that I have root?
You can backup your apps using Titanium Backup found in the Google Play store.
Use apps that require root.
Etc.
This thread here has great information on root!
Click to expand...
Click to collapse
What can I do now that I have a custom recovery?
Make a NANDROID backup of your current setup and restore that backup!
Flash ROMs, modems, kernels, themes, etc.
Wipe data, clear cache, etc.
This thread here has great information on root!
Click to expand...
Click to collapse
What are these lag fixes you speak of and what do they do?
There are two lag fixes available for this phone.
One Click Lag Fix - It converts your file system to ext2 rather than the default RFS.
Voodoo Lagfix - Replaces offending Samsung proprietary RFS filesystem by Linux standard Ext4.
These both boost the performance and remove the lag on your phone.
Voodoo being the most favorable one.
You can read more about OneClickLagFix here.
You can read more about Voodoo Lagfix here.
Click to expand...
Click to collapse
Useful links and resources:
[GUIDE]:::Welcome to your device. Read Me
[PROGRAM] AIO Vibrant Toolbox 2.5 *Beginners Start Here* Also for advanced users
[Repository] Essential Hard To Find Files
[How to] --->You Want Better Battery Life:::Read This
Click to expand...
Click to collapse
​
Credits and Thank you's:
- s15274n for his great guides and borrowed words!
- Woodrube for his great guides and borrowed words!
- Anyone else I may have missed.
Note: I will update this thread daily and keep everything current.
These are my ways of flashing my device and they have worked perfectly, there are other ways as well and they have been posted.
So look around if you find this confusing!
Reserved for changelog or anything else. <3
Uno mas?
Thanks for the nod man.
@E1 else. Listen to theexel, he knows what he is doing and has been around for a long time. If you have a question, make sure you ask. If you get stuck, make sure you read, search, read again and search again, then post your question.
This phone has been out for a very long time, so chances are your problem is not unique and has probably happened to someone else.
I like this part and I know how true it is
Woodrube said:
make sure you read, search, read again and search again,
Click to expand...
Click to collapse
Thanks for this wonderful guide , I wish read this a year ago , it would had been very helpfully but now it going to lead the noobs the good road thanksss
Sent from my SGH-T989 using xda app-developers app
awesome post for noobies or in general when u have brain farts lol great work you do for all in this community and other with your themes and sweet knowledge ! keep it up brother CheerS! EXEL AND WOOD you guys r brick savers lol
Grade A work, you've truly outdone yourself (theexel) by producing such an easy to follow & well organized guide. A friend of mine recently got his first android device, a used Samsung Vibrant running Eclair, and after seeing mine running ICS he's very, very jealous . Although I'm willing to upgrade and root his device for him, I feel that it is always best to learn by hands-on practice. This guide is what I'll recommend him--or anyone who owns a Vibrant for that matter. Thanks and keep up the good work!
Honestly, this thread should be stickied.
been searching for an answer, found many. MAybe u guys can help. I soft bricked my phone. no biggie, i can still get into dl mode. BUT here is where the problem comes in. usb debugging is off and odin WILL NOT recognize my vibrant. I tried a dif comp, different port, uninstalled and reinstalled drivers, nothing. So what do i do to get the pc to see my phone now?
(i figured a everything guide would have the answer, or at least a person to answer. I really did try to find the solution first before i get yelled at)
You don't need to have debugging enabled for you to be able to ODIN.
Have you tried a different cable?
Next time, please make your own thread.
error E:Signature verification failed
Trying the method above to root my wife's vibrant. I am getting an error that says "E:signature verification failed installation aborted."
Info on phone is as follows:
Firmware version 2.2
Baseband T959UKVB5
Kernal
2.6.32.9
Build FROYO.UVKB5
Any help is appreciated. Also I only have a mac so I can only do methods that use a mac!

[ROM][KERNEL][JZO54K][01.12.2013] GeeWiz 3.4 (Retired)

GEEWIZ 3.4 SCH-I500 JZO54K JELLY BEAN 4.1.2 ROM/KERNEL
RETIRED -- GEEWIZ 3.4 WAS THE FINAL RELEASE OF GEEWIZ BASED ON ANDROID 4.1
OTHER AVAILABLE GEEWIZ VERSIONS:
GeeWiz 4 - AOSP Jelly Bean 4.2: http://forum.xda-developers.com/showthread.php?t=2088224
GeeWiz 3.4 is a ROM for the Samsung Fascinate, based on AOSP Jelly Bean 4.1. Like it's predecessors of the same name, GeeWiz doesn't aim to provide a lot of bells and whistles or incorporate all of the latest and greatest tweaks and enhancements developed by the community; the aim is to provide a basic, stable, functional device.
GeeWiz 3.4 uses a modified version of the GeeWiz 2.8 Gingerbread (Linux 2.6) kernel with a number of very specific tweaks/hacks in order to continue to support the proprietary Samsung RFS file system and other features I wanted to carry over. As a result, this ROM may not be used in conjunction with any other Kernel, and this Kernel cannot be used in conjunction with any other ROM. Please consider it a "matched set", and they will always be updated/distributed together. XDA community developed enhancements to the ROM or Kernel are encouraged, and will be given prominent feature status in this post.
Your device needs to be set up as stock or stock-like (e.g. GeeWiz 2.8) before installing this ROM/Kernel. If you are currently running with an MTD-based platform, the device must be reverted back to the original OEM volume format. Please refer to the forum/thread were you acquired your current ROM for guidance on how to revert the device as necessary.​
Installing this ROM/Kernel or any other provided component(s) will void your device's warranty, and I cannot be held responsible for any damages of any kind (including data loss) that are incurred either directly or indirectly by these packages and components. What you do to your device is ultimately your problem!​
FEATURES
Android Jelly Bean AOSP build JZO54K (android-4.1.2_r1)
Google Apps version JZO54K from the Galaxy Nexus
All devices (GPS, compass, orientation, camera, flash) are functional
Wifi (WPA/WPA2) and Bluetooth Tethering support
Supports OEM DBDATA volume to keep performance reasonable
Supports both RFS and EXT4 formatting on all volumes
OEM USB modes (CD-ROM/Kies/MTP) replaced with standard Android Mass Storage
Advanced Battery Settings: Maximum Charge, Automatic Recharge Point
Advanced CPU Settings: Maximum/Minimum Clock Speed, Governor Selection
Advanced In-Call Volume Boost Selection
Backlight Notifications built into system, controlled by the OS
Supercurio Voodoo Sound 10
Fascinate Dock audio simulates a true USB audio device for seamless output path switching
Custom Dock options - Enable BLN, Stay Awake, Enable audio output
CREDITS
While it would be impossible to remember/cite every possible reference that was used during development, I would like to specifically thank the following teams/individuals for making their work public so that others could learn from it and in more cases than not, shamelessly "borrow" it:
jt1134 - A primary source of knowledge for all things Samsung Fascinate
sgtkwol - Maintains a Linux 2.6 kernel for the Epic that provided a vast amount of reference material for the kernel updates
pawitp - Fixed my video driver changes to eliminate a 'microlag' issue (thank you!)
Entropy512- Customizations to allow WPA/WPA2 Wifi Tethering to work on the Galaxy S
teamhacksung - Maintains a large repository for all Galaxy S devices, I can't count how many code compares I did against their material
Cyanogenmod - The fact that this ROM can make a call at all is thanks to this team. So much of this effort is based on theirs!
rxwookie - A long-time supporter of all things GeeWiz and always takes the time to help other folks out here. I think he probably knows more about GeeWiz than I do!
ACTIVATION AND PROVISIONING
While I have no reason to believe that activation/provisioning wouldn't work properly on this ROM, it is a difficult thing to test on CDMA networks. Until it's been established that activation/provisioning is indeed working properly, I suggest you do not use anything like the ODIN "EFS Clear" option that may affect it. If the phone was properly provisioned before installing this ROM, it should maintain that provisioning. I have successfully activated a Fascinate on this ROM, but have not tested the process enough to be fully confident with it.​
KNOWN ISSUES
USB Mass Storage / ADB may not work after device has been docked
After docking and removing the device from a Samsung Fascinate dock, USB Mass Storage and/or ADB may stop working. When this occurs, the only way to restore USB connectivity is to power off the device and power it back on. Rebooting is not sufficient and will not alleviate the problem.​
FIRST-TIME INSTALLATION RECOMMENDATION
This ROM performs significantly better when the device uses the EXT4 file system. Unfortunately, using ODIN will always format the device with the RFS file system. Unlike previous versions of GeeWiz, the new "Full Wipe" ODIN package has been modified such that it will format the data volumes (DATA, DBDATA, CACHE) with the EXT4 file system on the first boot. This is now the recommended installation method for first-time installation.
If the "Full Wipe" ODIN package is not used, please note that your data must be wiped manually if coming from another ROM to avoid problems, and I strongly recommend converting, at minimum, the data volumes of the device (DATA, DBDATA, CACHE) to the EXT4 file system.​
UPGRADING FROM GEEWIZ 3.2/3.3
GeeWiz 3.2.x/3.3.x Versions can be upgraded directly to GeeWiz 3.4 without a need to wipe the device data or revert the file system back to RFS. The EDIFY update-zip below is compatible with most, if not all, recoveries and will work regardless of if the device is formatted with RFS or EXT4.
Your Dalvik-cache will be automatically wiped, so the first reboot will take a long time
Due to problems with some Google services after a kernel change, the Google Services Framework package will have its data cleared during installation. You will be prompted to accept Google's location services again
DOWNLOADS
EDIFY Update-Zip (ClockworkMod / GeeWiz Recovery) Compatible Downloads
GeeWiz 3.4 ROM/Kernel (EDIFY Update-Zip)
http://www.mediafire.com/file/ascgikdaqdg3ai5/geewiz-3.4-syskernel-01122013.zip
MD5: 6b2e280f9d51492febec43b8b9fa3bd4
GeeWiz 2.8 Recovery (EDIFY Update-Zip)
http://www.mediafire.com/file/5fxee76vrxv28eq/geewiz-2.8-recovery-04162012.zip
MD5: 9869d3138279d99f1237a442f7573cad​
ODIN Compatible Downloads
GeeWiz 3.4 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
http://www.mediafire.com/file/2266vgo7uma5xmk/geewiz-3.4-fullwipe-01122013.tar.md5
MD5: 0d6c2cf955d0024c925c2d10ce046e1d
GeeWiz 3.4 ROM/Kernel (ODIN)
http://www.mediafire.com/file/jzfwybqu6ns70ay/geewiz-3.4-syskernel-01122013.tar.md5
MD5: 46e17141a8f8a8ae48001c3e4653e088
GeeWiz 2.8 Recovery (ODIN)
http://www.mediafire.com/file/h5gov2c1r8836tj/geewiz-2.8-recovery-04162012.tar.md5
MD5: b70d4063dffaa9cd89629f307d3beae5​
SOURCE CODEThe entire baseline for GeeWiz is available on github: https://www.github.com/djp952.
Device repo: android-platform-device-samsung-atlas3g (branch android-4.1.2_r1)
Kernel repo: android-kernel-atlas (branch android-4.1.2_r1)
Please see post #2 of this thread for an overview of how to build the GeeWiz ROM/Kernel from source as well as how to package your modifications. I would be happy to include any XDA community developed modifications or enhancements to the baseline as featured packages, add-ons or patches for GeeWiz!
Disclaimer: djp952 reserves the right to mercilessly kang your changes and assimilate them when you fix things that he was unable to. djp952 will also give you *major* props and full credit for the fix, so it's not that bad, right?​
HOW TO BUILD THE GEEWIZ 3 ROM AND KERNEL
A common request I've gotten is how to build either the GeeWiz ROM or kernel from source. I think GeeWiz 3 is a little less intimidating as a first step for getting into AOSP builds since it doesn't stray too far from the Android baseline, and the kernel is based on Samsung's stock model for the device rather than the enhanced MTD model. Whatever the reason, I'm happy to try and describe how I build these components and generate the packages that I post for the community. Sometimes it's normal, sometimes it's a bit wonky, but as long as I don't miss anything important it should be a workable process for anyone that would like to get into building custom Android builds.
I think GeeWiz 3 would be a great learning tool, it works as-is but leaves enough room for additional customizations and enhancements that it may be a better place to start than jumping into something like Cyanogenmod or AOKP as your first project. It's up to date at the moment with the latest Android code as well, so that's a definite bonus as opposed to working with something like Gingerbread where tricks you learn may not apply to the next project you take on.
BUILD ENVIRONMENT
I use Ubuntu 12.04 Desktop x64 for my Android build environment, and even though Google states that this environment is "Experimental", I've not run into any issues with it. To get started, simply follow the directions Google has provided here:
http://source.android.com/source/initializing.html
If you are running on Windows x64, I can also recommend using a Virtual Machine as your build environment. I like Oracle VirtualBox the best, but the stock Fascinate code by Samsung has major USB problems with it, you won't be able to use ADB or Heimdall. For Fascinate-specific development I recommend VMWare Player since it can work with the stock USB. Note that you need an x64 OS and a CPU with Virtualization Support to host an x64 guest OS regardless of the software you choose. The best performance and compatibility will come from installing Linux natively on your system.
DOWNLOAD GEEWIZ SOURCE TREE
Once your environment is set up, you of course need some source code. I've opted to use Google's repo tool and AOSP manifests to control the source tree, so the first thing you need is the Google repo tool. Follow the first section of this document, entitled "Installing Repo":
http://source.android.com/source/downloading.html
I have two separate "builds", or in Android terms Manifests out there. One is called DEFAULT and includes just changes to AOSP necessary to support the Fascinate. The other is called CUSTOMBUILD and adds the light OS customizations I have done. Since I never use DEFAULT and I'm not sure t even builds at the moment, we're going to use CUSTOMBUILD, or as it's called here at XDA "GeeWiz".
Open a terminal window to your home directory (~/)
mkdir android
mkdir android/platform
cd android/platform
repo init -u https://github.com/djp952/android -m custombuild.xml -b android-4.1.2_r1
What we just did was initialize the repository for AOSP, but haven't downloaded anything yet. The -u argument to repo tells it where to find the manifest XML files. In this case, my github "android" repo. The -m tells it what manifest to use. The -b tells it what branch to pull. This is important because like most folks, I have multiple branches out there. I have been indicating at the very end of the first post what the current active branch is, android-4.1.2_r1 right now.
At this point, I suggest going into the ~/android/platform/.repo/manifests directory and having a look at the manifest file. (.repo is a hidden folder). Open up custombuild.xml in GEDIT and you can see that I've taken the AOSP manifest and simply replaced portions of it to point into my own github repos for things I've changed. I'll try to include details on how I manage this below so you could do something similar if you want to.
The most time-consuming part of building Android is downloading the code. Can't go much farther without it, so get yourself a cup of coffee and a good book ...
In the terminal, at the ~/android/platform directory
repo sync
The SYNC command uses the manifest to go get all the code. Most of it is going to come from Google, but all the bits I've altered will come from my github instead. It's going to take a very long time to download.
BUILD GEEWIZ ROM
Once downloaded, we have to choose what device to build for. GeeWiz has two target devices, "atlas" and "atlas3g" (Technically, there are three as I use the same build for "toro" - VZW Galaxy Nexus). Atlas is the Wifi-only target known here as "GeeWiz Media". Atlas3G adds to that changes required to include voice/data support (mostly courtesy of Cyanogenmod!). Let's assume if you're reading this, you're interested in Atlas3G.
In the terminal, at the ~/android/platform directory
source build/envsetup.sh
lunch
The "Lunch Menu" (haha Google) will present you with a list of device builds to choose from. You can select by number, or you can type in anything not on the menu. As of this writing, the build we want is #8, full_atlas3g-userdebug. userdebug generates a generally release-quality build, but doesn't odex (pre-optimize) the APKs and has some additional debugging support you wouldn't ordinarily find. You could also type in full_atlas3g-eng for an "Engineering" build or full_atlas3g-user for a "Release" build. I think you'll prefer userdebug most of the time.
Select 8 - full_atlas3g-userdebug
make -j4 rompackage
This will kick off the build. It will take a long time the first time through. The rompackage argument is something I added to AOSP to support the Fascinate. This will build the EDIFY update-zip that I upload for everyone and use to generate the ODIN packages (more on that later). On typical Android devices, you would use otapackage (update-zip install) or updatepackage (fastboot install) instead. Fascinate is a special needs child, so it gets a special needs build process.
Once it's done, provided I didn't forget anything important here, you'll have a full ROM/Kernel package ready to be flashed via Clockworkmod or GeeWiz Recovery in the ~/android/platform/out/target/product/atlas3g folder. It will be named along the lines of full_atlas3g-rom-YYYYMMDD.HHMMSS.zip. Making a package for ODIN involves more steps, but I'll get to that. First I have to tell you how to build a modified Kernel ...
BUILDING THE GEEWIZ KERNEL
The Atlas and Atlas3G repos have a pre-compiled kernel in them that is packaged with the ROM build. This section will describe how to build and include customized versions of that kernel. First step is, of course, to get the source code. Both ROMs share a kernel but due to differences in the ramdisk (initramfs), they are built independently.
In a Terminal, at the ~/android directory
git clone https://github.com/djp952/android-kernel-atlas.git
cd android-kernel-atlas
git branch android-4.1.2_r1 remotes/origin/android-4.1.2_r1
git checkout android-4.1.2_r1
Now the build environment needs to be set up. I use the compiler provided with AOSP to build the kernel as this is how Google does it. If you are using a different compiler, or have put your AOSP tree into a different location, you may have to modify these commands slightly.
In a Terminal, at the ~/android/android-kernel-atlas directory
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=~/android/platform/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
NOTE: From this point forward, don't close that Terminal, otherwise you will have to execute the environment export commands again.
The kernel is built in three steps. This is necessary because the Fascinate doesn't conform to Android's models and we have to include the ramdisk (initramfs) in the kernel image. The first step is to select which device you are building the kernel for, which in this case will be "atlas3g_defconfig". (The other configuration for GeeWiz Media is called "atlas_defconfig").
make atlas3g_defconfig
This initializes the kernel build for Atlas3G. Since we need to build the ramdisk as part of the kernel, the next step is to generate any loadable kernel module (.ko) files that need to be part of that ramdisk
make modules
The way I have the kernel set up, it will pull the necessary files for the ramdisk by looking at the device "initramfs.list" file, in the AOSP tree. The file that describes the atlas3g ramdisk, for example, is in ~/android/platform/device/samsung/atlas3g. If you examine this file you can see that it lists where all the files should come from, relative to the kernel source root directory. This explains why I went through how to build the AOSP tree before the kernel, the kernel depends on the AOSP build. Provided everything is in the right place, it's time to build the kernel
make
This executes the main kernel build. Should any ramdisk files be missing, it will error out early on and let you know what the problem is. Assuming everything goes well, your kernel will be in the ~/android/android-kernel-atlas/arch/arm/boot directory. It's named zImage and it's the combined kernel/ramdisk required for the Fascinate.
This zImage file can now be flashed directly to the device with Heimdall, packaged up for ODIN, etc. However in order to make it part of your AOSP build and corresponding EDIFY update-zip, we have to copy it into the AOSP tree and rebuild the ROM. It's a bit tedious, and other folks have different and more streamlined ways of accomplishing this, but this method has worked for me.
cp ~/android/android-kernel-atlas/arch/arm/boot/zImage ~/android/platform/device/samsung/atlas3g/kernel
cd ~/android/platform
source build/envsetup.sh
lunch full_atlas3g-userdebug
make installclean
make -j4 rompackage
This set of commands will clean out and rebuild your ROM package with the updated kernel.
CREATING ODIN PACKAGES
While not the most popular way for people to install your ROM, no guide would be complete without describing how to generate the ODIN-based installation packages. I like to provide a "Full Wipe" ODIN package that will take care of resetting the device while flashing the new ROM/Kernel, it's an easy way for people that are comfortable with ODIN to just completely replace the contents of their phone with your stuff. For this section, I'm going to assume that you are using GeeWiz Recovery, version 2.8 or later. Other recoveries will work, but as you may expect I'm most familiar with the one I made and I know for certain it has all the necessary features in place.
The ODIN factoryfs.rfs file must be generated by formatting the SYSTEM volume with RFS and then installing your ROM:
Copy your generated EDIFY update-zip to the SDCARD
Reboot into GeeWiz Recovery
Wipe the device data by selecting Wipe Device Data and then Wipe all User Data (Factory Reset)
Press the HOME key to return to the main menu
Format the SYSTEM volume with RFS by selecting Manage Volumes / Format Volumes / Format SYSTEM / Format SYSTEM [rfs]
Press the HOME key to return to the main menu
Select Install Update Package, and choose your EDIFY update-zip to install
After the installation is complete, reboot the phone by selecting Exit from the main menu. Not rebooting the device after the flash will result in a bad ODIN file more often than not. Trust me on this one.
After the device has fully booted, reboot it back into GeeWiz Recovery. The next step will be to generate a backup of the RFS-formatted SYSTEM volume to ultimately use with ODIN. GeeWiz Recovery can create these by choosing to execute a "raw dump" of the volume:
Select Manage Volumes / Backup Volumes / Backup SYSTEM / Backup SYSTEM [raw dump]
GeeWiz Recovery tries to keep volumes unmounted after it's done working, so the SDCARD must be mounted before the contents can be accessed with ADB:
Press the HOME key to return to the main menu
Select Manage Volumes / Mount Volumes / Mount SDCARD
GeeWiz Recovery will store the backup as /sdcard/backup/volume/SYSTEM-YYYYMMDD.img.gz, so as an example, I might pull it to my home folder with this command:
adb pull /sdcard/backup/volume/SYSTEM-20121022.img.gz ~/
The .gz file will contain a compressed copy of the backup, just open it up, extract the file, and then rename it to factoryfs.rfs. This is the SYSTEM volume for ODIN. There are also a number of other files you can include in your ODIN package to perform various other flash or wipe operations (I'll tell you where to get them, too)
boot.bin - Will replace the primary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
cache.rfs - Will wipe the CACHE volume; necessary if you want the device to boot into recovery automatically and run a command
dbdata.rfs - Will wipe the DBDATA volume
factoryfs.rfs - Will replace the SYSTEM volume
modem.bin - Will replace the CDMA modem
movinand.bin - Will wipe the DATA, PREINSTALL and FOTA volumes
param.lfs - Will replace the parameter block. Semi-dangerous to include, but required to ensure an initial boot into recovery mode
recovery.bin - Will replace the RECOVERY kernel and ramdisk
Sbl.bin - Will replace the secondary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
zImage - Will replace the BOOT kernel and ramdisk
To generate an ODIN-compatible tarball, gather the files you want to include and execute the following commands from a Terminal. Replace tarfilename.tar with the name you want to give the tarball, and replace file file file file with the names of the files from the table above you want to include:
tar --format=ustar -cf tarfilename.tar file file file file
md5sum -t tarfilename.tar >> tarfilename.tar
mv tarfilename.tar tarfilename.tar.md5
NOTE: If you rename the .TAR file, it will invalidate the MD5 checksum and you will have to md5sum it again.
OK, where to get the files. You can access a "full stock" ODIN package for the Fascinate, like the EH03 version that is available here on XDA to get copies of all the stock versions of these files. Or, you can use the ones from my ODIN "Full Wipe" package if you'd like as well. My ODIN tarball has a gimmick that you may find useful. If you include my copies of cache.rfs, param.lfs and recovery.bin, the device will initially reboot into recovery and automatically format the CACHE, DATA and DBDATA volumes with the EXT4 file system. It's a relatively simple trick, but an effective one to help improve the performance of your ROM. I also like to provide a "syskernel" tarball that includes only factoryfs.rfs and zImage. The benefit of this is that it will not wipe out any of your user's data. The downside is that the user may be responsible for going into Recovery on their own and executing any steps your EDIFY update-zip would have typically taken care of, like clearing the Dalvik-cache.
==================
For now, that pretty much sums it up! I can expand on this, or perhaps more appropriately compress it (I am a tad verbose!) based on feedback and how useful this little guide ends up being for everyone. Let me know -- PM me or post here in this thread, I'll see it either way!
reserved post
reserved 3
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Odined back to stock. Loaded full wipe 3.2 and everything is golden. MMS, WiFi etc works great.
Did have to restart before WiFi would start. ROM is a little laggy at first but once it settles performance is on par with other JB Roms:thumbup:
Thanks Mr.GeeWiz: looks great for a "beta"
Edit: speakerphone works great also, sweet^o^
Sent from my SCH-I500 using xda app-developers app
I still think in overall the ROM is laggy.
WiFi requires restart each time you switch it off.
Whatsapp is not working after SMS code verification.
Thanks DJP952
i decided to give this a try. everything works great. wifi did not require a reboot for me. camera, mms, wifi all work great. a little sluggish getting started, but pretty stable nonetheless. great work DJ. thanks
djp952 said:
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Click to expand...
Click to collapse
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
I can duplicate the Wifi issue and am looking into it. For me, it just took a REALLY long time for it to turn on, like 10 minutes. I think I know what I've done that might cause this and hope to fix it Getting the logs now.
edit: I think I see what the problem is, not sure why it hasn't been an issue with the "Media" version. I have to dynamically load and unload the Wifi driver to prevent bad things from happening, this isn't the usual way it's done. The OS is set up to start the Wifi "supplicant" automatically, when it probably shouldn't be. The supplicant can't load if the wifi driver isn't up yet. Sometimes it works, sometimes it doesn't, and when it doesn't Wifi will be hosed until the OS sorts it out. I have two solutions to try, the first is to see how Android behaves if I don't allow the supplicant to be started as part of the "main" service class, the second is to figure out that aforementioned bad thing and do it more properly. I'll get it. Sorry for the bug
Thanks for trying this guys! I never expected it to be as good as the "big" ROMs, and I wish I could do something about it being so ungodly slow for a while. It seems to pick up and work properly after all the apps have been updated and it's had a chance to do all the Google backups and whatnot that it wants to do.
One problem I saw yesterday for the first time that you might need to watch out for ... The battery TANKED in a matter of 2 hours for some reason. It looks like Google Search went off the reservation. I've also seen "GPS Status and Toolbox" destroy the battery if you don't close it all the way (long-press HOME, then swipe it away).
Oh, one cool feature we have now ... "Take Bug Report". Check in Settings/Developer options to see it. What this does is collect all kinds of logs and information about the phone and make an e-mail out of it. The default sends it to your GMail account. It's about 3MB, but it will be nice to have something everybody can use to gather logs for problem resolution rather than asking folks to hack around in ADB. So, if you run into weirdness, you can click that button, wait a while and watch scary "shell has been granted superuser permissions" pop up a lot, and you'll ultimately end up in GMail with something you can send you me or post parts of here! Great that Google added that in an accessible way finally!!
For the folks having trouble with turning Wifi on and off, I have an experimental/test patch for you. This patch will replace the GeeWiz 3.2 kernel with an updated version that changes the ramdisk/initramfs such that the wifi services are not started until Android requests them to be started. It may affect Wifi and Bluetooth Tethering, but my testing of the change here for both showed no ill-effects:
GeeWiz 3.2.1 Wifi Patch [Experimental] [EDIFY update-zip]
REMOVED: Please use official patch in the DOWNLOADS section of the main post​
NOTE: You will be asked to re-opt-into the Google Location service on the first boot, this is normal. I clear the "Google Services Framework" app on any kernel change now to avoid the well known Jelly Bean issues with losing connection to Google Services when you alter the kernel. This may have been fixed with JZO54K, but why risk it when all you have to do is click "Agree"
You may have to reboot once more after installing this to clear up the Wifi on/off problems so that the Android settings are synchronized with the changes. If after a second reboot this does not solve your problem, please let me know!
Rollback: This change can be rolled back by installing the EDIFY update-zip for GeeWiz 3.2 again on top of it without wiping data. I can also package/provide a more specific rollback that only undoes the changes if necessary.
Please let me know if this solves your Wifi issues or not, so that I can either post it as a primary patch for GeeWiz 3.2 (and GW Media 3.2) or take another crack at solving it Thanks!!!
djp952 said:
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
Click to expand...
Click to collapse
Hi!
Wiped data dalvik and cache & now I am on JellyBean. Thanks djp952. :good::good::good:
This Rom looks great and apart from the Wifi issue ( havent got time to update my phone with the patch for wifi issue as yet) which takes some time to start or sometimes just rebooted my phone altogether, everything seems to work fine. Had a problem verifying Whatsapp but used their "Verify by Call" method and now its working fine too. Battery life seems good to me as of now. Liked the inbuilt BLN.
Sadly, as i mentioned before, i lost my 1x/3g connectivity (nothing to do with this Rom) and thats Ok for a day or two till i try & figure out something to enable it again. By the way, i have always done the wipe through recovery only. Never used the factory reset option in settings menu. And that means the 1x/3g settings get wiped out the moment I wipe Data (note: wiping dalvik & cache does not affect it).
Anyways , looking forward for more developments on this rom from you.
edit... The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
QuickPic
swapnilss said:
The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
Click to expand...
Click to collapse
We are a little off topic, but... I too have had nothing but problems with the stock Gallery application... not loading at all, not showing pictures, generally being grumpy (okay, so I get that way too sometimes), etc.
Try Quickpic (http://market.android.com/details?id=com.alensw.PicFolder) , it's a free app that is a gallery replacement (ad-free too!). Just make it the default and you should be set. If, for some reason, you don't like it... Just uninstall and revert back.
As for the Jellybean ROM... too sweet! I love having an original Galaxy S with JB running on it! I get questioned all the time what phone I have, because it's running the latest Android build and doesn't look like any out there right now.
Sent from my SCH-I500 using xda app-developers app
I'll load up some huge amount of photos and have a look at Gallery. I could switch from using the Google Nexus version to the AOSP, if it shows any improvements. One bonus we could get there is that I enabled widescreen photos in the AOSP branch Didn't include it for various reasons, one I recall was that it would crash if you tried the "face detect" option.
I'll have a look -- maybe it can be fixed! I also have to download this "Whatsapp" that people are using ... never heard of it What does it do?
Thanks as always for the feedback guys! Glad it's going pretty well thus far
FYI for any aspiring developers, I've started making a "HOW TO" guide for building GeeWiz from scratch in Post #2:
http://forum.xda-developers.com/showpost.php?p=33011164&postcount=2
I've gotten as far as how to make the AOSP ROM and compile the kernel. At minimum, I need to add how to make the ODIN files as well, but maybe later. Depending on level of interest, I can go into as much as anyone wants there, short of how to make actual code changes (but I could try to help offline). I think describing how to get from source to the flashable files is a good first step, I'll see how it goes from there
DJ, you should link this on the home page of GeeWiz 2.9, so more folks can get this. Also, I think you should name it JellyWiz...
Can I ask what this is ?
AndroidGee209 said:
Can I ask what this is ?
Click to expand...
Click to collapse
JellyBean for the Fascinate, with GeeWiz recovery and kernel
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
where can i find the compass?

SystemUpdateService Wakelock Fix

My phone had a constant wakelock and it was draining my battery.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ with the name 'startsysupservice'.
Edit the script and put the following line in the file:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
NOTE: The correct way is for your ROM maintainer to update the sources with the new patch. Unfortunately, many ROMs are no longer maintained (especially for older devices) so this way is a good way to get around this issue for these ROMs. I originally created this for CarbonRom on my P769. I then switched to CyanogenMod 11 by dhiru1602 and this workaround still worked. It should work on other devices as well.
frostinide said:
My phone had a constant wakelock. After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/#/c/91021/
The fix I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime. I have P769 with CarbonRom.
Click to expand...
Click to collapse
Interesting info Frost..
and the script is a good idea. By the time I have Oneplus O2 OS all patched up, it will look worse than Frankenstein and I'll never remember all of the operations.
Frost,
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Thanks.
JeffDC said:
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Click to expand...
Click to collapse
I got that information from the CyanogenMod link I posted. You can see the patch there and see exactly what lines were changed for this fix.
I suggest you read the Android development documentation if you want to know how it all works.
I also found this link, but I can't vouch for its correctness as I don't have enough knowledge of how Android works: http://stackoverflow.com/questions/14548927/android-broadcast-receiver-vs-service
This is a major problem affecting all CM based custom ROMS. The problem is Carbon is not doing anything about it. If you go on their website, there is no new nightly for Galaxy S3 D2LTE - It has been the same ROM since 2014. When you boot the phone, it disables SystemUpdateService. So the phone never sleeps. Waiting for Carbon to Fix this issue.
So here's the real question...
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
ocd_amp said:
The problem is Carbon is not doing anything about it.
Click to expand...
Click to collapse
If you go to their website, they say they basically stopped working on KitKat except for certain fixes, and are concentrating on Lollipop.
https://carbonrom.org/on-to-sweeter-things/
You can check on their website for more info or if you want to try and contact them. Although I would say it's not really worth it.
I would just use the workaround that I posted (or any other workaround out there). It's not the cleanest solution, but it gets the job done.
ocd_amp said:
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
Click to expand...
Click to collapse
Check the link I put to the CyanogenMod fix. It has the patch showing the exact line changes and the files that have changed.
update!
Please check this thread.
[MOD] [v7.0.99] Google Play Services with System Update Wake Lock Fix
http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
Thanks a lot buddy.
From a battery drain of anywhere between 20-45% / hour, went straight to 0.3% / hour since the last 4 hours now ( was sleeping myself, but nonetheless the lower end aka 20% drain used to take place when I was sleeping.
Your fix has restored my battery life ( atleast in this short time I do feel that has happened)
Thanks again.
Hi there,
i got rid of the googleupdateservice wakelock by the above hack.
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
This is the only method I've found to work on my phone to automate the process upon boot. Thanks!!! I've tried about 10 different other ways, from init.d scripts to autoruns to appOps to modified play service apks to you name it.
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
noob to android said:
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
Click to expand...
Click to collapse
Sorry, no idea on that one. You should probably create a new post for that.
wasiq224 said:
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
Click to expand...
Click to collapse
Put in 'startsysupservice' as the name of the script. Then edit the script (there is an edit button at the top) and put the following line in there:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
After it's saved, edit it again to make sure the contents did actually save. If it doesn't work, you may need to save on your sdcard first and then copy it over manually with a root explorer.
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Dru79 said:
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Click to expand...
Click to collapse
Which are the new permissions for the file?

Updated 10-06-2019 ( ROM GUIDE ) How to install Android 9.0 through 4.4 on Touchpad.

----------------------- Thread MODIFICATION LOG -----------------
Shout out to Nevertells2 and DoubleStuff who both worked hard on this documentation in 2017. ( Some of which still remains )
Date:03/10/2017 Users: DoubleStuff/Nevertells2
Modification Description: Initial Release.
05/25/2019 DoubleStuff
Major changes in 2019: updated broken ROM/GApps by including HP_TOUCHPAD's master list of ROM/GApps, also fixed the YouTube broken link, made many additions to the documentation as per the changing landscape of the HP Touchpad development, most notably HP_TOUCHPAD's HpTp Universal Optimize Swap Settings and boot.img file.
07/08/2019 DoubleStuff
Created a Main Menu, with 2 options 1) Wipe All and 2) HP ToolBox.
8/3/2019 DoubleStuff
Implemented HP_TOUCHPAD's ROM_Reducer flash files.
8/27/2019 DoubleStuff
On the 2nd Post of this thread I added DoubleStuffs annotated journeys.
8/27/2019 DoubleStuff
On the 3rd Post of this thread I added HP_TOUCHPAD's advanced topic of the HP TOUCHPAD Novacom Repair Android Tool.
----------------------- Previous Zip Statistics -----------------
"The Original"
Obsoleted doubleStuff_v03.zip 3/19/2017 - 5/25/2019 ( RIP )( 797 days )( 7876 downloads )( 53306 views )
Avg. 9.87 downloads/day
"Double Stuff II"
Obsoleted DoubleStuff.2019.zip 5/25/2019 - 7/8/2019 ( RIP )( 045 days )( 372 downloads )( 3140 views )
Avg. 8.26 downloads/day
----------------------------------------------------------------------
Introduction:
In this "new" ( circa 2019 ) method of "starting from scratch", or called "clean installing", the user will flash various ZIP files depending on the ROM version user wants to install.
The actual install of Automatic_Wipe_All_and_Create_Android_with_Swap_Partition.zip ( boot.img ) will be done by the the script TPTB_WipeAll_TWRP_v02_win.bat. Wipe_All creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Boot partition is always 32 Mb, its a fixed size.
To be clear: this method will erase everything, even WebOS and makes the HP Touchpad 100% Android. It will also create new media, cache, data, system and SWAP partitions, and make the HP Touchpad work as a tablet ( laptop with a touch screen ), not a smartphone in Android.
Thoughts about the video:
The Video is now semi-obsolete, because alot has changed since 2017. So you must follow the instructions in this updated thread, but the video helps because if you understand the video you will understand the instructions in this thread. The Video below is Installing Nougat, but you can use this method for ALL VERSIONS of Android since 4.4 just use the proper ZIPs.
https://www.youtube.com/watch?v=KDu1bocZHqw
Assumption:
This method assumes you already loaded and have working TP Toolbox v0.42. ( w/Novacom and Java )
--- if you don't have TP Toolbox installed on your PC please watch the video in RolandDeschain79's link from 0:00 to 2:15 RolandDeschain79Link
======================================================================
Steps to success for loading any version of Android since 4.4:
Perform the following steps on a PC to prepare it for load:
I. Download the NEW DoubleStuff.7.2019.zip:( click link below )
Download DoubleStuff.7.2019.zip
DoubleStuff.7.2019.zip contains these two key files:
1. TPTB_WipeAll_TWRP_v02_win.bat
2. uImage.WIPE
Download and extract, and place both files in the same directory as your working tptb_v42_win.bat on your PC.
II. Select and Download which version of Android ROM, Gapps and other zips you want.
Locate and download the ZIPs: I will link to HP_TOUCHPAD's Master List of Zips: ( see Master list link below ), but you can also find ZIPs in other XDA HP Touchpad threads too.
Its best to put your downloaded ZIPs into a storage folder that you have created on your PC, purely for organization.
#1 ) ROM
#2) Pick one of these three Settings files for this #2 ZIP install: These files are in the "ALL files for this ROM" zip, then look under a folder of the same name, and then select the frequency zip of your choice.
-- MAX_Kernel_Ramdisk_build_prop_Settings ( Latest HpTp_MAX_Universal_Optimize_Swap )
-OR-
-- Stock_Kernel_Changed_Ramdisk_build_prop_Settings ( HpTp_Universal_Optimize_Swap )
-OR-
-- Original_ROM_Settings ( Use the Tablet with phone settings, no swap partition )
( The first two are the magic behind the performance and speed, because these settings enables Android to use the swap partition, the third is the original settings for the ROM and you will have better battery performance. )
All the Universal Optimize Swap Settings files provide the same settings and kernel, the difference is the preset CPU frequency. As per the Boost settings always start with 1674, and after that is working good, you can try to flash a higher frequency for speed like ( 1728, 1782 or 1836 ), and you don't have to re-flash all the ZIPs again, just the UOSS file from TWRP recovery. If it freezes screen, or keeps rebooting just go back and flash lower frequency, Because those symptoms are telling you that your particular HP TOUCHPAD can't handle the higher speed.
#3) ROM Reducer ( Optional ) These files are in the "ALL files for this ROM" zip, then look under the folder with name "ROM Reducer" then out of the 3 zip files in the selected folder, first go with the ROM_reducer, later if you want to permanently remove the features/apps, or restore the features/apps, you can use the "Remove" and the "Restore" zip files.
Essentially this HP Touchpad ( circa 2011 ) has around 650 MB of free RAM (Memory), this is relatively low, so the ROM Reducer flash file "removes" some Android Features and System Apps to give the old Touchpad some extra needed RAM. So in theory this will make for a faster experience.
#4) GApps
Select platform ARM and the android version that matches ROM and the variant you want, Pico is recommended. The goal is to keep the system "lean and clean", and by doing this you will get the best performance and efficiency.
#5) SuperSu v2.82 ( Optional )
ROMs have system Read and Write enabled, download and flash SuperSu v2.82 if you want root access.
#6 ) Latest TWRP ( Optional, but if you want and/or need a different version of TWRP other than 3.2.1-0, then you need to download one. )
==========HP_TOUCHPAD's Master Link: Get ZIP ( #1, #2, #3, #4 here )===========
Note: Once you click link, you have to press page down 3 times to get to the Master List of Zips.
Find all Android version: Rom, GAPPS, HpTp MAX Universal Optimize Swap Settings, and more links as per HP_TOUCHPAD here:
================Get ZIP ( #5 here )=============================
***You can Download and Flash the latest SuperSu zip to ROOT your device***
Root access with SuperSu v2.82
http://www.supersu.com/download
================Get ZIP ( #6 here )=============================
This "latest and greatest" TWRP for ALL VERSIONS OF ANDROID.
Download Permanent TWRP Recovery.
FLINTMAN-TWRP-3.2.1-0-03-15-2018.zip
Stick with the package you select, don't mix and match versions, and stay with WIFI version unless you know better.
Set all ZIPs that you have downloaded into the storage folder on your PC for now, we will need them later.
III. Touchpad/PC Execution steps:
Boot into WebOS Recovery ( giant USB symbol ) with cable connected to PC.
Run the custom script TPTB_WipeAll_TWRP_v02_win.bat:
It will give you the option of running the TPTB where you can perform some maintenance steps. Most users will select '1' to run WIPEALL from Main Menu.
III. Touchpad/PC Execution steps: continued
Most users will START here, after pressing '1' in Main Menu.
Continue ( press "c" ) with the TPTB_WipeAll_TWRP_v02_win.bat, it will then load the uImage.WIPE, you should see a quick blue flash, and an orange header with some white text. Wait until the orange header disappears, it will then automatically reboot. ( about 2 minutes ).
At reboot, select Recovery on moboot menu, then press home key.
Wait, and you will see the automatic load of 3.2.1-0 TWRP recovery.
Wait, and you will see Touchpad drive mounted on your PC.
TWRP recovery automatically creates a folder in the /data/media directory called TWRP, on the Internal SD card ( data ).
IV. TWRP Install steps:
( If screen falls asleep, and power and home buttons don't respond, tap screen )
Once in TWRP Recovery, go to your PC which is still connected via cable to TouchPad:
Locate the storage folder on your PC where you stored your ZIPs.
Copy the ZIPs: ( drag and drop )
1) ROM, 2) Universal Optimize Swap Settings 3) ROM Reducer 4) Gapps, 5) SuperSu and 6) Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP mounted Touchpad volume.
( P.S. actually you can copy the zips anywhere in 'Internal Storage' or 'Micro SDCard' Touchpad mounts, as long as you know where to find them on your Touchpad, I am just giving you the default location for simplicity sake )
2) Once copy is complete, you can disconnect the USB cable from the PC and Touchpad.
3) These zips will then show up in the /sdcard/TWRP or /data/media/TWRP directory on your Touchpad.
4) Select INSTALL from TWRP, drill to /sdcard/TWRP directory, then load in this specific order ( pressing 'add more zips' between loads )
== ROM,
== HpTp Universal Optimize Swap Settings,
== ROM Reducer,
== Gapps,
== SuperSu
== Recovery TWRP
then swipe to flash.
It will take awhile for the system to flash these zips ( about 5 mins ) until the reboot option shows up.
press reboot system button
At Moboot menu I selected "boot Evervolv" your menu item might be a different name depending on the ROM you installed.
During my experimental testing I loaded Evervolv Nougat and it took about 15 additional minutes until I got to the Android Start screen after "boot Evervolv" selected. Mileage may vary.... but soon your HP Touchpad will be in the promised land of Android with swap.
Advanced Topic #1:
DoubleStuff's Journeys to Novacom Repair Android Tool and Universal Authority: ( with annotated pictures!! )
Journey #1: How files get populated to /boot.
Journey #2: into HP RAMDISK: Using /boot from uImage
Journey #3: to Novacom Repair Android Tool: How are the icons made
Journey #4: Exploring Planet Universal Authority
Journey #5: RAM Memory Stress Test
...
..
Advanced Topic #2:
HP Touchpad Novacom Repair Android Tool
Hello Touchpad users, if you think your HP TOUCHPAD is bricked, your probably wrong and with the tools below you maybe able to fix your HP TOUCHPAD and make it like new again. Read the guide, and download the ISO file, now remember this is an advanced topic, its not for kids. Trix are for kids.
click HERE for guide
click HERE to download ISO file
...
..
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
W_three said:
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
Go have a read at this page in the DevsBase forum if you haven't already. It is discussed that there have been problems with the setup wizard.<Mod Edit: Link removed. Please don't redirect members to other mobile forums. Thanks!>
Also, I see in the discussion there that the nightly builds are now 4/13 so you might try that date build and see if the problem has gone away. I also saw discussed that some folks there were installing older builds that did not have the setup problems and then using TWRP to flash the newest builds. Otherwise, from what you posted, you are doing everything right.
NT
W_three said:
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
This part I don't think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
As long as the Media is greater than 1000 MB it should be OK.....
Essentially the program TWRP_TmpLoad_v03_win.bat loads TWRP temporarily by using a novacom command to load uImage.TWRP to the HP Touchpad, but you still have to download and have as one of your 3 zips something like this FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip, so that you can have a permanent load of TWRP after all is said and done.
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Seatreader said:
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Click to expand...
Click to collapse
No your not doing anything wrong, the new nightly builds are going through a particularly buggy phase the last few builds. I am assuming you used the 4-19 nightly. Lets try an earlier Testing build.
If you have time, just for kicks and for testing purposes can you try again but use Flintmans latest testing 3-25 ROM instead of the Evervolv Nightly.
Try this ROM and lets see if it fixes the issue:
http://evervolv.com/static/builds/testing/Queo/ev_tenderloin-7.1.1-testing-2017.03.25.zip
If you notice the user "w_three" had the same issue in an earlier post on this thread....
okay I'll give that a go tonight! I noticed on the release page forums they were talking about how you had to dirty flash the newer roms on and figured that was my problem.
=UPDATE=
Ran as per the instructions with a nice clean install and it booted fine! Takes forever to boot and get through the" finishing touches" but it looks like it's working fine!! Four days ago this tablet was bricked!
Thanks for all the help!
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
W_three said:
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
Click to expand...
Click to collapse
Great! W_three, that you finally got it working, from what I have been reading on devs-base, Open Gapps are only running through 7.1.1, and as of April 4th (4/4) Evervolv nightlies have switched to 7.1.2. ( see pic below ) Some people have a theory that this is causing the set-up wizard to break. To get around this issue, some people have been "clean" flashing an older 3-25 ROM see link to that in post #8 ( or in theory anything before 4/4 nightly ), then "dirty" flashing the newer ROMs on top of that. I am just reporting on what I read, not sure how accurate it is.
See in below screenshot how name changes from 7.1.1 ( green ) to 7.1.2 ( red ).....just sayin'
{
"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"
}
Just know that this Nougat ROM is still only in Beta, so there will be bugs and lagginess.
As Nevertells2 would tell anybody, JC Sullins KitKat 4.4.4 ROM is probably the most stable.
Setup Wizard fails
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
xdakzhf2d said:
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
Click to expand...
Click to collapse
Well underneath that red letter explanation in the Original Post, is a link to a 3-25 ROM, flash that using the alternative method described in OP. That is called a clean install.
Then once you get that going, you can dirty install the current 5-8 ROM, by selecting this once tablet is running:
Settings->About Tablet->Evervolv Updates->Nightly Tab->Refresh, then download the zip, and boot into recovery and flash it. If you don't understand this terse explanation, I have pasted RolandD's How to dirty flash and root video below ( from 1:19 to 3:17 is Dirty Flash )
Dirty Flash Instructions
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
deafasheck said:
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
Click to expand...
Click to collapse
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Missed a step.
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
DoubleStuff said:
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Click to expand...
Click to collapse
deafasheck said:
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
Click to expand...
Click to collapse
Hello deafasheck, I am glad your learning and taking the advice of Nevertells2 which is "read, my friend, read!!"
Yes the Stock Camera is still inverted, but haven't you heard? That if you go to google play store and download "Open Camera" app it works fine in Nougat, let me know what you think of it. I am glad you figured out your own problem that is telling me you are learning quite a bit since you were a "newbie" in 2014!! :good:
OK deafascheck I wish you luck in your dirty flash download? And your experiment with "Open Camera" and hope you learn how to code at least in BAT and VBS files, because when Oreo ( Android "O" ) comes out we will need to tweek the code for this Alternative method again!! I am doubling down that its called Oreo, hence my Avatar.
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
deafasheck said:
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
Click to expand...
Click to collapse
deafasheck, defasheck, defasheck, come on now we have been studying "dirty flashes" since you were a "newbie" in 2014, and our friend RolandD has made many videos on it....in fact in this ROM alternative thread in post #13 at the bottom of the post is a good video that explains "dirty flashes"....learn it, love it, live it!!!
Good Luck in all your learning Deafasheck!!! :highfive:
POST #13 for deafasheck learning dirty flashes.
Videos don't help much, I'm deaf as heck.. and getting lost in the steps.. from what I recasll dirty flash is asop I did one as I had in the original install ie placed in twerp flashed from twerp. that worked as far as I know? I'm trying to find the super user link I seen earlier, once I get ROM and SU I'm gonna get the camera app. thanks..

[ROM][Stock] Moto-Lite Stock Android 7.0 ROM for xt1575

Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••​
{
"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"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM​
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.

Categories

Resources