Develop Bugs

[Q] Correct Upgrade Path from 3.2 Gen2 to Custom ROM

Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks

You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App

NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.

Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked

Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.

From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App

masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!

I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...

Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip

Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip

I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium

toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.

Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.

NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.

This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.

NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.

Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.

NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.

I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.

[Q] 4.2.2 OTA "Error"

My phone prompted me today that an update to 4.2.2 was available.
Its a takju Nexus running with an unlocked bootloader and rooted but otherwise stock rom.
I've tried to get it to do the update, however it reboots to a screen saying "applying system update" then after a few seconds flicks to a screen with an android with an exclamation mark, and the word Error below.
Is this because i'm rooted? or is there something else going on?
Thanks
Kevin

Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.

I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.

chelseaeuro said:
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
Click to expand...
Click to collapse
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.

reysonance said:
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
Click to expand...
Click to collapse
I did that and my update is gone lol. Guess I'll have to wait for a few hours.

I had to force stop the frameworks and then try updating, which worked. Thanks!

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Thanks
Just to confirm, if i flash the system.img over my current system, will that delete all my installed apps/data? Which system.img should i be flashing? the one from 4.2.1?
Is there a list somewhere of the version numbers for the various parts (recovery, radio, kernel and bootloader) so i can check they are correct?
Also, is there a way i can flash the OTA update with some error logging or debug output turned on, so i can see what its actually failing at?
Cheers

Yes, the one from 4.2.1, check under Maps > Settings > About, it should gives you the version you're currently running, download it from the factory images page if you haven't already, and no, it should not wipe any apps+data, but back it up anyway if you're worried, better safe than sorry, I'm generally paranoid about data so I always backup, but no it shouldn't wipe anything. You'll lose root and that's it.
And for the bootloader and all that, it all should come all packaged on the factory image, so if you flash 4.2.1 via toolkit, or manually and haven't installed any radio or kernel you should be safe. IIRC, the bootloader version is PRIMELC03, the radio is XXLH1.

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Very thanks for this explanation. It help me a lot and I finally could update via OTA.

UPDATED 12/15 [ROM][P900][P900UEU1BNK1] Original Stock and Debloated Stock Variants

