Related
hello gentlemen
i bought my viewpad 7 last week. after digging this forum i tried to root my tablet with super one click but i was unable coz it stuck in screen and happen nothing somehow i tried gingerbreak and it worked. as i am totally newbie in android os and i have no idea on programming. but the most important thing is clockwork recovery i saw couple of youtube videos and tried working but ended up with error . i dont know how to setup adb on my pc so i tried terminal emulator but no keyboard.. tried qtadb but show me '' permission denied'' now i am pulling my hair off. i have got rom manager installed on my tablet but whenever i ty to install update.zip it say signature error or somthing (i have got custom rom in my sd and renamed to update zip also i have clockwork recovery img and flash recovery) the only thing i need is a working terminal emulator as i have no idea on comand from pc.
so is there anybody who can give me a easy tutorial or make a video to demonstrate how can i get clockwork recovery installed also custom rom i would be really really greatful
hope someone saves me...
Hello & welcome, there's no need to panic but definitely - very important to be patient, set aside at least half a day or more, and, read - read - read. Take notes as you go along & do NOT rush.
If you have not gone thru this sticky, please do so - http://forum.xda-developers.com/showthread.php?t=1236990
Sticky #1 is mandatory reading to take full advantage of the Vpad7 so that you can understand the basics, describe your Vpad's hardware & build information, etc. and how to press various buttons, go back, reset & get into Recovery and Bootloader. Without knowing it, you are prone to run into problems.
First, you need to check & make sure that your CWM (which verison) is properly installed & working (and, if so) - check under the Advanced submenu to verify "Signature Verification" status.
Do you have an "older" non-ITE or "newer" ITE multi-touch screen device, which determine which custom ROM can be used? Be specific, please ...
Generally speaking, there is no need to rename a downloaded ROM's zip file to update.zip for flashing ... so I suggest that you do more reading first.
Do you have USB debugging turned on? Applications - unkown sources turned ON to allow installation of non-Market apps? A working knowledge is essential to avoid (soft) bricking your device by being able to understand the process for Flashing - start here http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
There's nothing simple & easy about all these, sorry - time & patience is a requirement to get everything working together. Look under the "Development" section for how to install ROM & the issues involved - there are just a handful of ROMs and you don't need to spend a hundred hours going thru all of them, a few hours of reading will do - a 10 minute Youtube video isn't going to do it. The best person to "save" you is you - YMMV. Regards.
thanks a million i finally made it. i used rom manager to install un official clockwork recovery and did install custom rom however i need one more final solution i was trying to get app2sd but my rom maker said it is built in inside the rom just need to creat ext3 but i guess i cant do that without comand so again is there any manual method to do that i saw an option on rom manager but it offers only 512mb partition but i want more may be 8 gb or 4gb i have 16gb sd card.. so can u help me pls...
and i yes i had usb debug on. unknown source on
big_b0sss said:
... i used rom manager to install un official clockwork recovery ... custom rom however ... app2sd ... is built in inside the rom just need to creat ext3 but ... without comand ... rom manager ... offers only 512mb partition ... may be 8 gb or 4gb i have 16gb sd card..
Click to expand...
Click to collapse
1. Rom manager - I do not use them on my Android devices but if you are comfortable with it and help simplify your tasks & learning curve, good for you. Remember to backup, backup & backup your work & save it to more than one location - those "oops" happened to all of us, sometimes (and, at the worst time - Murphy's Law 101)
2. You only need a few files in its own sub directory or folder to properly run adb and busybox, and, to run the (good old DOS) command prompt from your PC - just need to type the commands carefully. Alternatively, Terminal Emulator (with or without the shell or user interface) can be downloaded from Android Market to the Vpad7 to install & run (it's not pre-loaded) with SU enabled ... (more reading for you on how-to's)
3. Not sure if you are referring to App2SD in Market (quite a few out there) or DT's A2SD and A2SDGUI in some of the custom ROM. Vpad7's custom ROM recommend 1 MB SD ext3/partition in general (ext4 is more advanced and challenging) - there is no need, advantage or benefit in a 2GB or 4GB ext3 with a 16GB mSD card (as you are allocating/reserving unused space that you cannot dynamically changed or reassign later on as you begin to run low on "general" storage space on the card - PLUS, you will have to reformat the card & wipe/lose everything on it, until it's restored from saved backup)
FYI - I keep the last 3 to 5 CWM Backup images/files on the mSD card and it's close to 3GB in size already, not counting pix, mp3's and saved videos.
4. Older version of CWM Recovery worked best for me in repeated ROM flashing & setup to partition/format the mSD, verison 5.0.2.6 can work but the newest one posted 5.0.2.7 did NOT work for me - YMMV, of course. Refer to the one in Cleanviewpad7 V1.0 and its instructions or EU Vapd 7 V1.7b - as I'm guessing from your description that your device is a newer ITE multi-screen hardware build. KWBR V3.2 ROM works with ITE and has the newer kernel and A2SD is easy to use per installation guide - it's lean & stripped of non-essential apps.
Have patience, backup & have run !
thanx again for ur reply but i dont know why i do not get keyboard on my terminal emulator. i tried to put comand through terminal emulator but due to keyboard issue i cant i also tried dos but i have no knowledge on that. can u make a video for me or a tutorial how can i get a2sd work on my vpad 7
thanks again
big_b0sss said:
... dont know why i do not get keyboard on my terminal emulator. i tried to put comand through terminal emulator but due to keyboard issue i cant i also tried dos but i have no knowledge on that.
Click to expand...
Click to collapse
First, as I asked before, we do NOT know which ROM you are trying to use?
But, I'm going to guess - since I've flashed all of the working ITE ones here, and you are using KWBR v3.x - and, if so, please confirm or verify, yes or no.
If so, I had issues with its keyboard not showing up in terminal emulator, and there are different reasons for it - namely, including the OP developer's choice of installed KB. However, as a workaround - by running adB/busybox from Windows Vista's command prompt, I can execute instructions to re/mount, reboot, etc.
By installing a different KB & switching to it, it worked under terminal and I can run command prompts directly. There is a learning curve involved here - not something to rush, rather steps by steps - there are "stickies" in the threads and I do not want to further clutter up excellent guides already written up, 6 to 9 months plus ago - which I took time to read, follow & work with. I encourge you to do so as well.
My advice, the easiest to do, is to install & start with a different ROM - Cleanviewpad ROM is basic, simple & easy to install, virtually "bug" free and I suggest that you start with that. KB worked directly as a toggle, popping up from terminal emulator, and you can run commands from it.
Once you are comfortable & has everything working, you can optimize your A2SD and move apps from internal storage to mSD card, etc. and progress to the next level - EU Vpad 7 V1.7b ITE ROM is nice but from experience and reading the thread's posts, some "beginners" lacking knowledge & skills have trouble with it. By running a # of patches, I get it updated to the latest and it's running optimized to my personal liking - it's not entirely difficult to learn but not for someone completely new to Android OS.
Here's a link that you could've google right here in XDA - guide to ADB - bookmarked the link for you, please search for other guides, thanks
http://forum.xda-developers.com/showthread.php?t=879701
hi there thank you so much for helping me again and yes i am using kwbr rom because i have tried cleanviewpad 7 but stuck at welcome screen doesnt work anything then tried lakehouse froyo enhanced but link disabled so stuck with this rom.. i really wish i cloud post on dev section coz im kinda stuck with this post..
but hey if u dont mind and if u have froyo enhanced rom can u upload that for me or give me a working link...
sorry for bothering u but would appreciate
Still waiting for a ROM for Viewpad 7e. Anyone know of one in development? Even the stock ROM bundled with CWM would be good so that we would have the ability to do a Nandroid backup.
Sent from my SPH D700 using XDA App
Cyanogen Mod 9.4, Shadow kernel, EI22. I like my Ice Cream Sandwich!
big_b0sss said:
... using kwbr rom because i have tried cleanviewpad 7 but stuck at welcome screen doesnt work anything then tried lakehouse froyo enhanced but link disabled ... and if u have froyo enhanced rom can u upload that for me or give me a working link...
Click to expand...
Click to collapse
Are you making good progress after rooting with custom ROM, learning a bit more about using adB and terminal emulator? I searched my storage bins for what I've kept for the Vpad7 - and I have NO luck yet finding the Froyo enhanced ROM. I did uploaded the EU V1.7b ITE custom ROM to Dropbox, along with the a2sd*.zip file (just in case, you are comfortable & ready to try - after backing things up) The A2SDGUI app is available in Market, just search & download & install up once the EU V1.7 ITE ROM is up.
A2SD does NOT need to be working for the ROM to do its basic functions, just that it will soon run low on internal storage/memory and that's where A2SD come in. If you find it useful, do a CWM backup first , then use the earlier version of CWM to reformat the mSD card again (thus, wiping it clean) and setup a 1MB ext3 partition per detailed instructions. Reboot & reconnect USB, and move/restored all of your saved files/folders/settings, etc. back to the mSD drive.
Next, flash the A2SD program by DT again just to be sure from Recovery - and then Restart into Recovery. Wipe cache & dalvik and boot up again - cross your fingers and A2SD should be up & running - check it with A2SDGUI and/or Titanium Backup will display various memory/partition/storage space & usage (used/free & total)
http://dl.dropbox.com/u/64025118/EUViewpad7v1.7b-ITE.zip
http://dl.dropbox.com/u/64025118/apps2sd-2.7.5.3-dt.beta04-signed.zip
Again, I am and will be be responsible for anything if something goes wrong by using & flashing these zip files, they are unchanged or unaltered as I originally downloaded them. I'm simply posting them with the mess created by the multi-upload servers being offline, etc. as many folks are completely at a loss for what to do next. Full credits go to the OP/xda-developers for creating their masterpieces. If you are not comfortable or unsure, please do not proceed or assume the risk - the stock ROM, especially unrooted, isn't bloated by any means at all. There is NO over-clocking at this point for any ITE kernel for the Vpad7, period - none that I know of. Folks, do NOT confuse or try this with Vpad7e (which is a different device, sorry - cannot help at all)
Regards & do post with your results and share, and, if I can help further with the specifics, will be glad to do so.
about the euvpad rom
hi there i am glad that u sugested me that rom but before i try to do anything i just want to ask that which rom is better, im asking u coz u might know as u have tried diffrent rom. i am currently having no issue with kwbr rom however somtimes lag and slowness i know its bocoz vpad has only 600mgh processor so does euvpad rom faster or is there any good thing just wondering...
if euvpad rom is better i will go ahead and intall it.. so kind of waiting on ur reply
big_b0sss said:
hi there i am glad that u sugested me that rom but before i try to do anything i just want to ask that which rom is better, im asking u coz u might know as u have tried diffrent rom. i am currently having no issue with kwbr rom however somtimes lag and slowness i know its bocoz vpad has only 600mgh processor so does euvpad rom faster or is there any good thing just wondering...
if euvpad rom is better i will go ahead and intall it.. so kind of waiting on ur reply
Click to expand...
Click to collapse
Personally, I prefer and continue to use EU V1.7b for ITE, it has support for European languages as well as Asian languages. KWBR only support Euro language and the ROM is more "stripped" down with fewer apps, but it does work nicely "out of the box" with A2SD - downside being that internal memory/storage still seem to run low (once I re-install 50+ apps on my device)
For EU V1.7 - it's using an older version of Android Market, but can be easily updated if one wanted to, and, has a few more "basic" apps pre-installed including Documents To Go - and, by adding "Car Home" - I have a working 7" GPS device in the car when needed (sound volume is low, however due to those tiny stereo speakers) - I have been running it for 5+ months now, very smooth & few, if any, FC or freezes, and, Angry Birds running nicely on it, same with YouTube videos over WiFi connection (my 3G is on Edge network, so speed is SLOW and thus very choppy due to broadband speed, not CPU-related)
If you are running KWBR nicely now, do a Backup from CWM first, wipe cache/dalvik & system next - then flash the EU Rom and setup - to see whether you like it. And, if you do - follow the post's steps that I wrote up a while back and get A2SD running with the earlier verison of CWM for ext3 partition, restore/copy back all the files to the mSD card - and reboot/check for A2SD functionality, hopefully - it works without further tweaks - and I think you will like it.
If not, it's easy enough to get back into Recovery, wipe clean it first (very important to clear all traces) and RESTORE the KWBR image from the mSD, and reboot - and you can continue using it. Set aside 2 or 3 hours to do this slowly & right, and you will find the process educational & informative - and, as I always remind newbies - the rules are simple - Backup, Backup and Backup !!
Cheers & go have fun !
So, I am looking at getting a Off the shelf nook tablet, and want to build a SD card to run cm7 or cm9 from it. but i have questions on apps, compatibility, speed and overclocking
1) the most important to me is the apps. if i build the SD cm7 boot card, and boot from it will :
a)google play be able to install and work with it?
b)will there still be apps missing because of the generic build.prop file
c)is there a way to export a build.prop from a same size (screen density) similar cpu/gpu and import it to make missing apps work ?
d)failing question c is there any way to get every app's apk file for the nook device ? (ie a google play link to apk ?)
2) on a class 10 sd card's fast enough to still be "snappy" ?
3) on sd cards, UHS class 1 capable?
4) i saw a overclocking img that can be dropped on top of the stock cm7... the question i have is how far is considered normal for overclocking success? meaning, 100mhz is not worth the time, 300mhz over would be a nice boost but what are the chances of getting 300mhz stable for plugged in gaming.
5) codecs play a lot in playback of 720p mkv and mp4 files.... how well does the stock cm7 image play moderate bitrate 720p rips ?
6) cm9.... how usable ? i need it to be idiot proof for the wife... if its "touchy"... i will opt for cm7...
7) cm7 perm install... sooo many links, broken links, private files, multiple images with different caveats... and of course the issue with build.prop... any recent updates and less link-happy guides that dont require reading all 250 pages to make sure there is not a secret sauce img file update that doesn't faff your device? and how stable ... is stable ???
thoughts ??? help???
I'm still a noob myself. But I purchased a 16gb NT last week, and within about 20 minutes had it up, rooted, and running CM7 from the internal memory card.
The process isnt difficult, and CM7 Seems to work well, HD video playback is fluid, and mostly glitch free. The Play store seems to work fine (Cant download chrome for Android, but Dolphin Browser HD seems fine!)
Sound input/output works fine, voice search, ect.
There are some (Quite minor, IMHO) bugs with CM7, but I wouldn't call it "unuseable"
CM9, which I also tried, had more ... issues.. Sleep of death unless underclocked, no HD video playback, sound input not working.
I'll link the guide, and the Support thread I used for my CM7 install.
I also, during one of my "oh crap, I bricked it" moments (Dont mess with ROM managers recovery.. espeically half awake.) Ran CM7 from SD, It seemed snappy enough, but I only used it to copy/replace a few files that I needed so I cant give a full report.
This is the guide I used
This is the support thread.
Hope this helps!
maxxcool7421 said:
So, I am looking at getting a Off the shelf nook tablet, and want to build a SD card to run cm7 or cm9 from it. but i have questions on apps, compatibility, speed and overclocking
1) the most important to me is the apps. if i build the SD cm7 boot card, and boot from it will :
a)google play be able to install and work with it?
b)will there still be apps missing because of the generic build.prop file
c)is there a way to export a build.prop from a same size (screen density) similar cpu/gpu and import it to make missing apps work ?
d)failing question c is there any way to get every app's apk file for the nook device ? (ie a google play link to apk ?)
2) on a class 10 sd card's fast enough to still be "snappy" ?
3) on sd cards, UHS class 1 capable?
4) i saw a overclocking img that can be dropped on top of the stock cm7... the question i have is how far is considered normal for overclocking success? meaning, 100mhz is not worth the time, 300mhz over would be a nice boost but what are the chances of getting 300mhz stable for plugged in gaming.
5) codecs play a lot in playback of 720p mkv and mp4 files.... how well does the stock cm7 image play moderate bitrate 720p rips ?
6) cm9.... how usable ? i need it to be idiot proof for the wife... if its "touchy"... i will opt for cm7...
7) cm7 perm install... sooo many links, broken links, private files, multiple images with different caveats... and of course the issue with build.prop... any recent updates and less link-happy guides that dont require reading all 250 pages to make sure there is not a secret sauce img file update that doesn't faff your device? and how stable ... is stable ???
thoughts ??? help???
Click to expand...
Click to collapse
1.
a) yes
b) yes
c) yes you can edit build prop (many threads) you'll never get everything on any single device
d) no nor any other device
2. I don't find anything above class 4 faster except when writing to it from pc
3. ?
4. As you have noticed at this time most roms are still on the edge (they are constantly being improved), I would not push them with overclocking. You'll pay a price for little gain!
5. ?
6. Even the stock software is not idiot proof! (my opinion)
7. ?
The question marks are things I can't or at least didn't answer. I'm sorry but you have a task ahead of you. As you will see with time, rom XYZ operates perfectly for me and when you flash it you have a brick.
Any modification to your nook you should weigh and accept that possibility. Anything can and will happen.
The folks here on XDA can do anything. Sometimes others don't feel that way but the right person has not put in their two cents at the time of that decision.
Read this thread before you begin. http://forum.xda-developers.com/showthread.php?t=1826516
Good Luck!
maxxcool7421 said:
So, I am looking at getting a Off the shelf nook tablet, and want to build a SD card to run cm7 or cm9 from it. but i have questions on apps, compatibility, speed and overclocking
1) the most important to me is the apps. if i build the SD cm7 boot card, and boot from it will :
a)google play be able to install and work with it?
b)will there still be apps missing because of the generic build.prop file
c)is there a way to export a build.prop from a same size (screen density) similar cpu/gpu and import it to make missing apps work ?
d)failing question c is there any way to get every app's apk file for the nook device ? (ie a google play link to apk ?)
2) on a class 10 sd card's fast enough to still be "snappy" ?
3) on sd cards, UHS class 1 capable?
4) i saw a overclocking img that can be dropped on top of the stock cm7... the question i have is how far is considered normal for overclocking success? meaning, 100mhz is not worth the time, 300mhz over would be a nice boost but what are the chances of getting 300mhz stable for plugged in gaming.
5) codecs play a lot in playback of 720p mkv and mp4 files.... how well does the stock cm7 image play moderate bitrate 720p rips ?
6) cm9.... how usable ? i need it to be idiot proof for the wife... if its "touchy"... i will opt for cm7...
7) cm7 perm install... sooo many links, broken links, private files, multiple images with different caveats... and of course the issue with build.prop... any recent updates and less link-happy guides that dont require reading all 250 pages to make sure there is not a secret sauce img file update that doesn't faff your device? and how stable ... is stable ???
thoughts ??? help???
Click to expand...
Click to collapse
CM7 beta internal is the only way to go at this time, atleast for my use. Reading, netflix, surfing and most games. Easy to install and very stable. Just follow the instructions given in Celtic's post and you shouldn't have any problems. Good luck.
Sent from my Nook Tablet using xda premium
Thanks everyone, i bought a 16bg nook tablet (for the 1gb ram) and booted from the SD successfully. but now have a couple more questions i will put in a new post.. cheers!
maxxcool7421 said:
Thanks everyone, i bought a 16bg nook tablet (for the 1gb ram) and booted from the SD successfully. but now have a couple more questions i will put in a new post.. cheers!
Click to expand...
Click to collapse
You don't really need a class 10 card. The best card you could use would be a Sandisk class 4. The class 10 is probably going to give you problems down the road if you're running CM7 off it.
Tel864 said:
You don't really need a class 10 card. The best card you could use would be a Sandisk class 4. The class 10 is probably going to give you problems down the road if you're running CM7 off it.
Click to expand...
Click to collapse
oh ? details please ?
class 10 cards are for like...video recording, i.e. lots of data read/write at high speeds...for normal functionality, they are, in my experience often slower and buggy
stick to a class 4 card
lag0matic said:
I'm still a noob myself. But I purchased a 16gb NT last week, and within about 20 minutes had it up, rooted, and running CM7 from the internal memory card.
The process isnt difficult, and CM7 Seems to work well, HD video playback is fluid, and mostly glitch free. The Play store seems to work fine (Cant download chrome for Android, but Dolphin Browser HD seems fine!)
Sound input/output works fine, voice search, ect.
There are some (Quite minor, IMHO) bugs with CM7, but I wouldn't call it "unuseable"
CM9, which I also tried, had more ... issues.. Sleep of death unless underclocked, no HD video playback, sound input not working.
I'll link the guide, and the Support thread I used for my CM7 install.
I also, during one of my "oh crap, I bricked it" moments (Dont mess with ROM managers recovery.. espeically half awake.) Ran CM7 from SD, It seemed snappy enough, but I only used it to copy/replace a few files that I needed so I cant give a full report.
This is the guide I used
This is the support thread.
Hope this helps!
Click to expand...
Click to collapse
Am I dumb !?!??!
I go to rom manager, it asks a question on which rom manger to install, not sure which one to pick (i assume 2.2.x) but in either case when i go to "install rom" and select the zip file. it reboots to a splat and tells me to call B&n ....
??
Guidence you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
ME: istalled to a sd card abd booted from it right now
Guide: 1. Goto install zip from sdcard
Me: go to apps > rom manager > install rom from sd card
Guide: 2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
Me: done
Guide: 3. choose the CM7-TEAM-B-BETA1-signed.zip
ME: selected
Guide: 4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
Me: done
Guide: 5. sit back for a couple of minutes while the installation is carried out
Me: splat on reboot...
do i need to sign into the android market and install a recovery tool ? there is wording to that when selecting which version of recovery ...
That’s CM7 installed, next you need to prepare the rest of the device
maxxcool7421 said:
Am I dumb !?!??!
I go to rom manager, it asks a question on which rom manger to install, not sure which one to pick (i assume 2.2.x) but in either case when i go to "install rom" and select the zip file. it reboots to a splat and tells me to call B&n ....
??
Guidence you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
ME: istalled to a sd card abd booted from it right now
Guide: 1. Goto install zip from sdcard
Me: go to apps > rom manager > install rom from sd card
Guide: 2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
Me: done
Guide: 3. choose the CM7-TEAM-B-BETA1-signed.zip
ME: selected
Guide: 4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
Me: done
Guide: 5. sit back for a couple of minutes while the installation is carried out
Me: splat on reboot...
do i need to sign into the android market and install a recovery tool ? there is wording to that when selecting which version of recovery ...
That’s CM7 installed, next you need to prepare the rest of the device
Click to expand...
Click to collapse
\
Right, sounds like you messed something up a bit trying to use ROM manager. I always install my roms from a CWM SD card.
First, lets try the simple solution.
Boot your CWM SD
Install update from SD card
From the CWM main menu, and choose "Wipe data/Factory reset"
Also from the main menu, choose, "Wipe Cache"
Next, go to "advanced" and choose "wipe dalvik cache"
Now, go back to the main menu, choose install zip from sd, choose zip from sd, and install your
CM7 Zip.
If your CM7 did not include the gapps, you'll also want to install thoes as well (That will give you google play and other google base apps)
Now you should be able to reboot into your new CM7 install -- if not, hold the power button down untill the system powers off, and try booting again.
Post your results!
EDIT::::
I just realized it looks like you're booting from CM7, SD version. If that's the case, instead, you need to make yourself a bootable CWM recovery card. I keep one near my NT at all times as it allows me to create backups of the entire sytem before mucking about, and makes installing new ROM's a snap!
In order to make your own CWM card, format your current SD card to wipe it out,
then follow my last post Here
That should get you a bootable CWM SD card, from there you'll want to copy over your CM7 zip file, and, if your CM7 image dosent contain the gapps, the gapps I linked in the above post (Thanks Veronica for hosting!!!)
Hope this helps!
lag0matic said:
\
Right, sounds like you messed something up a bit trying to use ROM manager. I always install my roms from a CWM SD card.
First, lets try the simple solution.
Boot your CWM SD
Install update from SD card
From the CWM main menu, and choose "Wipe data/Factory reset"
Also from the main menu, choose, "Wipe Cache"
Next, go to "advanced" and choose "wipe dalvik cache"
Now, go back to the main menu, choose install zip from sd, choose zip from sd, and install your
CM7 Zip.
If your CM7 did not include the gapps, you'll also want to install thoes as well (That will give you google play and other google base apps)
Now you should be able to reboot into your new CM7 install -- if not, hold the power button down untill the system powers off, and try booting again.
Post your results!
EDIT::::
I just realized it looks like you're booting from CM7, SD version. If that's the case, instead, you need to make yourself a bootable CWM recovery card. I keep one near my NT at all times as it allows me to create backups of the entire sytem before mucking about, and makes installing new ROM's a snap!
In order to make your own CWM card, format your current SD card to wipe it out,
then follow my last post Here
That should get you a bootable CWM SD card, from there you'll want to copy over your CM7 zip file, and, if your CM7 image dosent contain the gapps, the gapps I linked in the above post (Thanks Veronica for hosting!!!)
Hope this helps!
Click to expand...
Click to collapse
it is bricked. /sigh/ i knew this would not be as easy as everyone claimed.
it wont come out of recovery ..
has errors in the cwm recovery page :
cant mount /cache/recovery/log
cant open /cache/recovery/log
cant mount /cache/recovery/last_log
cant open /cache/recovery/last_log
loading the cm-7-team-b-beta1-signed.zip from the install says complete but never gets past the recovery boot
#[email protected]#$#@#[email protected]#[email protected]#$
maxxcool7421 said:
it is bricked. /sigh/ i knew this would not be as easy as everyone claimed.
it wont come out of recovery ..
has errors in the cwm recovery page :
cant mount /cache/recovery/log
cant open /cache/recovery/log
cant mount /cache/recovery/last_log
cant open /cache/recovery/last_log
loading the cm-7-team-b-beta1-signed.zip from the install says complete but never gets past the recovery boot
#[email protected]#$#@#[email protected]#[email protected]#$
Click to expand...
Click to collapse
Dont give up!
I completely -trashed- my partition tables. (Unfortunately, wiping out my serial # in the process, no more B&N factory rom for me, but I only wanted it to root anyhow)
Took me a few days, but I got it working again.
If you need, feel free to add me on skype at lag0matic ((just tell me who you are!))
See below for my answers....
1) the most important to me is the apps. if i build the SD cm7 boot card, and boot from it will :
a)google play be able to install and work with it? - installed and works fine
b)will there still be apps missing because of the generic build.prop file - can't get chrome but Dolphin works fine.
c)is there a way to export a build.prop from a same size (screen density) similar cpu/gpu and import it to make missing apps work ? unknown
d)failing question c is there any way to get every app's apk file for the nook device ? (ie a google play link to apk ?)
2) on a class 10 sd card's fast enough to still be "snappy" ? - Class 4's work best with NT...the NT seem to have issues with class 10's.
3) on sd cards, UHS class 1 capable? - unknown
4) i saw a overclocking img that can be dropped on top of the stock cm7... the question i have is how far is considered normal for overclocking success? meaning, 100mhz is not worth the time, 300mhz over would be a nice boost but what are the chances of getting 300mhz stable for plugged in gaming. - I don't overclock it CM7 works fine for me.
5) codecs play a lot in playback of 720p mkv and mp4 files.... how well does the stock cm7 image play moderate bitrate 720p rips ? HD video works find in CM7. CM9/10 are still WIP. Dev are working hard updating the releases.
6) cm9.... how usable ? i need it to be idiot proof for the wife... if its "touchy"... i will opt for cm7...CM7 beta is stable...the beta version fixed a wifi issue that the alpha version had. CM9 looks good...some issues yet with videos and SODs' I haven't tried CM10 yet.
7) cm7 perm install... sooo many links, broken links, private files, multiple images with different caveats... and of course the issue with build.prop... any recent updates and less link-happy guides that dont require reading all 250 pages to make sure there is not a secret sauce img file update that doesn't faff your device? and how stable ... is stable ??? CM7 beta is very stable. Follow Celticweb's instructions. I've done both the sd version and the internal version.
thoughts ??? help???[/QUOTE]
NikkieL
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
This is my first attempt of creating any Android Rom myself, so don't expect too much.
Changes to the original OTA update which was the base for all:
Removed Superuser in favour for a fully integrated SuperSU by Chainfire.
Changed some root related settings in the kernel to allow a full root instead of factory default.
Keyboard bug fixed for all included keyboards and added a definition for those cheap wireless keyboards with touchpad you often get with the box.
This means pressing ENTER or OK really does just that instead of only producing unwanted characters.
Several versions for download (once I managed to test and upload all), all include a power menu for Kodi to shut down the box without the need for the IR remote.
General instructions:
Download the RAR archive of your choice and unpack the contents to a micro SD formatted in FAT32.
Insert SD into box and press the little button inside the AV port while you power the box up.
Once the logo appears release the button.
TWRP recovery will start and you should do a full backup of your box first!
I do recommend a full wipe after the backup to avoid conflicts after the firmware installation.
Install the ZIP and reboot once done.
Take your time as the initial boot will take quite some time, especially for the versions with more added programs.
Just the recovery image - for those who need it.
X96 stripped down...
In this version I removed all content from the OTA update that might be considered to be a concern in legal terms.
So no Kodi addons, no streaming apps, just a naked system with the standard Google apps and a modified Kodi.
The crappy file browser was replaced by the FX filebrowser.
For those with the need for more than the Media Box Launcher I added the ADW Launcher as well as the XMBC Launcher to have Kodi as the homescreen.
After the boot is finnished I strongly recommend to update the SuperSU binary.
I left this part manual as a confirmation that the first boot and setup really completed.
Only then can SuperSU update the binary in normal mode with success.
After that reboot to clear the memory and all leftovers.
Once you are done with all modifications and app installations you might need do a full backup trough TWRP again to safe you the time if something goes wrong.
Download RAR
After a lot of swearing, flashing, more swearing and flashing I finally managed to create a fully unbranded system that can be installed through TWRP.
If you still know how the original X96 looks with the original firmware you will be surprised
What has changed from the branded firmware:
Bootlogo original S905X.
Google bootanimation - that was the hardest part, allowing for a custom animation...
Media Box Launcher unbranded and with unbranded theme.
Unbranded Kodi completely removed so the rom will comply with all piracy laws and restrictions - more in the added apps section.
OTA updater removed.
All programs from the branded version removed, so no social media, Chrome, Netflix and so on.
Apart from the naked system with Google apps I included:
AdAway
ADW Launcher
XMBC Laucher for Kodi
File browser replaced by FX filemanager
Power Menu added - still requires to root the box! More under added apps.
Added apps and modifications:
Kodi was removed, but the install script for the addon packs is still valid.
The script no longer refers to the system folder but to /sdcard/apps
This means if you decide to install Kodi you can place the tar.gz archive for the addons in the apps folder of the internal SD.
Kodi itself is not included.
The additional apps I thought to be of use will be in the apps folder of the internal SD.
In FX file explorer it is called "Main Storage".
Here you will find:
Chrome
Facebook
Film On (from the branded firmware)
Lucky Patcher
Mobdro (from the branded firmware)
Netflix (from the branded firmware)
Showbox (from the branded firmware)
Skype
SuperSU by Chainfire
Twitter
VLC for Android
Three different Youtube apps to choose from, including a TV version.
How to install SuperSU:
All modifications to the boot image, scripts, libraries and so on are done and included.
This means the system is rooted except for the actual Superuser app.
Install from the apps folder and let the binary update, once done reboot and enjoy.
Ads...
Not all ads in programs or while surfing can be disabled by AdBlock.
For example everything coming from "trusted sources" like Google will still be allowed.
This is the only reason I included Lucky Patcher as it can be of use for some apps to enjoy without ads.
Install and use at your own risk!
Installation of the ROM:
As before wipe all through TWRP then install the ZIP file from extracted RAR archive - so unpack the RAR first to your SD card.
Installation through TWRP does take a few minutes due to the hash verification.
Since all included apps are integrated into the system the first boot is a bit faster compared to the above ROM.
And the additional apps land on the internal SD for everyone to choose or delete if not wanted.
Please allow about 5 minutes after after the launcher selection appeared before you actually start using the apps - some things are still installing in the background!
Once you finnished the network and personal setup of accounts and such bott into TWRP and make a full backup in case you need it.
A factory reset will set you back to the point of the installation of the rom - so no SuperSU and the added apps folder might be gone too.
Known bugs:
Just noticed the WiFi is not available at first activation.
As the chipset is identified during activation you might have to select the network twice until you see WiFi available.
Watch the boot on Youtube
Download from Filefactory
Beta2 with shutdown using F12 on the Wifi Keyboard and some other fixes. - This is just with the most basic apps.
I finally found a neat way to use the WiFi remote to shut down the box the same way the power button on the IR does.
Just press F12 and you will be asked if you want to power down
Will upload the Beta2 with this fix soon.
What's left to do?
Well, now that there is an unbranded and working S905x system out there it means someone could use it to make a ROM that works on all S905X systems out there...
Just needs including WiFi and where existant BT drivers, libraries and calls....
And of course a recovery capable of working on all boxes but that should not be too hard actually
Update: 12/05/2017:
Beta 3 and a Fully Naked Rom is available now.
The Fully Naked Rom has the FX File Explorer and SuperSU included, apart from that it is a naked Android without any Google apps left - great if you want to play around with different GAPPS packages.
The Beta 3 has some minor fixes and most apps moved into the system area instead of the user space.
If you need more apps or launchers then please check the Playstore.
Both have a system partition inflated to 1536mb, which is the same size as the factory OTA update.
On the Fully Naked Rom you can only install apps through the filemanager as no store of any kind is included.
Update 17/07/2017:
A new firmware was released and finally we have a navbar and notification shade "out of the box".
Other changes include the launcher and Kodi, now you find KD Launcher and KD Player...
The OTA can be found here, just unpack to the SD and use as usual, either with the supplied original recovery or your favourite TWRP.
Only downside is we have a locked bootanimation again
A cleaned rom with the usual fixes for keyboard and root can be found here as my Beta 4.
All removed and some additional apps can be found in this archive, just unpack to your SD and install with FX.
Those with just 1GB system memory or wanting to customise all themself can try the Beta 5, which is made small enough to fit on 1GB systems.
Use the above archive to add the programs you need.
Libreelec for SD or USB install.
Unpack the archive to your PC and use Rufus to get the tar.gz image to your SD/USB stick - all existing data will be wiped.
Copy the dtb.img to the SD, overwriting the existing file.
Plug in the box and boot using a toothpick.
Once Libreelec is set up it will work with the SD/USB inserted without you boot the normal Android from the internal memory.
Videoboot
With this version you can use a MP4 video file instead of a bootanimation.
Works with sound of course and should support every MP4 video the normal video player can play.
For your own video simply replace the bootvideo.mp4 in the systems media folder.
Update 04/06/2017: Finally with Open GAPPS!
The X96 showed some real resistance to overcome the chinese limitations and to allow a working installation of updated Google Apps.
As I already spent a lot of days trying to get it to work I only focussed on Open GAPPS but no manual install or the XIAOMI Gapps installer.
With the troubles in the beginning I created a way of installing it all that worked with no errors for me - I suggest to follow it before you try other ways.
This Beta is right now considered to be in an experimental stage until users provided enough feedback to confirm it indeed works fine.
All is based on a naked and slightly modified Beta 5.
The system itself is pretty much naked except for the usual fixes, everything that could make troubles was removed, this includes:
Camera, video and music, wallpapers and so on - install what you want and need through the playstore once all is working.
Main reason for this was to avoid problems with the GAPPS package and to allow the use on 1GB systems as well.
How to install:
Unpack the RAR archive to your favourite SD card or USB stick.
Plug into the box and start with a toothpick - TWRP will show up.
Go to Wipe, Advanced Wipe and wipe Dalvik/Art cache, Data, Internal Storage and Cache.
Go back and install the X96-no-gapps archive and add the opend gapps archive into the line.
Upgrading the neural network takes a few minutes, once the AI is fully operational the GAPPS package will install.
Simply ignore the fact that some of the listed apps will not be available, like Faceunlock - this is due to the removed camera and other things but also because of our harware platform.
After that reboot.
If all goes well and the intial boot goes well you can simply follow the on screen instructions from the wizard.
In case after 10 minutes the Google animation is still going you have to try again but with a different approach (50/50 chance for the first to work).
Start over with a another wipe as above, then install only the X96-no-gapps firmware.
Reboot and do your usual setup of network and screen settings - don't start any apps or mess with SuperSu yet!
Once all is good reboot into the TWRP recovery and install the Open GAPPS package.
Reboot.
Now all should go according to plan.
Troubleshooting and additional infos:
If neither the first nor the second way of installing works for I suspect that your previous ROM was not based on mine or the OTA firmware.
In this case try one of my other beta firmwares if the included firmware itself already failed to boot.
The initial connection to Google can take 4-5 minutes instead of the advertised 2 minutes, so please allow 5 minutes before you panic.
The additional Google apps are not available at this stage and the loading will stay on the screen until you click next - simply add whatever Google app you need from the playstore.
This included Google Music and Google Play TV.
Again: no additional apps of any kind are included, I suggest to use VLC for audio and video or simply whatever you prefer.
Oh, before you ask: Navbar and notification shade are active and working.
Allow some time and check the notification shade for the updates once the system is running, I did not include all updated versions at this stage.
Download the new Beta 6 - Open Gapps version.
Update 15/11/2017:
They finally released another update, got available two days ago but file date is a bit older.
You can check on the Baidu servers yourself if you like Baidu X96 Downloads
Password there is: hp7u
Download as a RAR from Filefactory.
Once I find some time I will check if and what fixes are needed that I can do.
My new x96 arrived yesterday also I found this thread and instructables yesterday. I'm really glad that you take care of this little machine.:good:
Sent from my I9195I using XDA Labs
Guess I was just in the same boat as everyone else with these noname things.
Figured almost everything out I need, ecxept how to change the bootloader/kernel to allow for a custom bootanimation.
Main thing though was to have a working recovery to avoid weird UBS cables and manual flashing.
I wish I was 2 weeks further so I could test your build but I have to look through these things atm. Its interesting that the youtube tv app hasn't changed for a while.
Too many boxes available but I do think x96 is a solid little machine.
There's also opportunity to work with libreelec.
On my s4mini I have a dolby atmos app running modded by ahrion here on xda. Maybe it would be interesting.,wheather it runs on our little devices or not.
I am working on a fully unbranded firmware for the X96 atm.
The problem of converting USB burn images into flashable ZIP was one problem to get the "unbranded" original firmware to at least install another.
They really don't like you messing with their toys in china LOL
If I can't solve the bootanimation problem I will at least upload the otherwise unbranded version with a choice of launchers and updated apps.
Chinese toys. LOL.
Who has made the custom rom from February 16th. Rar @entertainmentbox?
No clue as I did not do it and did not check either.
But the fully unbranded firmware is on the way to upload
Finally custom bootanimations are possible
The pictures I've seen on instructables are awesome. Nice launcher.
Hope you're having fun tuning these Chinese toys.
Sent from my I9195I using XDA Labs
Congrats to your unbranded system. Hope there will be soon more users for testing and enjoying your work
Fixed the shutdown through WiFi remote problem
Is it possible to have look like the normal android tablet/phone?
Hey Downunder35m http://www.tvboxforum.com/archive/index.php?thread-671.html
Just curious is the remote working? I btw changed the keyboard layout so the annoying enter key is fix as well as added the F1 = Power function
Nevermind I fixed my issues with the remote too. Now it is 100% working.
Wasn't aware that the keyboard needs fixing as it works fine here, including powering down the box
I didn't upgrade to the Beta2
Hello!
I have the X96 box mentioned here. Exactly this 2GB model: https://www.aliexpress.com/item/Hot...32779857015.html?spm=2114.13010608.0.0.dF9x4G
The problem is... No matter what i do, i get the error 7 in TWRP. I tried beta1 and beta2, but same error.
I have tried retrying, rebooting, but no effect.
Any suggestions?
What i did was;
-backup files (to internal memory)
-wipe all (byebye backup )
-try to install image from sd-card or usb-stick (both fat32)
-installed TWRP recovery (which caused SD card not to be recognized anymore)
The recovery is specifically for the X96, I had no time to make a generic recovery for all S905X boxes, but seems it should be the next step here.
The error 7 through TWRP is caused by two things (at least during all my tests):
a) The system is totally wiped and the updater script is unable to find the correct hardware info as the build.prop is no longer present.
For this problem and during my tests it just works if you flash again without a wipe.
So right after the error 7 go back and install the firmware again without any reboot or anything else and it should flash successfully.
b) Your system uses different space allocations for the boot, bootloader and recovery partitions.
For this problem the only real cure is to first use the OTA installer for the genuine firmware to get the system working again.
Then only wipe Dalvik, cache and data - the system partition will be overwritten once the update starts but then the installer can find the build prop and if compatible will continue.
If you have a download for the original firmware I will try to incule your system stuff into the next recovery I make.
Otherwise you can always try the hard way if the system is currently toast anyway:
Open the updater script in the META-INFO folder (down in the last subdirectory) and remove the device check for the X96.
That would be the first two lines of the script- everything before th OTA check.
Downside of this approach is that your entire system will be replaced by mine and if your hardware is differernt or the partition sizes won't match then it still won't boot.
Let me know how you go and I will see that by tomorrow evening I have a universal TWRP for all S905X ready.
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
New!: Spacesung Oreo Debloat ScriptNotes:
1. Flash in recovery after the first boot.
2. Wipe dalvik cache ONLY! (Oreo cleans up data from removed apps automagically after rebooting.)
3. Profit!
*If you want to modify what's removed, simply open the updater-script with a text editor (preferably Notepad++) and add or remove the # sign. All apps in the stock Oreo system are listed in alphabetical order. This script should be safe to flash as is. Touchwiz, Theme store, Google play, and Samsung keyboard, are not removed by default. No files will be added to your OS either.
Ex.
delete_recursive("/system/app/AmazonMP3"); ← This would be deleted. #delete_recursive("/system/app/AmazonMP3"); ← This would be ignored.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
peter couniaz said:
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
Click to expand...
Click to collapse
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
J727P
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
Thank you for getting back to me an good luck with your build on a custom kernel for this phone we can really use one !! Thanks again !
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
Downloaded and installed nicely. Tried to switch superuser with magisk but no go, need stock boot image but all in all a good clean debloated Rom. You should include a keyboard though, your link did not work so I downloaded one on my PC and transferred to internal sd and installed. If you can get magisk instead of superuser, you will have a winner !
Sent from my SM-J727P using Tapatalk
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
You may want to try this Build I Built on TomeGJ7p's WIFI BUILD it's a good one I THINK YOU WILL LIKE IT !
https://mega.nz/#!aUlU3CiD!QERLRerFDA8497aKopbqZqZh-ZSTVfZ9GhfQQy2mBrs
PS if you like it you can use it to Build on you have mine an tomeGJ7p's Blessing !!
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
This ROM is totally debloated. I went back and tried it again, very smooth, very fast but Contacts would not sync so I could not call anyone. Google account would not sync so no play store apk update from old account.Samsung account missing so no way for me to bring certain apks and utilities from stock ROM. Bare-bones android op. But I will keep it on my sd card.
PS
I just remembered those system apks that are missing that I need, I could have installed thru Titanium Bkup! [emoji846]
Sent from my SM-J727P using Tapatalk
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
JeepinxJosh said:
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
Click to expand...
Click to collapse
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Spaceminer said:
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Click to expand...
Click to collapse
Thanks man
I used this rom as the base for my gaming phone and then stripped it down to only system framework apps. If the latter were removed it would crash the phone. Anything I removed to get to that point, had minimal impact on space (fifty or so megs) and bootup times compared to a fully loaded phone (5 seconds). Spaceminer did an excellent job on this.
Video here of bootup comparison between two Galaxy J7 Perx, one with the Spacesung rom:
https://www.youtube.com/watch?time_continue=2&v=z9bcqwLVIAA
Is the Oreo stock ROM a battery chugger?
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
ct760ster said:
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
Click to expand...
Click to collapse
Have you tried turning off all the scanning features? Also in the dev options, the switch that keeps mobile data always on, is enabled by default. It's normally off in Nougat. Turning that off should help tremendously.
That being said, I do think Oreo is a battery hog, and I don't think there's any performance gain over Nougat. My best benchmarks with this phone are running Nougat (ARG2), debloated. My battery gives me 51-52hrs on Nougat, with 17-18hrs of that being screen on time. I plan on running Oreo this week to get a good comparison between them.