yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Idontknow186:
Backup and Recovery (Clockworkmod)

I have uploaded the recovery images (with clockworkmod) there are two variants:

1) The first variant is with the standard partition map meaning it backs up everything but the custpack partition. (If you want a full back up use the second variant but read potential issues).

You can get it at (replace the [dot]):

dl[dot]dropbox[dot]com/u/71594697/recovery.img

2) The second variant allows you to back up the custpack but not the cache partition. Basically custpack and cache are swapped in it so when clockworkmod goes to back up cache the custpack is backed up. The big issue is DO NOT format the cache or wipe it or else your wiping your custpack with this variant. We quietly map the custpack to cache so please be careful using this variant.

You cant get it at (replace the [dot]):

dl[dot]dropbox[dot]com/u/71594697/recovery-backup-to-cache.img

Keys to navigate the menu are below:

The the left key (next to space) => Moves up in the menu

Power button => To select an entry

There is no way to move back (sorry the key map I picked sucks) so if you get stuck in the wrong place just removed the battery

Flash your preferred variant with fastboot. Hold (Q and Power to boot into fastboot mode if you don't know the combination). For recovery hold volume down and power
[Android Q&A, Help & Troubleshooting] Draky50110:
Sorry for being noob but this id just for bricked phone ?
[Android Q&A, Help & Troubleshooting] Idontknow186:
Its for making a nand backup for your device. So you can back up the contents of your device and restore them if you want to mess around with the system partitions. It will also be needed for the Froyo update (I'll include a link when I release the update.zip,). Its probably a good idea to make a back up with the second link to avoid bricking before applying the froyo update (I'll include steps when I upload it, also WIndows instructions on how to flash the recovery etc..).
[Android Q&A, Help & Troubleshooting] Draky50110:
Ok :)

By the way "RomManager" can't be ran on Alcatel OT-980 :(

I downloaded it from official website and there is a problem when I try to install it and it is not viewable to download on android market :(
[Android Q&A, Help & Troubleshooting] Idontknow186:
Camera works!

Yay I was able to get the camera to work in Froyo with a minor kernel change as far as I can tell everything is functional now so its just matter of packaging it for distribution :D.
[Android Q&A, Help & Troubleshooting] Draky50110:
Nice :)

A matter of distribution and tuto :p
[Android Q&A, Help & Troubleshooting] Draky50110:
Wow GREAT !! :)

Thanks a lot.

Some questions before trying, as I need to buy a cable next monday :p

Do we need Windows driver ? I have Win7 64bits.

Will the phone be recognized so the .bat will transfer files automatically ?

If I can, I'll test on monday :)

By the way, I also have a WinXP x86 so maybe better for USB recognition ?

Thanks again !
[Android Q&A, Help & Troubleshooting] Idontknow186:
I used Windows 7 64-bit to test and I didn't need additional drivers (they got picked up via Windows update) to flash the recovery (I was worried about the same thing since I was mainly testing under Linux).

EDIT: The drivers got picked up via Windows update
[Android Q&A, Help & Troubleshooting] octavioln:
Thanks a lot

i've now installed Froyo on my Alcatel OT-980a. it really works great!

i just have a little issue with the brightness control, every time i lock the phone the brightess return to the max level.

for now that's the only thing i've found, but everything else it's fully funtional. :D

Thanks Idontknow186!!
[Android Q&A, Help & Troubleshooting] Idontknow186:
I'll look into the bug its probably me breaking something the kernel while working on early suspend.
[Android Q&A, Help & Troubleshooting] Watcher0:
Hello people, I'm a noob.

The only reason I registered here, is the pain in my butt called Alcatel OT-980. I've been searching for some kind of guide how to upgrade worthless 2.1 android to decent 2.2, read through this thread several times in the past, and then finally, a few days ago there is this awesome guy, who finally made it possible, and even the steps how to do it.

I quickly ran into a problem though, while trying to back up. When I run InstallBackupRecovery.bat, I get the cmd window which says:

Boot into fastboot by holding power and Q after shutting device off.

sending 'recovery' <3522 KB>. . .

and then nothing happens. I was thinking the mini usb port on the phone is faulty, but I never have any problems tethering it to the laptop for internet, or file transfers.

Nevermind that, after 2 days trying it, for the sake of trying again, it almost worked.

