Database Develop

Probably Hard Bricked, but want to check with you guys

first post and epic fail for me!
FYI, I rooted and flashed multiple droid phones to GB in the past with no problem.
I followed the wrong instructions and flashed my Galaxy Tab 7 in with the rooted kernel (i have the wifi only version)
I am unable to get into download mode or boot up. When i hold down the power and volum controls, I get the LCD backlight turned on, but nothing else.
Same thing with the power button alone. Once i release the button, the light goes off.
It doesnt look like windows or Odin is even seeing the device when connected. I think I'm boned

hitokiri2007 said:
first post and epic fail for me!
FYI, I rooted and flashed multiple droid phones to GB in the past with no problem.
I followed the wrong instructions and flashed my Galaxy Tab 7 in with the rooted kernel (i have the wifi only version)
I am unable to get into download mode or boot up. When i hold down the power and volum controls, I get the LCD backlight turned on, but nothing else.
Same thing with the power button alone. Once i release the button, the light goes off.
It doesnt look like windows or Odin is even seeing the device when connected. I think I'm boned
Click to expand...
Click to collapse
It does sound like it is bricked, if you are interested I can un-brick this for you send me a PM if you are interested.

well, fortunately for me, i just got this today and called up circuit city saying "uh, i think my uh...ipad type thing... galaxy something is broken" lol
put on the old "i r dumb in tech" routine and am getting a new one shipping for next day service (for free)
Appreciate he offer though, however, I do have a question.
Does this work at all for wifi only? Or is this strictly GSM?
I thought the rooting files were optional and THAT part was GSM needed

nope...you can only flash roms that are made for Wifi only models...GSM roms will not work on Wifi only models due to differing infrastructure....furthermore wifi only model has downgraded CPU as well as GPU and Bluetooth

hitokiri2007 said:
well, fortunately for me, i just got this today and called up circuit city saying "uh, i think my uh...ipad type thing... galaxy something is broken" lol
put on the old "i r dumb in tech" routine and am getting a new one shipping for next day service (for free)
Appreciate he offer though, however, I do have a question.
Does this work at all for wifi only? Or is this strictly GSM?
I thought the rooting files were optional and THAT part was GSM needed
Click to expand...
Click to collapse
To answer your question if you got the wifi only version, then thats it.
GSM version are T-Mobile and AT&T and also has wifi as well and
CDMA version would be Verizon and Sprint and wifi.
There are several different reasons to root:
1 - Installing a different flavor / version of Android
2 - Enabling cellular phone dialing
3 - etc, etc
Just be carefull when you root

Press1Now said:
To answer your question if you got the wifi only version, then thats it.
GSM version are T-Mobile and AT&T and also has wifi as well and
CDMA version would be Verizon and Sprint and wifi.
There are several different reasons to root:
1 - Installing a different flavor / version of Android
2 - Enabling cellular phone dialing
3 - etc, etc
Just be carefull when you root
Click to expand...
Click to collapse
yeah, i screwed up.
I dont mind the weaker cpu and junk as it is a gift for my brother (he is the best man at my wedding), but I wanted to root, get rid of bloatware and throw on GB (gb is rockin on my droid), then throw on launcherpro and some other things. You know, but this nice and smooth and junk.
But I killed it. Wont happen with the next one as it doesnt seem like there is any type of gm rom for the wifi only model

wifi calling and CM7, O2X, and T-mobile USA

i figured i would post this here while i try to make UMA/GAN on my O2X.
i'm on t-mobile usa, and wifi calling is a handy feature on G2X (and many other handsets)
i compared p990 and p999 builds of cm7. even though RIL is different, the wrapper (librilswitch.so) seems to be compatible.
i also looked at other threads, particularly on nexus one by unforgiven512.
from there, it looks like what i need is
libganril.so
libkineto.so
librilswitch.so
Kineto.apk
and a patch for build.prop
--- /system/build.prop 2011-06-24 13:00:44.955254744 -0700
+++ /system/build.prop 2011-06-29 13:57:51.229291278 -0700
@@ -33,12 +33,14 @@
#
# system.prop for p990
#
-rild.libpath=/system/lib/lge-ril.so
+rild.libpath=/system/lib/librilswitch.so
rild.libargs=-d /dev/ttyspi0
+rilswitch.vendorlibpath=/system/lib/lge-ril.so
+rilswitch.ganlibpath=/system/lib/libganril.so
ro.sf.lcd_density=240
-mobiledata.interfaces=vsnet0,vsnet1,vsnet2,vsnet3
+mobiledata.interfaces=gannet0,vsnet0,vsnet1,vsnet2,vsnet3
i made a flashable zip, flashed from CWM recovery, rebooted phone.
my o2x boots fine. no hiccup as far as i can tell.
cellular network calling still works fine. (whew.....)
wifi works fine....
gps works fine.....
Kineto app runs without crash.... but no connection. it complains "w005.4 t-mobile network error"
i googled it, and it seems a quite common issues. however, it is not clear how to resolve it.
one thing i'm not sure is kineto_gan.ko kernel module. i know that LG enabled kineto_gan in their froyo kernel (for p999, but not for p990)
cm7 g2x seems to support wifi calling. (am i right?) so i figured i would look into cm kernel.
that's where i hit a dead end. i followed the wiki to compile kernel, but i get a bunch of error.
also what i don't understand is that cm kernel source is missing kineto_gan.c

