Database Users

[wip] icedroid/froozendroid [ics-sdk] Still not booting

First of all i want to give all my Thanks To mike1986
For Letting me use Android Revolution HD as Base for this port: http://forum.xda-developers.com/show....php?t=1245892
This is an attempt to get the ICS-SDK Port for our beloved EEE-Pad's
ive been working on this for a half day and i came so far that it do boot up to black screen, as feonix friend did,
now i need to edit kernel to load the screen properly (yes this probably caused by the kernel)
still no sucess
Before commenting, I appreciate all your help, i seriously do, just please ask before what iv'e done instead of say what i have to do
To do

RESERVED!
ICEDROID/FROOZENDROID
V0.1
#edited boot image, makes it load correct framework files
Gets passed the asus logo!
Now got it to boot to black screen!
YES Feonix. I came here to!

Reserved also!
Upcoming
Edit bootfiles, currently screen is not started correctly!

Will this flash over a honeycomb rom?
When i had a galaxy s we had to repartition going from 2.2-2.3. As ICS is such a change from H, i just wanted to check.
Ps. Good work so far. Thanks.
Sent from my Transformer TF101 using xda premium

Reopening - let's make sure we all stay on topic and contribute to real development

[WIP] ICS SDK-Port
Ok so iv'e been following the "developer's" foox22
THANKS TO ANDROID REVOLUTION HD (Mike1986) for letting me use their port as a base of this!
(my 1.st zip was this way but then i got no boot.img that was optimized for this)
Forgive me for this post/topic, but this is the zip that should make the ICS to boot,
if you notice its a black and nothing else then its should be due to no "edited build.prop of our resolution!
that's why someone here before never got it to "boot"
http://www.multiupload.com/IU8R71F500
if this doesn't boot up, try get a logcat
And yes you all other developers can try get me a logcat // REGARDS

Im gonna delete your other thread

Do we have a list of what may not work currently?

acdcking12345 said:
Do we have a list of what may not work currently?
Click to expand...
Click to collapse
i need to know what if its loading properly, if anyone just can try V007, as that's the one that is correct, boot.img loads all correct framework file's if it doesn't boots up then its a, screen resolution problem or a lib problem,

about to flash in a min when back up finishes. will report
just hangs on black screen after eeepad splash

tomqman said:
about to flash in a min when back up finishes. will report
just hangs on black screen after eeepad splash
Click to expand...
Click to collapse
black screen, you did wipe everything ??

Moving this to General - there really isn't any real development going on other than some copies, pastes, and asking testers to bork their device. The OP can't test this on his own device but is asking others to do it for him. This is not development. When something of substance happens - then create a new thread that is actual development in the development section.

ok so to repack the boot.img
blobpack <headerfile=kernelblob.HEADER> <outfile=kernelblob> <partitionname=? kernelblob.ebt or kernelblob.LNX > <partitionfile=kernelblob.ebt or kernelblob.LNX >
and is this even nessesary ?_? kernelblob.LNX-config
what did this come from, after i repacked the kernelblob.LNX O___o

http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Did you see this?

Ranatsu said:
http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Did you see this?
Click to expand...
Click to collapse
leaked o__O test build omfg thats so cool, even if its avaible for sdk!
anyhow im sure we cant use it :/

SWEATTAIMI said:
leaked o__O test build omfg thats so cool, even if its avaible for sdk!
anyhow im sure we cant use it :/
Click to expand...
Click to collapse
You are right, it's no use for us... the Galaxy Nexus has NEON support, all binaries are compiled with that, and our TF (and every Tegra2 tablet) misses NEON...

fonix232 said:
You are right, it's no use for us... the Galaxy Nexus has NEON support, all binaries are compiled with that, and our TF (and every Tegra2 tablet) misses NEON...
Click to expand...
Click to collapse
Got it anyway

New CM9 Nightly Builds for TF101

Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.

So who wants to be the Guinea pig? I'm already running that KANG that was posted up earlier this weekend. I may try it after I charge up.

yea...guinea pig here....goes through boot animation and then system ui and trebuchet (the launcher) fc...i would say stay away until some official announcement is made

Yeah. It doesn't even boot up probably. :-(... going back to stock
Sent from my Galaxy Nexus using XDA App

