Database Develop

Recovery Mod - HELP!!!

First off, I am not sure if I am posting this in the correct forum or not. If it is the wrong forum, I do apologies.
Now on to the problem...
I have a T-Mobile G1 running on Rogers (currently running CyanogenMod-4.0.1 with Firmware version 1.5). The problem I am having is that my G1 got soaked a while ago and the Send/Call and Home buttons no longer work whatsoever. I have mapped my send/call button to the camera button, so I can still answer calls. However, I am unable to install any new ROMS (updates) through any of the current bootloaders since they all require you to confirm the install/update with the send/call button.
I have now since been informed by Rogers that since I am running 1.5, my data will be cut off if I do not update to 1.6. Normally this would be no problem, but since my send/call and home buttons do not work, I am unable to do this (I know how to boot into recovery using terminal I just am unable to confirm anything once there).
I was wondering if anyone out there is able to make a new recovery or customize either Cyanogen's or Amon_RA's recovery so that I can confirm a installation/update by using either the Menu, trackball, back, End, or camera button INSTEAD of the Send/Call button?
Any help would be GREATLY appreciated.
Thanks,
Thomas

definetly the wrong section
if you have the relevant .img files you can flash through adb (in theory, never done it for a full rom, just boot.img and recovery.img)
adb flash_image boot /sdcard/boot.img
for example
or get the source to the recovery images and try and edit it manually
or....suck up amon_ras ass and try and get him to make you one
good luck
you might want to think about buying a junker off of ebay for spare parts tho...

Dude go on the Market. Download Quickboot.
It lets you reboot into recovery and more.
Then you can do everything like before
if its possible to install ROM's through the Recovery Screen Console then do it that way. idk how just a suggestion.

the problem is that he needs to hit home to confirm - which he cant

wrong section. But they are just checking the build.prop so make another one and adb push it that will tell them your running 1.6
but also get your phone fix when your phone goes into water you gotta take it apart right away and use a blow dryer

garok89 said:
the problem is that he needs to hit home to confirm - which he cant
Click to expand...
Click to collapse
is there a way to flash a ROM via Recovery Console though? jc
and hmm maybe you should just wait until your fone is fully dried. Thats happened to me with my old fones where they get wet and some didnt even turn back on until they fully dried.
how long ago was this?

The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.

szuba said:
The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.
Click to expand...
Click to collapse
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.

Macrophage001 said:
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.
Click to expand...
Click to collapse
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system

szuba said:
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system
Click to expand...
Click to collapse
Sorry forgot to tell you to type in:
adb remount
before you do it.
so do this:
Code:
adb remount
adb push desktop/build.prop /system
should work. just tried and it did for me.

Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?

szuba said:
Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?
Click to expand...
Click to collapse
Its most likely because you are running an old version of Cyanogen. If that's the case then yeah your ok
Glad to be of Help

old school recoveries...
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?

junkdruggler said:
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?
Click to expand...
Click to collapse
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol

Macrophage001 said:
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol
Click to expand...
Click to collapse
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.

szuba said:
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.
Click to expand...
Click to collapse
ok well hope you find a way good luck =)

Found JF's original recovery, downloaded Super D's latest ROM and renamed it to update.zip, rebooted into recovery, hit Alt-S and what do you know... WORKED LIKE A CHARM!!!
Thanks a lot guys, it is greatly appreciated!

Great and np.

beautiful... Glad I could help... I made a 1.o theme a while back.. that would be cool to have with JF's original Recovery..
mad props to JF and Cyangen for such great work...

stock build.prop needed

