yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] tumaini418:
Not yet. I'm still working on trying to flash this blasted CWM recovery image. :mad:

I can boot into fastboot mode with "adb reboot-bootloader"

I can also boot into the recovery with "fastboot boot recovery-2012.06.09.img"

NOW, even though the phone's driver is seen in device manager under adb

when I try to flash the image with:

db push recovery.img /sdcard/recovery-2012.06.09.img

adb shell

[the following will be in adb's shell]

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

exit

exit

[now you're outta adb shell]

adb reboot recovery

I keep getting "Device Not Found".

At least I Know I can restore my phone booting the recovery via fastboot, so I'll be getting to the V-6 portion of my little show shortly. But it kills me when I can't make something work right. :mad::confused:
[Android Q&A, Help & Troubleshooting] mistercheese:
try "adb reboot-bootloader"

then "fastboot flash recovery recovery-2012.06.09.img"

thats all
[Android Q&A, Help & Troubleshooting] tumaini418:
I've tried it that also.

When I try cold boot into the recovery it gets stuck on the android with the animated belly. The only way to back out of that loop is to take out the battery, then resets my phone, and I mean a full factory reset too.

Then I have to restore from the backup I made earlier. I've restored about six times now.
[Android Q&A, Help & Troubleshooting] mistercheese:
its a strange issue.. it looks like the recovery isnt flashed

did u copy the recovery.img to your fastbootfolder?

did u cd to your fastbootfolder first?

(with fastbootfolder i mean the folder where fastboot.exe is.. for me that is platform-tools)

do u get any message after flashing via fastboot?

u should see something like this

C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img

sending 'recovery' (4544 KB)...

OKAY [ 1.138s]

writing 'recovery'...

OKAY [ 1.130s]

finished. total time: 2.268s

just try flashing it the way i just posted

when finished pull battery (edit: use 'fastboot continue' like iuss says)

then boot the system and use quick boot (in play store)

or use ''reboot recovery'' command in terminal
[Android Q&A, Help & Troubleshooting] iuss:
Is that copied 1:1 from your terminal? You push 'recovery.img' to '/sdcard/recovery-2012.06.09.img' and then write a different file to the recovery partition (/sdcard/recovery.img).

Are you sure you're not accidentally writing a backup of your original recovery partition? It really should 'just' work, as demonstrated in the post above.

You can use 'fastboot continue' to get out of fastboot after flashing.
[Android Q&A, Help & Troubleshooting] tumaini418:
@mistercheese

No I can't say I've done any of those things. I'll try to see if I can figure out what your talking about and how to do it. lol I'm not new to android but I'm still learning and not anywhere near the level you guys are. :o

Thanks for the tips.

@iuss I have no idea what your talking about either. :D

I'll be back later to pick your brains (if you don't mind that is) if I can't figure it out for myself. I love this kind of stuff.

But I bow to the masters here at xda! :)

Wait..... after REALLY reading your reply iuss I can say that I'm not making a backup file.

If I do the "push" code via the terminal on the phone I get "adb not found".

If I do it from my computer via CMD I get "Device not found".

Either way I don't get far enough to write anything at all.

Could you explain what you mean by 1:1 though?

Thanks
[Android Q&A, Help & Troubleshooting] mistercheese:
ok a

noob friendly guide to flash CWM

to device

* download and install the android SDK http://dl.google.com/android/installer_r18-windows.exe

when finished open android sdk manager and install SDK tools and platform-tools

* download http://dump.pargon.nl/alcatel/cwm-recovery/recovery-2012.06.09.img and copy it into C:\Program Files\Android\android-sdk\platform-tools

* enable USB-Debugging on the phone (settings>applications>development) and connect to pc via usb but dont activate the mass storage

* open command prompt (Windows Flag + R then type CMD and enter)

in command prompt type cd C:\Program Files\Android\android-sdk\platform-tools

u should see this:

C:\Program Files\Android\android-sdk\platform-tools>

* type adb devices

u should see:

List of devices attached

1234567890ABCDEF device

if u get device not found then there is probably something wrong with the drivers.. remove and reinstall

* type adb reboot-bootloader

the phone will reboot into bootloader (wait untill u hear the windows connect sound)

* type fastboot flash recovery recovery-2012.06.09.img

u should see:

sending 'recovery' (4544 KB)...

OKAY [ 1.138s]

writing 'recovery'...

OKAY [ 1.130s]

finished. total time: 2.268s

* type fastboot continue

u should see:

resuming boot...

OKAY [ 0.001s]

finished. total time: 0.001s

