Database Info

Can we use this for 32B?

http://www.noverca.it/shop-aggiorna-htc-magic-con-sense#googtrans/it/en
The problem is that we don't know if this is for 32B or 32A... But if you push "Scarica Sense" a .zip that contains a .exe is downloaded... And it flash Sense.
Here is the Google-translation:
Update HTC MAGIC
Download SENSE
SENSEtm installing on your terminal you can manage and customize your HTC Magic as anyone in the world. SENSEtm is an easy interface that lets you make your single terminal at your fingertips, highlighting programs, widgets or features you need and giving you the ability to create an end-measure.
The update is dedicated solely to mobile Noverca's HTC MAGIC, it is not so compatible with terminals acquired from other sources!
Download the application Htc Sense stepmother clicking on the button and install it on your computer2
The phone must be connected to the PC through the USB cable. The PC should recognize the terminal showing the connection icon in the window at the bottom right of the screen.
The battery level must be at least 30% (minimum 3 green blocks on the battery icon).
It 'must have installed on your computer HTC Sync. It 'can be found in MicroSD HTC Sync on the bottom of the terminal or download from the link http://www.htc.com/www/support.aspx
Once all the points mentioned above were followed installation of the application can proceed SENSEtm
The update takes about 10 minutes, DO NOT interrupt the update process, disconnect the phone from a PC, or push any button before the process is concluded.
Warning! Updating the phone will lose all data stored on the phone, therefore, before proceeding, you should make a copy of all relevant information such as names in the phonebook, list of installed programs, events or meetings on the calendar saved , mail accounts etc..
Note 1: The application that allows you to upgrade your HTC MAGIC is supported on the following operating systems: Windows XP Home Edition Service Pack 2, Windows XP Professional Edition Service Pack 2, Windows XP Media Center Edition Service Pack 2, Microsoft Windows Vista Ultimate Edition, Microsoft Windows Vista Enterprise, Windows Vista Business Edition, Microsoft Windows Vista Home Premium Edition, Microsoft Windows Vista Home Basic Edition.
Note 2: If after installing HTC Sync, during the upgrade of the terminal software is required to install new drivers, download the file Android_driver.zip decompress the file on your Desktop and select the drivers folder when request by the computer.
Click to expand...
Click to collapse

I think it's a 32A rom, I'm downloading and test now.

I checked. This is a 32A rom, (hboot support 7200A CPU)

Pity we(G1) can't get a update like that...

Extracted and converted
I extracted the .zip and posted here:
http://www.4shared.com/file/249235242/5f919810/HTC_Sense_Noverca.html
I converted to 32B using relentless roaster here:
http://www.4shared.com/file/249236905/bb7988b8/Roasted-HTC_Sense_Noverca.html
guessing by the size you will need danger spl if on G1, might work on normal MT3G. Anybody willing to try?
Using the extracted files you should be able to convert to english, I just don't know how at the moment.

If anyone got that all english I would have a go.
But I wonder if ot would un-root the phone?

what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b

blinker1683 said:
what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b
Click to expand...
Click to collapse
Any luck dude?

#
# customize.prop for Rogers
#
# Set to PAP
ro.ril.enable.a53=1
ro.ril.ecc.HTC-ISR=100
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20091208.215718
ro.build.version.incremental=98222
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Tue Dec 8 21:58:52 CST 2009
ro.build.date.utc=1260280732
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X03
ro.build.tags=release-keys
ro.product.model=HTC Magic
ro.product.brand=htc_europe
ro.product.name=htc_magic
ro.product.device=sapphire
ro.product.board=sapphire
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
#
ro.build.product is obsolete; use
ro.product.device
ro.build.product=sapphire
# Do not try to parse
ro.build.description or .fingerprint
ro.build.description=3.05.401.3 CL#98222 release-keys
ro.build.changelist=98222
ro.product.ua=
ro.build.fingerprint=htc_europe/htc_magic/sapphire/sapphire:1.5/CUPCAKE/98222:user/release-keys
keyguard.no_require_sim=1
# end build properties
#
# system.prop for device
#
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep = 1
wifi.interface = tiwlan0
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.hsupa.category = 5
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
ro.com.google.locationfeatures=1
# For SD storage insert notification sound
persist.service.mount.playsnd = 0
# For auto backlight default value
settings.display.autobacklight=0
# For brightness default value
settings.display.brightness=132
# For the default value of agps
ro.ril.def.agps.mode = 2
#
# ADDITIONAL_BUILD_PROPERTIES
#
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.locationfeatures=1
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
persist.service.mount.playsnd=0
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