Hi all,
I got my nexus 7 today and I used an app to change the LCD dpi to enable tablet ui, and because I am an idiot I didn't take a manual backup of the build.prop.
It looks like the program I was using as actually removed the build prob rather than editing it.
the tablet boots up and i see the google logo but after that its just a black screen.
I can still access the tablet using adb and i looked in the system folder and there is no build.prop file now.
I am sure that if some one could provide me a build.prop file I can get the tablet back to normal again.
if anyone has it I would be very grateful.
Thanks, Mark.

Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03D
ro.build.display.id=JRO03D
ro.build.version.incremental=402395
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Jul 13 01:03:41 UTC 2012
ro.build.date.utc=1342141421
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpba30.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 7
ro.product.brand=google
ro.product.name=nakasi
ro.product.device=grouper
ro.product.board=grouper
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=grouper
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nakasi-user 4.1.1 JRO03D 402395 release-keys
ro.build.fingerprint=google/nakasi/grouper:4.1.1/JRO03D/402395:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-icera.so
rild.libargs=-e wwan0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
# set default lcd density to TVDPI
ro.sf.lcd_density=213
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
tf.enable=y
drm.service.enabled=true
ro.carrier=wifi-only
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
ro.facelock.black_timeout=1250
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=1000
ro.facelock.use_intro_anim=true
ro.media.effect.bgdropper.adj=0.2
camera.flash_off=0
ro.setupwizard.wifi_required=true
ro.setupwizard.gservices_wait=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
You can also download it here:
http://core.routed.com/build.prop

I did the same thing, I didn't think anything of it since it has worked flawlessly on every other device I have had. In my case it removed the build prop as well. I do however, have a nandroid backup on my device. Can I fastboot out of the bootloader into recovery and restore my backup or will I get stuck on the Google screen with the padlock just like I do when I try to manually access it?

chrisjm00 said:
I did the same thing, I didn't think anything of it since it has worked flawlessly on every other device I have had. In my case it removed the build prop as well. I do however, have a nandroid backup on my device. Can I fastboot out of the bootloader into recovery and restore my backup or will I get stuck on the Google screen with the padlock just like I do when I try to manually access it?
Click to expand...
Click to collapse
You should be able to get into recovery one of two ways:
1) Connected to a computer, using adb reboot recovery (or fastboot method).
2) If you can get into your tablet, open up a command shell and enter the commands "su" then "reboot recovery".