update
testing librilswitch.so:
on wifi calling, can't connect to tmo.
on cell network, making a call still works.
on cell network, receiving doesn't.
i guess libril's are not compatible after all...

I wonder if you have had any luck since then on getting the app to work in o2x?

well, i had deserted this approach, mostly because wifi calling sucks battery... but maybe that was because it failed to connect. (can't recall)
i liked sip option better, and that is the main reason i stopped this.
now that i can compile kernel, maybe i will look into this again.

[SELFKANG AOSP ROM] CyanogenMod 7.1 GSM Version [UPDATE 10/23 AM]

I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).
** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **
** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
I dabbled in files for some time, twaked the build.prop a little (added some generally known hacks into it for faster touch reaction, better HSPA reception etc.), and added some files .lib/.ro files from Droid 2 Global.
It all worked out nicely. However, as I cannot use a CDMA network (I live in Turkey, so I have only GSM access), I cannot guarantee this will work with CDMA too. I will appriciate it if someone can test it.
Also, Your GSM card will be recognized instantly, but you need to activate the 3G network form the settings, you will need to add your APN manually, atleast in my case I had to put my carriers APN into the list, so this might not be necessary."
Here is the link: http://www.mediafire.com/?d17l4z4885ph4ov
Thanks needs to go to Hashcode, as I just modified and added a missing feature to it.
Click to expand...
Click to collapse

Thanks for the help Hashcode!
I got my clearence to Dev forums, so I will try to contribute even more to this community =] .
First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.
You can find a screenshot of my phone working under the GSM network and 3G enabled.
!!!However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone. !!!
For installing, just use Hashcode's safestrap, for the rest i think you know the drill.
BUGS:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken,
Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .
Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.

Referved for future use/updates/etc...

Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....

thank YOU !! Hashcode and Coreless88

No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!
nikeusfr said:
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
Click to expand...
Click to collapse
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.
Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).

one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.

nikeusfr said:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
Click to expand...
Click to collapse
Hi,
First of all, thanks for your input. I need your opinions to make this better. So here we go,
All notifications and ringtones are silent by default.
You need to get to:
"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.
Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.
But you can make the phone louder on the speaker by going to:
settings>cyanogenmod settings>sound menu then choose the settings you like the most.

What "general" GSM build.prop tweaks are we talking about here?

DoubleYouPee said:
What "general" GSM build.prop tweaks are we talking about here?
Click to expand...
Click to collapse
Hi,
I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.
BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.

Could I apply these build.prop changes my XT862 rom?
Or did you use droid 2 global hacks like someone tried before?

DoubleYouPee said:
Could I apply these build.prop changes my XT862 rom?
Click to expand...
Click to collapse
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.

coreless88 said:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
Click to expand...
Click to collapse
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)

DoubleYouPee said:
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
Click to expand...
Click to collapse
Oh!
I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.
You may try, but that will only make the risk even bigger.
Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .

Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.

coreless88 said:
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Click to expand...
Click to collapse
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.

Willis111 said:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
Click to expand...
Click to collapse
Hi,
Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.
I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.
The Solutor said:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Click to expand...
Click to collapse
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).

coreless88 said:
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
Click to expand...
Click to collapse
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
Click to expand...
Click to collapse
Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.
XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).

Indeed, a GSM ROM would be great

FYI, audio and video codec issues are being addressed in my next build of CM7.
I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.
Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).

Samsung Galaxy 8.9" 4G Jelly Bean?

I have the 4G version, is this specific model have a working CM10 ROM? I know the Wi-Fi model does, just want to make sure this won't brick mine or anything.
I'm new to this, just got this today!