so what is this in detail ?
Android 1.5 with Sense ?
Does the Roastet_Rom work with 32B? Did anyone try ?
cheers
bullys

blinker1683 said:
what boot.img file did you use to convert this to a 32b ,downloading
i will post back .
hope it works , i have relentless too,but don't know how to convert 32a to 32b
Click to expand...
Click to collapse
I didn't select a particular boot.img, I only used the button that said compatibility.
I guess the system.img could be unyaffed, but as for further details on modifying the language, I'm not sure.

I tried flashing... got a error saying E,unableto find update script. I'm guessing that. We need a suitable boot.img to make it right conversion. If anybody can get the boot.img and the update script I can then convert it right. ITS TIME TO SEARCH!!!

Its 32A so dont flash to 32B.

[Q] ADB problem

I switched to a 2.3.3 based rom today, and now adb won't allow me to remount or push. I can pull just fine. But if I type adb remount, I get the error, "remount failed: operation not permitted."
If I boot into CWM and mount /system or /data, I can remount, push, or pull with adb with no problems. But once I boot into the rom, all I can do is pull.
I am using a rooted rom with the latest superuser and busybox.
Anyone have any ideas?

Still really needing some help with this, please.

If you type adb shell, do you get a $ or a #?
Try opening the SuperUser app on your phone then doing adb remount.
Sent from my LG-P999 using XDA App

mmapcpro said:
I switched to a 2.3.3 based rom today, and now adb won't allow me to remount or push. I can pull just fine. But if I type adb remount, I get the error, "remount failed: operation not permitted."
If I boot into CWM and mount /system or /data, I can remount, push, or pull with adb with no problems. But once I boot into the rom, all I can do is pull.
I am using a rooted rom with the latest superuser and busybox.
Anyone have any ideas?
Click to expand...
Click to collapse
Look at the default.prop file on the root of your device. I bet that there's a line that says: "ro.secure=1".
For whatever reason, the maker of your ROM set ro.secure to be on, which limits a lot of what you can do via adb. No pushing to /system, no remounting in rw mode. This is part of the boot.img file in the ROM, and is set with every reboot. Ask the maker of the ROM to set ro.secure to 0.
I had this problem with EaglesBlood Froyo until I *****ed enough that the dev changed it on the next release.

Try typing in adb remount then adb push your files.
Sent from my LG-P999

mstrk242 said:
Try typing in adb remount then adb push your files.
Sent from my LG-P999
Click to expand...
Click to collapse
Ah, he says in the first post that he tries that but gets an error.

Still having the issue.
I searched through default.prop and ro.secure=0.
I also attempted to adb remount while running superuser, with no success.
I am on EB1.08 for 2.3.3 currently, but I also tested this on Weapon G2x 2.3.3 with the same results.

mmapcpro said:
Still having the issue.
I searched through build.prop and there is no ro.secure line at all...not set to 1, not set to 0...not there.
I also attempted to adb remount while running superuser, with no success.
I am on EB1.08 for 2.3.3 currently, but I also tested this on Weapon G2x 2.3.3 with the same results.
Click to expand...
Click to collapse
Not build.prop, but *default.prop*, should only be a few lines long, in the root of your phone's filesystem:
adb shell
ls
you should see the file. Mine looks like (minus the -----):
----------------------------------
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.serialno=******* (censored by me)
----------------------------------

wewoapsiak said:
If you type adb shell, do you get a $ or a #?
Try opening the SuperUser app on your phone then doing adb remount.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
when I type "adb shell", it displays: sh-3.2$

lannister80 said:
Not build.prop, but *default.prop*, should only be a few lines long, in the root of your phone's filesystem:
adb shell
ls
you should see the file. Mine looks like (minus the -----):
----------------------------------
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.serialno=******* (censored by me)
----------------------------------
Click to expand...
Click to collapse
Yeh, I went back and edited my post because I re-read your response and realized I was looking at the wrong file...but default.prop says ro.secure=0

mmapcpro said:
Yeh, I went back and edited my post because I re-read your response and realized I was looking at the wrong file...but default.prop says ro.secure=0
Click to expand...
Click to collapse
Well crap, scratch that idea. But the behavior you describe is exactly what happened when ro.secure=1 was set in EB Froyo, so it must be something...similar?

