[Q] How does android boot and how to change the init proccess? - Android Q&A, Help & Troubleshooting

I really want to run pure linux on my android based device (please, no chroot, etc. suggestions) and I want to fully understand how my device boots. I'm trying to dig into the recovery and boot partition, without success (I figured out boot.img, but I can't open recovery.img) What do you suggest me to read?
Also, I saw that there is a second kernel inside recovery.img. is that right? If yes, what happens? When the real kernel is loaded? I want to make the android init to mount an img from the sdcard and execute /bin/init in it, in order to boot my linux system. Should I alter the ramdisk (hence the boot partition) or the recovery?
I also posted this to stackexchange [1] but got no helpful response.
Thank you.

bump

Related

[Q] Best way to backup and restore on a number of devices

Hi
I've done a bit of searching but can't find anything too specific to what I'm trying to do. Basically we have 10 Android tablets, and I want to make them all standardised e.g. have the same Apps on, configured in the same way (e.g. enterprise wireless network added).
Now the thing is if anyone messes around with them I want a really easy way to restore them to the original config which I've done.
One way I thought was to configure one fully, install Titanium Backup on it, do a full backup of apps/system data etc, and put the backup onto an SD card. Then I already have the base ROM on an SD card so if theres any problems, I can just flash the ROM over it again, install TB, and restore all the data. Would this be suitable to do to duplicate the data onto 10 tablets, and also restore the data if required?
The other thing I looked into was customising a ROM myself, don't want to do anything too tricky it'll just be a case of removing all the preinstalled crap I don't want, preloading the Apps we do want, and if possible preloading the wireless key and getting rid of the first boot initial set up wizard.
PS I've looked at installing CWM and doing whole image backups, but supposedly the tablet isnt supported (its an Ainol Novo 7 Elf 2)
Any advice would be great, hopefully theres some fairly straight forward way of managing this
Thanks
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
kuisma said:
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
Click to expand...
Click to collapse
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
fro5tie said:
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
Click to expand...
Click to collapse
Ok, I see. Compile the image to you likings (boot image and system partition), and then flash it using fastboot onto you devices.
Hi
Does anyone have any more thoughts on this?
I have experimented with Titanium Backup and this seems to work quite well. I have installed a ROM, and customised it e.g. installed the apps I need and configured the apps, wireless settings and home screens etc. Then I do a full apps + system backup in TB to my SD card.
Then the plan is, I can reflash the ROM onto the other device, install TB and then restore this backup. This saves my user state and wireless settings etc.
Only problems is when I flash the ROM, I have to go through all the initial set up again and also remove some preinstalled apps which I dont want. Any ways around this?
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
kuisma said:
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
Click to expand...
Click to collapse
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
fro5tie said:
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
Click to expand...
Click to collapse
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
kuisma said:
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
Click to expand...
Click to collapse
Hi
Thanks for the quick reply, much appreciated.
Unfortunately you've lost me a bit here!
Yes the device is rooted, I dont have a linux machine though.
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
fro5tie said:
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
Click to expand...
Click to collapse
I can provide you specific answers to specific questions, but I have no experience of the tablet in question, so you'll have to do some digging yourself first. Make sure it supports fastboot, investigate what the proprietary bootloader is capable of, see how/if you can obtain an original image etc.
One maybe easier solution, especially if you plan to restore the tablets on a regular basis, is to only make a new boot image to reflash the devices with. The only modification done is that you change the /init.rc script to mount /data and /system from the SDcard instead of from the internal nand disk device.
Once this is done, you'll power up and run the installation wizard and everything on your master tablet. Then power it down, and clone the SDcard. This SDcard now contains everything, so you'll simply restore a device by replacing its SDcard with a copy of this master card. I guess it's easier to clone a SDcard than reflashing several internal partitions. Easier to make the master as well - you don't need to dd or tar them, they are already in "image" format. If you can get hold of the original firmware, this should be quite easy without the need to preserving data from the device itself.
fro5tie said:
Any chance you'd be able to provide some more specific instructions?
Click to expand...
Click to collapse
Issue the commands "cat /proc/mtd" and "mount" on your device at command prompt (e.g. via "adb shell" or the "ConnectBot" terminal app). This shows you if the device allows you to copy the boot image from it. Paste in the output into this thread. If you believe the "clone the tablet via the SDcard" is a good solution for you, the process is in short terms something as below;
Copy the boot image to the sdcard:
# dd if=/dev/mtd/mtd2ro of=/mnt/sdcard/boot.img bs=2048 (device dependent of contents of /proc/mtd)
Remove the sdcard, insert into a computer, split the boot image info kernel + initramfs. Read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images for instructions about how to work with the boot.img file. I really recommend a GNU/Linux environment for this.
Then edit /init.rc replacing the "mount yaffs2 [email protected] /system" with "mount ext3 /dev/block/mmcblk0p2 /system" for system and data (use p3 for data partition, the device name may be different on your tablet, see mount output).
Create an SDcard with three partitions: #1 vfat (standard), #2 and #3 ext3. Insert into you device and boot it up again.
# mount -t ext3 /dev/block/mmcblk0p2 /root
# cd /system
# tar cf - . | (cd /root ; tar xf - )
# umount /root
# mount -t ext3 /dev/block/mmcblk0p3 /root
# cd /data
# tar cf - . | (cd /root ; tar xf - )
# umount /root
This copies your partitions to the SDcard. Shutdown the tablet again.
Make a new boot.img using the instructions in the link above, using the edited init.rc script.
Now you can non-destrutive give this a try.
Place you tablet in fastboot mode (often vol-up (or vol-down) during power on).
$ fastboot devices
This vill verify the tablet is in fastboot mode. It should be listed. Then:
$ fastboot boot boot.img
Note here, only BOOT the tablet, do NOT use the "flash" keyword. This in case of the image isn't working, you'll just have to restart you tablet, and no harm's done.
Look around. Do a "mount" command. Everything works? Mount shows /data and /system from sdcard? Perfect. Now you can reflash it. Shutdown and flash:
$ fastboot flash boot boot.img
Now the device will use /data and /system from the SDcard every time. Customize your device, and then clone your SDcard and try it in tablet #2 you'll booting with your new boot.img and the cloned SDcard. Verify that #tablet #2 is a perfect clone of tablet #1. It is? Now you can flash the boot,img into all your tablets.
--------------------
But don't forget, there may be other solutions as well, maybe more suitable. This you'll have to investigate yourself.
And the usual disclaimer - you can probably not follow above by the letter. There sure is some obstacle you'll have to overcome, something non-standard, etc.
Also keep the original boot.img file for safekeeping in the case you want to restore the device's boot image some day.
Wow! Thanks for the info! This is really helpful, I need to set aside a bit of time to work through this and have a look. Thanks again its really appreciated, I'll be back with info once I've had chance to give it a go!
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
tweeny80 said:
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
Click to expand...
Click to collapse
Hi
Yes that was my first thought as well, tablets are rooted yes but there is no CWM for the tablet. Its an obscure Chinese branded tablet.
Unless there is another way to do nandroid backups?
hmm tricky situation. Catch 22 ! From what I know, your best bet is to backup all possible things through Titanium Backup given that you don't have the use of Nandroid backups. You can include wifi settings, messages etc but it's modular & not systemic.
I did a quick google search with no luck - time to upgrade your fleet dude :-0
Best of luck.

