My first ROM Flashing [MoKee]

My first ROM Flashing [MoKee] - Motorola Atrix 2

Hi all
I flashed my stock ROM for the first time. I thought i would write a bit about the process and my impression of the ROM.
This is what I did:
Download the ROM zip and place on the SD card.
Download the corresponding gapps and place on SD card
Make sure that the USB drivers for your phone are up to date
Root the Phone. You will find the *.bat file that i used for rooting Atrix 2 in the forum itself.
Install BMM. I read on a lot of places that BMM is dead but it was recommended by my ROM's web page so i stuck with it.
Boot into BMM's recovery console.
Select System 1 (or system 3-6 in case you want to multi boot)
Take Fast/Full Backup
Take backup of CID
you still want to ahead? this is the point of no return.
wipe stuff. the console has a section dedicated to wiping various type of data
format /system, format /cache, format /data
Flash the ROM zip
When Flashing is done, BMM will auto install BMM on the same partition. if that is not done, manually install BMM on system 1 using System Keeper
Flash the gapps zip
Reboot and enjoy.
My impression of the whole process is that it is rather silly. it is needlessly intimidating. most of it can be easily automated. Hopefully we will get better software over time which will make the process painless.
My Impressions of Mokee:
Pros:
Much faster than stock
tons of options that i am yet to explore
very stable, no crashes at all
Looks and feels like AOSP which i like
Cons:
Battery drain. My battery got drained in 6-7 hours. I am still investigating this.
Huge icons. So far haven't found how to make them smaller. More irritating that a critical issues though.

Rishav Sharan said:
Battery drain. My battery got drained in 6-7 hours. I am still investigating this.
Huge icons. So far haven't found how to make them smaller. More irritating that a critical issues though.
Click to expand...
Click to collapse
Install BetterBatteryStats, and allow root permission to it, it will help you tracking battery usage
---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------
If you want pure stock experience, try CM 11

sameerm02 said:
Install BetterBatteryStats, and allow root permission to it, it will help you tracking battery usage
---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------
If you want pure stock experience, try CM 11
Click to expand...
Click to collapse
Thanks. Btw, MoKee is very near the pure stock experience as well. Their design was to take the stock android and the best bits from CM and package it. I finally decided to go with Mokee over CM as i felt they were way more active in their checkins.
If there was any bug fix from CM side, they usually pick it up and merge it asap. else they seem to be fixing a lot of stuff on their own.
Another con of MoKee that i forgot to write:
they preinstall 4-5 chinese applications which i found irritating. The first thing i did after installation was remove all of them.

Rishav Sharan said:
Cons:
Battery drain. My battery got drained in 6-7 hours. I am still investigating this.
Click to expand...
Click to collapse
Try Xposed-Greenfiy:it's amazing
BetterBatteryStats: as Rishav Sharan says， find out which apps keep your Wakelock all the "deepsleep" time
Xposed-Per App Hacking:sharp wakelock blocker

U won't find a better recovery than BMM..what's so complex about it i cannot understand..if u had been here two years earlier when there wasn't even a recovery on boot u will understand..BMM= perfect custom recovery
Sent from my MB865 using XDA Premium 4 mobile app

devilhunter47 said:
U won't find a better recovery than BMM..what's so complex about it i cannot understand..if u had been here two years earlier when there wasn't even a recovery on boot u will understand..BMM= perfect custom recovery
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think ROM installation right now is where PC OS installation (OS2, Win 3.1 etc) was 20 years ago. You had to do every bit manually. Except nowadays its incredibly easy and even non tech savvy people can easily do it. I expect that the process gets easier for newbs in the next few years.
Take it as you will, but there are a dozen improvements to the process that can be done to improve it.

Rishav Sharan said:
I think ROM installation right now is where PC OS installation (OS2, Win 3.1 etc) was 20 years ago. You had to do every bit manually. Except nowadays its incredibly easy and even non tech savvy people can easily do it. I expect that the process gets easier for newbs in the next few years.
Take it as you will, but there are a dozen improvements to the process that can be done to improve it.
Click to expand...
Click to collapse
With whirleyes not supporting BMM anymore...i dnt see it improving any further.....Because BMM isnt built for the A2..we run it after making subtle modifications and customizations to the app...
And i dont see a new Boot manager being built from scratch..... BMM is already very perfect for me....Cant find a safer and better Bootloader for our a2 and i doubt there ever will be
And ABOUT the CM vs Mokee , CM wins hands down , it gives nearly 3 times the battery backup of Mokee...
I loved the asthetics of mokee.. i tried to do everything could do to have better batetry on Mokee(Like using the CM kernel directly , flashing JBX and stuff i better not go on about ).... But the ROM just refuses to let go off sucking battery all the time...I knw they update their kernel with newer commits from CM but trust me on this...i held on to Mokee as long as i could but the truth cant be denied...it just sucks wen it comes to battery consumption

Related

[Q] Trying different roms

I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.

Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.

