I have an android device running Android 5.1.1 but on a proprietary build that doesnt include GApps.
What i want to do is root the device, but in order to do so with Magisk, I need the Stock ROM boot.img file which I cant find anywhere because they arent open source like Samsung ect. There is also no TWRP build for it, official or ortherwise.
The device is a Rand McNally OverDryve 8 Pro.
Anyone have any ideas on how to get the boot.img file without having exising root or TWRP? Maybe with adb without root though, unless some way to gain root shell without root device.
Or can anyone point me to a DETAILED, uptodate guide on how to compile TWRP myself, inculding setting up the build envirment and which version of Ubuntu I should use. I have tried previously with some older guides using Ubuntu 12.01 or somthing but lots of sync and repo issues and such and i gave up as im jist learning on the fly and not capable of deep troubleshooting.
Related
Hi everyone,
Thank you for reading this thread question.
I have an Android 2.3.3 Mediatek MTK 6573 Phone. I am trying to learn how to make a custom rom. I like to know what tools we need to use in order to develop on this phone and in general. I have a few questions about the process to setup and make a custom ROM.
I rooted my phone using SuperOneClickv2.3.3-ShortFuse. I'm trying to perform backup of the rom before I flash the ROM. I'm atta
1. Backup
http://forum.xda-developers.com/showthread.php?t=1683883
The backup shell script uses mkyaffs2img, but it appears to be missing on my phone. Is there a correct site to get the right binary for mkyaffs2img to execute on the phone?
Currently when I try to backup the last part of the sh file this binary was missing
cat /sdcard/Install/BackUp/yaffs_back_2.3/gen/mkyaffs2image > /system/bin/mkyaffs2image
I tried to get a copy from code.google (http://code.google.com/p/fatplus/downloads/detail?name=yaffs2-source.tar&can=2&q=)
I get the error /system/bin/mkyaffs2image: 1: Syntax "(" unexpected
I tried using Nandroid, but I don't see the system.img or ramdisk.img file that represents the ROM system.
2. Flash ROM
http://bm-smartphone-reviews.blogspot.com/2011/10/mt65x3-flashing-tutorial.html
From the same thread there is mention about SP Flash Tool. What is the scatter.txt file? Do we need to find it some where?
3. Android source
Can we use the android source (http://source.android.com/) to make our own custom ROM? If so how do we include the drivers that are specific to the phone? I can build my own custom system.img and ramdisk.img with the android source and load it on the emulator, but I don't know if I can use those img and flash it onto a real android phone. I'm aware of the idea of android fragmentation, but looking at android source code, it seems we need the specific vendor drivers to be included in the source build. Is this the difficult part in flashing roms for specific phone hardware?
Thanks for you help and explanatins .
I think I'm trying to over complicate things, but this is my first time flashing ROM in android, rather than windows mobile >_<
Best,
SoLi26200
after looking at numerous threads and advice, it seems quite complicated to install a simple fn app, which by definition, is supposed to be easy,
why firefox doesn't have it, considering that most stuff is only available on itunes or google store these days, is beyound me.
Even more so that i thought that the dual core would a) let me run ffos or android ie via easy restart mode,
and b) android would have the google store app.
so. how do i get this on. some ppl seem to be able, and there explanation is: its complicated.
fair enough. i hope you will help me and others to work through this. An explanation for dummies.
this is the best post i'v seen so far.
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
along with these links:
http://developer.android.com/tools/help/adb.html
https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
so i can change my os from ffos to android and back. no problem:
https://www.youtube.com/watch?v=axOYIfo7y2s
http://down.comebuy.com/Open_c_root_Android4.4.rar
but i get stuck with "adb reboot bootloader"
that won't work, so advice for dummies, from that point forward would be much appreciated. Thanks
ok, so tried installing two other adb programs, http://www.rockchipfirmware.com/sites/tntfiles/PDAnet-64bit.zip
and while neither where completely successful, they did manage to allow adb to access phone,
and for the commands to have determined affects, so have moved on to Upgrade tool, which does not recognize device, thoughts? help?
Hi darth lotus,
To install google play store, you need to be able to write to the system file system, to do this you would either need to root and push google apps (gapps) via adb, or replace the stock recovery with a custom recovery which will allow you flash .zips that are not signed by ZTE.
Installing clockworkmod recovery, for example would allow you to do this,
There are examples of clockwork recovery here http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173 and here http://www.modaco.com/topic/373213-recovery-clockworkmod-6050-for-zte-open-c-kis-3/
And TWRP recovery here http://www.modaco.com/topic/373288-recovery-twrp-2710-for-zte-open-c-kis-3/
The second clockwork and the twrp recovery are by a developer named Konstat who has uploaded all his sources to github https://github.com/KonstaT/android_device_zte_kis3
Konstat has also started work on getting a stable version of Cyanogenmod 11 on the ZTE Open C, please see here http://www.modaco.com/topic/373214-devrom149-cyanogenmod-11-android-444-for-zte-open-c-kis-3/
I apologise for linking to a different website but until we can ask xda to create a zte open c forum, I do not really have an option :crying:
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.
Hi everyone,
as title suggests, I'd like to "port" clean AOSP to be able to install and run it on the custom device.
Basically, the situation is following: I got a custom device, based on rockchip rk3288 SoC. The device currently runs Android 5.1 successfully. I'd like to update Android to version 6 (got AOSP sources and AWS builder image up and running), but the company that created Android v5 for us no longer exists.
Thus I am here to ask for advice(s) on how to proceed (or whether it even is a good idea to do that myself, given the fact that I have zero experience with Android ROMs development), possibly a step-by-step guide on what to do.
The question is, do I just find drivers for hardware components present in the device (usb hub, ethernet, etc.) and just somehow "link" those to existing sources (of AOSP) and just run the build with different parameters? Or do I need to build a whole new kernel for the given device-OS combination?
Thank you for any advice or opinion!
Well this is an interesting one. There are several routes you can take here.
If you have the kernel source code, and the source code for the drivers, you could probably build the kernel from source and use it to boot Android, however, as that's unlikely, you're looking at a more regular porting process, which usually consists of pulling the vendor blobs from the existing Android system, building AOSP/Lineage with those blobs involved, and hacking together a new ramdisk that HOPEFULLY will be compatible. It's a very long and very tedious process, but it's certainly possible.
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
abtekk said:
Well this is an interesting one. There are several routes you can take here.
If you have the kernel source code, and the source code for the drivers, you could probably build the kernel from source and use it to boot Android, however, as that's unlikely, you're looking at a more regular porting process, which usually consists of pulling the vendor blobs from the existing Android system, building AOSP/Lineage with those blobs involved, and hacking together a new ramdisk that HOPEFULLY will be compatible. It's a very long and very tedious process, but it's certainly possible.
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
Click to expand...
Click to collapse
Thanks for pointing in the right (or at least some) direction! I found some guide on porting ROMs which I followed, basically like you said. So I just replaced some files in System image. Will flash later today, so maybe I will get some results!
abtekk said:
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
Click to expand...
Click to collapse
So I was following this tutorial, although found some irregularities, let's say: For example, none of those 2 folders contained init.d/ directory, thus I didn't update it. Also, I haven't found META-INF folder therefore haven't updated updater-script.
Basically, when I did (or at least what I think I was doing was that I took /system partition from our current ROM, that is working on that custom device and replaced stuff in there by stuff from the new system I wanted to port. My idea from what I've read was that i took kernel (and boot/recovery) from the original, working ROM and "injected" the new system onto it. Is that correct? Is that what I needed to do? Because the problem is, I cannot boot into the system (might as well be because of Kernel version, because I am trying to port Android 6 on Kernel 3.10. which was used in the current ROM running Android 5). It looks like the device is stuck in bootloader, or "somehow doesn't know what to start" (sorry, I can't put it better), displaying only my device's logo.
When I connect it to the computer via USB cable, running adb devices shows me that device, but when I try to access shell using adb shell I got error saying that /system/bin/sh wasn't found, which made me thinking that somehow the /system partition isn't "linked" properly, like I stated in the beginning.
Was I doing everything correctly? Do I need to do something above that? (maybe do you know about some tutorial). I am trying to port AOSP 6 Android.
Thank you!
Hello,
I was just wondering, how would I go about adding several binaries to a busybox installation.
For ex: I would like to add "exa" to use instead of ls, "fd" in replacement for find, the text editor "micro", as well as possibly git (although I would guess that adding too many additional binaries would make busybox too dense)
I know a good deal about android development, c programming, and shell scripting, so I don't by any means expect someone to "do" this for me or recompile it for me. Just the steps necessary (if it's possible to do this effectively), or an alternative solution in which would accomplish this objective.
Currently I have a (working) solution using termux boot, that copies the files to "/system/xbin" on boot. It works fine... however I can't help but feel like this is not the best way to go about it.
If it matters: I am on a Google Pixel, rooted, on a custom rom (resurrection remix, android oreo build) with TWRP recovery installed.
Thanks,
HLTDev