New kernel with dual boot

Old method, read post 2
Date 05-11-2012 Huawei s7-105 dual boot kernel
by hal_2000
Hi all, first i like to thank irfanbagus without is help this cound not be possible, look at the
original post: http://forum.xda-developers.com/showthread.php?t=1598803
This is stock kernel 2.6.32-9-ideos plus dual boot features
kernel 2.6.32.9-ideos == android 2.2.2 == froyo
Warnings:
If your kernel different from 2.6.32.9 it will not work
If you dont know what you are doing stop, I'm not responsible if you brick your device
the rom2 must be compatible with kernel 2.6.32
Works on:
my huawei s7-105
huawei s7-10x – possible if kernel = 2.6.32-9
huawei s7-slim – possibly not, because different hardware
How to install:
Follow this steps, if not sure, stop do not go on
1.1-back up your rom, just in case
1.2-must be root, huawei must be rooted to work properly, if not stop
1.3-must have cwm install, if not stop
1.4-in external sdcard make 3 partitions, format it in ext2, in stock kernel ext3 does not work
1st fat32 for your data
2nd ext2 for system
3rd ext2 for cache
4th ext2 for data
if you have already an scard in fat32, resize is a good option
I use a 2gb sdcard, 1gb for fat and 300mb for other partitions, i'm a linux user so I use gparted
to create partitions, windows tools are also available, google for it
1.5-unzip the file in a directory
1.6-connect huawei s7-105 to pc
1.7-boot huawei in fastboot mode, exec “c:\directory\adb reboot bootloader”
1.8-wait, until it blanks the screen, on top in says --fastboot mode--
1.9-exec “c:\directory\fastboot flash boot boot-dual.img”, it will take 20 to 30s
1.10-exec “c:\directory\fastboot reboot”
1.11-thats it, you just install the stock kernel with dual boot
How to test it:
2.1-read the how to install, and install the kernel with dual boot
2.2-back up your rom, if not done in 1.1
2.3-you must have rooted the huawei, if not stop
2.4-you must have cwm install
2.5-boot huawei in cwm = recovery exec “c:\directory\adb shell”, then “#su”, and finally type
“#reboot recovery”
2.6-you have rebooted in cwm, choose install zip from sdcard, then choose apply zip, chose file
stock-test-rom2.zip
this will install the custom rom “stock-test-rom2” to sdcard partions 2,3,4
it will take 4 to 6 minutes, it depends on speed of sdcard
2.7-after install, it will return to menu, click power = get back to menu
2.8-reboot
2.9-huawei will boot in rom1, the one you have already,
2.10-go to file explorer, create a empty file in external sdcard = 1st fat partitions, name it
“bootsdcard”
2.11-reboot
2.12-it will boot the rom2, it will take 4 to 6 minutes, the 1st time, depends on speed of external
sdcard
2.13-to boot the rom1 again, simply delete the file “bootsdcard” in 1st fat partitions
Why have dual boot ???
I have done it just to prove it is possible
No, I did it to improve my huawei s7-105, the people at huawei stop development for this fine
little tablet a long time ago and I want to have gingerbread on it or android 4.01, got tired of waiting, so
this way is easier to test custom rom, and less provable to brick the tablet when in development.
The rom2 must be compatible with kernel 2.6.32, you can not install android 2.1 in rom1 and
android 2.2 in rom2, is not possible
To do next:
– compile better kernel, with ext3 or battery saving options
– compile a better custom rom, maybe gingerbread or ics or cm9
file list in zip:
boot-dual.img = kernel 2.6.32-9 with dual boot
stock-test-rom2.zip = simply custom rom = stock rom test = android 2.2.2
fastboot = fastboot for linux
fastboot-windows = fastboot for windows
adb = adb for linux
adb-windows = adb for windows
problems in install, post it, I will try to help you
link to the zip file: https://www.dropbox.com/s/6x5pcymooopb4z6/s7-105-kernel.zip
Sentence of the week... “,,,dont ask for it, do it...”
multi-boot kernel
New method, multi-boot n roms
With this method we can test new roms faster then the dual-boot, no need to create the partitions, and we can have many rom, as long we have space in external sdcard, for now only 3 rom available, if you need more ask, i will extend to 20
you will need about 500mb of space for each rom
How it work:
Begin by creating the following directories in external sdcard:
/sdcrad2/multiboot/rom2
/sdcrad2/multiboot/rom3
/sdcrad2/multiboot/rom4
inside of rom(x) must be 3 files, system.img, data.img and cache.img
to create files, in linux do:
dd if=/dev/zero of=system.img bs=1000000 count=200
mkfs.ext2 system.img
make it a ext2 file type, the 2.6.32 kernel only accepts ext2 files, for me is better I think because ext3 and ext4 have journaling that implies a lot of reads and writes, reducing the life of the sdcard
then mount the system.img file in linux
mount -t ext2 -o loop system.img /some_dir
copy the files of the rom to /some_dir, adjust the files permissions like you see in updater-script
unmount /some_dir
and copy the 3 files to “/sdcrad2/multiboot/rom2”
create a empty file in external sd card like “/sdcard2/rom2”
install the multi-boot kernel, boot in fastboot (vol up+home+power) then execute in command line
fastboot flash boot boot-multi.img
fastboot reboot
that it,
in the case the rom doesn't boot, remove battery and sdcard, power on and it will boot from rom1 (phone internal memory)
roms that work with this kernel, tested in one S7-105
-- stock rom, Indonesia 2.2.2
-- froyofusion rom, by joelian good rom
-- trizet v03, by tri-zet
to do next:
--maybe port cm7 to S7
questions:
ask, I will reply.
https://www.dropbox.com/s/697ye5exf6386nw/multi-boot.zip
hal_2000
Hi,
do you know if CM9 oder CM10 will function? Which kernel is used by CM9 or CM10?
Hi, i'm not sure but all the cm9 and cm10 roms i have lookup use kernel at least 2.6.35 or 2.6.38, this dual-boot kernel is 2.6.32 so probally will not work, but if you have a more recent kernel for huawei s7, give it to me and i will add that function and see it it works.
Note: i was wrong, last night found a cm10 version in a russian forum that uses kernel 2.6.32-ideos with some add on.
I also want in the future to compile a more recent kernel, but write now i'm learning how i can port roms
Hal_2000
hal_2000 said:
Hi, i'm not sure but all the cm9 and cm10 roms i have lookup use kernel at least 2.6.35 or 2.6.38, this dual-boot kernel is 2.6.32 so probally will not work, but if you have a more recent kernel for huawei s7, give it to me and i will add that function and see it it works.
Note: i was wrong, last night found a cm10 version in a russian forum that uses kernel 2.6.32-ideos with some add on.
I also want in the future to compile a more recent kernel, but write now i'm learning how i can port roms
Hal_2000
Click to expand...
Click to collapse
Hello hal_2000
Would u share ur initramfs source?
Im try to port to my p1000 from original thread (irfanbagus) but not luck.. exec command not running when i add to init.rc
Ps. Thats irfanbagus too give me info that u try to port to tab so i ask to u..
Thanks before
savie
Hi Savie, your kernel for galaxy y works great, thanks for that.
My initram source is the same as irfanbagus (dual-boot) , the multiboot its the same with a few more lines , you can extrat from the boot img file, here is the link
https://www.dropbox.com/s/0cxj05isqvswucp/boot-multi.img
If you need more help, ask.
p.s.
One question about arm toolchain, do you know wicht toolchain comes gcc version 4.4.0 ?
My S7-105 kernel is compile with that version, i have version 4.5.2 when i compile the kernel it boots but then reboot, i guess the modules are not compatible, i need to test with arm toolchain with gcc 4.4.0.
hal_2000
hal_2000 said:
Hi Savie, your kernel for galaxy y works great, thanks for that.
My initram source is the same as irfanbagus (dual-boot) , the multiboot its the same with a few more lines , you can extrat from the boot img file, here is the link
https://www.dropbox.com/s/0cxj05isqvswucp/boot-multi.img
If you need more help, ask.
p.s.
One question about arm toolchain, do you know wicht toolchain comes gcc version 4.4.0 ?
My S7-105 kernel is compile with that version, i have version 4.5.2 when i compile the kernel it boots but then reboot, i guess the modules are not compatible, i need to test with arm toolchain with gcc 4.4.0.
hal_2000
Click to expand...
Click to collapse
Thank you hal_2000 will check later im on phone mode this week..
Thats make me confuse in young only follow irfanbagus and working but when try to gtab p1000 with same procedure its nothing happen..
Still follow samsung source recomended use arm-2009q3-none-linux-gnueabi gcc4.4.1 coz so far only that can make my kernel booting..
I think something not good in my initamfs coz cant execution 'exec' command and i dont know why..
Hi Savie, lets see if i can help you, if exec dont run, check if you have busybox in /sbin, check the version and permission, also check type of cpu, best bet is copy busybox that is working on device, irfanbagus dual-boot as busybox for a arm v6 cpu, my mutlboot as busybox for arm v7 cpu, diferent types of devices uses diferent type of cpu, busybox need to be compatible with type of cpu.
Hope it helps, try to connect to device with adb as soon it boot up, and check what is executed.
good luck, need more help ask.
hal_2000
hal_2000 said:
Hi Savie, lets see if i can help you, if exec dont run, check if you have busybox in /sbin, check the version and permission, also check type of cpu, best bet is copy busybox that is working on device, irfanbagus dual-boot as busybox for a arm v6 cpu, my mutlboot as busybox for arm v7 cpu, diferent types of devices uses diferent type of cpu, busybox need to be compatible with type of cpu.
Hope it helps, try to connect to device with adb as soon it boot up, and check what is executed.
good luck, need more help ask.
hal_2000
Click to expand...
Click to collapse
Mmm i see i use irfanbagus busybox,., thats maybe the problem,., i will try next week coz my laptop still repair,., thank you for ur advice friend,.,

