Develop Bugs

[ROM] CM7 for the Kindle Fire

Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
12/4:
12/13
This ROM is obsolete; it was more of a proof of concept than an actual everyday ROM. It would suggest staying stock until ICS is ready and stable.
The ROM's update.zip
The KF's clockwork recovery to install files located under /sdcard/update.zip
The KF's stock recovery
md5sums
update.zip e0e8f8bb08318ef15c8afc042c2e9766 update.zip
updaterecovery.img 38eb5308439a6f1e256a4914ab06d508 updaterecovery.img
stockrecovery.img c4f028310bd112649c94be6a4171f652 stockrecovery.img
Make sure your battery is fully charged, rooted, you know your way around adb, and that your kindle fire actually connects to adb and works successfully before installing CM7. Installing CM7 will wipe your system, data, and cache, and I'm not responsible for any malfunctions :/ I've done this for versions 6.0 and 6.1, but I have not tested under 6.2
Copy the CM7 zip to the root of your sdcard, so it's /sdcard/update.zip, and copy the updaterecovery.img file to your sdcard so it's /sdcard/updaterecovery.img. For Clockwork, you will need two files to be present under /cache/recovery/ so copy these two files to your sdcard log last_log. You'll need to copy them to the root of the sdcard as well. Before proceeding, I highly recommend you go into adb and verify the md5sums of the two files you just put there. If you aren't familiar with this, you need to unmount your kindle from the PC, type:
adb shell
cd sdcard
md5sum update.zip and make sure the numbers generated after a few seconds match the numbers posted above
md5sum updaterecovery.img and again, make sure the numbers generated after a few seconds match the numbers posted above
If these numbers don't match, I wouldn't proceed as your file might be corrupt, and I would try again
Now we will need to copy these two log files to your cache partition under /cache/recovery so type
adb shell
cd cache
mkdir recovery
cd /
cp /sdcard/log /cache/recovery/
cp /sdcard/last_log /cache/recovery/
If your files are verified to be okay via the md5sums before, we can flash clockwork now, by typing
adb shell
dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Now, we can reboot recovery by typing "idme bootmode 0x5001"
If it says the bootmode has written, you can type reboot and it'll reboot
I install all of my zips without removing the usb plug from the computer or the kindle and I have never failed once, I don't think I've ever tried it without doing so, but if you don't wanna mess with success, don't remove the usb cord. I'm not saying anything bad will happen because I've never done it, but I'm just saying I'm batting 1.000 without removing the usb cord
Now that you're in clockwork, look below the menu to see if there are any error messages written in white. If you see one about something being read-only, that's fine. If it complains about log and last_log, you might've missed a step above. If you see an error that I haven't mentioned, and you would like to reflash the stock recovery and reboot like none of this ever happened, skip to the bottom.
About Clockwork: since we can't navigate to items in Clockwork, we have to bring the items to us. Basically what I did was I shifted the entries of Clockwork so the "Install update.zip from sdcard" was listed first, not the Reboot system now option. That way, we can just press OK (The power button) and it'll install the CM zip. I also changed it so you don't have to scroll all the way down to the "Yes" option to confirm install as I pushed that to the top also so we can just press OK. In the update.zip I included the wiping of system, data, and cache because we can't navigate to mounts and storage to wipe those things in Clockwork, so we have to do it automagically.
In the clockwork that I made for you, all you have to do is press the power button a bunch of times. There will be a point there you have to scroll down to "Yes", but you can't, that's fine, just press OK, even though it says "No" it will mimic you pressing Yes.
After you press the power button 3 or 4 times, it will being the installation. Give it a minute or so, it will install
After installation, we will need to reflash the stock recovery to your kindle. Type adb shell
mount sdcard
exit (this will bring you back to the non-shell command line)
then adb push /sbin/
So for me, (I use linux) I use adb push /home/jonathan/kf/stockrecovery.img /sbin/ **there's a space after .img and /sbin/**
Then type "dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery" it will say something about 16 megs written or something. Once that happens, type adb reboot or reboot and your kindle will reboot. Actually it will reboot twice. Give the initial boot a few minutes, and the CM7 boot logo will appear

