Related
I am having a problem with rooting my n7 recently I decided that I would flash back to stock clean wipe sd card and reroot, well it didnt work out that way, flashed back to stock without a problem, then rerooted ok, but then was prompted to install 4.2.1 from google, well I did and here I am cant get rerooted after installing update. I use wugs tool kit and has always worked on my GNex and until now my N7, any ideas anyone?
It seems to see ADB, but no Fastboot? very strange, could I need a fastboot file or something?
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
could you send me more info, or links I am kind of new to this and would like to know what I did and how to avoid/fix it in the future Thanks.
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you around.
I cannot forget the tremendous help you and Frankdrey gave me to discover, learn, and use an Android system on my G1.
Without both guidance I would, maybe, use now a toolkit and learn nothing.
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
adb for dummies.. http://www.mediafire.com/?qrjo6bi8ayblj1r
this includes everything that is needed so you dont need to grab the whole sdk. easy access to adb and to fastboot.
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
First of all thank you for the help, I'm currently running win7 64 bit. Ill check this post tomorrow and give it a try.
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Thank you guys for you efforts, Ill try it today.
You can just copy and paste the fastboot and adb .exe and .dll into c:\Windows instead of adding a variable.
Fast and easy lol just like I like 'em
Success! Thanks guys. I think Ill stay rooted and skip unroot rerooting.
Hi guys!
I have noticed that developers continue to develop new Android versions for the HD2, there is always something of new (KitKat it's already avaible).
Developers make Android Roms bootable from MicroSD through a partition without delete W.M.
They can edit the Linux Kernel in any way.
Surely you know projects like XDAndroid that use the "haret.exe" file.
But which sofwares and which coding languages do they use to "build" these Roms?
I read about
-Eclipse and Android Studio
-Gedit and Nano
-Kate and Vim
...
What do you know? Help me
Mich-C said:
What do you know? Help me
Click to expand...
Click to collapse
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
HypoTurtle said:
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
Click to expand...
Click to collapse
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
Well, yeah...
When you compile you rom you need to imstall ot this way:
You need 3 things:
1. Ext4 partition on your sdcard
2. Some recovery build for booting over haret ( you can take sd twrp's)
3. Your rom in flashable zip.
When you have all that, make a folder in your sd card, put your android flashable zip and extract your sd recovery there. Then run haret from that folder, and flash your android trough recovery. Then reboot, and go to the folder you have made for your android build, there should be a folder called NativeSD. Go in it an run haret an you will be booting in your android
ADD: You need to install w/ NaticeSD method only
Sent from my leo using XDA Premium 4 mobile app
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
In a way yes. A Rom is made up of a kernel which is bundled with a ramdisk (essentially boot instructions). to make a boot image.
On top of which is the system files which make up the OS itself. During compilation device specific details are taken from the files and baked in to the files that'll be running on the device itself.
The problem with making ROMs for non-Android devices is getting the device specific stuff - the HD2 is close enough / the same as a couple android phones (Nexus One / Desire S (??)) so getting these files was relatively easy.
You've mentioned haret.exe, which i believe just needs a rearranged ramdisk, other than being able to flash an open bootlader (magldr / lk in the HD2's case) that would be the only way to run android on a WM device.
The real question is, do you have working android kernel for your device..
Sent from my leo using XDA Premium 4 mobile app
I have compiled a new build for galaxy nexus. but after booting UI is not starting
just a blackscreen.
any solutions??
feherneoh said:
Check the filemodes in /system/b2g
/system/b2g/b2g is most probably 644, that is, not executable.
Click to expand...
Click to collapse
so you mean it should be 644 or not?? and what about other files there are some files too which don't have 644..
it is not working..tried all way..:/
feherneoh said:
Do you use the zip created while building, or create a package manually? Maybe zip does not install /data
Sent from my MyAudio using xda app-developers app
Click to expand...
Click to collapse
actually i have used all the images created system.img userdata.img and boot.img.. but no luck
http://forum.xda-developers.com/showpost.php?p=46830463&postcount=399
here are my builds
I'm currently trying to make a new build to see if things have changed.
Could anybody please tell me how I can open/edit the *.img files? I have to do this on Fedora Linux because I have no other operating system.
feherneoh said:
Why do you need that? Files should be next to the .imgs when build finishes
Click to expand...
Click to collapse
I thought it was useful if I have just image files. But that's not so important because after 4 hours syncing sources my internet disconnected so I'm a bit angry now. So all over again...
jeetBLswami said:
I have compiled a new build for galaxy nexus. but after booting UI is not starting
just a blackscreen.
any solutions??
Click to expand...
Click to collapse
i suspect the proprietary binaries are culprit here.try comparing the kernel size of android and B2G. this may give idea.
or else try what all binaries are pulled in B2G and are they same as Android ?
i didn't faced any issues in Nexus 4. code sync + build + flash in single attempt.
~Amit
This is beginner talking. I was looking for a Factory images for my Nexus 4 and I saw on Google Developers's website that there are some Binaries for Nexus Devices (NFC,Graphics, GSM, WIFI....) and now I'm curious about what can I do with them ( *.sh file)?
Can I flash them separately module by module in case that I need one, or it is just enough to flash a Factory image. Are they correlated? Thanks!
A factory image contains everything you need. The OS, kernel, drivers etc. It's basically a complete image of how the phone would look if you buy it.
Sent from my Nexus 4 using xda app-developers app
volvoxxda said:
This is beginner talking. I was looking for a Factory images for my Nexus 4 and I saw on Google Developers's website that there are some Binaries for Nexus Devices (NFC,Graphics, GSM, WIFI....) and now I'm curious about what can I do with them ( *.sh file)?
Can I flash them separately module by module in case that I need one, or it is just enough to flash a Factory image. Are they correlated? Thanks!
Click to expand...
Click to collapse
Binaries are nothing but the specific hardware drivers. Its of no use to you unless you plan on compiling a ROM.
*.sh files are linux files, they are used to extract the drivers/binaries to a folder in you source code folder.
sandy-achar said:
Binaries are nothing but the specific hardware drivers. Its of no use to you unless you plan on compiling a ROM.
*.sh files are linux files, they are used to extract the drivers/binaries to a folder in you source code folder.
Click to expand...
Click to collapse
Thanks guys, that was helpful! :good: Maybe this is beginning of something revolutionary (regarding me -> compiling ROM) :laugh:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
Click to expand...
Click to collapse
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Yes, you can try
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
Well I use in my apk AIK.mobile tools proposed by osm0sis.
atoxyd said:
Well I use in my apk AIK.mobile tools proposed by osm0sis.
Click to expand...
Click to collapse
https://github.com/osm0sis/AnyKernel2/ ?
from http://forum.xda-developers.com/showthread.php?t=2670512
bigsupersquid said:
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
Click to expand...
Click to collapse
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
atoxyd said:
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
Click to expand...
Click to collapse
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
nero curin said:
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Click to expand...
Click to collapse
Hi, did my apk work for you?
atoxyd said:
Hi, did my apk work for you?
Click to expand...
Click to collapse
only unpacking and repacking,didnt help on my device but yet again nothing else helps me compile kernel for this idol 3 so i guess this app works just not for me, bad luck :/
Sent from my 6045X using Tapatalk
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay
atoxyd said:
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay
Click to expand...
Click to collapse
The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.
Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts.
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well
atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
Click to expand...
Click to collapse
Thank you for adding the appropriate credit back to your post. Patching, cross-compiling and scripting has taken significant work. :good:
The only other thing that I'd ask is that you do not use the name of Android Image Kitchen or AIK in the title of your app. I'd like to suggest maybe "Image Editor and Flasher" as a snappy alternative?
bigsupersquid said:
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well
Click to expand...
Click to collapse
Thank you my friend , you are the only one who supported me , and from the beginning.
atoxyd said:
Thank you my friend , you are the only one who supported me , and from the beginning.
Click to expand...
Click to collapse
it's a useful project, definitely worth a little testing and feedback.
besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."
bigsupersquid said:
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
Click to expand...
Click to collapse
Did you have an unlocked bootloader ?
nothing changed on the device, unlocked and still s-on, I'm not sure what went wrong the first try.
PEBKAC error probably
(problem exists between keyboard and chair)
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
atoxyd said:
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
Click to expand...
Click to collapse
Please use a different name for your app as I have requested.