Recovery as a another operating system?

Hey everybody!!! I was just wondering to myself, is it possible that someone out there will make an android recovery which will work just like the actual operating system?
I mean that when you would boot into recovery - you will see a homescreen with apps you can tap on and open - just like android.
Soooooo is it possible? And if it is - is there anyone out ther willing to do it? Because it will be awesome!!!!!!!!!!! ( i know it's like dual boot, but it's cooler!!!!)
because the partition of recovery is too small, we can't put full features os like android into recovery partition
Sent from my Redmi 2 using Tapatalk
Maybe with root rights you can change that partition? I'm nearly 100% sure it's possible
The recovery is already a separate operating system. However it's not Android - as other users have pointed out, there is no space for a second Android system on a normal device.
Most devices have two boot images that each contain a Linux kernel and a ramdisk image - one boot image for Android, one for the recovery. The bulk of the Android OS is on a separate /system partition. Recovery runs fully from the ramdisk.
If you have a storage device (like a microSD card) with additional free space, then it is possible to create separate /system and /data partitions there for a second independent OS. You could use the recovery boot image to boot that OS, but you may still need a recovery, so you'd need to add some code in your secondary boot image to switch between recovery and your secondary OS.
So... is it possible? Yes. Will I do it? No.
Thanks for the answer and clarification!!!
And if you could help me a bit more: do you know of some kind of dual - boot development project which has already been started for the gs5? I have a micro sd card and am flabberghasted by the idea of two OSs on one device. Thanks!!!
You can try this http://forum.xda-developers.com/showthread.php?t=2447534
Thanks!