It does not. Our version (i957) uses a different chipset then the Wi-Fi version. Best to not flash.
Sent from my Galaxy Nexus using Tapatalk 2

CM10 will eventually support this device -- In fact, the device tree was just created by cyanogen yesterday @ https://github.com/CyanogenMod/android_device_samsung_p5att -- However, work still remains to get this code to even boot, let alone be functional as a daily driver. It will get there, eventually.
The ICS (4.0.4) ROM from Samsung for this device is currently in test with the carriers. The Korean variant (SHV-140) just received the ICS update a few weeks ago, and some of that code might help speed along the Cyanogen update.
The CM10 code currently on github does build, but the kernel does not seem to fully boot -- Locks up just after displaying the initlogo, with adb unavailable, so I have no idea how to get the dmesg. I suspect there are some needle-in-a-haystack sort of details that need to get ironed out, the kind of which probably will require some hardware hacking (ie: serial and/or jtag access) to get at... or for the official i957 kernel to get released.

The shv rom has to be out there somewhere
Sent from my SGH-I727 using xda premium

In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
- breakfast cm_p5att-userdebug
- replace msm-8660-common kernel with code from jb-full branch
- *** edit to update: it seems there is no longer a jb-full branch, there is now just jellybean and jb-old. I'm guessing the out of date msm8660-common kernel from what was jellybean is now jb-old, and jb-full has become jellybean.. hmm.. working on seeing if this is the case (need to clone/build/boot it)
- hack p5att boardconfig
- pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
- brunch p5att, consume more coffee and stuffs
- hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
- hack ramdisk to enable adb on boot so you can debug why it doesnt come up
- hack proprietary files until you get working graphics
** (not for the faint of heart)

nrvate said:
In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
lunch cm_p5att-userdebug
replace msm-8660-common kernel with code from jb-full tree
hack p5att boardconfig
pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
brunch p5att, consume more coffee and stuffs
hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
hack ramdisk to enable adb on boot so you can debug why it doesnt come up
hack proprietary files until you get working graphics
(not for the faint of heart)
Click to expand...
Click to collapse
nice job man!