You have to start somewhere.
Now at least we have an official CM9 branch, which means someone is working on it

brzgw said:
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
Click to expand...
Click to collapse
ehm where from?
Edit: http://download.cyanogenmod.com/?device=tf101
Found IT ^_^

I got launcher force closes when i had an overclocked kernel with a stock rom. Gonna check this out a little later.
Sent from my Transformer TF101 using Tapatalk

I'm surprised that this news seems to be not generating much buzz here. Not knocking any of the other devs, because most of them do amazing work, but CM is the bee's knees. When those nightlies get semi-mature, I'll be running them and never look back. They've never done me wrong before. Any device I've ever had that was supported, was the best ROM available for my needs. YMMV, of course.

I think when its own thread is created youll see the buzz, cm rocks lol
Sent from my R800i using xda premium

I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet

shadrach47 said:
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
Click to expand...
Click to collapse
Yep, same here, even with wipe dalvik and fix permissions, FC´s :S
Let us wait for a new update....

Alas, I ran across this on get.cm also. Got excited and then had the FC issues like everyone else. At least it is a step in the right direction.

Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S

Was just about to try flashing it until I saw how many people were unsuccessful. Oh well, guess I'll wait until an official release.

ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.

shadrach47 said:
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
Click to expand...
Click to collapse
Ok got it to work again, had to use Super Wipe Lite from http://forum.xda-developers.com/showthread.php?t=1245892
after running the script flashed latest revolver and got wifi backup....

Same here, will try your suggestion below.
Edit: Had to run the wipe zip, reflash and boot into current rom and the restore a backup to get it working again. PITA But it works.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse

CM rocks

lollazzo said:
CM rocks
Click to expand...
Click to collapse
i would like to see MIUI V4 on tab, as it will be easier to port than 2.x was ^_^

New official CM9 nightly on get.cm. It boots!!! Gonna test it and report back in a bit.
EDIT1: Wifi works and was able to log into my Google account. Currently restoring my Titanium Backup and will test a bit more after that. Also, camera makes the tablet reboot on first launch, but works after that. Odd. More info to come.
EDIT2: Face unlock is there, but doesn't recognize my face, so I can't test it out. It couldn't recognize my face on my Nexus S 4G either. Maybe my face is just derped up. Anyway, there is nothing that I could tell that is broken. Even the MicroSD mounted with no issue. I don't have a keyboard dock to test it out, otherwise I would. Games and videos both work fine.

Paranoid Android for SGH-I757M

New Thread
http://forum.xda-developers.com/showthread.php?t=2016114

mic2012 said:
Paranoid Android for SGH-I757M thanks to Socim
PA2.99 22NOV2012 for i757m
http://d-h.st/users/Space/?fld_id=7675#files
Needs wipe data before upgrading from cm10. Sorry guys, I don't own an i757m so haven't tested it.
Click to expand...
Click to collapse
Was this rom built using the paranoid android port guide?

......

Definitely a HUGE thanks to Socim!! The Paranoid rom is working really well on my phone. Only 1 reboot during initial setup with an up time of 45h. Very stable.

Thread needs to be retitled look at cm9 or Cm10 thread title for format. If not following proper thread title etiquette for custom roms we may get locked by mod.
Screenshots are a big + for rom thread, list of features.
List of working and non working elements of the rom with current release. Ensure this remains updated with each build.
Thanks
Sent from my SGH-I757M using Tapatalk 2

I have just transferred my data to new hard disk and it cost me two days.
Hopefully new build will be uploaded later today. With new kernel config it should be highly stable, many thanks to dr4stic. My phone haven't met any reboot for 52hrs.

Socim said:
I have just transferred my data to new hard disk and it cost me two days.
Hopefully new build will be uploaded later today. With new kernel config it should be highly stable, many thanks to dr4stic. My phone haven't met any reboot for 52hrs.
Click to expand...
Click to collapse
Looking forward to trying it.
Sent from my SGH-I757M using xda app-developers app

Thanks for the updated ROM Socim. Just downloading and flashing now.
Quick Q - has anyone tried the Gapps version 20121011? Goo Manager informed me an update was available and I have downloaded it, but haven't flashed it yet.