Original Stock and Debloated Stock Variants for the Samsung Note 12.2 Pro Wi-Fi Version
​
These roms are simple flashable zips that you can flash from your custom boot manager. It does not use an aroma installer. Instead I made two versions. This should avoid almost all the problems people were having because there are not modifying options in the installer before running it. It is based on the latest software out officially for this model: P900UEU1BNK1
Device and Firmware Info:
Model: SM-P900
Model name: GALAXY NotePRO 12.2 Wi-Fi
Country: Cellular south
Version: Android 4.4.2
Changelist: 2582108
Build date: Mon, 10 Nov 2014 02:08:13 +0000
Product Code: XAR
PDA: P900UEU1BNK1
CSC: P900XAR1BNK1
MODEM: P900UEU1BNK1
Originated from: http://www.sammobile.com/firmwares/download/39463/P900UEU1BNK1_P900XAR1BNK1_XAR.zip
YOU NEED TO HAVE A CUSTOM BOOT LOADER. i.e. you will need to have tripped your knox counter. There is no way for the P900 currently to have a custom bootloader and not trip knox to 0x01. Some of the non-wifi variants using the snapdragon setup can do this with TowerlRoot. We cannot
Custom Bootloader:
I use TWRP version 2.8.0 - INSTALL WITH ODIN NOT THE MANAGER.
It can be found here: Download TWRP
Once you have installed the custom bootloader you can now load roms and make and restore backups for your device. The first thing you should do at this point is boot into TWRP and immediately MAKE A FULL SYSTEM BACKUP. First, before anything else. Do this to be safe.
Next you need to choose which version you of the rom you want to flash. Both of these were built mostly from ArchiKitchen and then I did some modifying after but I need to thank JustArchi for making this easier to put together for you guys, take a look at it here. Most will probably go for the debloated version, but some people like an untouched setup.
Steps to Install:
1. Copy this version onto your device, I use my SDcard.
2. In TWRP, go to wipe, advanced wipe and check Cache, Dalvik, Data and then wipe. This seems like it takes a good 5 minutes so don’t think it’s locked up. Let it do it’s thing.
3. Go to Install, select the flashable zip. Flash.
4. You can reboot the system at this point.
5. Startup should bring you to the 4 dots google splash screen. First load takes a few minutes let it do its thing.
6. Setup your device, done. Enjoy.
Near Stock Untouched Version:
This version the system has had no debloating freezing or removal of apps. This version has simply been Rooted, Zipaligned, Deodexed, Added Init.d Support, Busybox Support, Knox has been removed, and supports custom Boot Animations. This is the closest you can get to how the device comes new. The near stock untouched version can be found here:
Click to Download the Near Stock Untouched Version
md5: b337d0b4f01e96ad869b0f7e55ebaac7
Debloated Version:
This version the system applications have been modified to greatly improve performance of the device. This version has been Rooted, Zipaligned, Deodexed, Added Init.d Support, Busybox Support, Knox has been removed, and supports custom Boot Animations. On top of this it has been debloated by removing and freezing apps. Below is a list of apps that have been frozen or removed. The debloated version can be found here:
Click to Download the Debloated Version
md5: 1993c45dc71dedd7b65e2575b9a57740
Apps that have been removed:
Books.apk
Chrome.apk
Magazines.apk
talkback.apk
Videos.apk
Blurb.apk
Flipboard.apk
FWUpgrade.apk
InteractiveTutorial.apk
MediaUploader.apk
MobileTrackerEngineTwo.apk
PickUpTutorial.apk
PreloadInstaller.apk
RoseEUKor.apk
SamsungSans.apk
sCloudBackupApp.apk
sCloudBackupProvider.apk
sCloudDataRelay.apk
sCloudDataSync.apk
sCloudQuotaApp.apk
sCloudSyncCalendar.apk
sCloudSyncContacts.apk
SNS.apk
SPPPushClient_Prod.apk
TravelService.apk
AutomationTest_FB.apk
BluetoothTest.apk
HwModuleTest.apk
WlanTest.apk
NoiseField.apk
PhaseBeam.apk
video
LowBattery.ogg
PowerOn.ogg
TW_Silent_mode_off.ogg
TW_Volume_control.ogg
Apps that have been frozen:
LocalFOTA.apk
AccuweatherTablet2014.apk
AntHalService.apk
ANTPlusPlugins.apk
ANTRadioService.apk
BBW.apk
ELMAgent.apk
eMeeting_HANCOM.apk
Kies.apk
MyMagazine.apk
NYTimes.apk
PCWClientS18.apk
Pinboard.apk
RemotePC.apk
Samsungservice_xlarge-xhdpi.apk
sCloudSyncSBrowser.apk
sCloudSyncSNote3.apk
SFinder.apk
Twitter.apk
watchON.apk
WebExMeetings.apk
If there is an APK you need that was removed, and you honestly cannot find it yourself, I can pull it from the stock folder for you, but don’t be lazy. Only ask if you really can’t find it yourself.
APKS Users May Want Back Individually
Samsung App Store thing: Samsung Store Apk
If you use the air command function with the S-pen and want back sfinder or the clipboard function.
Use Root Explorer or a similar app and browse to /system/priv-app/ rename both Sfinder.apk.bak and Pinboard.apk.bak to Sfinder.apk and Pinboard.apk (remove the .bak extensions). Reboot your tablet.
Disclaimer:
Your warranty is most likely already void if you have completed the steps to actually flash this ROM, I am not responsible for anything you do with your own device, if you can't follow directions or read that is not my problem. Follow Directions as they are listed and you should be fine. Knowing all this you do this AT YOUR OWN RISK!
Things that will make your tablet even better:
The Xposed Framework
The Xposed Framework is a custom framework using a hook that works on top of stock android systems that have root access. It is made by Rovo89 and the general thread can be read about here: Click Me!.
The Xposed Framework uses components called modules, which can be loaded on the device in various combinations to achieve many of the functions that used to only be provided by fully customized roms. I use several on my device and will list each below.
Recommended Xposed Framework Modules:
Activity Force New Task
App Settings
Boot Manager
Burnt Toast
Cool Tool
CrappaLinks
Disable Clear Dialogues Default
Disable Batter Full Alert
DitheredHoloBackground
KitKat SD Card Full Access
Remove USB Storage Warning
Samsung Keyboard Short Delay
Smooth System Progress Bars
Wanam Xposed
XVolume30
Xposed Recent Tasks Ram
YouTube AdAway
Allow Youtube Fullscreen HDMI
Old Versions:
P900UEU1BNI2 September 2014
Stock
https://www.androidfilehost.com/?fid=95747613655040578
md5: 97ba25203862f75cac18c91f44cb427c
Debloated Stock
https://www.androidfilehost.com/?fid=95747613655040601
md5: 19849ea3b143ba3f376405341764b8b3
P900UEU1ANC5 August 2014
Stock
https://www.androidfilehost.com/?fid=23622183712461879
md5: 0c2020121d2ae93dcda47acd1e4a1b04
Debloated Stock
https://www.androidfilehost.com/?fid=23622183712463362
MD5: 5eed908f12bb29f3319d56e64b09d10b
XDA:DevDB Information
Gatsrom, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
Gatsrom
ROM OS Version: 4.4.x KitKat
Based On: Stock Touchwiz
Version Information
Status: Stable
Created 2014-08-27
Last Updated 2014-12-14

