Related
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
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)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!
This is thread for devlopment and discussion for cm10.1 (BCM21654)
myself working on Samsung galaxy pocket neo duos(S5312)
@Alonso1398 working on Samsung galaxy music
Contibutors:
@k2wl @Unjustified Dev @Alonso1398 @dhinesh77 @psych.half
Status for Cm10.1 on pocket neo duos (s5312)
Status for Cm10.1 on pocket neo duos (s5312)
First bootable cm 10.1 rom on S5312/S5310
Whats working ?
vibration
hardware buttons
external-sdcard
apps install
egl
camera(video recording force close because of antibanding feature)
sound
sensors
bluetooth ( minor bug only => unable to connect to any devices)
Wi-Fi
Storage
Ril,
whats not working ?
Source:
https://github.com/dhinesh77/android_device_samsung_corsica
Status for Cm10.1 on galaxy music
Status for Cm10.1 on galaxy music
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Alonso1398 said:
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Click to expand...
Click to collapse
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
dhinesh77 said:
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
Click to expand...
Click to collapse
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Alonso1398 said:
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Click to expand...
Click to collapse
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
dhinesh77 said:
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
Click to expand...
Click to collapse
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (all modes)
-Vibration
-Rotation
-CRT effect
-Sound
-Wi-fi
-Bluetooth (it can receive files but not sure if it can send)
-Storage (both internal and external)
-Button for start reproducing music tough it can't stop it
-Microphone
-Ril
What's not working?
-fm radio
Notes:
-For some reason the glow effect wile sliding is orange instead of blue
Edit: Link to the thread here
Great going guys . Hatsoff to ur work. Waiting for completion
Sent from my GT-S6012 using Tapatalk
Alonso1398 said:
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (I think)
-Vibration
-Rotation
-CRT effect
What's not working?
-Sound
-Ril
-Wi-fi
-Bluetooth
-Storage (both internal and external)
-No baseband
Notes:
-The button for start reproducing music I think it works but since there's no music because of storage problems, it can't reproduce anything but long pressing the button will open Apollo
-For some reason the glow effect wile sliding is orange instead of blue
-Also is it me or the unlock glow thing is kinda small?
Click to expand...
Click to collapse
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
dhinesh77 said:
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
Click to expand...
Click to collapse
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Alonso1398 said:
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Click to expand...
Click to collapse
bro over 95% of all bugs solved except one thats is ril
dhinesh77 said:
bro over 95% of all bugs solved except one thats is ril
Click to expand...
Click to collapse
Lol, I'm like turtle speed fixing problems then will try too with ril
Alonso1398 said:
Lol, I'm like turtle speed fixing problems then will try too with ril
Click to expand...
Click to collapse
any progress regarding ril ?
dhinesh77 said:
any progress regarding ril ?
Click to expand...
Click to collapse
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Alonso1398 said:
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Click to expand...
Click to collapse
dont worry bro i am here to help you between , all issues on samsung pocket neo duos is solved including ril....
Thanks a lot, the weird not installing problem it still there, however I can take the old working build and replace the system folder and boot.img with new ones compiled so somehow that way I can still be working however replacing the META-INF from the new builds doesn't work. I'm trying to apply the fixes for my device so now so far internal storage is finally working but external still doesn't, now that camera opens, discovered that camcoder isn't working for me, and bluetooth its activating but actually don't know if it can connect to other devices.
Thanks a lot for the help you are offering, really.
Edit: Wi-fi fixed however still without baseband and ril
Enviado desde mi MW0711 mediante Tapatalk
hi bro , i saw on github that you have merged pull request, w8ing for outcome
dhinesh77 said:
hi bro , i saw on github that you have merged pull request, w8ing for outcome
Click to expand...
Click to collapse
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Alonso1398 said:
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Click to expand...
Click to collapse
Do you patched the patches mentioned by pawitp in thread for grand duos ? ....
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.
Introduction
A new, updated version of Android for the Nintendo Switch. Now based off of Android 10 (Q) (LineageOS 17.1 with Shield TV trees) it's faster, more responsive and has many new features over the previous release, including deep sleep and an Android TV build.
Features
Android 10 based on Lineage 17.1
Significantly improved UI smoothness compared to Oreo.
OTA updates (bugfixes and new features without a reinstall).
Deep sleep that can last for weeks compared to hours in the previous version.
RSMouse support for controlling a mouse cursor with your right stick
Full Joy-Con and Pro Controller support with analog sticks and rails.
Hori Joy-Con support.
Uses Joy-Con HOS Bluetooth paring data.
Both Android TV and Android Tablet builds.
Reworked fan profiles for quieter operation.
Optimized dock support with resolution scaling.
OTG support including DisplayPort or HDMI output (no power supply necessary).
3rd party dock/hub support including DisplayPort or HDMI output.
Rewritten charging driver to properly support USB-PD.
Optimized touch screen driver.
Easier install via hekate partition tool.
Reworked, simpler, power profiles.
Much improved WiFi driver with less dropouts.
Shield TV remote app support for easy docked control.
Reboot to payload support.
Improved Bluetooth accessory support.
Auto rotation support.
Installing
Follow the tutorial here
Stay in touch
Discord:https://discord.gg/6gWvaASF72
Twitter: https://twitter.com/switchroot_org
Website: https://switchroot.org/
Sources
https://gitlab.com/switchroot/android
https://gitlab.com/switchroot
See manifest repo for build instructions.
Credits
Ave - Handling hosting of OTAs and the switchroot website. Check out her patreon!
CTCaer - Fixing a lot of things in the kernel - charging, dock, touch etc - and adding Android install support for nyx. Donate to his patreon here!
Langerhans - Figuring out the majority of stuff for deep sleep and helping massively with initial bringup.
Steel01 - Maintaining the Shield TV Lineage trees which ours are heavily based on.
Nvidia + Nintendo - ❤
Everyone else who contributed!
Reserved
Amazing! Thanks to all the devs working on this <3
Wooohoo finally here, running since Jan without issues, definetly faster than Oreo, looking forward to reflash now that it is official
Super excited about this. Long time coming!
It's a Great day for the Switch modding scene.
Thank you Switchroot team you are the best.
You guys have made my Switch a ton more useful, thanks for all the work you guys put in! ★＼(^▽^ )♪
Android 10 and Deep Sleep are great to have! Haven't tested the build yet since I won't be free until tomorrow but I'm looking forward to it!
Edit: Forgot to edit it, just chiming in to say that I've been loving it! Thank you so much devs!
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Absolutely fantastic! Thanx a lot for the release
Very exciting day, big thanks to everyone who worked so hard on this! I loved playing with the original Android release, but decided to wait for a version with the kinks worked out, looking forward to diving back in!
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
rac08241988 said:
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Just follow the guide in post
Click to expand...
Click to collapse
sashka69 said:
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
Click to expand...
Click to collapse
Dirty flash wont work, you need to wipe and repartition in hekate
bylaws said:
Dirty flash wont work, you need to wipe and repartition in hekate
Click to expand...
Click to collapse
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Fukurou83 said:
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Click to expand...
Click to collapse
The Installation Guide's 20th step is "If setup gets stuck on voice detection go back to the wifi config page in the setup and select "Skip for now"".
This should solve your issue!
Wow there it is finally!
Well done!
rac08241988 said:
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Click to expand...
Click to collapse
try redownloading, we updated the zips
bylaws said:
try redownloading, we updated the zips
Click to expand...
Click to collapse
I got it. I don't know what happened but it worked the second time I did it. Sorry for wasting people's time lol I like the improvements alot. So glad lockscreen and battery charging indicator is working properly now.
I'm simply amazed. Thank u so much for all the months of hard work @ANyOne involved!
I've got two questions:
1. If I go for the non-Android TV image, can I control the Switch in the dock with the Joy-Cons wirelessly?
2. If going for the Android TV image, would it support the Google Cast protocoll receiver-sided (meaning I could cast to it)?
Edit: Please let me add a third question:
3. Can Android access the FAT32 partition I'm using in Horizon?
Aka can I continue my SNES savegames in Android's RetroArch by pointing it's directory settings to the same folder on the FAT32 partition I'm using in Horizon's RetroArch for the savegames?
Followed the guide and been testing for a bit, this version is incredibly smooth compared to the previous one, i barely get any lag with a 64GB class 10 card
So I know this device hasn't really seen much in the way of development yet. But I was hoping to get a thread started on GSI's. If anyone does happen to get a GSI flashed that works for them even if buggy.
Please post here which GSI you were able to boot and bugs as you find them.
@AndyYan listed a root method here:
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
as AndyYan mentioned, DSU sideloader is a great tool for testing GSI's without permanently flashing them.
here is a list of GSI's that may or may not work on the device, i have tested some and you may want to as well.
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Already did, even made an overlay. Why else you think I'd be hanging around this forum?
However, quote me in your other thread...
AndyYan said:
...having tried GSIs on both, I felt N20 was weirdly stuttery/unresponsive for its specs.
Click to expand...
Click to collapse
OPlus did a bad job with its kernel/vendor, and GSI on N20 is actually slower than N200 (slightly lower-specced, and has a 90Hz display to tow). I even bought another SD695 device (from Moto) just to see if it's SD695 itself that's awful, but nope, Moto's handled GSIs swiftly even on 120Hz.
AndyYan said:
Already did, even made an overlay. Why else you think I'd be hanging around this forum?
However, quote me in your other thread...
OPlus did a bad job with its kernel/vendor, and GSI on N20 is actually slower than N200 (slightly lower-specced, and has a 90Hz display to tow). I even bought another SD695 device (from Moto) just to see if it's.......
Click to expand...
Click to collapse
Could you be more specific as for which GSI's you were able to boot? To be honest this whole treble, GSI stuff is new to me. Can we now simply flash any GSI without worrying about bricking the device? After this morning's mistake I don't want to rush into anything. I would like to flash a prerooted GSI as you mentioned in another thread but I don't want to flash something that I'm gonna have to spend a lot of time trying to repair something when I could avoid breaking it in the first place lol.
Seems like by the time I really start to understand a device, it's time to upgrade and more has changed in the mobile worlf than I have the time/capacity to get familiar with.
I need to get root on my broken device to attempt to repair it
To your worries of messing up, I answer DSU Sideloader (again, already did), which is a way to temporarily boot GSIs; pretty self-explanatory otherwise.
But if you can't boot right now, I'm afraid your #1 priority is to get it flashed back to stock reliably. My advice is don't rely on backups/dumps from others unless you know exactly which build you have (e.g. you noted down the stock "OTA number" - in which case even I can help you). Either get the customer service to do a remote session or just send it in.
PsYk0n4uT said:
Upon Searching the forums for the N10, it's unadvisable to flash a magisk patched boot.img as it breaks radios. I can attest to this as well as I did the same this morning along with a few other members.
Click to expand...
Click to collapse
I feel you just flashed some mismatching (variant/version) image...
It boots, just no radios. As for DSU, guess I just need to do some more reading. Sorry if some of this seems obvious to you, I just seem to spend so much time pouring through so much information that some of it gets to be confusing, especially when I'm researching for school at the same time. I'm working on IT certs and I think maybe the years of scouring the net and these forums too for the many other devices has left my memory a mess, wish I could remember everything I've read but my ADHD kicks in midway through anything I set out to do and I go down rabbit holes that come out somewhere far from where I started. Hopefully you guys will remain patient with my questions. Im trying to learn and mistakes seem to be the way I have always learned. Break something and fix it. Lol. But I do have the drive to do whatever it takes to fix what I break. Curiosity has always been my friend.
And as for the mismatching image, my first intuition was the same. I doubt i won't be able to fix it eventually. For now it's a project that gives me more motivation to learn.
As discussed separately you've already fixed the device and got up to rooted stock. You can now proceed to try out DSU Sideloader. The app itself isn't complicated, and the GitHub page has a readme too.
Thanks. Yeah I'm not sure. I guess something was different or wrong with the boot image I flashed. Another thread on the N10 mentioned that the magisk patched boot images broke wifi and Bluetooth for some reason. But I'm not having any issues so far with the magisk patched image of what I can confidently say is the right boot image
DSU Sideloader has been an awesome tool for sideloading and testing GSI's most GSI's work if not buggy but i have actually noticed performance Improvemtn in some. i particularly like crdroid even though the launcher crashes
Would love to get Kali ported. Too many issues with permissions on stock ROM
AndyYan said:
As discussed separately you've already fixed the device and got up to rooted stock. You can now proceed to try out DSU Sideloader. The app itself isn't complicated, and the GitHub page has a readme too.
Click to expand...
Click to collapse
If you got DSU to work on the N20 what settings did you use and which GSI? I've tried PHH, Lineage 19.1 and PixelplusUI...left the userdata to 2GB and every time I'm given the option to "restart" to boot into it, it just reboots the phone.
famewolf said:
If you got DSU to work on the N20 what settings did you use and which GSI? I've tried PHH, Lineage 19.1 and PixelplusUI...left the userdata to 2GB and every time I'm given the option to "restart" to boot into it, it just reboots the phone.
Click to expand...
Click to collapse
use dsu sideloader not the built-in one. see the dsu sideloader github page for instructions. ive actually flashed pixel experience so i know that one works. i used crdroid in dsu sideloader...... someone else mentioned they used lineage. for unrooted devices ...
DSU Sideloader by VegaBobo:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
PsYk0n4uT said:
use dsu sideloader not the built-in one. see the dsu sideloader github page for instructions. ive actually flashed pixel experience so i know that one works. i used crdroid in dsu sideloader...... someone else mentioned they used lineage. for unrooted devices ...
DSU Sideloader by VegaBobo:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
Click to expand...
Click to collapse
That's the one I installed. V1.03 on the github. adb pushed the GSI's to sdcard and then did the install do a directory called "dsu" on internal storage. Left everything default...got through install including running the adb command but when time to restart it showed the metro logo and then just rebooted. Thought I might not be giving enough userdata or something.
famewolf said:
That's the one I installed. V1.03 on the github. adb pushed the GSI's to sdcard and then did the install do a directory called "dsu" on internal storage. Left everything default...got through install including running the adb command but when time to restart it showed the metro logo and then just rebooted. Thought I might not be giving enough userdata or something.
Click to expand...
Click to collapse
did u restart through the notifications?
and do the adb command it asks u to do if your not rooted?
i just downloaded the gsi's on-device and used from internal storage but i dont think that should make a difference. and as for userdata thats up to you. if im gonna be in a gsi for a while. and especially if you wanna pull your backups your gonna need around 20gb of userdata to hold those backups unless you plan on dd'ing them to external storage in shell or something. actually i set my default userdata to 32gb in settings so i dont have to remember to do that. but usually if im testing in a GSI i plan on being in there for a while and dont want to end up wanting/needing the space and then not having it. you dont have to do 32gb but your gonna need 15gb or so for backups if you pull a full system backup, which i HIGHLY recommend and you may as well do it while your getting the boot image and do it all at once. i made a post on DSU sideloader. maybe this is good info for that thread.
also can you tell us what security patch your on and if you GN2200 or CPH2459
PsYk0n4uT said:
did u restart through the notifications?
and do the adb command it asks u to do if your not rooted?
i just downloaded the gsi's on-device and used from internal storage but i dont think that should make a difference. and as for userdata thats up to you. if im gonna be in a gsi for a while. and especially if you wanna pull your backups your gonna need around 20gb of userdata to hold those backups unless you plan on dd'ing them to external storage in shell or something. actually i set my default userdata to 32gb in settings so i dont have to remember to do that. but usually if im testing in a GSI i plan on being in there for a while and dont want to end up wanting/needing the space and then not having it. you dont have to do 32gb but your gonna need 15gb or so for backups if you pull a full system backup, which i HIGHLY recommend and you may as well do it while your getting the boot image and do it all at once. i made a post on DSU sideloader. maybe this is good info for that thread.
also can you tell us what security patch your on and if you GN2200 or CPH2459
Click to expand...
Click to collapse
I did restart through the notification and yes I did the adb command for non root. I left it as 2gb strictly because I was testing. Once I had one up and running I planned to up the space for a backup. It's currently on the may security update and I have not given it access to wifi or sim to prevent updates till I could take a backup. (well they didn't INCLUDE a sim card with my order and I'm still waiting on a replacement. Trying to use the metro sim from my n200 order did NOT work so guess it's locked to that phone). When you mention Pixel Experience do you mean this one? https://forum.xda-developers.com/t/gsi-unofficial-12-pixel-experience.4354695/
This pixel experience GSI failed to even install after running the adb command with userdata set to 32GB. Space shouldn't be an issue given it's freshly setup with ONLY DSU sideloader added via adb install. I'd like to know what you are doing different to make DSU sideloader work. I'll try moving the image to the internal storage instead of external sdcard.
I factory reset the n20...did offline setup, added dsu sideloader and the lineage GSI and followed the instructions only to have it just say "install failed" now...I give up for now. Has anyone still on MAY firmware had DSU work for them? Perhaps I HAVE to let it update. Is August firmware still A11?