Problem with ROM!
Sorry for the late reply, but this seems close to the answer.You must be using a custom ROM not Stock GingerBread ,right? Well, some initialisation script(files like init.rc) are responsible for setting the state of adb daemon at boot time. There scripts normally check files like build.prop, default.prop,local.prop, environment variables and stuff like that and accordingly setup many features like heapsize, display mode, adb secure or insecure,etc. There should be something different with your ROM's initialization scripts.
Oh, and i forgot! You can't change default.prop like that. Every time you reboot, default.prop'll be reloaded from boot partition image, effectively undoing any changes you made. Flashing a better boot.img may solve the problem.

Anyone else unlock immediately?

I'm so busy with work (and the Team EOS kernel for the Xoom) that I haven't had a chance to write this yet, but it should now be fairly straightforward after unlocking to write a recovery (script) that pulls in the old recovery and boot images to SD-Card, then extract those, turn off "ro.secure" and be able to get root once I fastboot that back in.
Maybe this weekend.

kcrudup said:
I'm so busy with work (and the Team EOS kernel for the Xoom) that I haven't had a chance to write this yet, but it should now be fairly straightforward after unlocking to write a recovery (script) that pulls in the old recovery and boot images to SD-Card, then extract those, turn off "ro.secure" and be able to get root once I fastboot that back in.
Maybe this weekend.
Click to expand...
Click to collapse
I'd give it a shot but my recovery is gone.

KitsunePaws said:
I'd give it a shot but my recovery is gone.
Click to expand...
Click to collapse
... then I should do this sooner than later, so you can get it back!
I plan on saving off all three major images (boot/recovery/system) and I guess posting 'em somewhere- that way, until I/we/somebody mods up CWM (et al.) for us, we can always unbrick via "fastboot".
I was quite surprised the modems are in a dd-able/fastboot-able partition. I should probably save that off once I get root, too.

kcrudup said:
... then I should do this sooner than later, so you can get it back!
I plan on saving off all three major images (boot/recovery/system) and I guess posting 'em somewhere- that way, until I/we/somebody mods up CWM (et al.) for us, we can always unbrick via "fastboot".
I was quite surprised the modems are in a dd-able/fastboot-able partition. I should probably save that off once I get root, too.
Click to expand...
Click to collapse
I would have to hug you.

Signature verification is turned on in recovery. So much for this method, and I don't want to blow my recovery yet until I get an image to replace it with. I guess I'll look for an exploit somewhere, so I can grab the images while it's running.
So WTF, Moto? There's no point in being unlocked if the recovery is still locked!

kcrudup said:
Signature verification is turned on in recovery. So much for this method, and I don't want to blow my recovery yet until I get an image to replace it with. I guess I'll look for an exploit somewhere, so I can grab the images while it's running.
So WTF, Moto? There's no point in being unlocked if the recovery is still locked!
Click to expand...
Click to collapse
Gotta love on the unlock page
"To return to Original Software, you will need to reflash a Motorola signed software image to your device, or send it in to our service center to get reflashed. MOTOROLA reserves the right to charge for any assistance required by users during this process. At this time, we are not posting a recovery image for the Photon Q 4G LTE."

"Moto" said:
"At this time, we are not posting a recovery image for the Photon Q 4G LTE."
Click to expand...
Click to collapse
Well, at least the good part is once they do post one, then I should be able to dissect that for the images I need. As long as I have the contents of /dev/block/mmcblk0p32 I'll be able to fastboot the stock recovery back in (even though I'm not sure why I should care about it, if it's got asserts turned on ).
... but I still say that being unlocked w/o the benefit of images is kinda useless. If this is really the Droid 4 (with a Sprint overlay and an LTE radio), I wonder if there's a root exploit that'll at least let me dd over the block devices to the external SD-Card.

me said:
If this is really the Droid 4
Click to expand...
Click to collapse
Nope. That's an OMAP. The search continues!

wait.. what? you do realize signature checking has been here since froyo right? unlocked bootloader doesn't equal unlocked recovery.
just chatted with bigrushdog when i get them ill pass the images to you.

Honestly, been so used to unlocked / unlockable devices, not to mention the stuff at work, thai I'd assumed one followed the other.
Thanks for looking out for the images. How do you know BRD?

