Database Info

[Q] Product code to be used in nv_data.bin for IMEI restore process

A friend has the null IMEI issue and I want to try the procedure outlined for the Samsung Captivate in the following thread:
http://forum.xda-developers.com/showthread.php?t=881162
Samsung Captivate Android Development - > RESTORE IMEI and Product Code w/o ADB, PC (ALL DONE ON PHONE) nv_data.bin
I don't think the product code used for the captivate will work with the nexus S. Can someone tell me the product code to use when editing the following lines in nv_data.bin? (copied from the above thread!)
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
Sorry if this has already been conclusively shown as not possible for nexus S. Some people on the captivate thread have managed to restore it using this method and I thought it would be worth a shot.
The nexus S in question is the SLCD version i9023.
Given below are the steps that caused the issue.
==============================================
Some days ago, official ICS for Nexus S was released, but my cell couldn;t auto update because it was running a custom ROM. I tried to follow this procedure to switch to 2.3.3 or .4. (http://www.pcworld.com/article/242759/how_to_revert_your_android_smartphone_to_a_stock_rom.html )
Installing the above ROM, my cell went berserk. The ROM booted fine but 3 of my touch buttons wouldn't light up and keyboard input alignment was all wrong and I had to remove battery and restart it every time I wanted to go back into some other setting.
After 9-10 restarts, I managed to reach the update setting, downloaded Gingerbread 2.3.6 OTA and installed it. It worked perfectly, and I was all set to download ICS and install it. Then I followed this link and installed ICS reaching where I am at the moment. (http://www.addictivetips.com/mobile/manually-install-android-4-0-3-ics-update-on-nexus-s-download/)
This ICS works perfectly fine, except that the phone is not receiving any network signals whatsoever.
I had made Oxygen's backup using CWM's backup feature on the cellphone and I thought I'd restore it, so I did a vol up + power, and selected recover. The cell restarted, showed a dead android, and booted into ICS. Several attempts have resulted in the same.
==============================================

what were the cercumstances when he lost the "IMEI" ?
would you tell us please , so we avoid that from happening to us ?
Thanks

mahanddeem said:
what were the cercumstances when he lost the "IMEI" ?
would you tell us please , so we avoid that from happening to us ?
Thanks
Click to expand...
Click to collapse
Have updated the opening post with the answer to your question.

Kogan Agora touchscreen not working

Hi I recently flashed cwm and rooted my kogan agora but now the touchscreen does not work.
I have accidentally deleted my backup so if anyone has the stock rom so I can't go back to stock unfortunately

Kogan Agora Touchscreen and menu buttons not responding
Hey are you still having this problem? I just followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=1101094
and now my touchscreen and menu buttons don't respond. Even in Clock work mod I can't press the menu (back) button any more.
Anyone have any advice?

Acnetworks said:
Hi I recently flashed cwm and rooted my kogan agora but now the touchscreen does not work.
I have accidentally deleted my backup so if anyone has the stock rom so I can't go back to stock unfortunately
Click to expand...
Click to collapse
Can you tell me which rom you flashed ? Sometime , it may be that the rom is causing your phone to not response , so , the touchscreen may not work and you will have trouble using it . I would say that maybe your device is bricked . You shouldn't be randomly testing roms . You should check the ROM's thread and compatibility with your device before flashing the roms . I hope you've learnt a lesson this time , and will not randomly flash roms again.

I don't know about Acnetworks
Skyღ, I agree that one shouldn't randomly test ROM's however the one I flashed onto mine explicitly states it works with the Kogan Agora. I don't know if Acnetworks went the same way I did, but if so the ROM that was flashed seems to work for a lot of other people.
Would you happen to know why the menu button would stop working in Clockwork mod but work when the tablet is booting up?

hi Acnetworks and GrombleTromble,
have you had any luck finding a backup of your original kogan tablet as i am in the same boat, I have installed the CyanogenMod 7 rom from androtab.info/cyanogenmod/telechips/ for the Emdoor EM73 capacitive GC2M 8K TCC8803.
I have lost the use of the touch screen and the buttons are in a stange and non existent order, the volume down is the power button and the menu home button is the sellect button.
have you guys managed to fix your problems if so what did you do and how...
thanks for the help

No unfortunately
Hey pomie1,
Nope haven't had any luck. I've been waiting it out to see if anyone else makes a stock backup but I haven't seen any so far.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
pomie1 said:
hi Acnetworks and GrombleTromble,
have you had any luck finding a backup of your original kogan tablet as i am in the same boat, I have installed the CyanogenMod 7 rom from androtab.info/cyanogenmod/telechips/ for the Emdoor EM73 capacitive GC2M 8K TCC8803.
I have lost the use of the touch screen and the buttons are in a stange and non existent order, the volume down is the power button and the menu home button is the sellect button.
have you guys managed to fix your problems if so what did you do and how...
thanks for the help
Click to expand...
Click to collapse
Oh and the reason for this apparently is because the guy who made that Cyanogen Mod ROM for the TC8803 didn't realise there was a 10" Kogan Agora tablet. He made it for the 7" one and that's why the touchscreen doesn't work. sighhhhh

I had Same Issue, Touch Screen would not work. managed to get mine back up and running restoring recovery from ADB

get touchscreen working with custom rom
Use the following at your own risk.
Have put very basic instructions here so it is for the experienced users.
After installing the clock work mod make sure you take a backup encase you regret not having Wifi and Bluetooth like I do.
Issues I have found with these include problems with the Bluetooth, Wifi, Reading SD-Card.
Make sure you download all and put the zips on the SD-Card
Download all the files from the port from starvin on whirlpool url: forums.whirlpool.net.au/archive/1921972
Need little script for installing a Clock Work Mod Recovery that works nicely
Extreme_CWM_Recovery.rar
** at this point boot into the recovery and make a backup and post it to the forum for me
** by posting a copy of the stock image this will also help the community extract the drivers so that we can get cyangenmod working on this tablet. Help the community help you
Cyangenmod that works but Bluetooth and Wifi dont work
cm9_nightly_20120721.zip
Will need to apply this so that touch screen works also fixes the buttons not doing the right things:
t05a-unk_compatibility_1.2.0.zip

[A700] Touch screen not working after latest OTA

Something very strange happened yesterday.
I got the latest OTA and installed it, after this the touch screen is not responding at all.
I managed to control the tablet with an usb mouse, so I have been able to do a factory reset, but to no avail.
Just now I'm clueless on what to do.
I actually did on more thing in the same process; the initial reason for why I took up the tablet yesterday, was to put on a screen protector film.
So while it was updating I put on the screen protector, after all this was done the touch screen was not responding. I don't think this issue has nothing to do with the screen protector, and I have also now removed the film. But still the screen does not react to touch.
But what to do from here?
Is it possible to revert to a previous version of the firmware?

I doubt reversion is the best option.
If this was common this forum would be flooded with complaints.
It might have been something to do with putting on the screen protector DURING an update.
Factory reset may help. Did you try the pinhole reset switch?
Sent from my HTC One X using Tapatalk 2

I can use the tablet with a usb mouse, and have been able to do a factory reset. But this did not difference.
I have also tried the pinhole reset, no luck...

I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:

imtheyoyo said:
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
Click to expand...
Click to collapse
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.

owangen said:
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
Click to expand...
Click to collapse
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B

My touch screen work again.
I back to ICS stock rom (Acer_AV043_A700_RV07RC06_EMEA_FR), then I apply the update (Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR).
Now I'm on JB (Acer_A700_AV043.RV23RC04_AV051.RV10RC01_EMEA_FR). All Work fine.

jacksonkuo said:
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
Click to expand...
Click to collapse
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2

owangen said:
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
Click to expand...
Click to collapse
Seems the touch FW is incorrect.Maybe you can download the OS upgrade image from Acer website and reflash OS. I checked the image and it should packed touch FW. If still failed, maybe contact Acer service is good way to solve your problem.
Good luck.

I had the same problem this week, bought the Tablet on monday, made the OTA Update and boom, no Touch input.
I resolved it by unlock my device, flash CWM and then flashed a older full rom.
After that i made the OTA Update again and this time it worked well.
I can upload the ROM i used for this if it's needed.
MfG Frank
via Acer Iconia Tab A700 mit Tapatalk 2.0

Thanks. I have fixed my tablet now.
I managed to reflash an older rom, taken from Acer site. And then upgraded via ota to the latest version.
I did not need to use cwm. Just started the tablet the power + volume - combination
Sent from my A700 using Tapatalk 2

Problem: Screen touches are bugged..
Hi,
I need some urgent help..
I upgraded my A700 (was shipped with 4.0.4) to JB but the screen touches are completely off track. I did the following:
1) unlocked the bootloader
2) flashed CWM Rom 6.0.1.5
3) installed cm-10
Don't know what to do next..