Sadly, I ended up with a much worse problem. Backing up progressing got stuck after not being able to back up cache or something, after it told me there is no android programs on sdcard, I can't remember. I tried it again, same thing again. Then I wanted to leave it for later, tried to turn on the phone, but after the Alcatel screen, the screen just looked awfully messed up, distorted colours. Although the screen seemed responsive, it was absolutely useless.

Then the idiot noob I am, I tried to mess around with recovery and hard reset, and since I tried everything in that menu, when I try to turn the phone on, it gets stuck on the Alcatel screen.

What can I do?

I tried just going through the update process, but I have the same problem with running bat file I had with the original...

What should I do? Thanks in advance.
[Android Q&A, Help & Troubleshooting] Idontknow186:
Most likely your custpack got corrupted so when you booted you were seeing screen corruption because hardware acceleration was enabled (build.prop is on the custpack and its on by default). Try the system is intact steps first (assuming you didn't format your system partition) after following these steps continue from the upgrading to Froyo from step 7. If these steps don't work try the additional steps below and continue to step 7. I'm going to release an update for the update package if these steps work for you since I probably should have added an erase for good measure :/ (probably will also replace the recovery with one which doesn't back up data instead backs up the custpack only downside is that if you recover you lose your data but its better then the risk of corrupting your custpack if you select the wrong option while making a backup).

If your system is intact (assume it is):

1) Run the AndroidShell.bat included in the package (you should get a command prompt)

2) Place your phone into fastboot like the original instructions see steps 3 and 4 in upgrading to froyo

3) In the command prompt type: fastboot erase recovery

4) In the command prompt type: fastboot flash recovery Image/UpdateRecovery.img

5) Continue from step 7 in original guide (if your system is intact everything should be fine after reboot)

If the above steps fail then do the following additional step (and then continue from step 7 in guide)

1) Grab the system image from http://www.mediafire.com/?9o7dggfawwb4oxc and extract it into the Update package folder.

Note the file above isn't mine I just grabbed it off a post in another forum (if there isn't an image file in it please tell me I haven't checked the package).

2) Run the AndroidShell.bat console (you should get a command prompt)

3) Place your phone into fastboot like the original instructions see see steps 3 and 4 in upgrading to froyo

4) In the command prompt type: fastboot erase system

5) In the command prompt type: fastboot flash system <image here>

(Replace <image here> with the file you just extracted [dragging and dropping does work]. Please be patient with this step the system is fairly large)

6) Continue from step 7 in original guide.

If none of those work post again I can probably put the original custpack / boot and you can just flash those to go back to stock 2.1
[Android Q&A, Help & Troubleshooting] Watcher0:
Again, defeated before start...

Same thing happens as before: I get a popup in the lower right corner when I run the first command telling me:

Connection ailed

Unknown error occurred. Reattach the smartphone and try to connect again

I tried a million times. How could I possibly fix this...
[Android Q&A, Help & Troubleshooting] Idontknow186:
Can you post an image of the pop-up? The only output should come in the command prompt via fastboot. Also did the fastboot driver get installed via windows update?

EDIT: Also can you check that the fastboot driver loaded via device manager? Also check if a different USB port makes a difference. The changes don't touch the underlying baseband in any way so fastboot cannot be broken by just flashing the recovery the problem is more likely something else either with the USB port used or drivers.
[Android Q&A, Help & Troubleshooting] Idontknow186:
Can you try updating the fastboot drivers? If you have the handset manager installed please remove it. Download one touch upgrade from http://www.alcatelonetouch.com/global-en/support/download/ot-980.html. Then enter fastboot mode on your device. Go into device manager under ADB interface you'll find the Fastboot drivers currently used. Right click go to properties, select the driver tab, select update drivers, and browse the file from C:\One Touch Upgrade Q 1.9.0\usb_driver\installdriver\[youros]. After that try flashing the recovery see if it helps.
[Android Q&A, Help & Troubleshooting] Watcher0:
This worked, I managed to get Froyo on my phone! Thank you so much!

I will report any problem with hardware, but thanks a lot again!

EDIT: the phone does get very hot very quick when it's plugged into the computer.. I haven't used it unplugged yet though
[Android Q&A, Help & Troubleshooting] Draky50110:
Wow.

It works.

But I have small things to say :)

I have a french OT980.