kcrudup said:
Honestly, been so used to unlocked / unlockable devices, not to mention the stuff at work, thai I'd assumed one followed the other.
Thanks for looking out for the images. How do you know BRD?
Click to expand...
Click to collapse
toroplus
hopefully some point later today once we get a person who has this phone to join the irc so we can grab stock kernel from there i can grab stock recovery and system and make cwm
then you guys can port team eos rom to the photon q ;P

What method are you going to use to get (to) the kernel? Anything I can do (that doesn't risk bricking)?

oh there is never a chance of bricking, my associate is gunna root someone via remote connection, ideally ssh since teamviewer sucks. but it seems only few people actually care about rooting, so its slow goings

shabbypenguin said:
oh there is never a chance of bricking, my associate is gunna root someone via remote connection, ideally ssh since teamviewer sucks. but it seems only few people actually care about rooting, so its slow goings
Click to expand...
Click to collapse
If your pal is going to be around tonight I'll get SSH running when I get home.
Actually, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130 I'll just toss fastboot and adb on my pi and call it a day.

KitsunePaws said:
If your pal is going to be around tonight I'll get SSH running when I get home.
Actually, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130 I'll just toss fastboot and adb on my pi and call it a day.
Click to expand...
Click to collapse
hes actually busy today but hell be around tomorrow, rangerbry stopped in and he is locked so id rather use his so we can get stock images of the boot partitions and compare them to the unlocked ones.. see if we cnat do anything about that pesky splash screen :/

shabbypenguin said:
hes actually busy today but hell be around tomorrow, rangerbry stopped in and he is locked so id rather use his so we can get stock images of the boot partitions and compare them to the unlocked ones.. see if we cnat do anything about that pesky splash screen :/
Click to expand...
Click to collapse
Good deal, finally another taker

shabbypenguin said:
... my associate is gunna root someone via remote connection, ideally ssh
Click to expand...
Click to collapse
Wait- what?!
How does this work- I mean, it sounds like something I can do now and get things started. Do we have a working exploit for the MSM8664?
Details, man- DETAILS!

kcrudup said:
Wait- what?!
How does this work- I mean, it sounds like something I can do now and get things started. Do we have a working exploit for the MSM8664?
Details, man- DETAILS!
Click to expand...
Click to collapse
the exploit isnt going public

Can you post the /system/build.prop (and /system/default.prop if it exists)? Or show me a screen in Phone -> About phone (everything in there)?

default.prop:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
system.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=7.7.1Q-6_SPR-89_ASA-36
ro.build.display.id=7.7.1Q-6_SPR-89_ASA-36
ro.build.version.incremental=42
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Aug 3 23:32:39 CDT 2012
ro.build.date.utc=1344054759
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid85
ro.build.tags=release-keys
ro.product.model=XT897
ro.product.brand=motorola
ro.product.name=XT897_us_spr
ro.product.device=asanti_c
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=XT897_us_spr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=asanti_c-user 4.0.4 7.7.1Q-6_SPR-89_ASA-36 42 release-keys
ro.build.fingerprint=motorola/XT897_us_spr/asanti_c:4.0.4/7.7.1Q-6_SPR-89_ASA-36/42:user/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
ro.sf.compbypass.enable=1
ro.sf.lcd_density=240
dev.pm.dyn_samplingrate=1
#
# system props for the cne module
#
persist.cne.UseCne=none
persist.cne.UseSwim=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.nsrm.mode=false
ro.hdmi.enable=true
lpa.decode=false
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=false
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
ro.config.vc_call_vol_steps=7
ro.audio.default.ring.volume=4
ro.audio.default.notif.volume=5
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system prop for Bluetooth Dialup Networking
#
ro.qualcomm.bluetooth.dun=false
# system prop for Bluetooth FTP profile
ro.qualcomm.bluetooth.ftp=true
#
# system property for Bluetooth Handsfree Profile Wide Band Speech
#
ro.qualcomm.bluetooth.hfp.wbs=true
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# system property for thermald
persist.thermal.monitor=true
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#For TCMD bringup
persist.tcmd.log.limit=0
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System prop for Sprint device management
#
persist.sprint.dm.status=1:1:1:1:1:1:1:1:1:1
#
# System prop for Sprint device management GPS
#
persist.sprint.dm.gps.status=0
# BEGIN Motorola, fsk050, IKASANTISPRINT-207 - slate suport
slate.keyevent=false
slate.penevent=false
# END IKASANTISPRINT-207
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=http://device.sprintpcs.com/Motorola/XT897-Chameleon/latest
#
# System prop for default network(NETWORK_MODE_LTE_CDMA_EVDO) and LTE enable
#
ro.telephony.default_network=8
telephony.lteOnCdmaDevice=1
# BEGIN Motorola, kgh864, IKASANTISPRINT-218 Hidden menu life data
persist.sys.wifi.rx=0
persist.sys.wifi.tx=0
persist.sys.mob.rx=0
persist.sys.mob.tx=0
persist.radio.lifecalls=0
persist.radio.lifetimer=0
# END IKASANTISPRINT-218
# BEGIN Motorola, rcjk78, 03/19/2012, IKASANTISPRINT-187
ro.cdma.home.operator.numeric = 310120
ro.cdma.home.operator.alpha = Sprint
# END IKASANTISPRINT-187
# BEGIN Motorola, emb046, 04/24/2012, IKHSS7-27158
persist.data_netmgrd_mtu = 1472
# END IKHSS7-27158
# Enable Sleep mode option when power button is pressed
ro.mot.deep.sleep.supported=true
# BEGIN MOTOROLA, eww012, 04/24/2012, IKASANTISPRINT-819: TTY is not working on SPR-31
ro.mot.fid.30544.tty=true
# END MOTOROLA, IKASANTISPRINT-819
# BEGIN IKHSS7-32053 Sprint GPS settings
persist.mot.gps.locktype=4
persist.mot.gps.assisted=false
# END IKHSS7-32053
# Enable HAC mode
ro.mot.hw.HAC=1
#Setting default Ringtone/Notifications
ro.config.ringtone=Pegasus.ogg
ro.config.notification_sound=Bellatrix.ogg
#IKHSS7-8095 VZW-IOT requirement for Ex-DisplayRecord
persist.radio.0x9e_not_callname=1
# BEGIN Motorola, a21739, 04/05/2012, IKASANTISPRINT-160
ro.sprint.lte.ipv6.supported=false
# END IKASANTISPRINT-160
# BEGIN Motorola, rjones1, 4/10/2012, IKHSS7-22881
# NFC Card Emulation Config
# bitfield:
# 15141312 11109 8 7 6 5 4 3 2 1 0
# u u u u u u u u u u p d u u s e
# where:
# u = unused bit
# p = ce on when device is powered off? 0 = no, 1 = yes
# d = ce on when display locked or off? 0 = no, 1 = yes
# s = uicc based secure element
# e = embedded/smx based secure element
#
# 1: embedded, ce off when display or device off
persist.mot.nfc.ce=1
# END IKHSS7-22881
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
# BEGIN Motorola, a22812, 05/29/2012, IKHSS7-35343
ro.camera.sound.forced=1
# END IKHSS7-35343
#MOTO, nfjb73, 06/04/2012, IKHSS7-34220
#Set the preferred cdma subscription to 0-RUIM, 1-NV
ro.cdma.subscription=1
# BEGIN motorola, a186010, 06/12/2012, IKHSS7-38099
ro.cdma.nbpcd=1
#END IKHSS7-38099
# BEGIN Motorola, a21269, 06/12/2012, IKHSS7-38085
persist.radio.add_power_save=1
# END IKHSS7-38085
# In order to hide the market name from the public during user trials,
# set the ro.property.model.exif in system.prop to a non-descriptive string, such as MODEL A.
# This string will be populated in the "model" EXIF field of camera captured image JPEG files.
# When the product team is ready for the market name to be available to the public (e.g., in a TA build),
# then the ro.property.model.exif in system.prop MUST be changed to match the PRODUCT_MODEL string.
ro.product.model.exif=XT897
#
# ADDITIONAL_BUILD_PROPERTIES
#
drm.service.enabled=true
ro.config.ringtone=Bio_Research.ogg
ro.config.alarm_alert=Cesium.ogg
ro.config.notification_sound=Bio.ogg
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
ro.com.google.clientidbase.gmm=android-sprint-us
ro.com.google.clientidbase.yt=android-sprint-us
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.com.google.gmsversion=4.0_r3
persist.radio.apm_sim_not_pwdn=1
persist.radio.call_type=1
persist.sys.qc.sub.rstrtlvl=3
persist.sys.qc.sub.rdump.max=20
ro.qualcomm.cabl=0
ro.bug2go.uid.type=TELEPHONY_DEVICE_ID
ro.usb.mtp_usbnet=0x2e32
ro.usb.mtp_usbnet_adb=0x2e33
ro.usb.cdrom=0x2e20
ro.usb.ms=0x2e21
ro.usb.ms_adb=0x2e22
ro.usb.ptp=0x2e30
ro.usb.ptp_adb=0x2e31
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.mot.dpmext=true
ro.com.google.clientid=android-motorola
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.build.version.full=Blur_Version.77.6.36.XT897.Sprint.en.US
ro.mot.hidden_keyboards=evfwd
ro.mot.build.version.sdk_int=7
ro.mot.product.modelno=XT897

[Completed] [HELP]Porting AOSP KK Zopo ZP999 to MX4

Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:

Naphtha said:
Hi,
i have a big problem with my first porting (an Aosp rom from zopo zp999 on my Meizu MX4). Stuck in bootanimation, only one times come the "Installing Applications". Any suggestions? libs modify? :crying:
Click to expand...
Click to collapse
Hello,
As a senior member, you probably know that logcat is your friend. Since you may not have found how to simplify adb access for 4.4 builds, temporarily add this to your device tree (in the <your chipset name>.mk):
Code:
# Since Android 4.2.2, USB debugging requires authentication, something that is not possible during boot.
# To disable this, set the following property in default.prop (inside initrd):
# ro.adb.secure=0
# To get root access this is a must:
# ro.secure=0
# will allow you to run adbd as root via the adb root command:
#ro.debuggable=1
#service.adb.root=1
ADDITIONAL_DEFAULT_PROPERTIES += \
ro.secure=0 \
ro.adb.secure=0 \
ro.debuggable=1 \
service.adb.root=1 \
persist.service.adb.enable=1 \
persist.service.debuggable=1
Build that, flash, and then take a logcat while booting. You should be able to see what;s going on (even if you need another set of eyes...even then this thread is good for that).
Hope this helps, and good luck!

Thanks so much!
Inviato dal mio MX4 utilizzando Tapatalk

Flashed some weird recovery, now: Verification failed Unable to restart your device

I am very sorry if this is a dumb question, I have been having sex with this phone for a few days and I have no idea what I am doing. and my wife is going to kill me if I don't get her phone and data up and running soon :crying: so I was trying to recover some files that got acidentally removed from the device and I decided to root it. I thought, it's not going to be a big deal... and so I didn't backup. (facepalm)
So I used instruction on gadgethacks dot com (can't post a link because I am new here), however I ignored the part where they say you need to validate that your phone is compatible. (again, facepalm)
I flashed AP = CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5 using Odin3-v3.10.6.exe and now when the phone restarts I get "Verification failed Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase your data."
Then I discovered that in download mode it says that my phone is SW-G930W8
Then I found this file and I tried to flash it.
CF-Auto-Root-heroltebmc-heroltebmc-smg930w8.tar.md5
same error message.
Then I flashed twrp-3.2.3-0-herolte.img.tar
I can get into the twrp recovery, but still can't boot the system. then I used adb in twrp mode but can't see any of my wife's files in internal memory, I am guessing because they are on an encrypted partition or something like that. but I can access /system/ and so I found a file called build.prop where it says that my Android version is G930W8VLS3BRC2
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.display.id=NRD90M.G930W8VLS3BRC2
ro.build.version.incremental=G930W8VLS3BRC2
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2018-03-01
ro.build.version.base_os=samsung/heroltebmc/heroltebmc:7.0/NRD90M/G930W8VLU3BRB2:user/release-keys
ro.build.version.security_index=1
ro.build.date=Thu Mar 8 14:44:49 KST 2018
ro.build.date.utc=1520487889
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHE9410
ro.build.tags=release-keys
ro.build.flavor=heroltebmc-user
ro.product.model=SM-G930W8
ro.product.brand=samsung
ro.product.name=heroltebmc
ro.product.device=heroltebmc
ro.product.board=universal8890
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-CA
ro.wifi.channels=
ro.board.platform=exynos5
so I found this amazing site called firmware.mobi where I was able to get a recovery from that specific version of android... and still the same error message comes up.
So I was following the instructions of the root manual so I have developer mode turned on and "OEM unlock" enabled if that helps at all.
Please help me Any advice is very much appreciated.
Question 1: Is it possible to save the data in the internal memory of the phone? i.e. either boot the system or fetch and decrypt the partition? How?
Question 2: If not, then how do I at least get the phone to work again? Just do what it says and wipe it? Or flash some complete stock ROM?

So nobody knows? Or is my question so dumb that no one wants to bother to answer?