I have an Acer A700 and I'm having the same problem as others here.
Once I upgarded my ROM, the A700 touch-screen did not work.
I found a post that explained a fix. Here's what I did:
* Flashed the non-touch CWM v6.0.1.5
* Wiped everything (system, data, cache, dalvik)
* Installed the IconiaN ROM (by Vorbeth) and choose the option to have IconiaN upgrade my "Touch Firmware"
* The A700 is now booting with version JB-653b3d3 (Unlocked)
* The ROM loads just fine
However, in the ROM, the touchscreen does not work. Clicking in one place on the screen will trigger a click in an entirely different area of the screen.
I then tried installing one of the stock Acer ROMs from their website through CWM. None of them would load, not sure why?
Other people here seem to have solved the problem by flashing an "older ROM" from Acer. I could not find any trace of this older ROM.
I'm running an American version (PA1_CUS) if that makes any difference? I've also tried installing CM 10.1 with the same problems in the touchscreen.
Thank you in advance for any suggestions!
RKM

Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way

pyrochance said:
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
Click to expand...
Click to collapse
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody

Moscow Desire said:
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Click to expand...
Click to collapse
Thank you for the detailed help!
after many google searches i finally found the update files on the acer website!
i managed to go back to ics then re update to jb
and for a while my screen had no issues but they came back again. Im begining to think that its a hardware related issue because it comes and goes. I am going to see if my warranty with square trade will get it fixed.