AZERTY keyboard :D

So the "hold Q and power" to fastboot is wrong :p because I needed to hold A button instead ;) (the one with #).

Now.... WHAT IT THIS T-MOBILE and PINK colour in my phone ? :p

Anyway, I need to go back home where my wifi is to connect to Market.

Above that... IT WORKS !

Thanks a lot :)

Ho ! By the way, during recovery, the power button was not active, the "ok" was on "N" button, near spacebar...

Not important but maybe you want to know this, maybe because of the azerty keayboard ;)

Thanks again :)
[Android Q&A, Help & Troubleshooting] Watcher0:
Well, after a day of using the phone, I ran into some problems

Overall performance is rather slow, and spikey. Could I perhaps delete some stuff from the phone's memory? Like the clockworkmod folder,

Also, on an unrelated note, what is LazyList? And why is LOST.DIR getting so huge, and how can I stop files getting corrupted? grr stupid card/phone

Also, there were several unexpected and unprovoked restarts, the phone powers off, and sometimes powers back on by itself.

Also, sometimes everything froze when I connected it to a mobile charger, I had to remove and insert the battery.

Additionally, sometimes I can't download anything through the browser, it says the phone's memory is full. If I restart the phone, it sometimes works.

I think most of the LOST.DIR comes from trying to apply a picture as a wallpaper, but when I try doing that through file manager, it doesn't have a thumbnail, and clicking on it doesn't do a thing.

The brightness level indeed does get reset when locking screen.

I think that is all right now. :)

Good work nonetheless
[Android Q&A, Help & Troubleshooting] Draky50110:
Also have some problems too :/

First : each reboot gives me the calibration screen saying : up arrow to begin, down arrow or back to cancel/quit.

I don't have up or down arrow, so I quit but it keeps asking about calibration each time it reboots.

Second : each time I finish and hang up the conversation, the phone is crashing and force close and I come back to homescreen (asking my pincode, as if I had rebooted)...

Those are 2 main problems :(
[Android Q&A, Help & Troubleshooting] Idontknow186:
I have kernel update ready which I'll get out today to solve stability issues (random shutdowns, I haven't had them for 2 days so far so I'm hoping they are fixed). The calibration issue I just realized I screwed up the text it press enter to calibrate the last screen has correct instructions (I'll push it into the kernel update today). The dialer crash try the update first if it doesn't help I'll give some instructions to help me debug (information via adb).

EDIT: Can you also give additional instructions like do you receive a call or do you make one and do you see it in both cases?
[Android Q&A, Help & Troubleshooting] Idontknow186:
See the previous post for crashing should be up today.

Think I know the cause of what your seeing (it will be in the kernel update forgot a step :/). Can you back up your sdcard and format it and restore the files on to it see if it helps. Yes you can remove clockworkmod on the sdcard (your backup is corrupt because of the issue you ran into). I'm going to push a kernel update later today for your other issues (it also will have something to help with your performance and may be any one else since I left a line commented in the original update). Also please don't run the stock launcher on this ROM (it runs badly)

---------- Post added 18th April 2012 at 12:27 AM ---------- Previous post was 17th April 2012 at 11:53 PM ----------

Installing Froyo update 1

Download the update.zip from http://dl.dropbox.com/u/71594697/update.zip (do not extract)

1) Copy update.zip on to your sdcard (do not extract)

2) Hold the volume down and power (it should boot into recovery). If it doesn't

the power off device and try again.

3) Once in recovery use left button on keypad to move selections and power to select an entry.

If you get select the wrong menu remove battery and enter recovery again.

4) Select Apply update.zip from the menu

5) Select power off from the menu to shut down. After a couple of seconds remove

the battery, hold power and re-insert the battery to avoid booting into recovery.

Release notes

- Fixes general stability of device and minor performance optimization's via a kernel update

- Fixes TS Calibration to display correct text

Known issues

- Brightness settings do not save