NeverToLate said:
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Click to expand...
Click to collapse
By all means go for it! I have a few tips for you, as one flasher to another
As redpoint said, each time you flash a new ROM you are starting from scratch. This only refers to your personal data and ROM settings, though. There are a few ways to guarantee that you won't be spending a long time configuring each ROM:
Cloud Storage is your friend! I personally use Dropbox to save anything important to my daily use since I can easily pull up documents stored there from anything connected to the internet. There are much more secure options to store files on the cloud, but you have to pay for the more secure options, and security is not of top importance to me (since I just store homework assignments and basic documents).
Use Google Backup! When you flash new android ROMs, there is a prompt that asks you if you would like to backup your phone to Google's servers. I usually hit yes to this prompt. After you have done this once, when you flash a new ROM and enter your Google account, any Play store apps you had installed will be redownloaded (including any personal data associated with the app, IF it's developer has enabled this feature). It's not a perfect way of restoring your apps, but it sure beats re-entering all of your data each time you want to try a new ROM.
Use services to store your contacts! I took a few days to enter ALL of my contacts into my Gmail account, and it was one of the best decisions I have ever made. Each time I restore my phone, I have all of my contacts available. People who complain about losing all of their contacts along with their phone need to learn about this point.
Remember that your SD card partition stays intact between ROMs! Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Avoid using tools like Titanium Backup to restore apps! For a while I decided to use Titanium to restore apps. After a while I realized that all of the errors I was experiencing was the result of mismatched phone IDs, cache errors, and a bunch of other small glitches caused by Titanium backup. It is not the fault of TB and it is still a useful tool, but using Google backup to restore your apps is much cleaner and will result in fewer errors.
Save your text messages! Titanium Backup has the option of saving your text messages as a .xml file, but this is more complex than just using play store applications like SMS Backup & Restore. If you don't back up your SMS, you will look totally unpopular when you keep flashing your phone (and have no text messages at all)!
I hope this list helps you out in your flashing journey. Don't be afraid to try new things, and remember that if you can get into recovery mode, you will be fine (ESPECIALLY if you back up your data in the ways I described).

Thanks for tips
As far as saving everything as you posted. I don't have really that many documents I need and I am a big fan of dropbox haha. As far as my contacts any contacts I put in my phone automatically go to my google account so they always transfer over for me.
I usually delete most text messages at night and that's when I will flash these ROMS as I will not be texting anyone later in the night so, no worries there.
I really only have a few apps that I use, so even if they don't reinstall it doesn't take long to find em.
My main focus of now is just downloaded the roms I want and putting them all on my sd card. Whenever I have time to flash em all I will set them up kind of the way I want em with my apps, then set up the next ROM.
When that process is complete I'll just test each one for a few days/weeks till I find the perfect one for me haha.
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?

redpoint73 said:
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
Click to expand...
Click to collapse
I don't have to do reset between nandroid backups do I?

NeverToLate said:
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!

NeverToLate said:
I don't have to do reset between nandroid backups do I?
Click to expand...
Click to collapse
Going between nandroids? No, recovery is going to overwrite the user data with the user data from the nandroid, so I don't think you need to worry about it.
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
gridlock489 said:
Remember that your SD card partition stays intact between ROMs![/B] Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Click to expand...
Click to collapse
In theory, that is supposed to be true. But many people (including myself) have had instances of some or all of the SD contents erased or corrupted. The exact cause has still not been found, but possibly just a bug of the phone. I've had it happen several times now. If you have anything irreplaceable on the SD, I would suggest backing it up to your computer, Dropbox, or whatever, before flashing anything. This includes photos of videos that you took, and anything else not easily replaced. Backing up one known good nandroid is not a bad idea, either, just in case.

gridlock489 said:
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
Click to expand...
Click to collapse
I don't plan on flashing any radios. As I did with the inspire, and it messed up my service bad and I didn't know how to fix it again. I didn't now too much about it then. Which I still don't but I know more now than I did then.