if u follow these steps exactly it must work
[Android Q&A, Help & Troubleshooting] tumaini418:
Okay, I've done all of the above except the "fastboot continue" line.

I'll try that in a little while and let you know how it turns out for me.

Again, thanks!
[Android Q&A, Help & Troubleshooting] fonix232:
Apparently Alcatel heard about my plans to re-design the internal memory layout...

The latest update, issued to Hungarian devices (updates to YE616060), now has AMMS.MBN and EMMCBOOT (APPSBL) certificates, thus checking if the binaries are valid. Gentlemen, we are officially ****ed. Can't remove the stupid custpack partition.
[Android Q&A, Help & Troubleshooting] tumaini418:
I'm sure at least one of you will think of a way.

But maybe you want to keep things like that strictly to PMs in the future.

And just for the need to know crowd at that. Guys like yourself, mistercheese iuss...... you know who. :rolleyes:
[Android Q&A, Help & Troubleshooting] mistercheese:
i know iuss has a cm9 build running now but with a few bugs...

give this man some time...

btw i saw this video and its running ics

[YOUTUBE]FkkNqJts5TU[/YOUTUBE]
[Android Q&A, Help & Troubleshooting] fonix232:
Turns out I was wrong and the certificate was only used to check if the AMMS and EMMCBOOT were properly written :D
[Android Q&A, Help & Troubleshooting] OCouceiro:
Front camera ok

I try and like you say it work.

But front camera it's a crap

tanks
[Android Q&A, Help & Troubleshooting] warsylep:
Unfortunately yes, it's just VGA camera with 640x480px or aprox. 0.3 megapixel.
[Android Q&A, Help & Troubleshooting] gusthy:
Hm, Phonix, good to see you here after the Blade topic át MoDaCo, that were good times :-)

What this update fixes?
[Android Q&A, Help & Troubleshooting] fonix232:
Just enough for video chat. It was never meant to take photos :D

Nothing much. At least I didn't notice anything yet. For sure, the baseband was updated, and a few system apps too (including the FOTA manager).
[Android Q&A, Help & Troubleshooting] Anariel:
problem with youtube application

Hi !

Do any of you have saccades in the youtube application, in full screen mode ?

Apparently I'm not the only one in this situation, I found a comment on the google play store describing the same problem.

Saccades occur only in fullscreen mode of the youtube application. Using the browser version of youtube or any other ways to watch videos work fine. (I also precise that it's not lag, I tried to wait for the end of the download but it didn't help.)

I tried to update the application - come back to stock version - install flash player - uninstall it... no result !

It isn't a very big deal, but it's still annoying. So if ever someone know how to fix this little problem, it would be nice !

(Sorry to ask my question here, but I thought it'd be the best place to find alcatel OT 995 users :))
[Android Q&A, Help & Troubleshooting] tumaini418:
@mistercheese

I was able to boot into CWM recovery with the reboot recovery command in terminal. So I guess it really has been flashed.

I guess I'll try a cold boot as well. it's suck if I run into the same problem that wipes my phone settings again though. But for now it's bed time. I'll resume this in the morning. With luck I'll get to the testing of the supercharger.

Not that it matters in this thread but the supercharger worked great in both my ZTE Blade (no suprise there) and my Huawei u86550 (which kind of suprised me) and totally screwed up my Arnova 7b g2 tablet (which didn't suprised me at all lol).
[Android Q&A, Help & Troubleshooting] warsylep:
I just used Superchager and i'm running settings on boot with scriptmanager and so far so good.

Used the settings it sugested, maybe i'll read a bit and tweak a bit too :)
[Android Q&A, Help & Troubleshooting] tumaini418:
You mean you are running the 99supercharger script at boot I hope. Running the v6 supercharger script is gonna cause you problems.

Either way thanks for the info. That script rocks.

Oh, don't run the superclean script at boot either. Best to create a widget and run it that way.
[Android Q&A, Help & Troubleshooting] warsylep:
That. i didn't knew the script but i did read the warnings :)
[Android Q&A, Help & Troubleshooting] v1c3:
Hello,

I'm new to Android, and I'm trying to build a rom...

I've successfully built CWM from cm9 tree, and the kernel from alcatel source. I've flashed it and it works.

After that, I've built a full rom from cm7 tree, and I have a "cm-nightly.zip" ready to flash.

My question is, is it safe to flash it (it includes a boot.img), since I don't expect it to be really useable.

Is there a way to go back, using CWM backup, or may this brick my device?

Regards,

Vincent
[Android Q&A, Help & Troubleshooting] mistercheese:
If u make a backup first its ok.. u can always restore from it

Can u share the zip so we can check?
[Android Q&A, Help & Troubleshooting] v1c3:
Yes, backup is done ;-)

I can't share the zip now coz I'm currently moving ISP...

/system/bin, /system/lib, system/app, /system/xbin, /system/etc, etc. are populated, and here is the beginning of "unzip -l ":

36590 2008-02-29 03:33 META-INF/MANIFEST.MF

36643 2008-02-29 03:33 META-INF/CERT.SF

1714 2008-02-29 03:33 META-INF/CERT.RSA

136 2008-02-29 03:33 META-INF/com/android/metadata

224292 2008-02-29 03:33 META-INF/com/google/android/update-binary

8295 2008-02-29 03:33 META-INF/com/google/android/updater-script

3026944 2008-02-29 03:33 boot.img

218653 2008-02-29 03:33 system/app/AccountAndSyncSettings.apk

24413 2008-02-29 03:33 system/app/ApplicationsProvider.apk

Vincent
[Android Q&A, Help & Troubleshooting] DennisJKA:
Hey guys :)