- Potential bug where hanging up leads to a crash (still investigating wasn't able to reproduce)
[Android Q&A, Help & Troubleshooting] Draky50110:
the hanging problem occurs when I receive or make a call.

The call is without any problem, it is listed in the call list.

But it crashes :(

------------

Just tried after update.1

When a caller hangs up, or me, I have a force close on "com.android.phone"
[Android Q&A, Help & Troubleshooting] bootheantonio:
can any one help me

hi i was wondering if any one can help, i wont to upgrade my alcatel ot-890 to 2.2 i have all ready root my phone and i have all so install recovery manager, titanium backup. :cool:
[Android Q&A, Help & Troubleshooting] Idontknow186:
Sounds annoying as hell. Good news is that it should be easy to track down but I'll need you to reproduce the issue after running the following commands.

Make sure your virtual keyboard supports keys like: ">"

1) Get ScriptManager from the market (we only need it for grabbing the logcat so you can remove it after)

2) Run ScriptManager

3) Enable browse as root in the remember dialog

4) Press menu and select console

5)Select run shell

6) Run the following command in the console: su

7) Accept the super user dialog (may not show up if browse as root worked)

8) Run the following command in the console: logcat > /mnt/sdcard/logcatLog &

9) Run the following command in the console: disown

(if you get permission denied its fine)

10) Reproduce the issue your having (just leave the terminal running)

Note: Minor privacy issue is that the number you dial / get the call from

might show up in the log. To minimize concerns close all other

programs

11) Once finished reboot your phone

12) Upload logcatLog from your sdcard.

Couple of minor notes: if you don't get the superuser dialog tell me since rest of the steps won't work. I'm running a older version of the ROM (pretty much the image from which the update.zip was made) then you guys so my permissions on the su executable are screwed up so it doesn't work here. I think I fixed that in the original release.

---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------

Sorry kernel is completely different you'll have to find some one else to port it. Also the radio is probably incompatible so only a person with this phone can do it.
[Android Q&A, Help & Troubleshooting] Draky50110:
Send you an MP with link to download the log file :)
[Android Q&A, Help & Troubleshooting] Idontknow186:
Can you post the back up of the system.yaffs2.img that you made via the backup steps (I need the stock version think I found the problem :P). Its dying in the telephony stack so I want to just see if the radio libraries are different in the stock ROM. Also one more thing can you read the model on the back of your phone is it a 980 or a 981a (the radio files in the ROM are from a 981a)?
[Android Q&A, Help & Troubleshooting] Draky50110:
OT-980, not the 981a.

Link by MP
[Android Q&A, Help & Troubleshooting] Idontknow186:
Thanks. I'll compare the files when I get home if I think what it is I'll have an update for 980 users to replace the files.
[Android Q&A, Help & Troubleshooting] Idontknow186:
I was able to confirm that the two vendor radio files differ between the devices (doesn't seem minor). Draky I'll send you an experimental update with the right radio files (check your PM).
[Android Q&A, Help & Troubleshooting] Draky50110:
Ok, I answered in PM.

Not working but as I did another test just now, I noticed something :

If someone calls me, the phone crashes on hang up only if the person hangs up.

If I hang up, the phone does not crash.

Have to test if it is different if I make a call instead of being called...
[Android Q&A, Help & Troubleshooting] Idontknow186:
I was reproducing it incorrectly thats probably why I wasn't able to cause a crash. I'll try having the other side hang up (thanks for the hint :)). I'm probably going to mess around with the radio libraries / daemon again to resolve this (since messing with the framework would be masking a larger issue).
[Android Q&A, Help & Troubleshooting] Draky50110:
In fact, I'm not sure this is the only crash, but what I tested is that...
[Android Q&A, Help & Troubleshooting] Idontknow186:
I know there are still a couple of crashes / hangs which happen had one happen to me today. I'm hoping to get them all sorted out. I was able to reproduce the crash going to see if I can get it solved.
[Android Q&A, Help & Troubleshooting] Idontknow186:
Update 2

Installing Froyo update 2

Potentially unstable do not update till all clear. If you want to test it please go ahead but things might

crash

Download the update.zip from http://dl.dropbox.com/u/71594697/Update2/update.zip (do not extract) [Install update 1 first]

1) Copy update.zip on to your sdcard (do not extract)

2) Hold the volume down and power (it should boot into recovery). If it doesn't

the power off device and try again.

3) Once in recovery use left button on keypad to move selections and power to select an entry.

If you get select the wrong menu remove battery and enter recovery again.

4) Select Apply update.zip from the menu

5) Select power off from the menu to shut down. After a couple of seconds remove

the battery, hold power and re-insert the battery to avoid booting into recovery.

Release notes