4runner10 said:
Thanks for the updated ROM Socim. Just downloading and flashing now.
Quick Q - has anyone tried the Gapps version 20121011? Goo Manager informed me an update was available and I have downloaded it, but haven't flashed it yet.
Click to expand...
Click to collapse
When I had PA installed, I did the gapps update with no issues.
Sent from my SGH-I757M using xda app-developers app

I am still having some random reboot when I try to light up the screen from idle. But otherwise everything work fine and fast. ROM look amazing

Everything was great for me too... No reboots for 2 days, but what I did experience is lockups and slowdowns. I tried modifying cpu thresholds to no avail. Also had camera probs.
Really cool rom, I hope it gets support in the future to make totally stable... For now, had to revert back to 0829 cm9...stable stable land! Haha
Cheers

unclephil said:
I am still having some random reboot when I try to light up the screen from idle. But otherwise everything work fine and fast. ROM look amazing
Click to expand...
Click to collapse
Weird, I've never encountered that issue. I assume you did a complete clean install of the Paranoid rom? Maybe get cat log running and log the event if it happens, I hear that helps devs track down the issue. Are any specific apps running when these reboots occur?

been running this ROM for around 24 hours noticed around 4 or 5 random resets and am still having the issue with instagram and youtube controls being put in the background. Otherwise the build is quite reliable and very snappy, Thanks for the effort!

The reboot for me only occurs during screen unlock. I have remove the patern unclock and since then did not see any reboot. Will let you know tomorrow the result
Update: I got another reboot this morning without any lock active. Will try another fresh install to see

[DISCONTINUED][ROM] [CM10/10.1] [OaTLnT] [Mar. 17/June 08, 2013]

First, Happy and Safe Holidays to all.
Next, find below the links to my most recent kang'd, lightened, and tweaked JB ROM with working sound, mic, video, and camera; albeit with the camera images rotated 90 degrees per usual (at least in the camera app I use). Please note that this ROM does not require the expanded system partition achievable with ACMEInstaller3; I still have ~60MB left after flashing this and the accompanying lightened GApps. I flash these with the latest TWRP and have the latest moboot installed. Hope these work as well for you as they do for me, but it goes without saying YMMV!
Finally, I've been focusing most of my ROM development efforts on the new Nexus 4, so updates to this, if any, may be far and few between, and only triggered by major problems or a major update to JB. Still, at this stage I feel our beloved TP's have aged extremely well thanks to the entire AOSP and CM communities and specifically to the likes of Green, Dalingrin, JC Sullins, Dorregaray, etc. who have and continue to make this all possible. So without further ado...
CM10.0
Happy St. Paddy's Day ROM: http://www.mediafire.com/?98p8x56gpw82yid
MD5: 97236e3e6b4b4b2c64343eac45d3bb08
GApps: http://www.mediafire.com/download.php?trv74s64iodi71c
MD5: 1cefddbe11033c7b2f3763097c96d5b6

O.a.T. said:
First, Happy and Safe Holidays to all.
Next, find below the links to my most recent kang'd, lightened, and tweaked JB ROM with working sound, mic, video, and camera; albeit with the camera images rotated 90 degrees per usual (at least in the camera app I use). Please note that this ROM does not require the expanded system partition achievable with ACMEInstaller3; I still have ~60MB left after flashing this and the accompanying lightened GApps. I flash these with the latest TWRP and have the latest moboot installed. Hope these work as well for you as they do for me, but it goes without saying YMMV!
Finally, I've been focusing most of my ROM development efforts on the new Nexus 4, so updates to this, if any, may be far and few between, and only triggered by major problems or a major update to JB. Still, at this stage I feel our beloved TP's have aged extremely well thanks to the entire AOSP and CM communities and specifically to the likes of Green, Dalingrin, JC Sullins, Dorregaray, etc. who have and continue to make this all possible. So without further ado...
ROM: http://www.mediafire.com/download.php?vntt5p8eccborhe
MD5: daaf58bcac7738df86965c317418fdb8
GApps: http://www.mediafire.com/download.php?trv74s64iodi71c
MD5: 1cefddbe11033c7b2f3763097c96d5b6
Click to expand...
Click to collapse
awesome, great to see you back, even if its only for this once. Thank you, Merry Christmas!

Thanks a million for all you have done.
Sent from my cm_tenderloin using XDA Premium HD app

thanks o.a.t i was wondering how long i'd have to keep your secret