In a few weeks i'm getting the Alcatel OT-995 (really looking forward to that, it will be my first smartphone :D) and i'd like to know if one of those TV-Out-Cables (e.g the one from Nokia. I think its called CA-75U. My friend told me this cable worked for him with an Samsung Galaxy S+) works with the One Touch 995?

Yeah, i know it has a Micro-HDMI-Port, but my TV doesn't support HDMI :D

So if any of you know it, let me know :DD

And for those of you, asking about the 4.0 ICS-Update: I've talked to the Customer-Support and they told me, that "...as soon as it becomes available you will find it on our website."

Thanks :)

Oh, and please excuse my bad english, it's not my native language ;)
[Android Q&A, Help & Troubleshooting] mistercheese:
just wait a few weeks and buy a Alcatel OT-986
[Android Q&A, Help & Troubleshooting] iuss:
Highly unlikely (read: no).
[Android Q&A, Help & Troubleshooting] BENETNATH:
not targeted to europe, and frankly ot-995 was 129 € here in france.. around half the price told for ot-986
[Android Q&A, Help & Troubleshooting] maluko:
if you go behind this, never buy lol

there are always better and last phone :D
[Android Q&A, Help & Troubleshooting] mistercheese:
its all about what the price will be..
[Android Q&A, Help & Troubleshooting] iuss:
I've pushed my basic port of CM9 for to Github:

More details at: http://dump.pargon.nl/alcatel/ics/

Precompiled image is included as a demo. You'll need to prepare a SD card (refer to the README) and then fastboot the provided boot.img.

It only boots off SD and is far from complete.

It cannot be flashed using CWM (see above)

As mentioned in the README, there's plenty to be done; I'll be a little busy the coming weeks, so if anyone feels like contributing, shoot.

If you can't get it to work, move along - I'm mainly looking for some patches/contributions ;)
[Android Q&A, Help & Troubleshooting] BENETNATH:
Great start iuss

Hope some dev can join
[Android Q&A, Help & Troubleshooting] tumaini418:
Well here I am again. And I tell ya this version of CWM recovery will not and cannot be cold booted on THIS phone.

It's kind of strange though. Though I can't cold boot it, I can boot into it using CWM rom manager. Which means that it IS flashed to the phone. BUT RM can't "see" that there is a recovery partition. So I have absolutely no idea HOW its working. what is going on. Maybe I just have a defective phone.
[Android Q&A, Help & Troubleshooting] Yeasis:
More details at: http://dump.pargon.nl/alcatel/ics/!?!

ICS?