EDIT: I created a separate thread for doing the CM10 build: http://forum.xda-developers.com/showthread.php?t=1867579
Cheers!
Still hacking stuff.. lol.. using the file list from the msm-8660 common proprietary file list, i grabbed that set of files from the CM10 i717 ROM and dropped them onto the i957. Working audio! Don't know about the mic, but it plays sound now. Also, it almost got LTE working... logcat -b radio shows the LTE radio finding the LTE cell and reporting signal strength, but the data session doesn't actually establish, even with the proper APN config. GPS looks like it might even eventually lock on, it found 2 sats after a while, but didn't get a lock. I suspect when full 4G comes up, it'll be able to use SUPL to get it's initial location then actually get a fix.
Downloading the gigantic i717 stock image, going to see if 4G plays nicer with the note radios, since I'm using the note RIL now.. Dan had mentioned he had successfully got the note radios running on the tab 8.9 LTE in an attempt to get voice calls up... the honeycomb RIL stuff just results in lots of errors, so thats straight fail.
I didn't realize how many software pieces go into the cellular data connectivity, yikes!
The more I delve into code and binary packages... the more it appears the 957 is very close to a supersized note! sweet.
Also, bluetooth finds my neighbors macbook, so it probably works, but my headset is at work and I haven't been there in a while (hence having time to do this fun stuff).
If anyone has any suggestions on getting LTE up, I'm all ears. If I can get LTE working, I might be tempted to try to package this beast up.
More fun...
Good grief, it looks like the userdebug variant compiles with all the radio debug flags on, thousands and thousands of lines of everything from verbose text to hex dumps!
i957 honeycomb radio: baseband shows unknown, isn't worth anything
i717 ICS radios, both UCLF5 and 6: entire tablet slows to a crawl once rild starts, fail! Nothing useful in the logs as to why, nothing hogging CPU time... no idea, abort
i727 skyrocket ICS radio I727UCALC4 (no idea how current or valid this radio really is): gets HSPA+ on old 3G "wap.cingular" SIM, no luck with tablet only LTE "Broadband" APN SIM. ~2-2.5mbit download speed.
i727 skyrocket ICS radio UCLD2: Obtained HSPA+ with Broadband APN data-only SIM. ~4.0-5 mbit download speeds. After ~10 minutes, found an LTE cell and pulled 30-35mbit down. After each radio reset (reboot, airplane mode, etc) it takes the 3-10 minute period to get LTE again, and it's also slow (10-50 seconds) to get on HSPA. All around sluggish to jump on a cell, but returns nice speeds once it does so.
i727 skyrocket ICS radio UCLF6 (latest I could find): Pretty much the same as UCLD2 above, similar speeds, but seemed to jump on LTE quicker after a reboot, but still takes a while when coming back from airplane mode. It's the latest, i think, and it works, so it's probably the way to go.
Pending investigation: RIL files -- going to try the skyrocket UCLF6 RIL and see how it works out. Currently still using the note RIL files. Tried UCALC4 skyrocket RIL and it didn't work at all, will try UCLF6 from stock skyrocket ICS release...
Looks like it doesn't like the Broadband APN on a tablet (data-plan-only) SIM. I tossed in a "old school phone SIM" from the 3G days, which is set up on an unlimited phone/data plan (as you could get ages ago) and gave it wap.cingular, and whamo, HSPA+ connectivity. Looks more like a configuration issue and/or the phone RIL/radio combination refuse to play nice with data-only SIM.
I've never tried to debug getting onto 3G/4G service at the RIL radio log level, so not totally sure what to look for, but... guessing it's trying to set up a voice bearer and the UMTS system says F you. need foods, sleep, etc... haha.
And more fun... Skyrocket UCLD2 radio returns HSPA+ connectivity on data-only SIM with Broadband APN, but no LTE. Set APN type to "supl" to enable SUPL, got the first GPS fix in about 2 minutes, after 5 more minutes found 12 sats and obtained 12m accuracy.. sweet!
Update: UCLD2 radio, after sitting around idling for 10 minutes while I made some munchies, decided it would pick up an LTE cell. No idea why it took so long, I'm really close to an LTE cell and both my other LTE devices have never (and don't presently) exhibit this behavior at my location. I suspect this is probably normal behavior of UCLD2 or UCLD2 plays less than optimally with the i957 radio... which should be the same as a skyrocket radio, considering both identify as an M8260 when inquired with "ati" via ttyACM0. Whatever the case, 50ms ping and 30 mbit down works for me...
I really should go to bed sometime...... and make a backup of this device before I bust something!
Adding a little more info: I modified device/samsung/p5att/BoardConfig.mk a little before building... Other devices with no SD card slot had BOARD_HAS_SD_CARD_INTERNAL defined, so i tossed that in. The BOARD_SDCARD_DEVICE_PRIMARY, BOARD_SDCARD_DEVICE_SECONDARY and BOARD_SDEXT_DEVICE_SDEXT values seemed bogus, and I knew the init scripts would set up /sdcard as a fuse device on the /data partition anyways, so I just commented them out.
I don't know if anything uses the 3 values I commented out, but since there's no actual mmcblk device for the fuse (filesystem in user space) emulated sdcard, it doesn't seem a valid value could be found, so, why set one.... Seems to work!
BOARD_HAS_SDCARD_INTERNAL := true
#BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
#BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk0p28
#BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
Click to expand...
Click to collapse
But, this is my first attempt at hacking cyanogenmod onto a half-baked device, so... don't take my word for it
And before anyone asks, yes, I plan on releasing a flashable update for this, but first... figuring out enough to start from a fresh source tree and build from scratch so I can document how I did this... Let's beat the carriers to jellybean and forget ICS
(yes, I'm editing this post a bazillion times as try stuff, I'll put together something a little more coherent soon)

[Q] Trouble with no calls or text

My girlfriends D3 has gradually been getting worse with poor reception, dropping calls, not being able to make/receive calls or texts.
Data seems to work fine. This weekend it just finally stopped being able to make calls or send texts from our home.
If i drive a few miles down the road or to a higher elevation i was barely able to call *228 to update roaming.
I can still use the browser over 3G and Wifi, just no tethering, phone or text.
The phone shows 3G and a full signal, but as soon as i initiate a call it drops to 1 bar.
Another thing we noticed this morning is that when calling the phone it goes straight to voicemail.
I had tried changing the Network mode from Global to CDMA yesterday and at one point got an error message saying "No CDMA networks were found. Would you like to switch to Global Mode?"
Phone has been rebooted and battery pulled along with some other diagnostic tests that the verizon techs did over the phone yesterday.
The only thing i had done to this phone was i applied the TBH tethering hack without root over a year ago. It worked fine up until now.
The phone has the latest System version 5.7.906.XT862 and the latest Baseband N_03.18.32P.
Im thinking of reverting the TBH Tethering hack back using the instructions in this post
I spoke to Verizon tech support yesterday and they said there was some trouble in our area, but my Droid X is still able to connect so i doubt thats the issue.
Does anyone think that an OTA update from Verizon may have screwed something up due to the TBH hack being applied?
The GF is frantic about getting her phone back. I can take out insurance for 6.99 pr/month and pay $100 to get her a new phone, but if reverting the TBH hack and maybe rooting and installing a new ROM might help, im all for it.
Any thoughts? ROM advice? Was reading up about the AOKP Build 40 ROM, but wondering if all the hoop jumping will help or if the D3 has a hardware issue that has just got progressively worse.
Wont you help a poor guy keep the peace with his lady please?