O.a.T. said:
First, Happy and Safe Holidays to all.
Next, find below the links to my most recent kang'd, lightened, and tweaked JB ROM with working sound, mic, video, and camera; albeit with the camera images rotated 90 degrees per usual (at least in the camera app I use). Please note that this ROM does not require the expanded system partition achievable with ACMEInstaller3; I still have ~60MB left after flashing this and the accompanying lightened GApps. I flash these with the latest TWRP and have the latest moboot installed. Hope these work as well for you as they do for me, but it goes without saying YMMV!
Finally, I've been focusing most of my ROM development efforts on the new Nexus 4, so updates to this, if any, may be far and few between, and only triggered by major problems or a major update to JB. Still, at this stage I feel our beloved TP's have aged extremely well thanks to the entire AOSP and CM communities and specifically to the likes of Green, Dalingrin, JC Sullins, Dorregaray, etc. who have and continue to make this all possible. So without further ado...
ROM: http://www.mediafire.com/download.php?vntt5p8eccborhe
MD5: daaf58bcac7738df86965c317418fdb8
GApps: http://www.mediafire.com/download.php?trv74s64iodi71c
MD5: 1cefddbe11033c7b2f3763097c96d5b6
Click to expand...
Click to collapse
Happy Holidays OaT, so great to have you back!.....how's the battery life?? Lol...just kidding OaT.....

Haven't flashed anything on HP Touchpad since the first ICS release or so. Seems a lot has changed and I'm finding it hard to find the info needed. With these downloads waht exactly do I need to do? I have CWM recovery, but you mentioned TWRP I believe. Step by step instaling would be appreciated or if someone could point me to them. Haven't used the ACME installer in forever so I'd rather not brick it
Thanks in advance! And Merry Christmas and Happy Holidays!

Installed after installing TWRP and did a full wipe. It's been sitting at the android highlighting boot logo for 10 minutes easy. Any ideas?

Seanbest said:
Installed after installing TWRP and did a full wipe. It's been sitting at the android highlighting boot logo for 10 minutes easy. Any ideas?
Click to expand...
Click to collapse
What Rom were you running before hand ? Are see the same logo you used to see or is a new one?

New logo. I was on AOKP before. I rebooted it and tried restarting again. It sat at the logo again. I again tried to go back to recovery, now the unit wont even power on.

Seanbest said:
New logo. I was on AOKP before. I rebooted it and tried restarting again. It sat at the logo again. I again tried to go back to recovery, now the unit wont even power on.
Click to expand...
Click to collapse
Sorry I can't help , I was hoping that it had deleted the old ulimage and was trying to boot into that.
You could try sticking it on charge and then booting into recovery to install the backup I hope u made or webos to check what ulimages are in your boot folder in case that is to full.
Sent from my cm_tenderloin using Tapatalk 2

If i can get it to power on I could try that lol

that was nice surprise from oat. happy holidays

shah_vm said:
that was nice surprise from oat. happy holidays
Click to expand...
Click to collapse
Indeed. This finally gave me the motivation to try JB. Thanks so much!

asiliat said:
Indeed. This finally gave me the motivation to try JB. Thanks so much!
Click to expand...
Click to collapse
same here, thanks OATs

Got my Touchpad reset so gonna try again.

Seanbest said:
Got my Touchpad reset so gonna try again.
Click to expand...
Click to collapse
What did you do to reset it please ?

Noticed a camera app wasnt inluded, downloaded one and it opens but shows black screen like camera isnt connecting
Everthing else seems to be working smoothly
edit: nvm camera works, i just had to "take" a picture first to get rid of the initial black screen

In jb the camera is now merged into the gallery application.
Sent from my GT-N7000 using xda premium

eyeb said:
Noticed a camera app wasnt inluded, downloaded one and it opens but shows black screen like camera isnt connecting
Everthing else seems to be working smoothly
edit: nvm camera works, i just had to "take" a picture first to get rid of the initial black screen
Click to expand...
Click to collapse
What is or do you have a link for nvm camera .
Thanks

Did a clean install (webos doctor, format usb).
Keyboard stops with an error.
Unable to sync my boomarks with stock browser.
How can I fix it.

Mako Android L B4 causing problems?

Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.

ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)

Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.

ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.

Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.

Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?

try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176

RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks