Develop Bugs

[Q] Upgraded to Leedroid v4 and cannot connect to pc

Hi,
I've searched all over and cannot finf an answer to my problem??? I have just upgraded to Leedroid v4 and everything works beautifully except I can no longer connect to my pc. It is recognized in device manager but the phone doesn't come up with splash asking how I want to connect it, and so I can't use it as a disk drive. The phone still charges though? I have tried ticking and unticking the ask and usb debugging options.
I don't really want to flash back to an older rom but if that the only way ill have to, can anybody help please????????/

I'm sorry, there is no way in hell you have searched all over. It's one of the most known bugs in the version 4 beta from Lee. It's on pretty much every page in the dedicated thread.
This is what you do. Either download Auto mount from Market OR change kernel to Unity's or Lord's. Both those kernels have fixed the USB connection problem.

Thanks for that. I searched the term not connecting to pc on this forum and google and didn't realise it was a mounting thing!

Np mate. You are most welcome.

i Too was looking for the same thing. Thanks a lot mate

The kernel was updated by Lee, you can try the new one from his thread (see my sig). New rom version should come this week.
Sent from Desire HD using XDA app.

[Q] Can't get phone to re-root, please help

Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.

And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?

Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium

AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium

Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )

AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium

IT'S DONE!!! Again thank you both so much1

[Q] Old school [Newbie] - needs some advice

I am old school rooter custom ROM user on many devices. ( Nook Color / Transformer / LG-G2x ) So I understand the process of rooting and bootloader's and adb ect..... BUT ..... I am brand new to Kindle Fire. Just bought one today. I have looked over these forums for hours. I have learned a bit ... but still not 100% sure of the best route to take. I found a great option with BuritoRoot3, but seems im screwed because I have 3.6.x stock. I want FULL root. I don't care about Kindle desktop or stock crap. I have a ROM I want to run (HellFire) but I dont fully understand now without BuritoRoot3 how to go about
1) Rooting
2) Making a backup / recovery
3) FIREFIREFIRE
4) TWRP or CWM ?
or some easier why to go about this. Like a drop back to 6.2 stock some how ?? is that possible ....
Any guidance would be greatly appreciated.
Thanks again

Thibor69 said:
I am old school rooter custom ROM user on many devices. ( Nook Color / Transformer / LG-G2x ) So I understand the process of rooting and bootloader's and adb ect..... BUT ..... I am brand new to Kindle Fire. Just bought one today. I have looked over these forums for hours. I have learned a bit ... but still not 100% sure of the best route to take. I found a great option with BuritoRoot3, but seems im screwed because I have 3.6.x stock. I want FULL root. I don't care about Kindle desktop or stock crap. I have a ROM I want to run (HellFire) but I dont fully understand now without BuritoRoot3 how to go about
1) Rooting
2) Making a backup / recovery
3) FIREFIREFIRE
4) TWRP or CWM ?
or some easier why to go about this. Like a drop back to 6.2 stock some how ?? is that possible ....
Any guidance would be greatly appreciated.
Thanks again
Click to expand...
Click to collapse
Skim this...
http://forum.xda-developers.com/showthread.php?t=1552547
It will get you caught up on basic terminology, installing drivers, relevant fastboot/adb commands. Focus on post #3... near the end, it has a step-by-step on how you should go about flashing a custom ROM on a stock device. You do not need to root the stock software if you are going straight to a custom ROM. The document is slightly dated as it refers to an older version of FFF, but it will get you started nonetheless. You can update to the newest version of FFF when you are all done without much trouble.
Right now, the preferred recovery is TWRP because CWMR has problems flashing ICS based ROMs, so you should probably go with that one. Backups/restores should be pretty self-explanatory once you get TWRP installed.

The most recent Fire I bought, I didn't waste any time going through the rooting crap. I just put it into fastboot, installed FFF and TWRP, and used adb to push ICS to sdcard for flashing in recovery.
I never even let the stock OS boot
Use TWRP for now, CWM has issues with the latest kernel.
And definitely read the guide kinfauns gave you a link to. As long as you have a couple of brain cells to play with, it'll give you a good foundation to work from.