It's possible you'll find recovery doesn't work (I had same issues as you and couldn't get in, tablet just booted to a blank screen after the Google logo).
Following the steps http://forum.xda-developers.com/showthread.php?t=1781250
worked (didn't bother with the bootloader image) got things back up and running.
If you can get into recovery and/or ADB is working (with SU) you can recover by replacing the file.
Good luck!

Highland3r said:
It's possible you'll find recovery doesn't work (I had same issues as you and couldn't get in, tablet just booted to a blank screen after the Google logo).
Following the steps http://forum.xda-developers.com/showthread.php?t=1781250
worked (didn't bother with the bootloader image) got things back up and running.
If you can get into recovery and/or ADB is working (with SU) you can recover by replacing the file.
Good luck!
Click to expand...
Click to collapse
The OP said he can still get into the tablet with adb. So he can either use 'adb shell' to manually edit the file, or use 'adb push' to overwrite the one on the tablet. Either way should work.

phonic said:
The OP said he can still get into the tablet with adb. So he can either use 'adb shell' to manually edit the file, or use 'adb push' to overwrite the one on the tablet. Either way should work.
Click to expand...
Click to collapse
That'll teach me to only 1/2 read a post!

One of the problems with a custom build.prop is that it will break updates from Google. Granted using CWM/TERP will do so as well (unless you turn off signature verification, but you will wind up losing custom recovery and root (unless you backed root up)). The updater-script in the update verifies the checksum of build.prop to make sure that it's running the correct version prior to installing the patches/new files/etc. Any modifications will break it, though you could force it manually - not a good idea unless you know what you are doing.

Its all good now. With the tablet connected to the computer, it let me get into recovery. Restored a backup and all is good. The tablet ui is kind of cool, but really feels cramped.
Sent from my Nexus 7 using xda premium

Thanks for the build prop, that got my tablet working again!
lesson learned, just because an app that advises a backup has worked every time on your phone dont assume it will do the same on a different device.
I have also stuck with the stock "Hybrid UI" I do think google made the right choice the full tablet UI is a bit strange feeling on a 7" screen

I usually don't make backups because I'm an idiot and things usually work out for me, so I was stunned when I suddenly had a blank build.prop file after trying to edit it
thanks for this, all is working now

phonic said:
Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
You can also download it here:
http://core.routed.com/build.prop
Click to expand...
Click to collapse
Your upload Saved me frustration! Thank you so much! I can update to 4.1.2 now!!

phonic said:
Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
You can also download it here:
http://core.routed.com/build.prop
Click to expand...
Click to collapse
wow, thanks for that! i've been downloading various build.prop backups and versions from all over the place and yours was the only one that worked! :good:
you saved my (nexus 7) skin!

drpepe said:
wow, thanks for that! i've been downloading various build.prop backups and versions from all over the place and yours was the only one that worked! :good:
you saved my (nexus 7) skin!
Click to expand...
Click to collapse
Could you please share the JRO03D build prop again. The original link is dead and I was stupid enough not to make a backup, before editing mine. The copy paste is not working for me either. Thanks a lot.

P970 Noob Flash with No Backup and now no IMEI & Network

I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.

jugz54 said:
I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.
Click to expand...
Click to collapse
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.

xonar_ said:
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.
Click to expand...
Click to collapse
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?

jugz54 said:
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?
Click to expand...
Click to collapse
This will only work with the P970
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
The large bold print is for people that can't read headings that might run this and brick their devices.
Something I learned that isn't mentioned on the forum is that its important to backup your nv partition since that contains info that can't be retrieved after damaging it and nothing backs it up for you. Like MAC addresses, your IMEI etc.
On you computor
Backup using
Code:
adb pull /dev/block/mmcblk0p11 nv.img
Restore using
Code:
adb push nv.img /dev/block/mmcblk0p11
EDIT: Added notrunc to not truncate the rest of the partition

xonar_ said:
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
Click to expand...
Click to collapse
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?

Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.

sbdemir said:
Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.
Click to expand...
Click to collapse
I tried the LGMobile Support Tool various times. The recovery module does not work, if i type IMEI adn select check phone, nothing happens. The strange thing is the support tool picks up my phone model as LGKU5900 version V10I. That could have happened with me trying to repair the phone with various programs and youtube videos.
I have tried uninstalling and reinstalling the support tool as well as the drivers but still no luck.... I reflashed the original rom V10F with no patch etc.. but still the Support tool picks up the model as LGKU5900, and when i select update phone, it downloads the update and during installing of update it stays on 6% for roughly 20 minutes then just stops. I have tried this numerous times and same things happens everytime.
If this is of interest to you to, you can take control of my system and check it out via team viewer.

jugz54 said:
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?
Click to expand...
Click to collapse
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.

xonar_ said:
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.
Click to expand...
Click to collapse
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?

jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
dd should be included in busybox. What busybox are you using?
The conv=notrunc just tells it not to truncate the rest of the file (in this case don't truncate the rest of the nv partition)
the echo pipes the IMEI to dd which writes it to /dev/block/mmcblk0p11 (your nv partition) on two different spots. I
You need su permissions to write to /dev/block/mmcblk0p11. I forgot to mention that. Otherwise dd will fail and the included binutils dd doesn't always list error messages. Just terminates silently without doing anything most of the time.
You can also try reflashing just the baseband. (The fls file with SFT)
If all that doesn't work then you need to take it into repairs.

jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
I don't have a solution to your problem however I am in a similar situation. I purchased my Optimus Black from an ebay seller located in Hong Kong, it was advertised as an Optimus Black P970. The software version was similar to yours, outdated, so I grabbed a stable gingerbread version patched it with root etc. and flashed.
Upon reboot I had no cellular network, tried two different sims/networks. No Joy. Further troubleshooting uncovered the loss of the imei. I came across this thread and decided to give it a try, it didn't work. I suspect I messed up the command, in my case this was lucky because I was able to see the content of the mmcblk0p11 file using a hex editor. The imei is in there, and it is also in the same location as my Optimus Black P970, I assume it is stored elsewhere as well....
Long and short of this is you and I have purchased the KU5900, the Korean version not the P970, flashing with P970 firmware is what has messed the phones up.
Note. I did try flashing with the only Korean version that was available to me, a V30 something, that bricked the device. It is now unbricked but still shows no imei. I haven't given up but wading through reams of forum posts trying to get info on this is daunting ... My seller has agreed to replace the phone, but I fear I will end up with another KU5900 which isn't any good to me unless I can upgrade the firmware.

had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419

IAP001 said:
had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419
Click to expand...
Click to collapse
I just fixed one P970 with unknown IMEI by flashing it with Octopus box, I think that you can solve it by flashing with original flash file using SFT.
Best Regards.

Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app

sunnygunjesh said:
Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
i had similar problem when installing cm10 rom and cici rom, after flashing those roms my device had no IMEI and no network, it didnt even rcognize my contacs in sim card. the strange part is that i was able to make calls, but when i flashed back to the rom i had, everything was back and looking good.
i had marvel v9 rom thats runs pretty good.

[Solved][Thanks peetr_]Loss of touch screen

Hi folks, I am at a loss on this one.
I was testing DooMKerneL v3 and v4 last night.
After installing V4 I decided to try and make an init.d script to control the volume levels. Here it is
Code:
#!/system/bin/sh
#init.d script by gregbradley xda recognised contributer;
#kernel level sound control;
#in conjunction with DooMKernel V4+;
#gpl_cam_mic_gain is Camera MIC;
#gpl_headphonbe_gain is Headphone;
#gpl _mic_gain is MIC;
#gpl_speaker_gain is Internal Speaker;
#each supports gain levels from 20 (-20) to 50 (+10), base is 40 (0);
echo "41" > /sys/kernel/sound_control/gpl_cam_mic_gain
echo "41 41" > /sys/kernel/sound_control/gpl_headphone_gain
echo "41" > /sys/kernel/sound_control/gpl_mic_gain
echo "41" > /sys/kernel/sound_control/gpl_speaker_gain
I made it with notepad++ with the correct EOL conversion. I called it 98ksoundtweaks and put it into
system/etc/init.d
I rebooted the phone several times, and each time it did not work with values set at 41.
I then edited the file in the phones text editor, then on the next reboot I got a bootloop.
Then after a hard reset I lost the touch screen capability.
Here is what I have tried to fix it.
Restore a working backup
Restore doomkernel v2 and a working backup
Factory reset and reflash Rom and kernel
Factory reset and flash stock kernel
Factory reset and flash stock ftf
None of them work. The next thing I am going to try is relock the bootloader and a PCCompanion repair, but I want to know if there is anything else I can try before that.
I am currently on doomkernel v2 with my last working backup flashed. I have checked and none of the v4 files are present, and none of the init.d scripts I wrote are present. I did not drop the phone, it was just connected via usb to my laptop and lay on my desk when this happened.
However, I can use my mouse with USB OTG
Any help would be appreciated

Re: Loss of touch screen
Tried wiping /system, /data, /cache and do a full fresh install of a rom?
Sent from my LT30p using Tapatalk 2

matt4321 said:
Tried wiping /system, /data, /cache and do a full fresh install of a rom?
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
gregbradley said:
Here is what I have tried to fix it.
Restore a working backup
Restore doomkernel v2 and a working backup
Factory reset and reflash Rom and kernel
Factory reset and flash stock kernel
Factory reset and flash stock ftf
Click to expand...
Click to collapse
Thanks, but I have tried that.

Re: Loss of touch screen
There was already a thread about this, where I wrote that I it would be safer to delete the touch firmware from /system/etc/firmware.
I think it was reflashed with error.
Try to reflash the firmware one more time.
But your problem could be somewhere else.

peetr_ said:
There was already a thread about this, where I wrote that I it would be safer to delete the touch firmware from /system/etc/firmware.
I think it was reflashed with error.
Try to reflash the firmware one more time.
But your problem could be somewhere else.
Click to expand...
Click to collapse
I just replaced the touch_module_id_0x32.img in system/etc/firmware with the one from my ROM, but it still does not work.
I will try a FTF flash again soon

Re: Loss of touch screen
I would skip straight to pccompanion.
Something may have cooked, the only way to rule it out....
Sent from my LT30p using Tapatalk 2

Re: Loss of touch screen
gregbradley said:
I just replaced the touch_module_id_0x32.img in system/etc/firmware with the one from my ROM, but it still does not work.
I will try a FTF flash again soon
Click to expand...
Click to collapse
I mean reflash touch firmware manually in terminal or adb. You can find the command in /system/etc/hw_config.sh.
Edit:
rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
There are some more options you can try:
Usage:
rmi4_fw_updater [options]
Options:
-h Print this help text
-b Complete path and name of firmware file
-d Path to the sensor to be updated
-f Force flash
-c Update config area
-e Don't erase chip before updating FW
-r Really force. Don't care about chip ID
-u Unconditionally do full FW update
But first use the command line with -r -f only.

cheers,
I am just pccompanion updateing ATM.
I will try those commands in adb if this does not work...

Pccompanion did not work.
Unlocked boot again. back to doomkernelv4 with my custom rom.
This is pain to do with no touch scrren..
@peetr_ can I just write that command in adb, or do I need to do adb shell first?

Re: Loss of touch screen
adb shell first and su
Reflashing should take about 2 or 3 secons, but there's no output, so try to restart and you'll see. Then I would try with other options (-c or -u).

done that
Code:
C:\Android>adb devices
List of devices attached
CB5121SC7S device
C:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img
-d /sys/bus/rmi4/devices/sensor00 -r -f
rmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f <
[email protected]:/ # reboot
reboot
C:\Android>
AND IT LIVES!!!!!!
Many thanks!!!!!!

Good.
Now delete the fw from /system/etc/firmware.

What does that do?
Sent from my star trek communicator
Sony Flagship device circa 2145

It looks like real firmware for the digitizer.
From hw_config.sh:
# Touch FW updater. Force firmware upgrade if necessary (for e.g. if'function 11' is missing.)
There is this condition, when something is missing on boot, the firmware is reflashed.
While we are still trying, flashing, restarting and the system checks for filesystem integrity (triangle), this condition could be met for some reason and the firmware is reflashed, even when it shouldn't. And it seems like it can be reflashed with error (maybe without those -r -f flags).
I don't see any good reason for reflashing touch firmware so I suggest to rename or delete it or change that script.
If we get some update with new fw update, we can pull it back.

Ok, but won't deleting it from system/etc/firmware produce problems?
Sent from my star trek communicator
Sony Flagship device circa 2145

No. It's there only for reflash. Fw is inside the digitizer.
It causes problems when it's there.

Ok, still learning new stuff every day here on xda.
I have renamed it.
Sent from my star trek communicator
Sony Flagship device circa 2145

Unresponsive touch screen
peetr_ said:
I mean reflash touch firmware manually in terminal or adb. You can find the command in /system/etc/hw_config.sh.
Edit:
rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
There are some more options you can try:
Usage:
rmi4_fw_updater [options]
Options:
-h Print this help text
-b Complete path and name of firmware file
-d Path to the sensor to be updated
-f Force flash
-c Update config area
-e Don't erase chip before updating FW
-r Really force. Don't care about chip ID
-u Unconditionally do full FW update
But first use the command line with -r -f only.
Click to expand...
Click to collapse
Yesterday I unlocked BL and when I flashed new kernel (DooMKernel v4). Still I don't understand what happened but my touch screen became unresponsive. I thought it was caused by wrong ROM (I am using Xperiment v2.3 and there are separate versions for locked and unlocked BL) so I replaced it with the second one (for unlocked BL). But it didn't helped anyway and I noticed that touchscreen is unresponsive also in touch version of TWRP (included in the latest DooMKernel) so it is probably not related to ROM. After many attempts and searching I bumped into this thread and tried to apply your command above and it worked!!! Thanks a lot.
I am just disturbed by the fact I don't understand how I got into this situation so I don't know how to avoid it in the future. Do you have any idea what happened?

All I can tell to this problem, I wrote here - http://forum.xda-developers.com/showpost.php?p=39921357&postcount=14
I suggest to rename the touch firmware image in all ROM's.

Today i ran into same issue where i flashed touch firmware T from to my TX while i was playing with some mods
I was able to recover it by flashing back to stock ICS firmware

Reflashing stock on linux

Hi all, I'm going to be sending my phone off for repairs which will hopefully be done under warranty. So I'm looking to return my phone to stock android for the time being. I've done it before but that was on Windows and now I'm switched to Linux. Is there a method through Linux which doesn't include emulating a Windows environment?

kiladu said:
Hi all, I'm going to be sending my phone off for repairs which will hopefully be done under warranty. So I'm looking to return my phone to stock android for the time being. I've done it before but that was on Windows and now I'm switched to Linux. Is there a method through Linux which doesn't include emulating a Windows environment?
Click to expand...
Click to collapse
Finally a Linux user!
First of all, download FlashTool for linux by going to this link: http://www.flashtool.net/downloads_linux_prev.php Yes you will be using 0.9.18.6 version as a latest change in 0.9.19 wont allow you to properly flash ftf files.
Extract the file downloaded. Extract the extracted file again (its an archive, inside an archive).
You will now have the Flashtool program in your Linux. To run Flashtool, simply run the file "FlashTool" of the extracted files. But hold on, we need udev support so Flashtool can recognise Sony devices
Create an empty file then enter this in:
Code:
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="*", MODE="0777"
Save it as "51-sony.rules"
Then push (move) it into "/etc/udev/rules.d" with superuser (sudo) permission.
Open terminal
Set correct permission and ownership
Code:
sudo chown root:root /etc/udev/rules.d/51-sony.rules && sudo chmod u=rw,go=r /etc/udev/rules.d/51-sony.rules
Restart udev or system for changes to take effect

TechnoSparks said:
Finally a Linux user!
First of all, download FlashTool for linux by going to this link: http://www.flashtool.net/downloads_linux_prev.php Yes you will be using 0.9.18.6 version as a latest change in 0.9.19 wont allow you to properly flash ftf files.
Extract the file downloaded. Extract the extracted file again (its an archive, inside an archive).
You will now have the Flashtool program in your Linux. To run Flashtool, simply run the file "FlashTool" of the extracted files. But hold on, we need udev support so Flashtool can recognise Sony devices
Create an empty file then enter this in:
Code:
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="*", MODE="0777"
Save it as "51-sony.rules"
Then push (move) it into "/etc/udev/rules.d" with superuser (sudo) permission.
Open terminal
Set correct permission and ownership
Code:
sudo chown root:root /etc/udev/rules.d/51-sony.rules && sudo chmod u=rw,go=r /etc/udev/rules.d/51-sony.rules
Restart udev or system for changes to take effect
Click to expand...
Click to collapse
Thank you so much!!! It's good to know there are other Linux users out there . I will try it over the next couple of days when I find the available time.

kiladu said:
Thank you so much!!! It's good to know there are other Linux users out there . I will try it over the next couple of days when I find the available time.
Click to expand...
Click to collapse
Man Linux FTW man I can't live properly without it haha

TechnoSparks said:
Man Linux FTW man I can't live properly without it haha
Click to expand...
Click to collapse
I've successfully set it up and reflashed my phone back to stock. The problem is I've downloaded a ROM containing Asian apps whereas I would like a full UK official ROM, just to be on the safe side in case they try and void my warranty. Do you know where I could find a UK 4.2/3 (?) stock rom to use?
Many thanks once again!!

kiladu said:
I've successfully set it up and reflashed my phone back to stock. The problem is I've downloaded a ROM containing Asian apps whereas I would like a full UK official ROM, just to be on the safe side in case they try and void my warranty. Do you know where I could find a UK 4.2/3 (?) stock rom to use?
Many thanks once again!!
Click to expand...
Click to collapse
Flashtool as of 0.9.18.5 has integrated Xperifirm into its program, therefore you can now download the ftf that you want right from your flashtool!
Make sure you have Mono-complete package installed. Assuming you use Debian-based distro, please run
Code:
sudo apt-get install mono-complete
Open Flashtool
Click on the XF button (right next to the Plus button)
XperiFirm will be launched
Choose Xperia SP in the sidebar
Choose your Xperia SP model
Find the ROM that you want and click on it
On the right sidebar there will be a single item for you to click it. Click it (under the donate on paypal image)
Confirm download. Please make sure "Unpack automatically" is ticked.
After download complete, close Xperifirm. Flashtool will pack the files downloaded and generates a proper ftf.
Once it completes, you can click on Lightning icon and proceed to flashing the ftf that you have downloaded.