Congrats Calvin!!! Awesome!

The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.

good job!
do the apps and wifi work?

tck9223 said:
good job!
do the apps and wifi work?
Click to expand...
Click to collapse
http://i.imgur.com/8ZRCW.jpg - it looks like

I wasn't able to test much out because the screen and the touch sensor aren't in sync. Basically the screen is facing one way and the sensors think the screen is oriented 90 degrees in another direction. There's a quick fix but I had to leave for work
I managed to open the wifi screen but couldn't click my ssid let alone type the password with the orientation/sensor hiccup
Sent from my DROID Pro using XDA App

rmagruder said:
The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.
Click to expand...
Click to collapse
I don't have all of the answers for sure but I think at this point no one really knows.
1. The device would no longer be registered as a Kindle if it is just stock CM. If you add the regular Kindle for Android app you wou still have access to kindle books but not other content.
2. The Amazon video app should work because it is reported as working on other unrooted devices. You should be able to unroot CM7(9) the same way that we currently unroot the KF. I suspect that it will not be long before we see a modified Kindle Video app that runs on rooted devices as I have noticed an increase in developer activity and interest in the device.
3. Yes
I too am concerned about these things as I have become very accustomed to instant video and all of the other features of the KF. I see many ways of having both. I suspect that once CM is fully operational we will have a zip that we can flash in recovery to add all of the Amazon apps the same way we do with gapps.

Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium

Lol we have recovery. It's just ineffective
Sent from my DROID Pro using XDA App

pyrostic said:
Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Very surprising but the recovery might be released before the ROM

The Fire is my first Android device and I have been following the XDA forums closely because this kind of hacking and tweaking is just WAY to cool.
Congrats on the CM7 boot. Can't wait to see more!

Got a donate button? I'll throw in for the hard work! Would love working CM7 or 9 on this guy.

SikYou said:
Very surprising but the recovery might be released before the ROM
Click to expand...
Click to collapse
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium

I know when its released loads of Rom development will follow.

pyrostic said:
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk

SikYou said:
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium

Well I flashed cm with clockwork. I'll post a zip and instructions later
Sent from my DROID Pro using XDA App

JackpotClavin said:
http://i.imgur.com/8ZRCW.jpg
Click to expand...
Click to collapse
Great news.
But I think the biggest shocker is why do you have your wifi set to WEP?

pyrostic said:
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes TWRP. I am not 100% sure what is holding up the release. Agrabren has TWRP working on the KF but says that it may be a week or 2 until it is ready for release, he is the only one that knows for sure still needs to be done. I think 1 problem is lack of an easy way to boot in to recovery. Either way, looks like we aren't far off.
Sent from my Kindle Fire using Tapatalk

JackpotClavin said:
Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
Click to expand...
Click to collapse
Congrats! Do you have a github repository somewhere that you've got your code committed that we can look at? I do CM7 for the Samsung phones (Galaxy S and Galaxy SII), and so I'm interested in putting Ice Cream Sandwich on the Fire but haven't got around to doing anything on my Kindle because I've been busy the ICS for the phones. Starting with what you've got would be a good start and then I can try to put ICS on it.

Porting the new Kindle Fire

So the title pretty much explains it. What is the likelyhood that someone could port the new kindle fire software to the old KF? If the aspect ratio is the same it seems like it should be possible because both are based off of Gingerbread (I think). It is also possible that Amazon is planning on updating the old KF to the new software but I just went to the website where the updates are (http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620) and I am fairly certain that even though I haven't been on stock for a very long time that it is still the same that it was the last time that I checked. I realize that this isn't the normal type of thread and it may not generate a lot of interest but I just was thinking about it and what better place than here to ask about it? Thanks!