Have you made a ICS ROM ( i think i don't really get it) ?:confused:
[Android Q&A, Help & Troubleshooting] gusthy:
What is the problem with that?
[Android Q&A, Help & Troubleshooting] BENETNATH:
indeed, ICS rom, but README is CLEAR :

Possibly working:

- Graphics (kgsl backport from CAF ics_chocolate + Qualcomm Adreno libraries from March 2012)

- Input (kernel fixes; multi-touch requires additional fixing)

- Sound

- Basic radio functionality (GSM)

- Some sensors (accel, proximity/light)

- WiFi

Definitely not working:

- Bluetooth (stock uses custom/legacy glue)

- GPS

- Capacitive key backlight

- HW accelerated decoding

- Cameras

- HDMI out
[Android Q&A, Help & Troubleshooting] Yeasis:
That's awsome, but why don't we just wait for jelly bean?
[Android Q&A, Help & Troubleshooting] fonix232:
Okay, temp-fixed the keyboard leds, and added a basic NFC support (dunno if works properly, can't test). Gonna upload my AOKP and CM9 builds soon (CWM-flashable ones).
[Android Q&A, Help & Troubleshooting] tumaini418:
Wow! Your rockn' right along ain'tcha.

Thanks in advance for the hard work.

Can't help but wonder if installing a custom rom will fix my not being able to perform a cold boot into the CWM recovery. Things that make you say hmmmm:rolleyes:
[Android Q&A, Help & Troubleshooting] v1c3:
Yes, great news, CM9 is on the rails!

iuss and fonix, did you have to patch the kernel to make it boot?

My cm7 built doesn't work at all, stuck at the "one touch" white screen, and "adb shell" returns "/bin/sh no such file..." or similar error. I guess I have to fix init.rc, but moving to CM9 now.

Regards,

Vincent
[Android Q&A, Help & Troubleshooting] quovadissbg:
Hi guys.

Quick question. I have data plan with unlimited quota but unfortunatelly there is some problem - I can send mails, upload to dropbox/box, but I cannot browse or download anything with this data plan. There are 50 mbs at max speed and after that the speed goes on 128kbps. There's no difference between using the data at fastest speed and on limited speed. Does anyone have that type of problem experiencing with its Alcatel?

Thanks in advance for the response!

P.S. Well done progress with building ICS ROM and porting the CWM.:good:

Regards.
[Android Q&A, Help & Troubleshooting] mistercheese:
My ported ics doesnt boot either
[Android Q&A, Help & Troubleshooting] fonix232:
iuss made a separate, patched kernel (it's in the readme :rolleyes:) and I'm using that. Although it has a few quirks (like, default governor is performance), but pretty much usable.

I'm making a few alignments (light sensor data stuff, etc, so auto backlight will work), and releasing the ROM after.

EDIT:

Both AOKP and CM9 downloads are available here: http://goo.im/devs/fonix232/OT995/ICS

Disclaimer:

I am in no way responsible if your phone dies, blows up, takes part in any bad things (erupting a volcano, starting a nuclear war), or turns into a gigantic evil robot. You've been warned.

What's working:

- Keyboard lights

- Wifi

- Vibration

- Sounds

- GSM functions (calls, did not test 3G or any other networking)

- Automatic backlight

- Sensors

- Single touch

- Hardware acceleration of the UI

Not working:

- Bluetooth

- HDMI out

- Multitouch

- Video acceleration

- FM radio

- Anything else what wasn't mentioned

- USB storage mode (MTP/PTP/Mass Storage, neither works currently)

What's probably working:

- NFC

Please note: if you want good battery life, make sure that you go into Settings (AOKP Settings -> Performance in case of AOKP, or Simply Performance->CPU in case of CM9) and set the Governor from Performance to Ondemand. Performance keeps the CPU on the highest enabled frequency, while Ondemand keeps it as low as possible for the given task.

My fix for the keyboard backlight is temporary, and is possible that it will produce more battery drain. If you want to get rid of it, remove /system/etc/lights.sh. You will loose keyboard backlight, but possibly gain a bit more battery.

Also if you like my work, you can invite me for a drink (check my signature). But do not forget about iuss, as he is the one who made all of this possible!

For developers:

Here are my device and vendor trees:

https://github.com/fonix232/android_device_alcatel_cocktail

https://github.com/fonix232/android_vendor_alcatel_cocktail

The kernel used in both releases is compiled by iuss, all credit for most of the work goes to him! All I did was to compile a CWM installable firmware, and make some fixes here and there!

Installation:

- Download the firmware you want, also download Google Apps (http://goo.im/gapps)

- Copy both zip files to your SD card

- Reboot to ClockWorkMod Recovery

- Make a backup of your current system

- Under Mounts and Storage, erase data, cache, custpack and system

- Install the CM9/AOKP zip first, then GApps

- Wipe data/cache again

- Reboot and wait till it boots completely

- Have fun!

It is REALLY REALLY REALLY important that you make a backup of your system, and secure it. Without that, you won't be able to go back to stock, or update to any future Alcatel releases. So better be safe, make a backup, and copy it back to your PC to be sure!
[Android Q&A, Help & Troubleshooting] tumaini418:
First of all thanks again for your hard work. Yours and iuss's. This is a wonderful thing I think.

Second, just what dose "AOKP" stand for? I've see it over at cyanomod but I never gave it a second thought. You know I'm kind of a noob, so don't laugh..... at least not so we can see it in the tread if you don't mind. hehe

And is "gapps-ics-20120429-signed" the one that should be DL'd?

Okay one more question then I'll shut-up, promise.

Is the recovery img you have on the same page as the roms the same one that I have already? recovery-2012.06.09??
[Android Q&A, Help & Troubleshooting] depsy89:
hi! i just want to verify whether this phone have 1gb or 2gb of internal rom? and how should i check my rom's size? i went to settings>applications>then only see 1gb internal storage. tia!:)
[Android Q&A, Help & Troubleshooting] iuss:
CM allows the user to select a governor, as I hadn't checked yet how it's set I didn't touch it yet (init.rc would work, but maybe CM has some overlay for it?).

Anyway, it's currently on 'performance' by default, as fonix232 said you probably want to select a scaling alternative (ondemand, conservative). I'm not sure what e.g. Google is using on Nexus? They used to have their own governor..

I'll be a bit busy the coming 2 weeks, but fonix232 seems to be doing a great job..

Once I regain some spare time I'll look at e.g. the input driver (it still doesn't conform to the kernel 'B type' spec, that's why multi touch fails).
[Android Q&A, Help & Troubleshooting] fonix232:
You can set the default governor in the kernel, will do some stuff to it later too (I'm a kernel noob so... don't wait too much ;D). Also I think liblights can be modified to properly manage the leds. Currently I can't see why it won't pass the proper values, even though it is a proper liblights. With that, we can have notification leds, keyboard led (proper one!) and camera flash too :D

Camera definitely needs a new HAL. Problem is, both of the modules are not too well known and not too used in Android devices, and this slows things down.

Also, audio needs a bit of finetuning. I'm not usually the guy who says this, but it is too freaking loud.

Would you be able to test out NFC? I'm thinking I miss something there, but can't figure out what...

tumaini418:

AOKP is to ICS what CyanogenMod7 was to GingerBread. CM9 take an almost 180° turnaround, regrouped the settings in a different way, and incorporates less changes as for today. AOKP on the other hand has a lot more features, but they are more buggy. In my opinion, AOKP worth a bit more.

You need the latest GApps, and yes, the recovery.img is the same. Uploaded it for a friend (he had problems grabbing it from iuss' website).
[Android Q&A, Help & Troubleshooting] iuss:
The ~1 GB shown is for the userdata partition. It has (slightly less) than 2 GB emmc memory. Even with a custom ROM, you should count on having ~1 GB usable, as modifying the partition table (e.g. to reclaim /custpack) is a tricky endeavor (and only gets you ~250 MB extra). Grab a 32GB SDHC card if you need space (does the controller support SDXC too? ;)).

@ fonix232

Noticed you added your nvram.txt to proprietary; we really need an alternative solution for it, as the nvram data contains the WiFI MAC...

When running from SD you can get away by mounting /custpack, but for the flashable case it might be useful to snatch it from /custpack (or a backup of it) in CWM.
[Android Q&A, Help & Troubleshooting] fonix232:
Hmm, didn't noticed that.

The BCM4330 has an internal ROM, storing the WiFi mac, so maybe backporting some drivers and firmwares from such a device (Galaxy Tab 10.1 maybe?) should help. Problem is, I've formatted custpack, and my tutorial bases on that too... well, I will do so as you said then, in the next release.
[Android Q&A, Help & Troubleshooting] iuss:
Ah, then I'll change that.

Yup. Safest is probably to grab Google's version (tuna/maguro) and adapt it.

Yup. Haven't looked into it much, but apparently ICS changed the camera glue (to a HAL module in lib/hw). Cyanogenmod Gerrit contains a patchset to load a Froyo (and I guess Gingerbread too) camera HALs using a wrapper lib on ICS (same msm7x30 SoC). Apparently the tenderloin guys (msm8xxx) got it to work for them with a few minor modifications. That looks promising..

I can't right now, and probably have little time to spare. I did try to get it to work on stock gingerbread (by building the i2c pn5xx HAL from crespo or so). That wouldn't work either and failed somewhere low level, but I didn't investigate further.

The fact that it seems to upload EEPROM settings is a bit daunting, I'm not sure whether we'd be able to just reuse it..

---------- Post added at 05:07 PM ---------- Previous post was at 05:04 PM ----------

That would be ideal. Not sure which drivers Galaxy Nexus is using, but brcmfmac is in mainline and supports 4330 too. Compat-wireless (which TCL/TCT already used) should make using it alot easier..