Related
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...
Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.
Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.
I've recently learned that it's possible to mount a network share to your android file system using CIFS.
I still don't quite understand how this works, as I've been unable to accomplish this over the last week.
I've flashed 10 different roms and several kernel combinations trying to figure this out, still - to no avail.
I've also spent countless hours researching and haven't found a clear answer.
I was hoping someone could explain the requirements to make this functional.
I found a tutorial which explains how to use Mount Manager and load in the cifs.ko module, but nothing happens; it won't load the module.
At first, I thought it was finding a kernel with cifs support but there is obviously more to it.
Could someone provide some insight as to what makes this possible?
Could you suggest a rom/kernel combination that is known to work?
I'm currently running XenonHD 12-08-12 and would love to keep running Android 4.2. However, i'd switch to a different version if it would provide this functionality.
I'd be most appreciative of you assistance.
Hi all I'm needing some help, I've been reading through both original and android development sections and looking for the best rom for the Samsung T705. Currently I have rooted my device from Stock using CF-Auto-Root-klimtlte-klimtltexx-smt705.
Although this allows my device to have full root access, it keeps the device as stock as possible. However I have noticed that the battery usage is terrible on this device and that's even with power saving mode enabled. Also switching between apps sometimes lags and is full of Samsung bloatware.
I'm looking for a reliable custom rom that is designed to improve battery consumption and remove all the Samsung bloatware. Their are many roms to choose on this site but don't know which is the overall most favourite or most reliable.
Finally, if I go ahead with a chosen rom when it comes to installing, it is recommended to backup the current rom and install using a recovery tool installed to the tablet. With me using CF-Auto-Root-klimtlte-klimtltexx-smt705 rom no recovery rom has been installed to my tablet as I installed this rom using origin via PC. How can I install a recovery rom on my tablet before installing a custom rom/kernel?
Manny Thanks
No one is gonna give you the answer you want. It boils down to trying all and stick to what favours you most
And as for How to install custom recovery and custom ROM,i think you should befriend Google and YouTube,coz you apparently need to learn alot of basics.
Thanks for your response and I don't rely on YouTube for this type of support as a lot of it is false. I use this website as its more accurate and no bull****. But would be nice to get some help for a novice instead of shooting him down. After all it is a help and troubleshoot section of this forum, we all have to start somewhere.
morgiee said:
Thanks for your response and I don't rely on YouTube for this type of support as a lot of it is false. I use this website as its more accurate and no bull****. But would be nice to get some help for a novice instead of shooting him down. After all it is a help and troubleshoot section of this forum, we all have to start somewhere.
Click to expand...
Click to collapse
I as well am looking for a custom or even a stock rom for my SM-T705W. I have not been able to update bootloader or modem to MM. At present it is running Lollipop and I would so much like to run MM or Nougat rom.
I have literally tried to flash almost everything in the Tab S areas that are made for the T705. I wish I could assist you. Someone will help you out with some guidance I am sure, this is a great place.
One thing I have noticed on my device, when I try and wipe or backup using TWRP, I always get a 'Failed to mount /hidden ' error and I am not sure what that partition is or if all the Tabs have one. Perhaps that is why I can not flash a newer bootloader and modem and also a MM or custom rom. Anyways, sorry to hijack thread...good luck.
What is the most recent and stable ROM for the Gio GT-S5660M ?
Importantly it would be to have a ROM that is new enough to work with modern apps, which often require at least android 4 or 5. Also, I would prefer to avoid GApps and go with F-Droid and Aurora Store, and the latter seems to require android 5+.
I have a couple of these lying around and thought they might make good WiFi IP phones with a SIP client. With a modern ROM and a new replacement battery (remember those?!) they could have new life.
Is this workable? This phone is so cute and compact that I really don't want to get rid of it if it can be used for something.
It has an armv6 cpu wich is no longer supported on android the last supported version was kitkat 4.4.4, this is the latest rom available for the device: https://forum.xda-developers.com/t/rom-cyanogenmod-11-final-05-08-2015.3066771/
It can still be used to listen to fm radio etc, although it no longer has browser support, so it won't work on all sites. I have one too and think it is a very nice tiny phone but I am affraid you are going to have to buy a newer phone for daily usage.
@J.V.B. Thank you for your reply!
Does that rom work well? There is some conflicting feedback in the thread. Which is the correct rom (msm vs msm7x27)?
How can the rom be flashed from the stock non-rooted state? There aren't instructions in that thread, though there is a post saying to use this CWM recovery (requires root?): https://forum.xda-developers.com/t/...-11-wip-alpha-1.2582642/page-27#post-54754255
Good point, the browsers all seem to require android 5+.
Currently on stock (android 2.3.4) I am using CSipSimple and that's working reasonably well. A newer rom might give a bit more flexibility in settings (eg. I can't figure out how to enable wifi on boot and autostart CSipSimple on 2.3.4), and maybe just maybe a few apps through F-Droid.
Both versions work they are just different kernels, I forgot what the advantages over each other were, I think the 7x27 version was more buggy but I am not sure, I recommend checking out both.
That cwm is indeed the only correct version, newer or older ones can't install this rom. I think to install the cwm you just have to boot to recovery (home button + power button and keep the home button pressed in.) and apply update from sd card and select that cwm(wrong: see edit). After this you boot to recovery again and now you factory reset and flash the rom. You also need to flash the camera patch after you flash the rom, otherwise you won't be able to record using the camera. I am not responsible for anything that happens, custom roms are always a risk. Hope it works for you
edit: You need to be rooted and on android version 2.3.3 or higher to install cwm: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988
I also recommend using link2sd:
https://www.apkmirror.com/apk/bulent-akpinar/link2sd/ .
For instructions, follow this guide but scroll all the way down to the for cwm only users method: https://awanstuff.wordpress.com/201...ink2sd-in-any-android-phone-with-screenshots/
Link2sd will fully transfer apps to sd card instead of only the package. I changed the settings to make sure auto link is on and install location is set to sd. You can also transfer already installed apps to the sd and a lot more.
After this maybe post about how well the gio is running for documentation.
Some extra tips: the built in root is handy and if you enable developer options in the rom you will also get a performance menu in settings where you can make it run faster.
Thanks, I plan to try installing CWM and the CM11 rom soon. From searching it looks like "MSM7x27" refers to the Snapdragon S1 processor version:
List of Qualcomm Snapdragon systems on chips - Wikipedia
en.wikipedia.org
The Gio has a MSM7227 https://www.gsmarena.com/samsung_galaxy_gio_s5660-3741.php so maybe the MXM7x27 version is the correct one? I don't know if the plain "MSM" version rom is referring to a specific or generic designation.
Thanks for the tip about link2sd. It's nice to have that option since the very limited storage on this phone is maybe the biggest weakness. I'll see if I need it, since I don't plan to install many apps at all, rather I want to maximize battery life.
I got 1500 mAh batteries from Polarcell and in airplane mode with wifi and just CSipSimple running on the stock rom it lasts over 7 days in "standby". Let's see a modern phone do that!
I think this is the msm7x27: https://github.com/androidarmv6/android_kernel_samsung_msm
and this is the msm: https://github.com/HerroYou/android_kernel_samsung_msm/commits/cm-11.0
The msm just adds overclocking but might be more unstable and it also breaks the backlights. I don't know which is the best one. I recommend if the msm7x27 doesn't work well enough to try the msm and see if that gives you better results.
Also just so you know I have not found any gapps that work yet.
Also when you before you reset your device and flash the rom. Right after the cwm install I recommend fully backing up your device to an sd card so you can just go back any time you want.
I tested csipsimple and it works. If you want better battery life, the power menu that gets enabled after you unlock dev mode might allow you to downclock the cpu to get even more battery.
HerroYou has a mxm7x27 repo too: https://github.com/HerroYou/android_kernel_samsung_msm7x27
It would have been so helpful for them to leave a couple of notes about the difference. It seems like these terms might be common enough in the dev circles that they didn't think it needed explanation.
About gapps, I wasn't interested anyway, so I'll take its lack as a "feature". Not sure if microg is feasible. In any case, side-loading and F-Droid are ok for me on this device.
And yes, a backup after installing CWM but before the rom installation is essential. No intention to skip that.
oh I see the msm2x27 kernel is based on linux kernel 2.6.37 and the msm kernel is based on linux kernel 3.0
I have been reading up on things and see that most threads say you must be rooted and above version 2.3.3 to flash the cwm recovery: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988
I am sorry I forgot about it. It really has been a long time since I installed it
Nice catch. In that case it is tempting to try msm with the more recent kernel 3.0.
Is there no way to flash CWM without root?
If not, is this post on rooting still valid? https://forum.xda-developers.com/t/...wares-mods-tips-tricks.1397120/#post-20397899
It is to root the stock rom so it should still work since the stock rom hasn't been updated in forever. I would also recommend reading the rest of the beginning of that thread to make sure you didn't miss anything because while mostly outdated, the things like rooting the stock rom and installing cwm is still the same.
I would also just to be sure use the cwm version in the thread: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988 and then update it to the new version.
I started downloading the resources needed for this project, but the link (actually the whole hosting site) is dead for the root gb updated.zip hmm...
There are a few other files for rooting uploaded by random forum members:
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
A bit scary, but not sure there's another choice. It would be ideal if the recovery and rom could be flashed without root.
I found a rooting tutorial with a download on this post: https://forum.xda-developers.com/t/...kernels-recoveries-scripts-tutorials.1623393/
It is under the tutorials section.
Again I am not sure if you have to root to be able to install cwm but I wouldn't take any risks.
Also before you install anything is there anything you want me to confirm whether it's working or not on this rom?
I got youtube to work through newpipe and mx player although you have to download the videos because at low resolutions newpipe loses audio when sending to external video player.
Thanks, that's a nice resource thread. In the second page of the rooting thread someone has a modified version of the file for Bell S5660M variant, which is what I have, so I suppose I'll use that. I would prefer to go with CWM and CM11 without rooting, since I don't need or want root, but as you say it could be risky...
Oh, it would be great if you could verify on CM11 if 1) wifi can start automatically on (re)boot (eg. if it was on when powering off or rebooting, 2) if programs like CSipSimple can be autostarted on boot. That's all I really need right now to make it useful as an wifi IP phone.
I don't know how I would go about autostarting apps on boot. Is there a setting or a test for that? The wifi stays enabled after reboot.
I've had my pixel for some time and still don't fully understand how to test roms on the phone - more specifically how to backup/restore. (I have always used twrp in the past).
Currently I am on the stock rom - I would like to try ricedroid , lineage and possibly go back to stock . I have no issues installing roms, what is unclear is what/how has to be backed up ( i have neo installed) and how to go back to a previous rom ,retaining data. Is it even possible?
Any insight would be appreciated.
Thanks
Hmm - guess the lack of any response indicates that either my question is too stupid to bother replying to or that there is no simple way to test roms on this device.
I'm not sure of the question in general or how to answer it. I just normally just flash robs and then I will go back and reinstall all my apps again
I guess my question might be confusing.
I have always tested in a twrp environment. Things were simple - do a nandroid backup to an external device and test away. If I ever wanted to go back I would restore the backup in 3 simple steps.
In comparison testing on a pixel is a multistep process which leaves a lot of margin for error. All I was trying to determine is if there is a simpler way of going about it.
StanWiz said:
I guess my question might be confusing.
I have always tested in a twrp environment. Things were simple - do a nandroid backup to an external device and test away. If I ever wanted to go back I would restore the backup in 3 simple steps.
In comparison testing on a pixel is a multistep process which leaves a lot of margin for error. All I was trying to determine is if there is a simpler way of going about it.
Click to expand...
Click to collapse
Unfortunately, the old days of nandroid backups are gone. I use swift and google one to backup my data and apps. I clean flash every new rom and restore data. it definitely takes longer than restoring a nandroid backup.
I do know that someone was working on TWRP at some point no ETA with that coming out.
Did someone say TWRP? I'm hopeful that once Android 13 TWRP comes out someone will port it to 6 pro. As for your question, there's no easy way to restore a back up. You have to install everything from scratch most of the time unless you dirty flash a ROM.
ir0nb3rg said:
........ You have to install everything from scratch most of the time unless you dirty flash a ROM.
Click to expand...
Click to collapse
Sadly I've arrived at that same conclusion - hence this post (hoping). I don't think I'll be testing too many roms on the p6p. I would like to replace the stock rom - now it's a matter of deciding which rom suits my needs best and will be updated for the foreseeable future.
\Ricedroid and lineage are the 2 I've narrowed it down to.
Thanks
StanWiz said:
Sadly I've arrived at that same conclusion - hence this post (hoping). I don't think I'll be testing too many roms on the p6p. I would like to replace the stock rom - now it's a matter of deciding which rom suits my needs best and will be updated for the foreseeable future.
\Ricedroid and lineage are the 2 I've narrowed it down to.
Thanks
Click to expand...
Click to collapse
I'd suggest you check CrDroid if you haven't had a look at It yet. You can also load GSI if you don't want to flash everything all the time but support is limited and it may or may not work. Until TWRP is out, our options are limited