soupmagnet said:
The most recent Fire I bought, I didn't waste any time going through the rooting crap. I just put it into fastboot, installed FFF and TWRP, and used adb to push ICS to sdcard for flashing in recovery.
I never even let the stock OS boot
Use TWRP for now, CWM has issues with the latest kernel.
And definitely read the guide kinfauns gave you a link to. As long as you have a couple of brain cells to play with, it'll give you a good foundation to work from.
Click to expand...
Click to collapse
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers

Thibor69 said:
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers
Click to expand...
Click to collapse
On a stock device, you have 2 choices...
1) Use a factory cable to get directly into fastboot mode
2) Use pokey9000's fbmode exploit to set the bootmode to fastboot (4002) and reboot
In the URL I gave you, there are links and directions on how to use fbmode near the end of post #3.

Fastboot....
Thibor69 said:
Thanks to both you guys for the info. I will figure it out. Guess I need to just read more.... I dont see how to get into fastboot mode yet ....
Cheers
Click to expand...
Click to collapse
I had the same question when I first started with the KF. Basically you need to change the "Bootmode" of the KF to boot into Fastboot mode. This is most easily done using the Kindle Fire Utility then restart your KF.
It is really not necessary to do this to root/install a custom ROM and it has lead a lot of inexperienced users to get "stuck at the yellow triangle," but if you want to play around with it, it is easy to do.
Hope this helps. Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.

pokey's fbmode is the way to go for 6.3
Sent from my Amazon Kindle Fire using Tapatalk 2

Entropy512 said:
pokey's fbmode is the way to go for 6.3
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Were is pokey's fbmode link ? I can't find it.

Thibor69 said:
Were is pokey's fbmode link ? I can't find it.
Click to expand...
Click to collapse
It's this one: http://forum.xda-developers.com/showthread.php?t=1414832
They didn't fix it in 6.3
Alternatively, it's "easier" to hop into fastboot mode with FFF, so that shouldn't worry you much once it's installed.

Dasanko said:
It's this one: http://forum.xda-developers.com/showthread.php?t=1414832
They didn't fix it in 6.3
Click to expand...
Click to collapse
I think It'd be pretty tough to "fix" fbmode without locking the bootloader. It's only a matter of time though.

INTF0 when USB connecting to my computer

Phone Info:
Android version: 4.0.4
Baseband version: I515.10 V.FC04 / 1515.FC05 (From this thread)
Kernel version: 3.0.8-franco.Kernel-nightly-384GPU (from Franco Kernel Updater)
Mod version: liquid.toro.062412.025446
Build number: Liquid ICS v1.5 (From here)
Computer running Win XP Pro SP3.
This issue has been happening for awhile -- it first happened running BAMF Paradigm 1.2, after I flashed from Team BAMF's Kernel to Franco Kernel Milestone 3 (from the Updater, I believe), and using the above-listed radios. I have not updated the radios since I was running BAMF Paradigm, but I've updated everything else. Also, I have always tried to verify my checksums, but I'm sure I missed that step a few times along the way.
Issue:
When I plug my phone into my computer, if I've freshly flashed a new ROM, it will pop up as an Android Device (as expected). However, if I wait a few hours -- during which time I install APKs from the Play Store and the App store, not from a backup, and then I restore only app data from my backup -- when I plug my phone into my computer, it comes up as an unrecognized device and asks for drivers for devices INTF0, INTF1, and INTF2.
I have read that it could be related to my kernel, and I haven't tried flashing a stock kernel. I have also tried uninstalling all my Android device drivers from my computer, and while that fixed a problem I was having with a pesky G2, it didn't help anything with my GNex.
Otherwise, my phone is completely useable.
Any suggestions? Would a factory reset fix this?
Update: Solution found... Fast Charge was enabled, and now that I've disabled it, it works just fine.

Do you have fast charge enable?
Sent from my Galaxy Nexus using Tapatalk 2

Pskillz87 said:
Do you have fast charge enable?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did, and now that I've disabled it, it works just fine. Thank you.

No problem, I went through the same thing a couple of months ago lol.
Sent from my Galaxy Nexus using Tapatalk 2

Thank you thank you thank you. I was losing my mind trying to figure this out!

Not to dig up a way dead thread, but my stock GNex is showing this also, I don't believe it's been rooted, I did buy it off craigslist though.