- Fixes crash on hang up

- Slight clean up for custpack partition and native froyo radio libraries (versus the using eclair ones)

Known issues

- Brightness settings do not save

- There are still random reboots (I'll be investigating these if you have a reproducible scenario it will simplify hunting these down) [not too common but they happen]

Notes

If you find any other issues / crashes please post preferably with reproduction steps.
[Android Q&A, Help & Troubleshooting] Draky50110:
Ok, I test it and tell you about crash and sim import problem ;)
[Android Q&A, Help & Troubleshooting] Draky50110:
Mmm

It crashes a lot more :(

During use of anti-radar apps, im+ app, even camera is crashing : I can't take photo anymore :(
[Android Q&A, Help & Troubleshooting] Idontknow186:
I think I know what caused it. I just updated the update.zip can you try updating using it again (it fixes the camera and possibly other stuff). Can you tell me which IM app it is?
[Android Q&A, Help & Troubleshooting] Draky50110:
IM+ = https://play.google.com/store/apps/details?id=de.shapeservices.impluslite

Will update but in few hours (I'm @ work here, GMT +2)
[Android Q&A, Help & Troubleshooting] Idontknow186:
Checked IM+ doesn't seem to crash anymore can login and chat (morning here so just got to work). I'm going to release updates over the weekend (if the havoc from update 2 still exists :/). After that I'm going to weekly model so we will have one update every Friday to simplify things and hopefully break fewer things since I can dog food the update (if some one wants to try alpha's and can afford a unstable phone on the weekdays then send me a PM).
[Android Q&A, Help & Troubleshooting] Draky50110:
Oik, I'll see after next update.

By the way, I'm using "app2sd" apps ;)

And another annoying thing : Froyo keeps me saying I'm using roaming for data.

I know, it's normal for me.

But it keeps telling me about this whereas 2.1 stock rom didn't annoy me about this !

Any mean to stop this advert ? Because... it is annoying.
[Android Q&A, Help & Troubleshooting] Idontknow186:
Does it only appear in the notification bar or is it giving a pop up? Because I used to get it in the notification in 2.1
[Android Q&A, Help & Troubleshooting] Draky50110:
Popup.

In 2.1, no popup or no message.

Notification show the graph bars with a little "R" above, and this is ok but now I have a full popup message saying "be careful you're using roaming" etc..

It is saying after each check I think (like waking up from sleep mode or switching from wifi to data)...

Annoying because my operator (Free) is using roaming over Orange to transport data... so I'm always using roaming... (for free).
[Android Q&A, Help & Troubleshooting] Idontknow186:
I'll hunt it down and disable it.
[Android Q&A, Help & Troubleshooting] Watcher0:
Can't enable wifi, and therefore can't enable wifi hotspot. It either says error, or restarts the phone.

What launcher do you recommend by the way?
[Android Q&A, Help & Troubleshooting] Draky50110:
He told about "zeam launcher".

For me, no wifi problem : my personal router has wifi in it and I can use it.

Will try this evening and if I have problem, I'll report it here...
[Android Q&A, Help & Troubleshooting] Idontknow186:
Watcher have you applied update 1? Because I think the original release may have had bugs with the wifi which could lead to reboots. I think I forgot to push the updated wireless drivers (for the kernel modifications). Also wifi hotspot may not work at all I haven't tested it (its the same kernel as the original phone so if it wasn't in any of the ROMS by Alcatel my bet would be it probably can't work / isn't supported by the wireless chipset). The current port is a massive hack (its basically based off a ROM for OT990 since I couldn't pull the Froyo sources. The git for them was down I could only pull the gingerbread sources :/) its a stop gap before I build a proper version via Cynogenmod sources (Gingerbread). On the kernel end of things most of the stuff for Gingerbread is there so its mainly the userland / setting it up for the funny partition layout (custpack).
[Android Q&A, Help & Troubleshooting] Watcher0:
Yes I applied update 1, then update 2.

Also, the browser is crashing hard on some sites, perhaps even random sites.

Last thing I tried is checking the arrivals on manchester airport, but every time I tried it crashed.
[Android Q&A, Help & Troubleshooting] Idontknow186:
Thanks I'll look into the browser crashes. I just realized I didn't update the memory values for the lowmemorykiller which can explain the lag we are seeing in the ROM.