nschiwy said:
So the title pretty much explains it. What is the likelyhood that someone could port the new kindle fire software to the old KF? If the aspect ratio is the same it seems like it should be possible because both are based off of Gingerbread (I think). It is also possible that Amazon is planning on updating the old KF to the new software but I just went to the website where the updates are (http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620) and I am fairly certain that even though I haven't been on stock for a very long time that it is still the same that it was the last time that I checked. I realize that this isn't the normal type of thread and it may not generate a lot of interest but I just was thinking about it and what better place than here to ask about it? Thanks!
Click to expand...
Click to collapse
Its definitely posable, Its just a matter of doing it.

powerpoint45 said:
Its definitely posable, Its just a matter of doing it.
Click to expand...
Click to collapse
I would volunteer to head the project if I knew what I were doing. The only experience I have with cooking roms is in android kitchen so I am pretty much in the dark...

certainly more possible than the reverse

Thepooch said:
certainly more possible than the reverse
Click to expand...
Click to collapse
haha possible is one thing, I think that it's just extremely unlikely that someone would want to. Although, I've sometimes wished I could run GB on my gnex but nobody would ever try to build GB for the gnex because it was shipped with ICS

I got TWRP to attempt to flash the new update for the 2nd generation (it got to 70/80% before hanging), it's just the bootloader files that are keeping me from doing so. There are two flash instructions though... An engineer version, and a production one. Changes to the updater script and removal of some files is all we really need.
I have absolutely no idea how to do that though.

this is certainly the place to find someone that does

Here's the source: http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720

Jessical said:
I got TWRP to attempt to flash the new update for the 2nd generation (it got to 70/80% before hanging), it's just the bootloader files that are keeping me from doing so. There are two flash instructions though... An engineer version, and a production one. Changes to the updater script and removal of some files is all we really need.
I have absolutely no idea how to do that though.
Click to expand...
Click to collapse
That's a pretty gutsy move to try and flash the update without changes to the updater-script. The script tries to flash both the xloader and bootloader. Had it been successful, your device probably would have been bricked and left you only the possibility of usb boot to recover it. Anyway, I was curious about the possibility of getting our KFs to boot with this 2nd generation software, so I did some experimenting.
It's not the bootloaders that keep it from flashing... In fact, there's no way to get it to flash on the 1st generation KF without modifying both the updater-script and the partition table. Here is a list of items that need to be manipulated first...
- The updater-script uses the ICS style by-name references to the partitions. All of them need to be changed to refer to the partitions correctly.
- The section of the script that flashes the bootloaders and the boot partition are enclosed inside of a check of the product name that fails. These conditions have to be removed so the boot image can be flashed. I actually commented out the entire section with the exception of the command that flashes the boot partition.
- The system directory is now larger than the original KF partitioning will allow. The system partition must be enlarged to accommodate the difference. I shrunk the userdata partition to provide more room to the system partition. I suppose one could prune some files out of the system directory and make it fit into the existing partition, but I didn't want to try and figure out what was important or not.
The above changes should be enough to get TWRP to flash the update completely. Unfortunately, it won't even pretend to boot as it never gets out of the bootloader. Unless someone else has some useful insights, I think this particular idea is pretty much dead in the water.

kinfauns said:
That's a pretty gutsy move to try and flash the update without changes to the updater-script. The script tries to flash both the xloader and bootloader. Had it been successful, your device probably would have been bricked and left you only the possibility of usb boot to recover it. Anyway, I was curious about the possibility of getting our KFs to boot with this 2nd generation software, so I did some experimenting.
It's not the bootloaders that keep it from flashing... In fact, there's no way to get it to flash on the 1st generation KF without modifying both the updater-script and the partition table. Here is a list of items that need to be manipulated first...
- The updater-script uses the ICS style by-name references to the partitions. All of them need to be changed to refer to the partitions correctly.
- The section of the script that flashes the bootloaders and the boot partition are enclosed inside of a check of the product name that fails. These conditions have to be removed so the boot image can be flashed. I actually commented out the entire section with the exception of the command that flashes the boot partition.
- The system directory is now larger than the original KF partitioning will allow. The system partition must be enlarged to accommodate the difference. I shrunk the userdata partition to provide more room to the system partition. I suppose one could prune some files out of the system directory and make it fit into the existing partition, but I didn't want to try and figure out what was important or not.
The above changes should be enough to get TWRP to flash the update completely. Unfortunately, it won't even pretend to boot as it never gets out of the bootloader. Unless someone else has some useful insights, I think this particular idea is pretty much dead in the water.
Click to expand...
Click to collapse
yeah!
we need to modify the updater-script!
how can we change the MLO and xloader?