In case I need more room for something??
Oh I know, one thing. I'll volunteer to do this each time we get a new android version for our tablet. Time permitting.
Whats next?
1. If enough people ask for an app added back in I'll put it back in.
2. I'm experimenting with a version that has the Xposed framework and my setup cooked into the rom.
3. I'm also experimenting with some manual theming and tweaks to add into it, but I don't want to go crazy with it.

Awesome! Thanks for this!
Question: How does one go about developing these variants? Is it a matter of customizing an install through the tablet itself and then making an image of it or is development done completely offline on computer?
I'm curious because I'd like to experiment with making a debloated ROM myself just to play around with.
Thanks!

yay double post

muzzy996 said:
Awesome! Thanks for this!
Question: How does one go about developing these variants? Is it a matter of customizing an install through the tablet itself and then making an image of it or is development done completely offline on computer?
I'm curious because I'd like to experiment with making a debloated ROM myself just to play around with.
Thanks!
Click to expand...
Click to collapse
I do it on a computer completely. That way nothing from my device is taken personally like info etc. Plus it's cleaner. Main thing is you need Linux first and foremost or at least a vm setup running linux. I use ubuntu/kubuntu. That is how the image, kernel etc is compiled and smushed together. I do not think there is a possible way to build a linux kernel in windows.(?) The app removal/freezing is one of two ways. One I have a txt file with the apps names and/or dirs that I can tweak as needed and it will just rm them as it goes through the list. The other way is i go into the system/app folder before building it and modify the apks directly. This is how I do themeing changes, which I may or may not do for the note. For freezing I add .bak to them so they are not loaded.
While doing this I got our device added to the archikitchen database, so you no longer will need to manually enter the boot sector. It should autodetect the blk upon startup.

Wow, I'd love to learn how to do this so that I can tinker with making a slimmer touchwiz rom. Guess I got my work cut out for me on doing research.

Thank you!

Thanks man, this is great!
Sent from my SM-G900P using Tapatalk

Thank you SO very much ! I'm downloading the debloated version now. You rule !
Update: I'm up and running on the tweaked ROM ! I wanted to share a few things my 900 did so others will know...
... During the Dalvic cache wipe, the device suddenly rebooted! I got to the Samsung splash and it hung. I rebooted into twrp, then did the other three wipes first and waited for the 'successful' notification. Once I saw that, I rewiped the dalvic cache w/o problems and continued.
... during the actual flashing of the ROM, I expected the 5 minutes or so load time indicated by the instructions. Mine was closer to two minutes and it rebooted. The status bar had barely crept into the blue... It totally freaked me out, but I let it ride and soon was looking at the Google 4 dots screen. that lasted maybe 2 more minutes and I was up and running. So, don't panic if it happens to you too
... I saw you mention Xposed; for what it's worth I pretty much always load boot manager and App Opps; they are great! Occasionally I'll go for xPrivacy too, but haven't so far. I would suggest looking into AdAway as well ( an app, not a module )
thanks again for making this ROM!