I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?

MrObvious said:
I don't think it's that. It's possible that the 3G in the area is good but 1x is crap. 3G is just used for data while calls/texts are used on 1x. What is the PRL versions your phone and her phone have?
Click to expand...
Click to collapse
My Droid X running on VXLR V2.2.0: PRL 53018
Her Droid 3 Stock w/TBH Tethering Hack: PRL 52996
Just tried updating them both and the PRL's stayed the same.
About an hour ago i was in the middle of backing up her phone and it started ringing. I was able to answer the call and now im able to make and receive texts and calls. There must have been a tower issue. The signal still drops to 2 bars when i initiate a call, but at least its working again.
She says its been flaky for quite a while with dropping calls and texts not getting sent. Im all backed up and was thinking of rooting and trying a ROM on this. Not sure if itll help with signal issues, dropped calls or texts not being sent or received.
She was also complaining about the thing pocket dialing, and other random stuff happening like her browser launching and texts being sent etc. I saw it this morning. I picked up her phone to bring it downstairs and saw that there was a text reply box open with a bunch of jibberish typed in it. She says that sort of thing happens all the time.
Think maybe a good stable ROM might help?
After a little more research i came across Minimoto here at XDA. Minimoto Link
Seems to be the way to go if im sticking to a GB ROM. I see you contributed some to it. Would you happen to know where some step by step instructions for getting it installed on a non rooted D3 might be?

1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.

MrObvious said:
1) Root it.
2) Install Safestrap 3.05.
3) Reboot to it, create ROM-Slot 1.
4) Factory reset and wipe cache and delvik.
5) Flash the ROM.
6) Set her up with goodness.
Though if random crap is popping up, I suspect the digitizer is flaky.
Click to expand...
Click to collapse
Have you heard of digitizer issues with D3's before?
Any recommendations on which rooting method to use?
Do i have to remove the TBH Tether hack before rooting, installing Safestrap or Flashing the ROM?
So i take it your in agreement that this would be a good choice for a stable no frills GB ROM?

the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link

sd_shadow said:
the random stuff can be from from a bad digitizer, dirt/grime on digitizer/edge or a software conflict
try cleaning screen around the edge, and/or flash rom/sbf
you need to remove bootstrap before safestrap, tbh hack should be fine
i haven't use minmo, but many have, also you could look at
http://forum.xda-developers.com/showthread.php?t=2106722
use the Deodexed ROM (Courtesy of thingonaspring) link
Click to expand...
Click to collapse
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply? Is there a factory bootstrap included with the D3?
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.

LOTL said:
Thanks sd_shadow I think ill stick with minimo most likely. Too many dam ROMS to choose from!.
I think your the only person to say that for the d3 lol. Most of us are flash- a-holics and we love lots of roms to chose from.
Ok so from the hours of reading i did yesterday, i found a working link for motofail. It appears it is the best (or only) way to root the D3 if on 906.
From there i thought i could just install Safestrap 3.05 which i managed to track down as well.
I never installed Bootstrap, so does this even apply?
Just install safestrap on your safe system after root don't worry about bootstrap.
Is there a factory bootstrap included with the D3?
No
I believe i read that minimoto has its own tethering feature included. So are we sure i dont have to revert the TBH tethering hack?
No you do not have to undo the tether hack it is a hardwear hack not a software hack and will work on any rom no matter if the rom already has tethering in it.
Some great links in your signature by the way. If the digitizer keeps acting up, i may try replacing it. I did clean it last night and will see if things improve.
Click to expand...
Click to collapse
Sent from my DROID3 using XDA

replacing the digitizer is a pain
some [how to] links in my list