Related
Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks
kenyi25 said:
Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks
Click to expand...
Click to collapse
I have been pulling my hair out trying to figure out why I can no longer connect to my Desire HD via eclipse since I rooted my phone two days ago and installed the virtuous unity rom. It connects temporarily then gives the following errors:
Code:
[2011-06-29 23:23:44 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-06-29 23:23:44 - adb]Please contact the application's support team for more information.
[2011-06-29 23:23:44 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
I can open up a shell and type commands on the device, but the debugging doesn't work. When you google these errors it is usually people not having enabled usb debugging on their phone. I have of course done this.
I spent a large amount of time uninstalling droid explorer and moving adb.exe and adbwinapi.dll's around today trying to fix this issue before realising it's the phone not the PC.
I took my wifes HTC ChaCha with stock ROM, connected it and it works fine in eclipse, same cable, just different phone.
I can't believe as this poster suggests that this is standard with custom ROMs.
I tried the leedroid sense 3 ROM but this too had the same issue. Each time I did a full wipe before installing the ROM, and I installed nothing on the phone before testing.
Whats going on?
Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk
jkoljo said:
Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Hi jkoljo,
Thanks for the suggestion. I tried Raidroid 1.32.405.6, but unfortunately I had exactly the same issue.
I also tried the suggestions in the following thread which suggested setting persist.service.adb.enable=0 in default.prop, but this didn't work either.
http://forum.xda-developers.com/showthread.php?t=1051798&highlight=adb
Any other ideas? I'm willing to try anything you can suggest. It's really weird that even with an almost stock ROM the issue is still there...
CheesyPeteza said:
It's really weird that even with an almost stock ROM the issue is still there...
Click to expand...
Click to collapse
Exactly. There is basically no additional mods in raidroid, only root. Does it have unsecured boot.img? So if you go to terminal emulator (get it from market), does it open up with $ or #?
It starts with $, but if I sudo to root I get the superuser app requesting permission then I get root with the # prompt.
I thougt that was the way it was supposed to work, should I be going straight in as root? Should I uninstall the superuser app?
OK. With everything else ruled out clutching at straws I tried taking the sdcard out and it started working!
I put the sdcard back in and immediately it stopped working.
So it's something to do with the sdcard...
This should be solvable through a process of elimination.
I need to go to bed now, but tomorrow I'll try a spare completely blank sdcard and start the elimination process from that. Hopefully it is just a file on the sdcard causing the problem, not the presence of an sdcard itself.
I spoke to soon, looks like I just got lucky and it happened to work when I took the sdcard out. Occasionally it will work for a minute then it will stop working again. I'm no closer to solving this.
Same issue
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.
ajparag said:
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.
Click to expand...
Click to collapse
Unfortunately, you're in the Desire HD forums, so it's hard to help you when you're using different hardware. For all I know, the Spice MI could have known ADB connection problems. I would recommend finding forums specific to your hardware.
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
hey everyone,
I normally don't post on here because I find the info without needing to, but I can't find this even with google fu, any help appreciated
Problem: Wifi won't turn on
ROMs tried: Orignal Kindle ROM, CM 9 (hashcode make), CM 9 (Energy mod ICS)
Other notes: My methods worked on my other KFs, but not this one.... however its an older version. I was sure to make everything factory default, wipes the two caches, and out of frustration from TeamWin deleted everything on the flash and system (except TeamWin Obviously). I have the Android SDK setup to interface with the device, so if you need me to hit it from there let me know. Everything else works, but a wifi only tablet without wifi is useless in my book.
Thanks once again for any help I will go back to google fu'n and head to wall bashing
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
hmm
Thepooch said:
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
update
initialhit said:
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
Click to expand...
Click to collapse
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
final update
initialhit said:
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
Click to expand...
Click to collapse
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
initialhit said:
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
Click to expand...
Click to collapse
Did the factory ROM flash correct the issue or still a no-go for WiFi?
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
kibusaki said:
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
Click to expand...
Click to collapse
Wrong device. Wrong forum.
my nexus 7 2013 wifi edition is stuck in opening wifi set up because my wifi cant connect to any router. Is there any way to bypass this one like for example using ethernet cable instead of using the wifi, is that possible? or any other way to disable or skip the wifi set up and how can i flash custom rom for this one without using twrp ? My device is not rooted. fresh flashed from stock.
or please anyone who own the same with my device can i have your nandroid back up file please, ill give you load for the reward please please help me. :crying:
I'd recommend using Nexus Root Toolkit - it has full ilustrated instructions for tunning your device. You can flash a custom rom using it. cheers.
Aoi v1 said:
I'd recommend using Nexus Root Toolkit - it has full ilustrated instructions for tunning your device. You can flash a custom rom using it. cheers.
Click to expand...
Click to collapse
but how can i flash a custom rom since my usb debugging is not enable, do you know how to push file on my device without enabling the usb debugging, it really wont detect my device?
chaosme143 said:
but how can i flash a custom rom since my usb debugging is not enable, do you know how to push file on my device without enabling the usb debugging, it really wont detect my device?
Click to expand...
Click to collapse
Nexus Root Toolkit is a dead simple app that lets you flash content through fastboot mode. If your device is softbricked, it can also fix it. http://www.wugfresh.com/nrt/
Aoi v1 said:
Nexus Root Toolkit is a dead simple app that lets you flash content through fastboot mode. If your device is softbricked, it can also fix it. http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
ive done reverting to stock rom using nexus toolkit but my wifi still not working. i also use adb to push a file but it doesnt recognize my device though fastboot mode is working it does detect my device.
chaosme143 said:
ive done reverting to stock rom using nexus toolkit but my wifi still not working. i also use adb to push a file but it doesnt recognize my device though fastboot mode is working it does detect my device.
Click to expand...
Click to collapse
I don't know how to help you with your wifi problem, I just helped you with flashing through fastboot & NRT. Hope someone else knows something about it. Cheers.
Do you mean that it has no internet connection when connected to WiFi? I also experience it. You just have to reset the router or google how to fix it.
wellwisher said:
Do you mean that it has no internet connection when connected to WiFi? I also experience it. You just have to reset the router or google how to fix it.
Click to expand...
Click to collapse
its a wifi failure cant connect to any wifi devices due to i changed its mac address but its okay now.. already fixed it. anyway, do you know how to free my system memory in my nexus 7 flo fresh flash from stock rom marshmallow 6.0.1 MMB29O, i noticed after i flashed it, a little small memory left in my system memory, how do i delete those google apps like hangouts etc maps i dont need them except playstore.
chaosme143 said:
its a wifi failure cant connect to any wifi devices due to i changed its mac address but its okay now.. already fixed it. anyway, do you know how to free my system memory in my nexus 7 flo fresh flash from stock rom marshmallow 6.0.1 MMB29O, i noticed after i flashed it, a little small memory left in my system memory, how do i delete those google apps like hangouts etc maps i dont need them except playstore.
Click to expand...
Click to collapse
You have to root your device for that. In order to root your device, you will be needing a custom kernel then flash the superSU 2.60+
From there, you could easily delete the system apps.
chaosme143 said:
ive done reverting to stock rom using nexus toolkit but my wifi still not working. i also use adb to push a file but it doesnt recognize my device though fastboot mode is working it does detect my device.
Click to expand...
Click to collapse
Doesn't look like the NRT has been updated yet to this version, likely just have to give it a few more days.
SwimWithFire said:
Doesn't look like the NRT has been updated yet to this version, likely just have to give it a few more days.
Click to expand...
Click to collapse
anyways, as long as im already settled, i can breath freely now.
My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.
I having this problem too, cant set custom launcher.. anyone help us??
The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!
I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.
Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.
With 5.2.7.4 , you need root for this commands!!!
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot
Ahh where were you a couple days ago!
noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk
Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!
The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.