Related
Hello developers!
I have some tasks that I need to implement:
1. Save Windows Mobile OS from the mobile device (to make backup copy of it).
2 Add some cab file (or other files) to OS image and write it to device ROM.
3. On device hard reset to install some files which are currently on the ROM.
For this purpose I ‘m asking you who are more experienced in the field to describe me road map of the way to achieve this.
I think in first turn I need links to comprehensible material concerning how OS storing on devices, file formats and so on. For sure you know better at the moment the right end to start with.
Thanks a lot.
Hi and welcome to the forums.
In order to better help you (so that we can direct you into the right place), we need to know which device you are talking about and what OS it has installed. Also, if it is locked or unlocked.
Welcome to Androot-N7p-ROM for the NextBook 7 Premium *ONLY.
I decided to change up some of the apps and generalize the rom in terms of its boot-animation screen. It runs on LauncherPro (just choose it as the "always"/default upon first instance of it. The Launcher that comes with the device isn't so great, but I left it there just in case.
It's based on the first known rooted ROM for this device: 'DocHoppy's ROM'. Credit for most of this ROM goes to him and to 'Wendal' for his toolset for packing the ROM (into cramfs) for the Nextbook 7 Premium device.
As such, it is a beta/ work-in-progress.
Androot-N7p-ROM v0.2
[ 146 MB ]
download here
Instructions:
*WARNING: FLASHING THIS DEVICE WILL ERASE YOUR DATA AND APPS!!!!*
Download image.
Rename file to update.img
copy file to root of SD card.
Follow on screen prompt asking if you want to run update image.
Disclaimer:
I am not responsible for bricked devices.
Here's my changes..
removed:
-youtube player <- the real youtube app is better
-explorer <- redundant
-slide me app market <- redundant now that Google's Market is installed
-quick search box <- Google Search widget is better IMO
kept/added:
-Market <- the real Google one
-root explorer - an alternative & capable file explorer
-astro file manager <- we all know it well
-quickpic 1.5.2 - a much lighter & more efficient photo organizer/viewer
-3D gallery <- some love it, some hate it
-brightness level 1.0.0 - quicker brightness changes
-ConnectBot 1.6.2 <- for those that need a SSH tool
-Officesuite full <- may as well keep it
-Titanium Backup 4.6.7 <- has some very handy tools aside from backups
-LauncherPro 0.8.6 <- may be old, but it's smooth and capable
-superuser <- because this rom is rooted
-has some of the Google Apps (go ahead and add as you see fit)
-has a custom boot animation.
Click to expand...
Click to collapse
Known Issue:
Apps2sd reports SU Binary out of date. Attemps to update this via superuser fails due to cramfs file system.
It's not perfect, but it does work well and I run it as my daily driver on my N7P.
Please give feedback or suggestions! I trust the pro devs could easily help me out with the little things!
-------------------
here are other threads related to the Nextbook 7
http://forum.xda-developers.com/showthread.php?t=1410862 (dochoppy's rom)
http://forum.xda-developers.com/showthread.php?t=1190990 (rooting talk? )
Since I'm new to modifying/cooking ROMs, here's my
Questions I have for the devs that cook ROMs all the time...
(lol)
Where do I edit the items that show in 'settings > about' in the device?
How do I change the default shortcuts that LauncherPro puts on the dock?
How do I change what icons are default on the home screen?
Where do I put custom wallpapers as part of the rom?
How do I modify Android UI colours?
Can the dialer be removes without losing "contacts"?
How do I create a shortcut to "contacts" without the phone/dialer?
(more to come I'm sure)
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
In Dochoppy's original rom/post he mentions that the device will need to have a serial number starting with YF1011. That stands the same for this rom, as it's derived from his.
Having an invalid update.img firmware file could be due to a number of things, but the one I have here works on my device.
I wish I had more of an answer, but by all means try out the tools for repacking the rom.
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
xxProphecyxx said:
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
Click to expand...
Click to collapse
I had mine half dead for a short bit until i found i could go into a low level bootloader mode and recover it. I am working on getting a the tool/images i used to recover mine uploaded and such.
Download and extract n7p_rescue_kit.zip
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder from the download
Run RK29update.exe if it says "Found RKAndroid Loader Rock Usb" on bottom you are good but if it shows "No Found RKAndroid rock usb" repeat last step.
Either flash all of the default selected items or do just system (since bootloop is in system)
Hope this helps
P.S. If you pack then unpack your custom one you can flash JUST system using the tool but be sure to use the offsets that are pre-loaded.
use a pin to push the reset button on the back to break out of the boot loop.
If after this your rom still bootloops, try putting a different update.img rom to flash, on to the sd card. Then boot into safe mode by holding all 4 front buttons after boot. the update should be found and installed after that.
Thanks!
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
aberrantjots said:
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
Click to expand...
Click to collapse
Install "Quick Sync Settings" to get to the hidden settings view.
Also did you use this guide for market? That one worked great for me.
Thanks
Working great for me so far. Thanks sharing your work.
Nice!!!
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
lost enigma 208 said:
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
Click to expand...
Click to collapse
Not sure if this rom will work for you, just guessing by your serial number. If it is to work changing between roms on these tablets is very easy. Just download the image onto the root of your sdcard, rename it update.zip (not update.zip.zip) your tablet will recognize it as an update and ask if you want to proceed. If you say yes then follow the prompts and your in business!
Sent from my NXM726HN using XDA App
Just go this to day and was plesantly suprised to find this rooted rom. Just wanted toy let you know that my S/N is YF12112xxxx and this rom work prefect for me (so far) Thanks for all the work you guys have done here. Also is there anyway to over clock the processor in out tabs?
Thanks for the comments thus far!
I would like to overclock this thing too, but that might be further down the road, as priority is on getting a different file-system for the /system volume.
Version 0.4 is coming next.
FYI:
There will be a larger span of time between updates on this particular rom for the N7p, because I will be using more stable conjumbles of things from other roms for this device. This rom is more of a remix or derivative than an entirely different rom.
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
fireproof34 said:
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
Click to expand...
Click to collapse
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
sgtfoo said:
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
Click to expand...
Click to collapse
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
fireproof34 said:
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
Oh I was talking about currents and maps. Both of those can be installed via market. I have them both on my tablet.
The ad-hoc networking is something worth putting in a later release though.
good mention.
Runs great
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Welcome. Lots of searching and trial and error ,but this is a great place to start!
lrmahon said:
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Click to expand...
Click to collapse
Sent from my NXM726HN using XDA App
Introduction
The DreamServer ROM makes the T-Mobile G1 (HTC Dream) a low-powered headless Linux server. The DreamServer ROM provides only the essential services and libraries required in order to start ADB and Wi-Fi. There is no Dalvik (and thus no Android user interface), which maximizes the resources available for server use.
WARNING
The DreamServer ROM is only intended for use by those comfortable with Linux. Once the DreamServer ROM is installed you will no longer have an Android GUI or user interface of any kind, and you will not be able to run standard Android applications or even USB-mount the SD card. The only device interaction you'll get is via ADB (and of course your custom recovery image).
Download
dreamserver-1.0.0-build.tar.gz (11.6 MB)
Revision History
1.0.0, 2013-02-02, dreamserver-1.0.0-build.tar.gz (11.6 MB), http://kidsquid.com/files/dream/dreamserver-1.0.0-build.tar.gz
Initial release
Prerequisites
Rooted T-Mobile G1 (HTC Dream) with custom recovery image that has the ability to restore nandroid backups.
Verified working adb connection via USB cable.
SD with a FAT file system (not ext2). The DreamServer ROM uses fsck_msdos to check the SD card before mounting it.
Wi-Fi access point.
Familiarity with Linux and shell scripts.
Installation
Meet all the prerequisites in the previous section.
Perform a nandroid backup and make sure you also have an update.zip on the SD card for whatever boot ROM you are currently using. Due to the extremely limited nature of the DreamServer ROM (see the WARNING above), you'll want to formulate your escape route now.
Under your existing rom, go to the Wi-Fi settings and forget any networks that you will not be using. Verify that Wi-Fi connects to your desired network.
Copy /data/misc/wifi/wpa_supplicant.conf from the phone to the root of the SD card as wpa_supplicant.conf. You'll need this in order to connect to Wi-Fi.
Copy the dreamserver-x.x.x.zip to an SD card, and install the ROM via your custom recovery as normal. No wiping of the internal DATA or CACHE partitions are necessary, as these are not mounted by the DreamServer ROM.
Reboot the phone.
When the device boots, it will turn off the backlight during init so you know that it did not hang. Wait for a while (around 30 seconds) and access the device with adb shell.
Customize the installation by adding init.sh and cleanup.sh scripts to the root of the SD card. See the "Run-time Configuration Files" section in the README file.
When you want to reboot, use the reboot command. Note that /system/bin/reboot is a shell script that runs cleanup tasks prior to rebooting. If fifosh is running, you can also reboot cleanly from within a chroot jail: killall -USR1 fifosh
Please see the README included in the tarball for additional information (key locations and files, how-to's, rebuilding the ROM, etc).
The tarball also contains example configuration files for a Debian chroot environment that sets the time with NTP and starts sshd and lighttpd.
Credits and Copyright
DreamServer was created by Jeffry Johnston, 2012.
This ROM was originally based on a 1.6 (Donut) ROM by dwang that I found to be reliable. My filesystem modifications are extensive, but the
kernel and busybox from that ROM are used unmodified. Source:
Thread: http://forum.xda-developers.com/showthread.php?t=567023
Title: [ROM][32B/Dream][Dec23][Dwang][Donut][Speed and Stability][v1.17.1]
Filename: dwang-v1.17.1.zip
Download: http://files.androidspin.com/downloads.php?dir=dwang/ROM/
Existing programs and files are copyright their respective owners. Any customizations that I have made are released to the public domain, except for the tools programs I wrote, which are released under GPLv2.
Hey cool! I doubt I wold use this, just currently don't have a reason, but its awesome to know its here! I'll test it out though as I'm curious what all could be done here, thanks!
Sent from my Nexus 7 using xda premium
demkantor said:
Hey cool! I doubt I wold use this, just currently don't have a reason, but its awesome to know its here! I'll test it out though as I'm curious what all could be done here, thanks!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for trying it out! I expected the audience might be pretty small for this, but it gave my old phone a new lease on life, and I decided it was worth sharing. I often do a lot of small-time serving of web pages, IRC bots, and such. Nothing that requires a powerful machine or much bandwidth, so I didn't want to leave my main system on all the time. With this I have a completely silent server that uses a minimum of power. And of course it was fun learning more about my favorite Android device.
Thank! I was looking for something like your rom for my little log-what-and-where-my-car-does-with-obd2-and-gps-project Downloading right now You've just made my day
How was this done?
This is a very interesting project, how would one go about making this? like what files to mess with to remove JIT and other things?
Good Job @calamari
Wow. I just have to tear this thing apart and examine its innards.
I've used a HTC mytouch as a server before, but didn't take the time to rip dalvik out. Seemed like too much work that would lead to replacing a lot of functionality with shell scripts, and saying my coding skills are sub-par is an extreme understatement
Sent from my Evo V 4G using Tapatalk 2
Wow this sounds pretty awesome. Would you by chance be able to make a guide so I can do this with my heroc?
Sent from my HTC One V using xda app-developers app
Really great thing!
Just one questions:
Is it possible to access the camera?
I think about setting up a little wireless ip cam.
dadoc
KShion619 said:
This is a very interesting project, how would one go about making this? like what files to mess with to remove JIT and other things?
Good Job @calamari
Click to expand...
Click to collapse
whoshotjr2006 said:
Wow this sounds pretty awesome. Would you by chance be able to make a guide so I can do this with my heroc?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
I don't remember the full process (lots of trial and error and learning). However, you can download dwang's original ROM and compare his files against mine to determine the changes made. Full sources are included for any of my custom additions.
dadoc said:
Really great thing!
Just one questions:
Is it possible to access the camera?
I think about setting up a little wireless ip cam.
dadoc
Click to expand...
Click to collapse
I would assume so, but I haven't attempted it. There are several files in /dev that seem camera related: /dev/pmem_camera and /dev/msm_camera/*. Under Dalvik, you could try writing a program that replaces those and saves the I/O to files for analysis.
Hello there! I have been working this app for last few weeks. Its a Rooted app named "Mobile In SDCard" which allows you to:
Run mobile apps from SD Card directly.
Its highly Portable. One can take the SD Card and plug-it in with another mobile! All your apps,contacts,mail will be available for use. Just like the original mobile.
Increased Internal storage, depending on size of SD Card.
Removable Internal Storage, by this one can hide apps.
Backup mobile in SD Card and use.
Simple two step configuration.
Unleash the Real root power!I plan to release beta-version this Friday and looking for Beta-testers. If you are interested, please let me know. I tested this only with Android-4.4 Moto-E (1st gen) and 2nd Gen. Rooted using TWRP method.
For updates , created a new group "Lonely Root" https://plus.google.com/communities/113253726177871964982
thanks!
EDIT:
Here's the download link https://play.google.com/apps/testing/in.co.giis.SpaceMachine for beta-testing. You need to join above G+ group to use this link. Cheers!
ps: If this is misplaced - please move the thread to right location. thanks!
Please remember to backup critical data before checking this app.
Steps:
1 - Overview gives current Internal storage (Click on it to verify)
2 - Configure SD Card, first step is enable root access. Now select your removable SD Card from drop-down or perform auto-detect.
With auto-detect you need to remove and re-insert the SD Card. It should appear on the drop-down, then hit save.
3 - You need to format the selected drive to complete the configuration. WARNING: If you not 200% sure about the device name, please don't proceed with format.
4 - Flexible Space will tell you the total SD Card size and current used space. Allowed space is always 4GB more than current
Internal Storage. (First 4GB is free and remaining comes with In-app purchase). Go ahead and click on button to start the cloning
process. It took approx 5 minutes to clone/sync 2GB data into Samsung class-8 micro SD Card.
If everything goes right, device will be rebooted with new removable internal storage!
Please verify import apps like contacts,mail,Gallery. Some apps may ask you re-initialize data (like whatsapp), but this should
be one time step. Later when you use portable mode, no extra effort needed.
5 - If things are working fine, with flexible space. If you have similar rooted mobile, then insert the SD Card on mobile-2 then
Configure the device but don't format the drive. Just go ahead and click portable space . Now this rooted mobile will directly
from SD Card! If you don't have similar rooted device, try another SD Card repeat above steps. Now you have multiple SD Card
that run your device
Remember, If you reboot the device, your original device will be restored. Only when you click flexible or portable the mobile will run from SD Card. Other its normal mobile with attached SD Card.
I'll try to create video of these step in a day or two. Thanks for the support!
https://www.youtube.com/watch?v=FBaMaQroVusBasic installation screencasting
great jobs sir
by the way, its like portable OS...right?
Thanks.
>portable OS.
yes and no.
yes - because all the user apps will become portable and some system apps. You can take the SD Card and use it another Mobile - All your data is there!
no - Few system apps/binaries are not cloned. Since they are tied closely with hardware (like device uuid etc).
It would be challenging to make the system apps work, depending up-on the 'Space Machine' response, I'll take this challenge At-least improve current situation.
Great job sir... will this work on rooted tabs also? shall we test it on tab? I have a karbonn ST10 tab, in which I want to test it with 16gb samsung memory card...Please advice..
I think rooted tab should be fine. But I looked into 'karbonn ST10 tab' Android version - it uses 4.1 - is that right? . Android- 4.1 is little different. If I'm not wrong, current version should work fine for versions like 4.3, 4.4, 5.0.0, 5.1.0, 5.1.1, 6.0.1.
I'll look into support for version 4.1 in upcoming versions. I've a feeling, it should be easier than 4.4 because Android started to tighten things with higher versions.
I'm on Moto e 2014, cm13 with adopted SD...will it be of any help to me?
Looks like cm13 is equivalent to Android 6.0.1 . Adopted SD is same removable SD Card right? If so , I think it should work. Please take a backup of critical mobile internal and external data & apps before trying it. It's in beta-release mode tested only with Android-4.4 Moto-e 2014. Please be 200% sure of the device name before formatting the removable SD Card.
Hello, I'm looking for help with Android version 4.3/5.0 and 5.1 - Looks like there is lot of 4.4 rooted mobile just like me
Hi, I can't browse ur g+ link.
it show me- The requested URL was not found on this server.
Please check your g+ link.
Strange , Just now I accessed it from my network. Here is the Community link:
https://plus.google.com/communities/113253726177871964982
Click to expand...
Click to collapse
After join this group you can access play store URL. thanks
I updated the app with fixes for Android-M. Test results so far:
4.4 - Works
5.0 - Status Unknown
5.1 - Status Unknown
6.0.1 - Partially works. (Hopefully, it will be working with latest patch).
If you have 5.0/5.1 rooted device and interested in Running mobile from your SD Card, please have a look the app and share the status/bugs. thanks!
Test Results so far:
4.1.2 - Fail
4.4.4 - Pass
5.0 - Unknown
5.1 - Unknown
6.0 - Fails with older version. I'm hoping it works with latest code.
---
Not looking good. If it stays this way, I plan make initial release for only 4.4 version(thus play store doesn't show the app on other OS version). And add support another OS in next releases based on further work & tests.
ngm2378 said:
I'm on Moto e 2014, cm13 with adopted SD...will it be of any help to me?
Click to expand...
Click to collapse
Yes, Now Its working on 6.0 I think should work cm13 - Please give it a try
This is for sure a great work
Two weakness:
1)Performance
You know, eMMc is way faster than a sdcard and move almost an entire system could result in a very slow device.
2)From the video I seen that it's necessary to remove and then insert again the sdcard.
For lot of devices, like mine too, it's impossible to remove the sdcard without removing the battery too so...power off
Sent from my Y550-L01 using Tapatalk
I have rooted devices that run 5.0 and 5.1, I'll give this a test when I get home and let you know how it goes. May be a while, though, lol. Wifey has plans for today...
Hacker432 said:
This is for sure a great work
Two weakness:
1)Performance
You know, eMMc is way faster than a sdcard and move almost an entire system could result in a very slow device.
2)From the video I seen that it's necessary to remove and then insert again the sdcard.
For lot of devices, like mine too, it's impossible to remove the sdcard without removing the battery too so...power off
Sent from my Y550-L01 using Tapatalk
Click to expand...
Click to collapse
I agree on the (1). Performance will be slow. Probably faster (class-10) sdcards might improve the situation.
2) Removing and Insert again is optional target for users who are not sure about device name. If you know the device name , selecting from drop-down & save should be enough to proceed.
glaks said:
I agree on the (1). Performance will be slow. Probably faster (class-10) sdcards might improve the situation.
2) Removing and Insert again is optional target for users who are not sure about device name. If you know the device name , selecting from drop-down & save should be enough to proceed.
Click to expand...
Click to collapse
Good to know
Sent from my Y550-L01 using Tapatalk
NepoRood said:
I have rooted devices that run 5.0 and 5.1, I'll give this a test when I get home and let you know how it goes. May be a while, though, lol. Wifey has plans for today...
Click to expand...
Click to collapse
Sure, thanks.. Running it 5.0 & 5.1 would be great. So far, we tested this on 4.4 & 6.0. Results for 5.0/5.1 is completely unknown and currently in-progress.
Hello dear people,
I've managed to compile a Kernel for the A515F - using the source code provided by samsung (https://opensource.samsung.com/uploadSearch?searchValue=A515F) - Version A515FXXU3BTF4.
The usage of make (...) yielded an Image (no extension) and a Image.gz file under the path "arch/arm64/boot/" within the sourcecode.
The size of the Image is 30,3mb - the Image.tz size is 10,3 mb - looks good so far doesnt it?
SInce my last kernel-development work is from 5 years ago and a lot of things changed during that time - what are the next steps in order to install this kernel on the device?
I can remember somethings, like using adb / fastboot to flash the related partitions, etc. - im going to get my head around this, but maybe someone could give me some hints ?
Ive also have some other questions:
- Flashing a custom kernel on this device trips the knox status - ive read that this disable secure folders and samsung pay - so no software that im interested in - are there any othere drawbacks of installing cfw ?
- I've read alot of A/B partitions - Ive used an android app which logs some hardware-specific information about the device and as it looks - the A51 uses A/B partitions - what does that mean and how does it differ to smartphones 5 years ago?
- From other kernel-development-work (on x64 / x86 hosts) I know that the modules of a kernel should be a part of the resulting Image / Image.gz file - is this also the case in this scenario? Are drivers / and related modules part of the kernel?
- Is it possible to test this kernel on an android emulator? I dont want to flash something somehow on a device wihtout being sure that it doesnt result in a bricked device.
Thanks in advance!
theWicket said:
Hello dear people,
I've managed to compile a Kernel for the A515F - using the source code provided by samsung (https://opensource.samsung.com/uploadSearch?searchValue=A515F) - Version A515FXXU3BTF4.
The usage of make (...) yielded an Image (no extension) and a Image.gz file under the path "arch/arm64/boot/" within the sourcecode.
The size of the Image is 30,3mb - the Image.tz size is 10,3 mb - looks good so far doesnt it?
SInce my last kernel-development work is from 5 years ago and a lot of things changed during that time - what are the next steps in order to install this kernel on the device?
I can remember somethings, like using adb / fastboot to flash the related partitions, etc. - im going to get my head around this, but maybe someone could give me some hints ?
Ive also have some other questions:
- Flashing a custom kernel on this device trips the knox status - ive read that this disable secure folders and samsung pay - so no software that im interested in - are there any othere drawbacks of installing cfw ?
- I've read alot of A/B partitions - Ive used an android app which logs some hardware-specific information about the device and as it looks - the A51 uses A/B partitions - what does that mean and how does it differ to smartphones 5 years ago?
- From other kernel-development-work (on x64 / x86 hosts) I know that the modules of a kernel should be a part of the resulting Image / Image.gz file - is this also the case in this scenario? Are drivers / and related modules part of the kernel?
- Is it possible to test this kernel on an android emulator? I dont want to flash something somehow on a device wihtout being sure that it doesnt result in a bricked device.
Thanks in advance!
Click to expand...
Click to collapse
First of all, dang that's a lot of questions at once.??
Also you might've already figured out the answers to all of em but still here are all the Answers in case you didn't or for someone else seeing this post.
Q1) For installing the kernel on the device, one option is to flash the boot image using twrp while the other is to compress to boot.img.tar and flash in the AP section of odin.
Q2) The only drawback is tripping knox which makes some samsung apps like samaung pay, samsung pass, secure folder etc to not work on your device EVER. I repeat they won't work on your device ever because tripping knox is an irreversible thing.
Q3) Yes samsung A51 uses A/B partition structures which just means that it has 2 copies of some partitions like system and vendor, for example. For more details google should be able to explain it to you better than me. Aka A-only vs A/B partitions.
Q4&5) I'm sorry but I don't know about that ? but in case you are looking for tests you can ask in A51 telegram group.