Up and running here also! All went smooth. Nice fast rom. Looking for reboot menu but using same Samsung default color scheme!

Man!! Thanks so much! I cant wait for work to be over so I can get this cooking!!

----> Resolved......
I'm a little confused with how to get into TWRP. I downloaded the correct img and installed TWRP manager.. went thru the steps with busybox etc.. but when I reboot into recovery..
I get the following:
Android system recovery <3e>
KOT49H........... etc...
Reboot (which reboots back in normal tablet)
Apply update from ADB
Apply update from EXT storage
Wipe Data/Fac Reset
Wipe Cache
Apply update from cache
on the bottom of screen
#manual mode #
Apply Multi CSC
Applied the CSC-code : XAR
Sucessfully applied multi-CSC.
Until I know what to do, I just rebooted back into the normal factory os I been using.
I been using TWRP on other devices so I know something is going on here.. Please let me know what to do next.
Thanks!

I rooted using odin. The booted back into download and again used odin for twrp. Did my backup. Then wiped and installed the .zip. rooted and working.

amityg said:
I rooted using odin. The booted back into download and again used odin for twrp. Did my backup. Then wiped and installed the .zip. rooted and working.
Click to expand...
Click to collapse
Ok, thanks.. I used odin to root when I first rooted. But I didn't think we needed to use odin to load twrp but I guess I was wrong.

flipper2006 said:
Ok, thanks.. I used odin to root when I first rooted. But I didn't think we needed to use odin to load twrp but I guess I was wrong.
Click to expand...
Click to collapse
I just think for me it is easy. I saw three different ways to install twrp and I find Odin better then adb

amityg said:
I just think for me it is easy. I saw three different ways to install twrp and I find Odin better then adb
Click to expand...
Click to collapse
I ended up using flashify a 2nd time and it worked correctly, not sure why I had trouble the other times, but im up and runnin'

flipper2006 said:
----> Resolved......
I'm a little confused with how to get into TWRP. I downloaded the correct img and installed TWRP manager.. went thru the steps with busybox etc.. but when I reboot into recovery..
I get the following:
Android system recovery <3e>
KOT49H........... etc...
Reboot (which reboots back in normal tablet)
Apply update from ADB
Apply update from EXT storage
Wipe Data/Fac Reset
Wipe Cache
Apply update from cache
on the bottom of screen
#manual mode #
Apply Multi CSC
Applied the CSC-code : XAR
Sucessfully applied multi-CSC.
Until I know what to do, I just rebooted back into the normal factory os I been using.
I been using TWRP on other devices so I know something is going on here.. Please let me know what to do next.
Thanks!
Click to expand...
Click to collapse
Odin definitely odin. What you described is the manager not correctly installing twrp. I never use the manager for anything. Always odin. Simpler.
edit: actually going to add that to the first post.

Check out Flashify, it worked very well. I had downloaded the img ahead of time but it found the correct one anyhow..
regardless... It's now 7 hours later after flashing and loading my stuff back. 0% battery drain where before I had around 1-4% and nearly everything was greenified.
Thanks so much ...
PS. I hope we start seeing a bunch of these now that this is proven that it will work!

I get it setup and all is working. Use twrp to get a backup. Then after each reboot it will not remember my home WiFi password. Looking online now for solution
Installed backup and no longer have the problem. I did have to install the sdfix app because I could not get my mail app to export settings.

amityg said:
I get it setup and all is working. Use twrp to get a backup. Then after each reboot it will not remember my home WiFi password. Looking online now for solution
Installed backup and no longer have the problem. I did have to install the sdfix app because I could not get my mail app to export settings.
Click to expand...
Click to collapse
That's weird, I didn't have that problem, only issue was on first boot, Rom Tool Box wouldn't load, but after restarting, its been fine. No issue with Wifi here

[Q] Dev Edition: Cannot apply OTA update 2.22.1540.4, fails partway through

