Hi there,
I've recently dove into ROM Development for my Evo due to a weird issue that I'm seeing on my device. This issue is also seen on many other devices from tablets to the nexus one. I seem to be one of the only few that's seeing it on the Evo, and the general community doesn't have enough knowledge to assist. I'm hoping someone will know some ideas to try from a cooking standpoint to see if I can fix this for my particular situation and maybe help out the others that are grasping for a fix from Google and aren't getting one.
In my situation, ADB ONLY works on the initial base release of FroYo from Sprint with regards to HTC Sense-based roms. When Sprint released their second updated base, 3.28.651.1, ADB was/is broken. I can get ADB to work in Recovery as well as ANY AOSP rom, so I'm thinking the culprit might be the Kernel (g3a8614e and onwards) and/or the base version.
USB Debugging does not work because the ADBD process is not running. See this Google bug for what the Nexus users are seeing:
http://code.google.com/p/android/issues/detail?id=9437
I'm very knowledgeable, and have tried so many rom and kernel combos it's disgusting YES, I've turned on USB Debugging. the ADBD process does not run, and throws a segmentation fault whenever you try to start it. I've checked my properties file to make sure the service.persist is enabled, yada yada.
I've torn apart the kernel from that initial release and paired it with a later base. The ADBD process then runs, but ADB still doesn't work. I've also, like other users in that link, have pulled out an ADBD process from the working one, and that also does not work, although it too makes the ADBD process function again inside the ROM.
So my questions are:
Can anyone explain what might be causing the ADBD process to be blocked? There's not much documentation out there on it. What part of the ROM build controls all of that? My initial thought was the boot.img, and I've messed around with that, diff'ing an older working ROM with a newer one to no avail.
Can anyone suggest something to try, or a technique to frankenstein something that might work? I'm an Android dev, and I can't put my in process app on my phone and test it because ADB simply doesn't work. My app uses the camera, so I need my phone instead of the emulator. I'd rather not flash an old rom or AOSP rom, because I'm really trying to figure out what's going on!!!
Thank you so much in advance for any assistance you can provide. If you can help me figure this out, I'll gladly send you a donation!
BTW, this subforum is amazing! I stumbled onto it looking for a better way to pack and unpack boot images.
Related
Hey All
I have a requirement for setting up a dual boot on the HTC Hero using the SD Card for the 2nd OS.
I've looked around and have come across the Dual Booting for the Windows Mobile and Android on the HTC HD2 and was hoping somebody might be able to point me in the right direction archiving this on an Hero.
I'm not looking to run both OS at the same time, ie not running Ubuntu/Debian via a loop device.
So if anyone knows of any good guides for editing the Boot.img, i thinking that where the magic gonna happen, i might be wrong, please i would very much like to hear from you.
Many Thanks
c0mput3
ubuntu in its present form simply will not run. cmd based linux is a possibility for many mobile devices, as has been prooved by cmd linux on iphone os.
I wouldnt know about how to go about this though.
Speak to kendon over on Villainrom forums.I think hes probably the one to talk to as im sure he said ubuntu is possible
Many thanks Bonesy, checking that now. =)
Status?
... and what was the end result?
There is a thread on the villianrom forum for running ubuntu/debian alongside android though I'm still waiting for a new SD card before I try it. I would link but its still down, any ETAs for it being back up yet, I understand it might take a while?
Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
According to a discussion on a different forum, a few people have tried this on the Eris but it fails to flash. So still waiting on our phone, sadly they don't list the Eris on their compatibility list. They do list the HTC Hero but I'm not sure if they use the same USB Controller or not. Someone far more educated in this field can help with that.
Googling around a little pulled up a few discussions that appeared to indicate that the eris is a compatible usb controller. But I tried flashing it (one KayosFroyo v32) and as mentioned I get a error during flash... Hopefully someone can get it working.
What exactly is this?
coffindancer said:
Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
Click to expand...
Click to collapse
According to the PSFreedom compatibility chart development for the Eris is "In Progress." It appears that a custom kernel will have to be built to support the exploit, presumably not too difficult.
coffindancer said:
Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
Click to expand...
Click to collapse
well from what i read from the github tracker @ http://github.com/kakaroto/PSFreedom
he says: This linux kernel module should work on the N900 (RX51 machine).
It uses the musb driver to access the address of the usb and modify it.
If you want to port this, have a look at psfreedom_machine.c and implement the
missing functions for your device. Make it compile-time #ifdef and modify
the Makefile.
To compile, type 'make' inside scratchbox.
dont know how to do this just hoping this will help someone with porting it
UPDATE: just found a small how-to on how to port it if anyone understands this and/or how to do it all ps3+eris owners will forever be in your debt
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
Edit: the controller the eris uses is MSM72K
any new developments on this? i see it's now listed on the PSfreedom compatibility list as in progress.
h t t p://psfreedom.com/wiki/index.php?title=Device_compatibility_list
As of this morning the website psfreedom.com is not available as well as the link for the chart is broken. I did many tests with my eris, using a CM6 Froyo rom to Other roms that were ported from other phones with different pse-enable zips. The best I was able to get to was the boot screen with the 3 skateboard androids. That setup was a CM6 2.2 rom with the zip files for the HTC Wildfire. Every other setup the zip failed to flash thru recovery. Thats the best I got so far.
EDIT
cant sleep so I tried to get onto psfreedom website and it is back up. It has been ported to the motorla droid. hopefully soon we will be so lucky
posted in another thread but here it is again.
I dont think we will be seeing this on the eris for sometime as the USB driver used is actually the msm_hsusb driver. This was verified last night when i was in #psfreedom where someone was trying to get psfreedom on an eris and kept running into a problem and it turned out to be because of the msm_husb driver was in use. so until that msm_husb driver is working with psfreedom we are probably SOL.
This is now working on the Eris i tested it for the dev waiting for him to officially release it should be this afternoon.
If what your saying is true I will name my children after you and the dev LOL
Sent from my Eris using XDA App
For the love of humanity don't.
Any way you can list what you did try and where I can get the files needed to try this myself... maybe with instructions on how? I very much want to try this and have been patiently waiting for days now.
http://psfreedom.com/wiki/Device_compatibility_list
have fun guys all credit goes to the Dev rgov and the other devs working on psfreedom
I've carefully read the directions on the PSFreedom Wiki site for Droid Eris. My first question is this:
How can I achieve S-off in the bootloader? My Eris is rooted and I am currently running KaosFroyo v34. When I reboot to bootloader, it shows S-on and I cannot fastboot.
yeah i had the same exact issue that's why i made the note in the wiki. i essentially had to go through and redo the root following jcases post here.
hope it's not against the rules to link this......
http://androidforums.com/eris-all-things-root/121597-how-install-engineering-bootloader.html
Trying now... will keep you updated. Thank you.
Question: Since my phone is already rooted, do I just start at step 6 and flash PB00IMG.zip? To be honest, these directions are kinda confusing to me. I tried this method months ago and was never able to fastboot... maybe I am doing something wrong. coffindancer, I appreciate any and all help you are providing and hopefully you can assist me in getting this PSFreedom up and running.
i think you can start with PB00IMG.ZIP and it will go ahead and reflash the boot loader so it's S-OFF im not positive though. Im a freak and just followed the steps pretty much step by step maybe someone with more experience can explain it better.
So even though you were already rooted, did you still flash the engtools.zip? Or did you skip step 2?
skipped step 2 i believe.
also the dev is redoing the wiki so if you don't see the link for the files just be patient.
So lately ive been useing the android emulator trying to become familiar with it how to set it up useing eclipse, adb, rooting, flashing roms, and what are good Roms. So currently ive been useing genymotion because it seems to run the fastest and has some really good features such as the ability to fake your GPS device into thinking your in any country and i found a genymotion that runs Gapps already rooted. Issues that im currently having atm is i want to try out flashing some roms but when i go through the process of trying to put it in download mode all genymotion ever does is just reboot itself. Ive started trying to use the android SDK now but its always so slow and i cant use intel haxm because im guessing my computer is amd so it wont allow me to install it. other than that i have a feeling its going to work just like genymotion because it is based on same type of system. does anyone have some tips or insight that could help me out? Id like to learn all about this stuff and i think im doing pretty well. I feel i have a much better understanding of processes behind phones now alot more also. i have no idea what i will do with the knowledge maybe ill try programming again like i did when i was younger or hacking or something. Thanks for reading i hope someone has insight or information that could help me out.
I've recently installed the latest version of Havoc OS on my A only Lenovo S5 Pro. Since the install, I haven't been able to connect to my PC via a USB cable, and the ADB interface does not seem to work too. The phone is stuck in charging mode only, and USB tethering will also work.
Seems like this is quite a common issue, with these GSI Roms, but I was not able to locate a valid workaround after a few days of checking on the web. I'm hoping someone could actually guide me what could be causing the issue, so I can try and fix it myself, though my knowledge does not go all that in-depth.
Tried to actually read a logcat, while connecting the USB cable, via an app on my phone, but most of the lines of text have no meaning to me.
I'd be very grateful if someone could share their knowledge and help me out with this issue. If anything else is needed on my side of course, I will be more than glad to provide it.
Hopefully this could help solve the issue not only for me, but for other people that have purchased the phone, and upgraded with a GSI Rom, due to the fact Lenove has not provided any updates outside of China.
reconecta said:
I've recently installed the latest version of Havoc OS on my A only Lenovo S5 Pro. Since the install, I haven't been able to connect to my PC via a USB cable, and the ADB interface does not seem to work too. The phone is stuck in charging mode only, and USB tethering will also work.
Seems like this is quite a common issue, with these GSI Roms, but I was not able to locate a valid workaround after a few days of checking on the web. I'm hoping someone could actually guide me what could be causing the issue, so I can try and fix it myself, though my knowledge does not go all that in-depth.
Tried to actually read a logcat, while connecting the USB cable, via an app on my phone, but most of the lines of text have no meaning to me.
I'd be very grateful if someone could share their knowledge and help me out with this issue. If anything else is needed on my side of course, I will be more than glad to provide it.
Hopefully this could help solve the issue not only for me, but for other people that have purchased the phone, and upgraded with a GSI Rom, due to the fact Lenove has not provided any updates outside of China.
Click to expand...
Click to collapse
Hi,
First of all, here's how to read a logcat : https://forum.xda-developers.com/showthread.php?t=2274119
And second of all, your problems needs to be addressed by the dev, if this GSI does it surely does it for other people. Take a logcat (remove potential sensitive infos) and post it in the thread you find your GSI.
Hope this helped
Decided to roll back to stock 8.1 :/
Raiz said:
Hi,
First of all, here's how to read a logcat : https://forum.xda-developers.com/showthread.php?t=2274119
And second of all, your problems needs to be addressed by the dev, if this GSI does it surely does it for other people. Take a logcat (remove potential sensitive infos) and post it in the thread you find your GSI.
Hope this helped
Click to expand...
Click to collapse
I was unable to get this fixed, nor got a definite answer from the Devs, and I had to roll back to stock...
In the process I flashed the wrong stock rom via QFIL, and bricked the device as it was no longer booting into OS, recovery, or EDL, nor was I able to choose an option from within fastoob mode.
This made me look around for a few hours, and after butchering my original USB cable to make an EDL flashing cable I managed to get it back up and running, so at least this was something new and positive that came out of the whole commotion...
???
Thanks nonetheless!!
Hey all. Just wondering if anyone can help shed some light on BuzzTV boxes for me? I have the newest model - XRS4900 (Specs/Info: XRS4900) and while it's a great device, the one thing I don't like about it is that it runs straight Android. I would prefer it to run AndroidTV if possible.
I know there are compatible ROM's out there that would work on it, but I cannot for the life of me figure out how to get the thing flashed!
I am able to see it in the Amlogic Burning Tool, but every ROM I try flashing gives me an error.
I can boot to recovery, but it can not see any img files when I browse to the USB or SD Card (tried both)
When I try booting to the bootloader, it just goes to the BuzzTV logo and sits there, almost as though there isn't a bootloader on the device. And fastboot does not return any devices (ADB works though but it's not rooted so there isn't much I can do there)...
And they do not provide their OTA updates for people to download. They will only push them to you based on your MAC address so I can't even look at them to see what's up.
My assumption is that the bootloader is either locked (which I didn't think Amlogic devices had the capability of locking them?), or the ROM is encrypted, or something else is implemented that is preventing me from modifying the device. So I just wanted to reach out and see if anyone out there happens to know what I am dealing with here and maybe has some advice on how to get around these protections so I can flash a different ROM? I would assume the same protections are implemented on all their devices, so I'm looking for anyone who has experience with any of them and has been down this road before? Any help would be greatly appreciated!!