Comet1966 said:
Not to dig up a way dead thread, but my stock GNex is showing this also, I don't believe it's been rooted, I did buy it off craigslist though.
Click to expand...
Click to collapse
Just root and flash a rom :fingers-crossed:

ADB Trouble with Infamous Resurrection

This would probably be better placed in the Development forum but since I haven't posted here before I am not allowed. Anyhow...
I truly love the Infamous Resurrection and used the Infamous ROMs prior to this one. I have been having problems recently debugging my applications via Eclipse/ADB with this phone. I knew I had everything set up right and put it down to some incompatibility with something I had installed. So today I ran a test and flashed back to a rooted 2.3.6 ROM. I skipped adding any accounts or programs, set up for USB Debugging and Unknown Sources and, yes, it all worked great. I then did a factory reset and re-flashed Infamous Resurrection. Again I skipped adding any accounts, setup debugging and unknown sources. And it did NOT work.
I am getting two errors over and over again in the LogCat until it gives up:
cannot open CUSTOMER_XML
cannot open FEATURES_XML
Looking for a little help or at least to have someone pass this on to the developer.

adb T989 > 2.3.6 doesn't work
FWIW, I just tried the Jedi ROM and it through hundreds of more errors than IR. I guess I will need to be content with re-flashing down to 2.3.6 whenever I need to debug... unles someone has an answer.
bitlizard said:
This would probably be better placed in the Development forum but since I haven't posted here before I am not allowed. Anyhow...
I truly love the Infamous Resurrection and used the Infamous ROMs prior to this one. I have been having problems recently debugging my applications via Eclipse/ADB with this phone. I knew I had everything set up right and put it down to some incompatibility with something I had installed. So today I ran a test and flashed back to a rooted 2.3.6 ROM. I skipped adding any accounts or programs, set up for USB Debugging and Unknown Sources and, yes, it all worked great. I then did a factory reset and re-flashed Infamous Resurrection. Again I skipped adding any accounts, setup debugging and unknown sources. And it did NOT work.
I am getting two errors over and over again in the LogCat until it gives up:
cannot open CUSTOMER_XML
cannot open FEATURES_XML
Looking for a little help or at least to have someone pass this on to the developer.
Click to expand...
Click to collapse

First off putting this in development would of been a no-no. You are asking a question and this is Q&A so its in the right spot, now whenever I have had issues with adb its usually a kernel issue. Have you tried flashing a compatible kernel and then checking adb again. Also, this may or may not help your issue but try adbd Insecure by chainfire

Thanks for the response. I flashed the stock 4.0.3 kernel and still receive the CUSTOMER_XML and FEATURE_XML errors. And ADB does not work. There are a few additional mesages out of dalvikvm that may just be a fallout from the missing files.
class lookup Ljava/lang/Daemons; attempted with exception pending
VM Aborting
I have looked at the other kernels but nobody seems to be calling out ADB compatibility as a feature. Given that the stock kernel did not fix the problem, do you have any other advice? I am off to look for adbd Insecure.
playya said:
First off putting this in development would of been a no-no. You are asking a question and this is Q&A so its in the right spot, now whenever I have had issues with adb its usually a kernel issue. Have you tried flashing a compatible kernel and then checking adb again. Also, this may or may not help your issue but try adbd Insecure by chainfire
Click to expand...
Click to collapse

Actually, installing adbd Insecure did the trick. The errors I mentioned still happen but somehow it keeps on going. Thanks again!
bitlizard said:
Thanks for the response. I flashed the stock 4.0.3 kernel and still receive the CUSTOMER_XML and FEATURE_XML errors. And ADB does not work. There are a few additional mesages out of dalvikvm that may just be a fallout from the missing files.
class lookup Ljava/lang/Daemons; attempted with exception pending
VM Aborting
I have looked at the other kernels but nobody seems to be calling out ADB compatibility as a feature. Given that the stock kernel did not fix the problem, do you have any other advice? I am off to look for adbd Insecure.
Click to expand...
Click to collapse

bitlizard said:
Actually, installing adbd Insecure did the trick. The errors I mentioned still happen but somehow it keeps on going. Thanks again!
Click to expand...
Click to collapse
I have a new release out.

shnn2011 said:
I have a new release out.
Click to expand...
Click to collapse
Great, I'll check it out!