[Q] Rooting Android from Windows on the same dual-boot device

Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Burs said:
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Click to expand...
Click to collapse
Root needs a custom kernel. Not something you are gonna do with a Windows setup the way you have it. Also you will most likely not find anything as that is most likely not an official version of Android as Google doesn't allow dual booting.
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Burs said:
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Click to expand...
Click to collapse
what su is doing is pulls the kernel and patches it. root access is defined in the kernel. what itnis doing in system is flashimg just the apk
Ok, I see. So if I ask someone who rooted the same model successfully to send me patched kernel, I could easily flash it in fastboot mode (my bootloader is unlocked). So only thing left to do would be to copy apk inside /system/app, and cross my fingers? I'll post my findings if I manage to do something worth writing about. Thanks.
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
bahuy2003 said:
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
Click to expand...
Click to collapse
I managed to root my Onda few days after my last post, but forgot to post my findings, sorry. I didn't used any of my hacker's skills lol, but I researched a bit more and found out what I was missing. The same issue is with you, so you have to disable verity before flashing recovery by typing in these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
After rebooting install supersu.zip, and the next boot won't hang on Onda logo anymore. Hope this helps you.
btw, note that not just any adb version has verity command line switch. You have to download newer adb version!
Thank you! I trie a lots times, but i can't make successfully!
Basic root procedure would be: unlock BL -> disable verity -> flash (temp) recovery -> install SuperSU
Here are the links containing all the files neccessary for rooting Onda V80 Plus: Mega | MediaFire
Note the ReadMe.txt inside archive. It contains list of adb/fastboot commands needed to be executed in order to successfully root the device.
Thank you very much! I download your file and root successfully my Onda V80 plus! It works well for me.