[Q] Note 10.1 4G N8020 messed up

Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?

Removed

Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....

Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.

Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway

What is truly amazing is that i did not brick the device tough..

switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.

jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".

OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.

There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app

Strange Behaviour with Home button and Power Button. Software or hardware?

Hey guys,
Let me start by saying I'm really enjoying the forums, I've been lurking here for a while and decided it's finally time to make an account.
Let's get into it, picked up a Rogers Samsung Galaxy S6 (Canadian) Home button works occasionally, power button didn't work, but after a quick boot into recovery it started working. Now, I thought the home button problem is software related due to the fact that it only works sometimes, and then when it works amazing for a couple of times, the power button and the home button both stop responding (even after a firmware re-install)
Here's where things get fun.
So I attempt to root the phone and flash the kernel, except I flash the wrong build (noobish, i know) I flashed a g920f xspace kernel found on here, not paying attention to the model number. After getting the "Seandroid error on boot" i figured I did something wrong, but the device boots normally into the lock screen and the phone functions fine, aside from the that buttons repeat their usually sequence of working and not working. I can also install and root with supersu.
I found the right kernel for my device, g920w8 and i attempted to flash again. Which was successful according to Odin, however once I check the kernel build, it still has the old build. I would like to flash a new rom on it and hope that the rom fixes the problem with the home button and power button (I don't really care for the messages coming during boot, just want the darn buttons to work!)
Has anyone experienced this problem before? Warranty is out so I don't really care, as long as I don't brick it.
Should I "dirty flash"? (not sure how)
I'm going to try another firmware install to see if it removes wrong kernel
Update: Firmware reinstalled removed old kernel
Here are the specs for the phone (now stock after the firmware update):
Android Version 6.0.1
Baseband: G920W8VLU5CPI4
Kernel: 3.10.61-9232017 [email protected]#1 Sept 12th 2016
Build Number: MMB29K.G920W8VLU5CPI4