NeverToLate said:
Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Be sure you are using TWRP, and not Clockworkmod. CWM has known problems, as our device is not really supported (its just a port) and also USB mount is not working (which may be relevant if you run into problems such as the SD corruption I've mentioned).

I will be using TWRP. If I'm not mistaken I did a nandroid back up of stock rooted. I plan on copying my sd card to my computer external hd just for safety. I have a HTC One X Folder that I will put my roms in stuff in as well.
I will try to take screenshots of battery life for each day I use a certain rom. The battery probably won't go below 30% but screenshots would give a good idea to other people. And I will try to update my thoughts on each rom. Not promising I will get to but I will try.
I am going to download and check md5s today.
Idk if I will flash one tonight or not.

Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.

NeverToLate said:
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
Click to expand...
Click to collapse
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though

gridlock489 said:
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
Click to expand...
Click to collapse
Blue is actually my favorite color lol. Could you point me to the CM10 rom?
Here are the roms I am downloading as of now:
KingCobra
Nocturnal Special Edition
Viper
Clean Rom 5.0
Any other ideas on maybe one or two more roms?
I bookmarked that link you posted. I prob won't do much with themes until I find the right ROM. Even then the most I usually do is wallpapers lol. But will look more into after finding a ROM.

What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.

NeverToLate said:
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
Click to expand...
Click to collapse
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.

gridlock489 said:
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
Click to expand...
Click to collapse
What's the different in the Nightly and Experimental? I would like to try a CM since I never have before. Probably will be the last one I download

Also on the CM10 forum it says something about find Gapps? Is that something I search for and download and flash?

Update
Downloaded Roms with md5 checked and now on my sim card:
Clean Rom 5.0
CM10
King Cobra
Nocturnal Special Edition
Viper
Just need help on what I need to download for Gapps to install CM10

What Rom should I test first?
King Cobra
Viper
Nocturnal

I'm on nocturnal and loving it.
Sent from my HTC One X using xda premium

Samsung Exhilarate SGH I577 Unofficial(CM9)(CM 10)(PA)(Pacman)(TWRP)1 stop shoP

Thomas.Raines and Team Fah-Q! presents
source code Lightning_Zap_Powered CM-10 Unoffical for SGH I577
https://github.com/TeamFahQ/msm8660-common_lz_kernel.git
https://github.com/TeamFahQ/msm8660-common_LZkernel_tools.git (scripts and zipalign binary)
A BIG THANK-YOU goes out to DR4ASTIC for the many months of work he put into porting cm-10 and our kernel so if you see him hit his thanks button, and if you have the means help get him some soap..lol Also thanks to Thomas Raines for bringing us LZ. the site will be under construction for a while as I have had a few requests for links to the various guides and tuts I've used to learn how to build...mind you it takes alot of time and research but to me its deffenitly worth it...Here is a thread for the blaze TFQ tweaks and install instructions for the LZ kernel. also features from this thread http://forum.xda-developers.com/showthread.php?t=1959657
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
TUTS
[GUIDE] PARANOIDANDROID:JB
http://forum.xda-developers.com/showthread.php?t=1863547
Project Rookie How to build ROMS
http://forum.xda-developers.com/showthread.php?t=1798056
Guide how to compile and install CM10 for i9300
http://forum.xda-developers.com/showthread.php?t=1946481
TUT Building your first kernel
http://forum.xda-developers.com/showthread.php?t=1748297
Thanks to everyone who has helped this rookie put all this together
Dr4stic, thomas.raines, racing19969, and many others who i dont remember thanks everyone.
Warning: if you rooted your phone using the blaze recovery you need to use Odin and push our custom recovery tar file located below. make sure to uncheck repartion. if you push this with the blaze recovery it could cause issue's.
ok so d4astic cooked us up a CM 10 mod unofficial and our very own CMW recovery here are the links, and we need someone who can grab this and take over because d4astic doesnt have this phone and has a nightly on the blaze, so here you go everyone. I've taken over running the builds so....
,,,let the fun begin....
One more thing make sure you push the recovery first because the blaze one won't work with this rom
WARNING: if you brick your phone its not my fault i did this and it worked out fine just so you know
Also find this at this thread
http://forum.xda-developers.com/showthread.php?t=1730518
New Govs and U/V control brought to us by Thomas Raines and j3r3goss who dedicated his entire christmas break getting this to work for our phone. Also we know that at this time you cant control voltage with 3 rd party controls we are working on this so no need to tell us thanks
recovery cwm
cwm-6.0.1.4-exhilarate.tar - 6.92 MB
md5sum: f4f327659c35942ac8b5d08940b27efc
Cwm flash able zip
http://d-h.st/0KP
twrp 2.6
TWRP-2.6-Recovery-I577.zip - 7.67 MB
Official cm-10.2 thread
http://forum.xda-developers.com/showthread.php?p=45140599
official carbon rom by somcom
http://forum.xda-developers.com/showthread.php?t=2458690
official pacman by ink slinger
http://forum.xda-developers.com/showthread.php?t=2445143
4.3 is here hey guys so we skipped 4.2 and jumped right up to 4.3 due to efforts of many people
credits
j3r3goss
dr4stic
uberpeaguin
thomas raines
racing
somcom
teamchopsticks
meticulous(wifi-fix and several other things )
and of course yours truley
i know this list should be bigger and if you need to be on it because i missed you pm me and i will add you
i want to offer everyone on this list my heartfelt thanks from me and the rest of the i577 and blaze community without each and everyone of you we would still be stuck on 4.1 so thanks
4.3 moretz kernel source
thanks to these fine gentlemen
Team Chopsticks
CyanogenMod
Car vs Driver
elbermu
https://bitbucket.org/carvsdriver
moretz kernel oc to 1.5 ghz
flash from recovery and wipe caches
moretz_fixed_exhilarate.zip - 5.97 MB
4.3 roms
Liquid-JB-v3.0-UNOFFICIAL-exhilarate.zip - 115.52 MB
dirty unicorns all fixes included camera, torch, light sensor
du_exhilarate_2013-09-23.zip - 167.97 MB
beanstalk all fixes
BeanStalk-4.3.08-20130924-exhilarate.zip - 174.92 MB
pa_exhilarate-3.99-20130831.zip - 150.55 MB
i left out my slim build since meticulous has that under control there is a pac build in the thread by ink search for it its in the last 20 pages or so of the thread we are oficially supported by cm and team chopsticks and working on getting our own forum but xda seems to not be listening to me so all of you raise your voices and be heard by mods and anyone else who has a say in it i hope you enjoy my work this is the culmination of several months of time and energy and believe it or not i didnt even know what linux was when i started lol enjoy
old builds
4/25/13
SlimBean
Slim-3.1.0-i577-20130426-1514-UNOFFICIAL.zip - 80.51 MB
root box
5/6/13
fixed menu button and rom control
RootBox-JB-i577-Nightly-20130506.zip - 141.89 MB
http://d-h.st/3Nw
Remember with the LZ kernel if it hangs at boot let it sit for 10 minutes reboot and enjoy...
pacman LZ UPDATED 2/8/13
http://d-h.st/Afa
1/12/13
http://d-h.st/sjj
Paranoid Android: UPDATED 2/8/13
http://d-h.st/X5B
1/9/13
http://d-h.st/3AF
check this one out guys....
LiquidSmooth UPDATED 12/14/12
LZ:http://d-h.st/4z1
http://d-h.st/bqe. No LZ: NOT UPDATED
AOKP UPDATED revamped kernel
2/8/13
http://d-h.st/UEr
01/28/13
http://d-h.st/gg8
12/18/12
http://d-h.st/Wzb
rom and md5sum: cm10 sgh i577 exhilirate zip unofficial(Powered by LightningZap Kernel)
Cm10 updated 2/8/13
http://d-h.st/2Pd
UPDATED 1/9/13
http://d-h.st/4Hi
G-apps. JB
http://goo.im/gapps/gapps-jb-20121011-signed.zip
CM 9 stable unoficial build by dr4stic (At this time CM 9 does not have the lightning zap kernel)
so below is the folder where you will find the zip file for the cm9 build, make sure you get the md5 sum and compare it,please make sure you do a factory reset and wipe the dalvic cashe also, its under advance in the recovery
Now just in case you did not read from the top and just jumped down here; please push the recovery from the link above, if you do not do this you will have issues.
Thanks dr4stic for all your hard work, I'm going to post the ICS g-apps link . I hope everyone enjoys this as much as i do... With all that said .....enjoy....
CM9 unoficial rom with new kernel(updated by j3r3goss)
http://d-h.st/lNB
ICS G-APPS
http://db.tt/65fqUOcO
Ported ROMS
these roms were ported by InkSlinger420 they are not built from source but still very stable and a good expieriance
Credits
Avatar thanks for letting us post this here
the original thread can be found here
http://forum.xda-developers.com/showthread.php?t=2142130
Avatar Port
http://www.d-h.st/B4O
LiquidSmooth
Donation link for liquid smooth
http://bit.ly/Ruy2HF
thanks to Xwolf13 and the all star team for allowing us to port their work and post it for you guys the original thread can be found here
http://forum.xda-developers.com/showthread.php?t=2284763
Rom Port
http://d-h.st/RE5
i didnt do these ports guy so look up InkSlinger420 hit his thanks button and then go to the original thread and click the thanks button on the op post
this stuff takes alot of time and effort weather its a port or built from source so show them some love

thanks for posting it here... I will test it. Also you should post Gapps link. I have it.. but others might not and may flash the wrong Gapps.

This is NOT a rant...
These are some bugs I found so far.
1. Screen Orientation (Which OP mentioned)
2. While charging if you touch the power button It will black out and Hangs up (Pull battery and restart)
3. Camera sometimes having issues. (camera not found) but most of the time works perfect.
4. Call quality Low (Like all CM builds)
Rest everything seems to be very smooth. Google Now works without any issues.
I'm just writing this for information purpose only for those who like to use this build.
Thanks a lot to dr4stic for giving us this build.

Googler_1976 said:
These are some bugs I found so far.
1. Screen Orientation (Which OP mentioned)
2. While charging if you touch the power button It will black out and Hangs up (Pull battery and restart)
3. Camera sometimes having issues. (camera not found) but most of the time works perfect.
4. Call quality Low (Like all CM builds)
Rest everything seems to be very smooth. Google Now works without any issues.
I'm just writing this for information purpose only for those who like to use this build.
Thanks a lot to dr4stic for giving us this build.
Click to expand...
Click to collapse
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108

dr4stic said:
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108
Click to expand...
Click to collapse
BLN was never checked at-least on my phone. But its the screen rotation issue made me rollback to Stock ICS. I know you're very busy... but if you can guide me where to look into for that issue I will. Thanks again for ur hard work.

He needs a log cat run during the screen rotation and during start up so he can see what's going on. I don't know how to do this yet I've been looking into it but don't really know where to start. Do you know how to do this
Sent from my SAMSUNG-SGH-I577 using xda premium

Another thing that would be nice, the output of dmesg.
Just a brief explanation of what these things are. Logcat is basically the general android system logs as it boots up and runs. The dmesg is the log specifically of kernel messages as it boots up. This often includes details on drivers and potential errors there. ADB = android debug bridge, a way to connect to android, push and pull files, get a shell on the system, etc...
Install ADB drivers: If you've installed the drivers necessary to use Odin with your phone, it should include Samsung's ADB drivers for the phone. So I don't think you need to worry about that.
Install ADB: Not great, but not horrible ADB install tutorial
As for the phone itself, ADB is automatically enabled within recovery. When the phone is booted up as, you know... a phone... you'll want to go into Settings -> Developer Options, find "Android Debugging" and make sure it's turned on. That will enable ADB on android.
Now, some sample ADB commands to make your lives easier...
Check to make sure ADB sees your device (you should do this whenever you connect your phone to your computer, just to make sure you won't run into any errors with the commands below):
Code:
adb devices
Grab the output of dmesg (two versions, see it or redirect to a file.. you pick):
Code:
adb shell dmesg
or
adb shell dmesg > C:\name-of-some-text-file.txt
Grab the output of logcat (two versions, see it or redirect to a file.. you pick):
Code:
adb logcat
or
adb logcat > C:\name-of-some-text-file.txt
* NOTE: This will continue to grab output until either the system reboots or you hit CTRL+C on your keyboard. If you're just looking for the most recent messages, let it run for a few seconds and then CTRL+C it out.
Get a Linux shell on the system:
Code:
adb shell
Restart local ADB server (sometimes necessary... if you KNOW your phone is connected and ADB stopped recognizing it):
Code:
adb kill-server
Thanks guys!

I began setting a dB up on my comp last night I have java installed and started on the SDK but I fell asleep will work on it some more today. Now I'm going to read the links you posted and see if my research went in the right direction. One thing I will tell you is I've been spoiled by windows. Setting this up has given me flashbacks to the days of DOS. Lol
Thanks for the info and the time to point us in the right direction.
Sent from my SAMSUNG-SGH-I577 using xda premium

ktempleton said:
I began setting a dB up on my comp last night I have java installed and started on the SDK but I fell asleep will work on it some more today. Now I'm going to read the links you posted and see if my research went in the right direction. One thing I will tell you is I've been spoiled by windows. Setting this up has given me flashbacks to the days of DOS. Lol
Thanks for the info and the time to point us in the right direction.
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Another easy way is install Droid Explorer (http://de.codeplex.com/) Power off phone when connected. then click on the logcat console button. It will open the command window and lines keep scrolling... Don't do anything till it completely boots. then Save the file (option on cmd window).
But i think the rotation issue is in the kernel so we might have to use the cmd line provided for that. U can use it in the same app.
Currently I'm back on ICS... So once I can't do it now. Today when I get some time I will re-install and run this.

Googler_1976 said:
But i think the rotation issue is in the kernel so we might have to use the cmd line provided for that. U can use it in the same app.
Click to expand...
Click to collapse
It probably is in the kernel. That's why I want the output of dmesg as well.
Incidently, it seems my initial kernel patch is winning some reviews and with any luck, I'll have it in the official cm kernel fairly soon now.

I did a search in the play Store for Log Cat, there are numerous apps in there for saving, sharing logcats, will these do the job? I certainly seems it would be much easier than ADB. Just curious.

dr4stic said:
It probably is in the kernel. That's why I want the output of dmesg as well.
Incidently, it seems my initial kernel patch is winning some reviews and with any luck, I'll have it in the official cm kernel fairly soon now.
Click to expand...
Click to collapse
So Is it basically same kernel for ur device and I577? if it is.. That's really cool.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
pegb856 said:
I did a search in the play Store for Log Cat, there are numerous apps in there for saving, sharing logcats, will these do the job? I certainly seems it would be much easier than ADB. Just curious.
Click to expand...
Click to collapse
I think most of them cant run booting up... ("I think is the keyword")

Googler_1976 said:
So Is it basically same kernel for ur device and I577? if it is.. That's really cool.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
I think most of them cant run booting up... ("I think is the keyword")
Click to expand...
Click to collapse
*I think* that makes sense and you are probably right.

dr4stic said:
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108
Click to expand...
Click to collapse
Here is the Logcat... and Kernel Log

Well I'm all in. I was cleaning things up before loading everything up and accidentally deleted all my backups . Oh well, so far I'm loving this. Hope it's good to go for a daily or I'll be setting up a new ICS install too.

I could always upload one of my ICS backups to drop box for you if it comes down to that
Sent from my SAMSUNG-SGH-I577 using xda premium

ktempleton said:
I could always upload one of my ICS backups to drop box for you if it comes down to that
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Not a big deal. So far not having any issues other than rotate bug. Even notifications are working ok. I did turn off some notification light setting and I thought I saw something about softkey flash notification, but I couldn't find it again. Take me a bit to get used to the menu structure.
Everything is pretty smooth as of right now.

Unfortunately my phone randomly shut down twice today and I ended up going back to ICS for now. The first time I had foursquare open but had laid it down since the light changed and when I picked it up it was off, the second time it was just laying on the desk and when I picked it up it was off again. I did back it up before restoring ICS though. I've got a lot going on the next couple days and need a dependable device.
I might restore back to CM 10 and tinker with it when I'm not expecting phone calls.

pegb856 said:
Unfortunately my phone randomly shut down twice today and I ended up going back to ICS for now. The first time I had foursquare open but had laid it down since the light changed and when I picked it up it was off, the second time it was just laying on the desk and when I picked it up it was off again. I did back it up before restoring ICS though. I've got a lot going on the next couple days and need a dependable device.
I might restore back to CM 10 and tinker with it when I'm not expecting phone calls.
Click to expand...
Click to collapse
Same here after i provided the logs. The phone was lying and when i checked it was shutdown.
.

We were having similar problems on the blaze end. Most of them seem to be getting worked out pretty quickly so I'm fairly confident you guys should be seeing some problems fixed soon too.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

[Q] Just Rooted My Phone: Where to go from here?

Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!

Zarotu said:
Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!
Click to expand...
Click to collapse
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.

jmxc23 said:
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.
Click to expand...
Click to collapse
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Edit: Is there a thread I can look at find to get more information on how to prepare my phone for theming and modding? Information such as deodexing my phone, and other preparation information. I can't seem to find a good thread.

Zarotu said:
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Click to expand...
Click to collapse
In the original android development is where you will find the kernels. Most of the kernel threads will provide links and the information you need. If you are planning on flashing KT747 kernel here is some additional information: http://forum.xda-developers.com/showthread.php?t=2144004

Whoa, hold up on the custom kernels and custom rom stuff.
1. You need to make a back up with either twrp or cwm. Next put your important files on your external sd including your efi. Idk if titanium backup allows you to store app back ups on the external sd or not but I assume it does (I use a diff app). You don't have to format your internal sd to flash a custom rom, you have to format the system partition.
Take a minute to make sure you have the prerequisites before moding your phone more. You cannot possibly want to be doing all this so soon especially if you just got into this yesterday.
2. Your still on a stock rom, which is odexed. If you want to customize your rom you need to be on a deodexed rom most of the time. This is a the simple abbreviated difference between odexed and deodexed.
3. Luke took on Vader, even though he was a new rookie padawan. He didnt have a good grip on what he was doing, and karma took his hand and slapped him in the face with irony for it. You might find yourself falling a deep hole of problems if you don't read up more on what you're doing. Do yourself a favor and stay on the god damn dagobah system awhile.

One final thing I have to say is do some research it will help you a lot.

Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.

nrock2256 said:
Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.
Click to expand...
Click to collapse
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.

jmxc23 said:
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.
Click to expand...
Click to collapse
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.

Zarotu said:
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.
Click to expand...
Click to collapse
It is more confusing than it is difficult.

Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223

Surge1223 said:
Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223
Click to expand...
Click to collapse
Okay what if the person doesn't have the money as of now to purchase an sd card? Are there other ways to back up their data?

Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223

Surge1223 said:
Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223
Click to expand...
Click to collapse
Micro SD price range from $5-$100 retail when not on sale and the retail price depends on the storage size. So if the person is hard on cash or has more important things to spend their money she/he might not be able to buy the micro sd with the couple of bucks that you said it cost. The reason I asked those questions is that not everyone has a couple of dollars to spare on a micro sd card so all possible ways to back up data should be mentioned not just what you or I think is the best thing to do. For instance I have my data backed up on my computer via external hard drive as well as Google drive, box and Dropbox. I also use Carbon instead of the titanium backup app that everyone suggests to use. So they can use their computer, cloud storage service, external hard drive, micro sd cards and apps to backup their data.

Its not a matter of whether its possible or not, I mean yeah you can also make a system image of your pc using DVD's instead of a portable hdd or flash drive. I can understand people may be short on cash, but if you have enough time and money to root your phone, pay for a data plan, subscribe to the internet, you can budget 5 dollars. Hell, you could even start using bing rewards to get yourself a 5$ Amazon credit.

All I am saying mainly is that there are more ways to back up your data besides micro sd cards and that all people new to rooting should know more then one way as something can go wrong your micro sd card so your data should be backed up in other ways to insure that you can restore your data.

I hear ya, I guess I just think because I learned my own how to use other methods I assumed that as people got more familiar with flashing roms, etc, that they'd learn eventually too. But hey to each his own. IMO, the external sd is the easiest, fastest, and most reliable way so in this case, I think we should leave well enough alone.
Surge1223

Suggestion:TWRP, exfat, GT-N7000 external SD Card bug

On my Samsung GT-N7000 I'm trying Omnirom again. I've tried it in the past and also tried vanilla CM stable and nightlies. I have also tried SuperNexus and PA and some other stuff that left no impression. Basically on this device for functional hardware, reasonable user control and a coherent UI it is Samsung's Touchwiz rooted, or Omnirom.
It is a bit too hard to install Omnirom and it can be horribly tedious to go from Omnirom back to stock or to another ROM. It's OK after you have done it a few times, but it is a huge obstacle for anyone trying to discover the way via inaccurate, misleading and fragmented documentation. The install guide at omnirom.org is actually utterly useless for this particular device, a complete non-starter. XpLoDWilD your GT-N7000 specific thread at http://forum.xda-developers.com/showthread.php?t=2516933 almost guarantees a boot loop because it only mentions but doesn't identify or link to versions of CWM which are adequate. In fact unless the user by diligent searching (or more likely by blind chance) comes across a link to the specific suitable raw kernel then it is one big dead end. You could spend hours and days searching for a suitable CWM and never find it because actually you should be searching for raw_kernel_r#_j##.zip. But how is anyone meant to know this. It turns what is actually a reliable and rather trouble free 15 or 20 minute process into a some kind of waking torment. In the past the documentation on installing via CWM was so bad that I used ODIN, which is less than ideal IMO because it means that anyone switching from stock to Omni doesn't get the chance to make a full nandroid backup of the original system (so to revert means a very tedious clean install).
So assuming the end user somehow finds the right raw kernel whose recovery can install Omnirom, what should they do? Of course they should back up their current apps and also make a nandroid backup. Apps backup is easy with oandbackup or titanium or similar. How about a nandroid backup to external SD? No problem in CWM but once you have TWRP installed you can't use it to access anything on an exfat formatted external SD card! You can back up before installing Omnirom but afterwards you can't restore! This is 100% nuts. exfat has now been around for 8 years. CWM supports it brilliantly. Even my crusty old Debian stable desktop reads and writes to exfat at very high speeds even via a FUSE FS and my puny Asus EeePC netbook running XP Home handles it fine. TWRP? Nope. exfat? Wha tha? Aaaaaagh.
Sorry to rant But for these specific devices Omnirom (with an exfat SD) is really the only high quality competitor to the stock Samsung, and there surely isn't a good reason for it being so frustrating to install and also to revert? Is TWRP really such a killer facility that it is worth foregoing the ability to backup and restore to the now very common exfat microSDHC? I run plain CM 11 on another device and OTA updates work fine on that. In these days of phatter pipes is it really worth making a huge compromise in functionality simply to avoid 200MB of downloads sometimes? On this device the delta updates are going to fail for many anyway unless they use an exfat card, but if they use an exfat card they.....oooouuuurrrggg...vicious circle.
/rant over.
Loving Omnirom btw and writing as a fan.

#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system

Entropy512 said:
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Click to expand...
Click to collapse
Thanks for responding. I do appreciate that the exynos based devices are sons-of-b...b...bad persons.
I know documentation is boring and mostly thankless but it also matters a lot, most especially for projects which invite the user to perform realtively complex and potentially hazardous tasks.
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Omnirom has some issues but on the GT-N7000 is probably the only really mature and coherent alternative UI to Samsung's Touchwiz. To me it seems simply insane to direct newcomers into an unnecessary, time consuming, badly described and potentialy hazardous obstacle course, when in fact installation can be done with only small inconvenience.

I'm currently looking for information about installing OmniROM (I'm currently running CM11 nightlies), and I can attest the information in XpLoDWilD's post is somewhat vague, and also doesn't fully correlate with the directions to install Omni at the official wiki -- I'm assuming this lack of correlation is partly due to the fact, mentioned in this thread, that the N7000 doesn't have a separate recovery partition.
Something which made me especially uncertain about the installation process is the following part:
XpLoDWilD said:
- Make sure you're running a proper working ClockworkMod-Recovery - WITH SELINUX SUPPORT!
Click to expand...
Click to collapse
My understanding is that SeLinux is a feature of the kernel -- not the recovery console -- am I wrong about this? Or should I look for SeLinux in the features of the recovery console as well? (if so, how?)
What I currently do, is run adb, or start a console from the normal operating mode (not recovery mode), run the command:
Code:
getenforce
and confirm the reply is:
Code:
Enforcing
which means I have a kernel with SeLinux. Is that good enough to ensure the requisites for the installation are provided?
I'd appreciate any input about this matter.
julian67 said:
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Click to expand...
Click to collapse
Cant you add device-specific installation guide at the official wiki?

sagie said:
Cant you add device-specific installation guide at the official wiki?
Click to expand...
Click to collapse
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.

I'm pretty sure I can save my twrp backups to my exfat sdcard.
edit: yup. just touch "internal storage" on the twrp backup page and select your sdcard.

julian67 said:
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
Click to expand...
Click to collapse
i've been using omnirom as my daily driver for 2 weeks now. love kitkat and omnirom features, but its still very unstable i think. stuff that's bothering me for now:
-stock camera is really plain, can't even switch to front camera
-video playback sometimes fail
-music playback will fail the first time i launch and play a song or 2. have to reboot and it'll work all day long
-intermittent random reboots, about 3 times so far the whole week
-wifi signal range is somewhat lower compared to touchwiz rom
-stock clock app, can't manually input time via keypad when you want to add an alarm
-contacts app is very confusing, can't even add a contact with ease. well at least for me that is
other than that kit kat is sure a welcome on this legendary device. contemplating the switch back to stock touchwiz, but loathe at the idea of setting up everything again zzz

In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux

Polux44 said:
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Click to expand...
Click to collapse
Per my earlier post - You cannot change kernels on the Samsung GS2 family (including N7000) without also changing recovery.
Conversely, you can't change recovery without changing kernel. It's a limitation of this device since the recovery partition is not actually used, and recovery is in the normal kernel.
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.

Entropy512 said:
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Click to expand...
Click to collapse
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!

Polux44 said:
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Click to expand...
Click to collapse
Correct. Sony devices also have this limitation, there is a semi-workaround (where the kernel pulls recovery ramdisk from another location) on those that *in theory* could be done on the old Samsungs... but so few people are working on the old Samsungs that it isn't likely to happen.
Pretty much all GS1s and Exynos GS2s had this limitation. Qualcomm GS2s (Skyrocket/Hercules) had a separate recovery, as did all GS3s and onwards.

Root on fire HD 10 - but no custom recovery or ROMs?

Can someone help me understand how we can have root methods for the HD 10, but no custom recovery or ROMs?
Any news or updates on the effort here? I'm willing to pay or donate to get it done!
I REALLY want to turn my tablet into an Android tablet... Not a fire tablet with an almost Android experience.

If we can get some one to create safestrap probably we can have a custom Rom !ade

There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.

DragonFire1024 said:
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
Click to expand...
Click to collapse
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!

Supersonic27543 said:
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Click to expand...
Click to collapse
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!

Supersonic27543 said:
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Click to expand...
Click to collapse
That's one of my projects

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Could be that I don't know how to solve the problems I have, but for me not all the Google play applications I want (for my kid) work. Issues vary from validating my authorized purchase to core functionality of applications not working. Some of the applications refer to Android os content and services that either aren't in fire os, are named differently, or have different functionality.
Not to mention that I dislike my son's user experience... He's only 3, quite smart but I've not been able to strike a good balance of protecting him and allowing him to actually use his tablet without learning wierd tricks to access Google play apps.
I'm ok if I have to stay on Fire Os if I can have complete control over profiles, launchers and have a genuine experience using my Google Play applications. Some of the FreeTime stuff is ok... My son might like some of it. But more importantly I want him to have the far superior applications on Google Play which are not currently available on Fire.

I'm willing to contribute to get a custom rom on the fire 10.

I really want to compile one, my skills are getting blunt without some compiling, but it turns out that I only have a HD 8.

Can someone please educate me on getting the GPS to work with google maps, like my phone? My HD 10 7th gen is rooted w/supersu. I have xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.

kferling said:
Can someone please educate me on getting the GPS to work with google maps, naively like my phone? My HD 10 7th gen is rooted w/supersu. I have Xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
Click to expand...
Click to collapse
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Click to expand...
Click to collapse
Thanks, although I did not get location prompts at the end. :/
Data was wiped for all 4, and uninstalled. rebooted and verified no data with ES.
Installed google apks in the exact order, waited 2 minutes, rebooted, then logged into playstore.
Went to home screen, saw apps flash after waiting. Went to location services (was off) turned on and no prompts
Turned off, waited 30 secs, turned back on, still no prompts.
Is this any different from your guide here?
Step 6. states "Once all the APKs are installed, open the Play Store and sign into your account and IMMEDIATELY go to settings and TURN OFF auto-updates. "
Perhaps that's what I need to do?

Just ordered an HD10, will this tutorial still work? https://forum.xda-developers.com/hd...7-root-box-t3726443/post75187398#post75187398
Will that debloat Fire OS also?

So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.

Have a new 2015 HD 10. Will definitely be following your progress

FuNKSioN said:
Have a new 2015 HD 10. Will definitely be following your progress
Click to expand...
Click to collapse
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.

TechNash said:
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
Click to expand...
Click to collapse
Not sure about the encryption. It has to be a script problem, or the system partition won't accept zips and that's the barrier. However if I just flash the system directory instead, everything works fine. I can flash stuff into it just fine that way, but seems any time I go the way of the partition, I can't win. Flashing your own system image works too. However I haven't been able to get one to flash if I modify it. So I can decompile a system.img add to it, remove items and recompile it and it won't flash.
I am using flash fire to flash zips. We still have a locked bootloader so twrp isn't a likely option.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Click to expand...
Click to collapse
I mean, if PC performance is an issue I can give you access to a brand new xeon if it means there will be a custom ROM out.
Been thinking about buying the Fire HD 10 this black Friday and flash the Amazon garbage out, and was amazed to see none exist even though it has been a year since they figured out the rooting.
This will be an outstanding value if it was possible...

Database Info

welcome