Josepho1997 said:
This is probably a stupid question, but is there supposed to be a updater-script, or at least any apps inside the .tar.gz?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I'm really glad that we have gotten a conversation started about this. Does anyone think that there is a likelihood of Amazon updating the software for the 1st gen or is the hardware on the new one significantly different from the old one that they are probably going to just continue to send out bug fixes until they stop supporting it?

Hey. I was wondering if somebody could port the new launcher to the original fire because that is what I really want. Is that possible?

2390 said:
Hey. I was wondering if somebody could port the new launcher to the original fire because that is what I really want. Is that possible?
Click to expand...
Click to collapse
Rather than let this go on a lengthy discussion, detracting from the original topic, I'm just going to say...
No, it is not possible.

Hmm... would it be possible to modify an existing ics rom to get just the launcher?

soupmagnet said:
...detracting from the original topic...
Click to expand...
Click to collapse
There are plenty of other posts on that topic.

Where?
Sent from my Kindle Fire using xda app-developers app

How? Please tell me!!!!!!
Sent from my Kindle Fire using xda app-developers app

2390 said:
How? Please tell me!!!!!!
Click to expand...
Click to collapse
Since this is obviously a lesson in futility, I'll play along.
Do you know anything about ROM development and programming?

A little. But I will be willing to try. I can learn quickly.
Sent from my Kindle Fire using xda app-developers app

You can get the Kindle Fire's source code from Amazon's website. Set up your build environment and get to work. I will say this...Many experienced minds before you have tried, and failed.

will custom roms like cm10/JB allow bell mobile tv to work?

hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!

I just tried mine running task650 aokp and after the app opens it tells me that my device is not supported. But, maybe I'll try changing my build.prop so that it reflects a Bell Canada phone and not an American AT&T phone.....might work....I'll have to get back to you.

I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.

jethro650 said:
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
Click to expand...
Click to collapse
ok good to know, and rom wise what is a good rom to run right now? i notice there is jellybean roms and cm10 rom, well cm10 is jelly bean i know that but whats the differences? i know my old phone, all roms where gingerbread and cm9 was ics, so of course you'd go cm9 if you wanted ics because its your only choice
and not sure device id wise, but i got this for you if it might help, kernel version 3.0.8-20120814.100513-user and build number of imm76d.i747mvlalh1

patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.

BCSC said:
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
Click to expand...
Click to collapse
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks

Octanee said:
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Click to expand...
Click to collapse
The Bell leak is somewhat buggy, but not enough to keep me from using it as a daily. The reason I use it over CM10 is simply because I love Touchwiz. CM10 seems way faster and loads of other benefit, but I think that Samsung has done really well with this as stock. If you don't stay stock, the Bell TV app will not work (to the best of my experience). It all comes down to what you like and what you want to work.

Octanee said:
hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
Click to expand...
Click to collapse
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues

kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,

Octanee said:
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Click to expand...
Click to collapse
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change

kvpxray said:
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
Click to expand...
Click to collapse
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL

Octanee said:
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Click to expand...
Click to collapse
Haha, I think i got it. Yup, so far so good on my phone running CM10, in fact I'm using it right now! hahah.
There's a thread under the development section that tells you how to root without tripping the counter so that no one will know that you've rooted. And I believe that all you have to do to unroot is to flash an original stock rom

Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM

kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
This works for me also running task650's jellybean aokp.

I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app

otoolerc said:
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you reboot after making the changes? I got the exact same message when opening the app. Made the changes and rebooted and started watching TV.