Porting Arch Linux to Redmi Note 4

Hello everyone, I am new here, please excuse me if I am posting it in the wrong place.
I am planning to port Arch Linux to Redmi Note 4(mido). Am I doing something pointless?
And my current picture about this:
1)Try to use existing kernel
2)Create an initramfs and replace the default ramdisk in the boot.img
The initramfs contains necessary drivers for sdhci, display... I think udev hooks can be placed for loading on startup
Now, the FSTAB..., I am going to configure fstab to mount the system partition as rootfs.
I am going to make the system image file and flash it through fast boot
3)Kernel, as usual executes init from ramfs, which loads drivers, mounts /system as / as and executes systemd
I am a noob, please forgive me if it is stupid, I need opinion on how to proceed(or not), I am currently studying in grade 11, so no plenty of time. Help would be appreciated.
Thanks!
generex441 said:
Hello everyone, I am new here, please excuse me if I am posting it in the wrong place.
I am planning to port Arch Linux to Redmi Note 4(mido). Am I doing something pointless?
And my current picture about this:
1)Try to use existing kernel
2)Create an initramfs and replace the default ramdisk in the boot.img
The initramfs contains necessary drivers for sdhci, display... I think udev hooks can be placed for loading on startup
Now, the FSTAB..., I am going to configure fstab to mount the system partition as rootfs.
I am going to make the system image file and flash it through fast boot
3)Kernel, as usual executes init from ramfs, which loads drivers, mounts /system as / as and executes systemd
I am a noob, please forgive me if it is stupid, I need opinion on how to proceed(or not), I am currently studying in grade 11, so no plenty of time. Help would be appreciated.
Thanks!
Click to expand...
Click to collapse
en.miui.com/thread-724324-1-1.html i have already made a thread since i also want to port nethunter and lets see if can see some response

Categories

Resources