I have the AT&T version, but I did S-Off, converted to the Dev Edition (CID BS_US002) and now have the stock recovery back on because I'm trying to apply the OTA update which provides a patch to the GPS.
I've applied a previous OTA successfully (after I went back to a stock recovery, of course).
But this time, it fails partway through and shows the red triangle with exclamation point. I was able to boot the phone to Recovery and do a Vol+ & Power which enabled me to select a handful of different options, chose to do the option of installing an OTA .zip file. Anyways I browsed to the OTA file in internal phone storage, executed it and it stops and fails on the following message: "cimext9.odex has unexpected contents". I am stumped because Google couldn't help. But, something similar happened to another person and they had installed Adaway which must have changed system files. I did have AdblockPlus installed for a while but uninstalled it - so could ABP be the culprit, and now what are my options that would enable this OTA to get installed on my phone?
Thanks in advance. Still learning, appreciate the help this board has provided me so far.

I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4

It looks like I'm going to have to flash the stock ROM again because something apparently isn't stock anymore.
Can I do this but keep the apps installed, contacts, music/files, etc? Or does it go back to factory reset?

When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long

oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?

oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
oaklandm said:
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
Click to expand...
Click to collapse
Yeah I do not have THAT much, but I've done this a few times and have things just the way I like them. Oh well.

us3rnotfound said:
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
Click to expand...
Click to collapse
I meant grab the nandroid backup, don't know if just a factory restore from the menu would do the job. I just thought that if I'm starting from scratch then I might as well flash .3 : )

Stock Rom D851-20G Flasheable Zip (07 Oct)

D85120G-Untouched_Stock_Restore.zip
Flash Full Stock (system/kernel/modem/recovery) No Root, No Mods, 100% Stock

Thanks.

Since this is the full rom, not OTA, has anyone successfully twrp from stock rooted 20e and then SuperSU and kept root? Will TiBu frozen system apps stay frozen as well? TIA

What exactly is this rom?

cenwesi said:
What exactly is this rom?
Click to expand...
Click to collapse
The name of the zip file and first post tells you what it is.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

do we flash it through TWRP? or any other custom recovery?

Yes, just as you would w/ any other ROM. Perform a full wipe beforehand, excluding both internal and external storage. And if you want to retain root and recovery, make sure to flash those immediately after (add them to the queue in TWRP).

Just flash this rom.. Everything works fine..
Sent from my A1-840FHD using XDA Free mobile app

This may be a stupid question but I flashed this and it says I'm still vulnerable to stagefright, isn't this suppose to patch it.
Sent from my LG-D851 using Tapatalk

I flashed the same 20g ROM, and according to the Lookout Stagefright Detector app, my device is not vulnerable to Stagefright.

works but
Followed these instruction using twrp
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
I had to reset phone after flashing and setting up. Because the phone was no functioning correctly.
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to
Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
So here we go again in the waiting game.
Wouldn't it be better if google took Stagefight out of the rom, so it can could be updated in play store?

painless
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!

Works Great
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3

fc3211 said:
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
Click to expand...
Click to collapse
Thanks for the two links. Very helpful

Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.

skipaaa said:
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
Click to expand...
Click to collapse
I landed here because I tried the 20e to 20g update and got the "unexpected version" error via twrp. Responding to my own post cuz I got bold and did it anyways.
...So, I had TWRP 2.8.7.0 D851 installed. Did full backups with Titanium paid version and TWRP. Started with STOCK rooted d85120e, left it rooted, and used TRWP to install
1) STOCK d95120g from top of this thread,
2) TWRP d851 2.8.7.0 found elsewhere (above link is 2.8.6.0), and
3) the SuperSU zip from link found just above.
Rebooted system without any wipes. A few minutes to update apps on first reboot and mostly good to go. Had to update SupserSU binaries via normal mode, and reinstall busybox. Busybox froze on black screen on multiple attempts during it's startup check, so on next attempt, I didn't let it finish the check, just told it to install, and has been bliss all day. So far, so stable. Better have the backups and not need them than need them and not have them. Settings show D85120G and Lookout shows NOT vulnerable to stagefright.
Sitting pretty. Hope this helps others who couldn't use the 20E to 20G update method to keep stock roms with optional root.

Wiped everything as stated and flashing reboots TWRP, anyone know why this happens?

Thank you! Works - rooted 20e to 20g
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
I was on rooted 20e and did what you said. Works like a charm, I have 20g now without any problems. Thank you everyone! :]

I finally came out of lurk mode to say thanks. This untouched ROM has saved me from 2 soft bricks. Works flawlessly.

it has no sound please help