Beautiful, sir.
For the record: I had restarted, initially, but when it didn't work and I went back to the file to review the text once again, I realised I forgot to stick that capital M in there. I changed it, saved it, but still no tv - simply because, I didn't restart again.
Cheers bud.
Sent from my SGH-I747M using xda app-developers app

I'm curious if anyone has got this working with Rogers Live TV. I have edited my build.prop to reflect what has been posted in this thread to no avail. I am running the latest AOKP. I have even taken editing the build.prop as far as modifying the description and fingerprint.

The ro. product.name may be different for Rogers. The rest should be the same. After editing make sure you save the edited file. Hopefully you have a nandroid in case changing something here makes your phone non-booting. After saving the edited file reboot, if that doesn't work reboot recovery wipe cache/dalvic/fix permissions and try that. If none of that works you may have to get a Rogers stock ROM and see what those four lines are on stock and change them to reflect that.
BTW- which app are you using to edit the build.prop?

Trouble with Eclipse and manual adb app installing.

I did the unbrick method to restore my download mode a few days ago and have since gone ahead and installed the latest roms/kernels(currently on latest TBSGS3 and an AGAT FI16 kernel I believe, also tried with Jellyverse ROM and stock kernel). Now when I try to run my apps with Eclipse or even doing them manually they appear to go through successfully but the app does not end up on my phone. I tried a few samples from google as well as a basic "Hello World" app and it's no good.
Eclipse will report:
[2013-01-08 13:06:06 - BasicGLSurfaceView] Uploading BasicGLSurfaceView.apk onto device '464119fa1e8c1eb'
[2013-01-08 13:06:06 - BasicGLSurfaceView] Installing BasicGLSurfaceView.apk...
[2013-01-08 13:06:11 - BasicGLSurfaceView] Success!
[2013-01-08 13:06:11 - BasicGLSurfaceView] Starting activity com.example.android.basicglsurfaceview.BasicGLSurfaceViewActivity on device 464119fa1e8c1eb
But there is no activity on my phone and no app in the launcher and no further activity in Eclipse's console.
Then when I try to manually do it with ADB I get:
c:\Android\sdk\platform-tools>adb install BasicGLSurfaceView.apk
240 KB/s (11599 bytes in 0.047s)
c:\Android\sdk\platform-tools>
I've done the uninstalling/reinstalling of kies/drivers and the offline install method and all of that. The phone is installed properly for storage mode and download mode and is seen with the "adb devices" command. The lack of errors is baffling to me. Any guesses here?

Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

MoHoGalore said:
Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Beat me to it. HAHA!

If you are stock, I found this in stackoverflow for a possible answer.
Make sure when you setup the emulator in the Hardware properties you add GPU emulation and set the value to yes.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.

timhimosc said:
Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.
Click to expand...
Click to collapse
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.

MoHoGalore said:
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.
Click to expand...
Click to collapse
Instead of doing something as atrocious as going back to stock I tried an ICS rom/kernel(Blu Kubans) and everything is working smoothly and quickly. I only have a small sample pool of 2 JB roms and 2 JB kernels but I'm going to go ahead and assume it's a JB problem until someone with OS/hardware programming knowledge tells me otherwise(I only do apps). Can anyone confirm this by trying to run an adb install command on a JB kernel/rom? Being on a huge developer site I assumed SOMEONE would have run into this same issue, but maybe they were more content than I am about going backwards in Android versions and not bringing it up.
Again, problem technically solved but only by switching device rom/kernel completely to ICS. The whole developing on JB is a big deal to me just for the sake of being on the latest version so I'd like to keep research going. Thanks.

[Q] Tried to install ROM, Galaxy Nexus won't boot at all

I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?

hulslanderam said:
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
Click to expand...
Click to collapse
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app

FIXED
sensation lover said:
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.

Awesome!
hulslanderam said:
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Click to expand...
Click to collapse
Congrats! That's gotta feel good to resurrect a "dead" phone!
I've tried to use the OMAP flash to fix mine, but I still can't get into Odin mode (even tho the drivers and bat file seem to install successfully). If you have any tips, then please let me know.